Starting Your Product › Start the Product › Things to Check after Starting the Product

Things to Check after Starting the Product

After CA OPS/MVS becomes active, do the following checks:

• Make sure that CA OPS/MVS started at least one OPSOSF address space by issuing a DISPLAY ACTIVE command:

  D A,OPSOSF
  

• Test the OSF by entering the following command from a console. This command assumes that you are using the default value for the OSFCHAR parameter, which is an exclamation point (!):

  !OI OPSIVP
  

  • The user ID running the OPSIVP requires TSO OPER authority.
  • The OPSIVP OPS/REXX program is located in the REXX library. If CA OPS/MVS returns a Program Not Found message, the REXX library is not concatenated under the SYSEXEC ddname of the OPSOSF STC.
  • The OPSIVP program tests the CA OPS/MVS WTO and WTOR capabilities, so be sure to monitor the console for any messages or prompts. A reply to the WTOR is not required. The OPSIVP program also tests the ability of CA OPS/MVS to issue console commands using the OPSCMD TSO command. Any errors in the OPSCMD command will trigger debugging messages that indicate the OPSOSF security authority.
  • If the !OI OPSIVP command returns no output to your console, the Operator Server Facility (OSF) is not working. This situation usually results when OPSOSF address spaces cannot be started because of insufficient security authorization; that is, they do not have the authority to access their own data sets. Remember to scan console messages to check for additional problems.
• Verify your security authority by executing the OPSIVP program from your TSO user ID. To do so, issue the following command from the TSO READY screen:

  OI OPSIVP
  

• Test some of the CA OPS/MVS OPSVIEW capabilities using one of the following options:
  • Enter this command from your TSO session at the TSO READY prompt:

    OPSV
    

  • Enter this command from your TSO session under ISPF:

    TSO OPSV
    

    Important! The above command with the TSO prefix can only be issued under ISPF. Entering the command with the TSO prefix from the TSO READY prompt will result in the error message COMMAND TSO NOT FOUND.

• From the OPSVIEW Primary Options Menu, select option 1 to view the OPSLOG. You should see a display log similar to your SDSF LOG or SYSLOG. If your display is blank, the CA OPS/MVS main STC may be inactive or error messages may be displayed on the console. You should also access OPSVIEW option 4.1.1, which displays all of the CA OPS/MVS parameters.
• Access OPSVIEW through the procedures implemented during Make OPSVIEW Facilities Available Under TSO in this chapter.