$DOC

This member documenting the OPS/MVS II installation and conversion steps

UNLOAD

Unload OPS.CNTL from the distribution cartridge to OPSMVS.SAMPLIB

INSTSMP1

Allocate SMP/E and product data sets

INSTSMP2

SMP/E Receive/Apply/Check OPS/MVS product

INSTSMP3

SMP/E Apply/Accept/Check OPS/MVS product

INSTSMP4

SMP/E Accept OPS/MVS product

INSTSMP5

Delete temporary SMP/E install datasets

DEFDIV

Define VSAM linear datasets (data-in-virtual DIV) for the OPSLOG browse and REXX global variable checkpoint facility as PROD.OPSMVS.* in order to catalog them in the master catalog.   These data sets should never be placed on shared DASD, page volumes or, other volumes with high RESERVE activity

OPAMSVDB

Define shared file VSAM KSDS which allows for permanent storage of global variables and their values.  Records are read/written to this data set only through the OPSHFI command processor.  In order to use this file with OPSHFI, examine and set the GLVSHAREDFILE GLVSHAREDDD GLVSHAREDRESERVE GLVSHAREDRLS parameters accordingly.

SYSVIEW

User written CLIST to allocate libraries and then execute the OPPRIMOP CLIST; copied to PROD.CLIST.

OPPRIMOP

Modified CLIST to change JES3 to JES2 and then copied to PROD.CLIST(OPPRIMOP)

COPYLOAD

IEBCOPY OPSMVS.LOAD to PROD.OPSMVS.LOAD prior to linklisting it

TSO 2

Backup SYS1.PARMLIB(LNKLST00) as LNKLST99 and add PROD.OPSMVS.LOAD to LNKLST00

Backup SYS1.PARMLIB(PROG00) as PROG99 and add PROD.OPSMVS.LOAD on PP0005 to PROG00

TSO 2

Back PROD.PLIB(PPPANEL) as PPPANE99 and add option SV (SYSVIEW) to PPPANEL

TSO 2

Modify the following procedures and copy to PROD.PROCLIB

• OPSMAIN Main OPS/MVS II address space
• OPSOSF Server address spaces-see "Regulating OSF Servers"
• OPSECF Enhanced Console Facility address spaces

OPSTART1

Copied to PROD.CLIST(OPSTART1) without modification.  Executes any TSO command needed for product initialization; executes OPS/REXX program to set OPS/MVS parameters.   The source for the program the CLIST executes is in SYS1.PARMLIB(OPSSPA00)

OPSSPA00

This is the source for the OPS/REXX program executed by PROD.CLIST(OPSTART1).  Backup is in SYS1.PARMLIB(OPSSPA99) prior to modifying OPSSPA00 as follows:

• Allocate OPSMVS.LOG
• Allocate OPSMVS.SYSCHK1
• Set RULEPREFIX to OPSMVS
• Set RULESUFFIX to RULES
• Change OSFCHAR to + (plus sign)
• Change INITCA7 to ON in order to browse CA-7 ENF events
• Compare system id to TY2K
• The default ECFCHAR is ?

To syntax check this program, place a REXX "EXIT" statement as the first line of this program and then execute it using the !OI edit macro.

OPSTART2

This is the source for the OPS/REXX program that starts the OSF server.  When the main OPS/MVS address space becomes fully initialized, it invokes PROD.EXEC(OPSTART2) by sending the following command to the OSF queue: OI OPSTART2

Modified OPSTART2 REXX statements as follows:

• Define MSFID TY2K VTAM applid OPSAPPL with password OPSMVS
• Commented out the statements that define MVSB and MVSC

OSFSTART

This CLIST is invoked by OPSOSF as the first command.  Modified OPFSTART statements as follows:

• Execute OPSALLOC and the SPFALLOC CLIST in HowToAllocSPF code
• Commented out AllocSPF as there is no TSO/E user written REXX
• Commented out AllocSPF None as there is no ISPF in the servers

TSO 3.2

Allocate OPS/MVS ISPF profile data set OPSMVS.PROFILE

OPSALLOC

This REXX program is invoked by OSFSTART to allocate ISPF libraries in the server.  Renamed SPFALLOC to OPSALLOC and modified OPSALLOC as follows in the event a future server has ISPF capability

• Allocate PLIB = "'ISPF.SISPPENU'"
• Allocate MLIB = "'ISPF.SISPMENU'"
• Allocate SLIB = "'ISPF.SISPSENU'"
• Allocate TLIB = "'ISPF.SISTSENU'"
• Allocate profile data set with prefix OPSMVS
• Use preallocated (not dynamic) profile data set OPSMVS.PROFILE

OPJ2CB

Assemble and link the JES2 offsets module into PROD.OPSMVS.LOAD and OPSMVS.LOAD

Install interfaces:

The following installation steps were performed:

• Install CICS/ESA 3.3. interface as CICS 4.1 is installed on the test OS/390 2.4 Y2K LPAR
• Install Netview interface (step 3.16.1) to gain access to the Netview unsolicited message stream
• Install NOF (step 3.17)
• Enable OPS/MVS to interact with Omegamon (step 3.18)
• Establish an OPS/MVS Quickref environment (step 3.19)

OPBOCM00

Backup OPSMVS.OPSTLIB(OPBOCMDS) as OPBOCM99 and modify OPBOCMDS to add command OPSQW

CONSOL00

Backup SYS1.PARMLIB(CONSOL00) member as CONSOL99 and add 5 console statements for OPS/MVS to CONSOL00, console names OPSCON01-OPSCON05 with ALL authority

Install interfaces:

Implemented the generic data interface for started tasks, batch programs, or TSO programs.   To implement the interface, a DD statement has to be included in the format of:

//DD1 DD SUBSYS=(OPSS,OPSDSN,BLUE,AOFREPT) where,

• ddname = the ddname associated with the file
• ssid = the four-character OPS/MVS II subsystem ID which receives generic interface messages (normally OPSS)
  
• color = an optional operand which specifies the color in which messages can appear in OPSLOG.  Values can be GREEN, BLUE, RED, WHITE, PINK, YELLOW, or TURQ.
  
• reportid = an optional operand which specifies a unique report ID that an AOF rule can use to identify the source of the message

DidNotDo

Did not change the defaults for the following variables:

• GLOBALWARNTHRESH
• GLOBALWARNINTVAL
• GLOBALTEMPWARNTH
• GLOBALTEMPWARNIV
• Enable OPSAOF because OPSS is not active yet (SYSVIEW Option 4.5)
• Check and enable rules in OPSMVS.SAMPLE.RULES as OPSS is not active yet

IEFSSN00

Backup SYS1.PARMLIB(IEFSSN00) as IEFSSN99.  Add subsystem id TOPS for test and POPS for when it is in production

APPLOPSS

Add OPSMVS appl definition to SYS1.VTAMLST

ATCCON00

Backup SYS1.VTAMLST(ATCCON00) as ATCCON99 and add APPLOPSS to ATCCON00 to activate appl when VTAM initializes

Note: Terminal MODETAB and DLOGMOD will default

OPSLOGON

Copied to PROD.CLIST; did not code a simulated userid as we do not have one yet

S.LOG

Entered command to start OPS/MVS:  /S OPSMAIN,SUB=MSTR

Entered command to stop OPS/MVS:  /P OPSS

L990721A

SYSLOG dump for "S OPSMAIN" is in OPSMVS.OUTPUT

IEFSSN00

Add comment that OSFCHAR was changed from ! to ; in order to eliminate "START" error message.  ! is being used by TDB2

OPSMAIN

Job log is in OPSMVS.OUTPUT(OPSMAIN)

OPSOSF

Job log is in OPSMVS.OUTPUT(OPSOSF1), server #1

Job log is in OPSMVS.OUTPUT(OPSOSF2), server #2

S.LOG

Entered command "+OI OPSIVP" to test OSF

$AMXP01

Backup as $AMXP099 and add OPS/MVS data sets to SYS1.PROCLIB($AMXP01)

TSO

Entered command "SYS" from main ISPF panel to display SYSVIEW panel

SYSVIEW

Entered "1" to view OPSLOG

Entered "4.1.1" to display OPS/MVS parameters

Reload

Enter command "F OPSS,RELOAD(modname)" to reload OPS/MVS modules after applying maintenance; cannot reload OPBOEX OPGLEX OPOSEX OPAOEX OPMFEX.   This information is for future reference on how to change OPS/MVS without recycling it.

OPSSPA00

Changed SYS1.PARMLIB(OPSSPA00) ARCHIVETRIGGER from 0 to 200000 which is half the value of the BROWSEMAX parameter

Added BROWSEARCHIVEDSN and BROWSEARCHIVEUNIT parameters

ARCHGDG

Create OPSLOG archive dataset GDG with a maximum of 25 entries. 200,000 messages accumulate before OPS/MVS initiates the archive job. The model DSCB name is "GDG"

L232DCM1

Install CA-7 browse event in the ENF data base

DidNotDo

Did not install OPS/MVS ARM facility as there is no ARM couple data set, etc

TSO 3.2

Allocate the following data sets:

• OPSMVS.PARMLIB for Application Parameter Manager parameter data copied from OPSMVS.CNTL
• OPSMVS.TEST.CNTL
• OPSMVS.PROD.CNTL
• OPSMVS.TEST.GLOBAL.CNTL
• OPSMVS.PROD.GLOBAL.CNTL

ASOPRMIN

Backup OPSMVS.CNTL(ASOPRMIN) as ASOPRM99 and change the Application Parameter Manager REXX program as follows:

• #AP_ global status variable prefix
• GLOBALT. global variable prefix
• LCLAPPL Data sets that contain parameters local to this system are specified in the following order:
  • OPSMVS.TEST.CNTL
  • OPSMVS.PROD.CNTL
• GBLAPPL Data sets that contain parameters shared by all systems are specified in the following order:
  • OPSMVS.TEST.GLOBAL.CNTL
  • OPSMVS.PROD.GLOBAL.CNTL

KEYS

Add OPSMVS product keys to CA90.PPOPTION(CARIMPRM)

DFDSSB1

Backup OPSMVS.* data sets to tape prior to performing the next installation steps to convert from CA-Automate.

Note: CA-Automate should be at the SA95100 PTF level for OPS/MVS usage. Other PTFs are required for cross system communication with remote Automate via C-Comm. Backup data set name is OPSMVS.DFDSS.PRECONV.BACKUP

OPSMODE

Modify and submit job

Note: Automate must be at the SA95100 PTF level to link OPSMODE into OPSMVS.LOAD

COPYMATE

Copy Automate REXX, CLIST and, rule libraries to OPSMVS.ATM.** data sets for use by OPSMVS exclusively.

OPSMAIN

Backup SYS1.PROCLIB(OPSMAIN) as OPSMAI99 and add DD statement created in job COPYMATE to OPSMAIN

//RULES DD DSN=ISP.ATM.RULES,DISP=SHR

OPSOSF

Backup SYS1.PROCLIB(OPSOSF) as OPSOSF99 and add DD statements created in job COPYMATE to OPSOSF

Concatenate ISP.ATM.EXEC to SYSEXEC DD and SYSPROC DD statements

ATMPARM

Configure to match the Automate startup environment

OPSSPA00

Backup as OPSSPA98 and copy the statements in the ATMPARM member into SYS1.PARMLIB(OPSSPA00)

S.LOG

Stop the three OPSMVS started tasks with command "P TOPS" (stop the subsystem ID)

OPSMAIN

Start OPSMVS with the ATMPARM Automate parameters "S OPSMAIN"TSO 3.3

Copy the following members to OPSMVS.PROD.RULES.  These rules intercept commands entered by a user at a console or from within translated rules and procedures and perform Automate command simulation within OPSMVS

• OPAMCMMD
• OPAMCMCH

DidNotDo

Did not configure TSO logon procedures to allow ISPF access to Automate and SYSVIEW from the same TSO session

Did not enable converted Automate rules and applications running in other Automate MVS subsystems as we do not run multiple copies of Automate that communicate with each other via LCOMM.

Change Automate rules to OPSMVS rules by removing and/or changing non-supported Automate words in the OPSMVS version of the rules

TRANS1

Contains the search results for explicit Automate jobname.  Change the Automate jobname to ATMJOBNAME for all rules OPSMVS is to process or, any commands invoked with Automate will be routed to Automate and not to OPSMVS.

TRANS2

Contains the search results for Automate command character, CMDCHAR ")".   Change parameter to ATMCMDCHAR "))" in OPAMCMCH and OPAMCMMD members

TRANS3

Contains the search results for all non-supported Automate "words".  Change and/or comment them out in OPSMVS.ATM.RULES and OPSMVS.ATM.EXEC members

TSO 3.3

Copy from OPSMVS.EXEC to ISP.ATM.EXEC

• OPAMEXTB
• OPAMWRTB

A.0.2

Use this SYSVIEW option to migrate Automate relational tables to data set names OPSMVS.ATM.EXTABLES.*

OI_SESSIONS

ONLACT_PROD

ONLTBL_PROD

PROBMGR_TBL1

SSM_GROUP_MEMBERS

SSM_GROUP_STCUR

SSM_GROUP_STDEF

SSM_GROUP_STSEL

SSM_MANAGED_TBLS

STCACT_PROD

STCTBL_PROD

Note:

By this time, the export of all AutoMate/MVS RDF tables should have completed.  If you are unsure whether export processing ended, check the SYSLOG for message "OPS8728I".

Import processing will read each of the table datasets created and, create an identical table of the same name in OPS/MVS II.  If a table of the same name already exists in the product, the new table will not overlay the old table. If you would like the new table to replace the old table, it will first be necessary to delete the old table in OPS/MVS II.  Deleting the table can be accomplished using the SYSVIEW Table Editor option.

If the STATEMAN resource directory table was exported, it will be necessary to first set STATEMAN status to "INACTIVE" prior to deletion.  The SYSVIEW Control Option can be used to set the STATEMAN parameter.   STATEMAN should be returned to its normal status after import processing completes.

TSO 3.2

Allocate OPSMVS.ATM.TRANLATE.RULES which will contain the translated Automate rules

SYSVIEW option A.0.S.1

Translate Automate rules to OPSMVS rules

TSO 2

Backup SYS1.PARMLIB(COMMND00) as COMMND99; remove the following START commands from SYS1.PARMLIB(COMMND00) as these tasks will now be started by OPSMVS

• COM='S VPS   start VPS subsystem'
• COM='S VPSSRV   start VPS LRS server'
• COM='S BLX1PROC   start Info Mgmt task'

Backup OPSMVS.ATM.EXEC(IST010I) as IST02099; add the following START commands to OPSMVS.ATM.EXEC(IST020I)

• "OSCMD 'S VPS'
• "OSCMD 'S VPSSRV' CMDW(0)"
  "WAIT 120"
• "OSCMD 'S BLX1PROC'"