z/OS UNIX System Services Planning
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Steps for finding modules that were not defined to program control

z/OS UNIX System Services Planning
GA32-0884-00

Before you begin: You need to check your job log and have the security administrator check the security console for diagnostic messages.

Perform the following steps to find the module that was not defined to program control.

  1. Search the RACF® database for a list of the modules that are defined to program control.
    Example: Issue the following TSO/E command:
    SEARCH CLASS(PROGRAM) NOMASK
    Result: You will see output similar to the following:
          CEEOLVD
          CEEOV
          CEEPLPKA
          CEEZ24
          DAEMON
          EDCUCSNM
          EDCUEYI1
          EDC$EUEY
          ...
     

    _______________________________________________________________

  2. Look for the daemon module (for example, DAEMON) and locations in the format EDC$xxyy (in the output in Step 1, EDC$EUEY is the module for the U.S. English locale).

    _______________________________________________________________

  3. If the output of the SEARCH module shows *, issue:
    RLIST PROGRAM *
    The * covers any module name in the libraries displayed in the output of the RLIST command. If a VOLSER is displayed with a library name, make sure that the VOLSER is also correct.

    _______________________________________________________________

  4. Gather data about which programs need to be defined to program control by using SLIP. The complete details are in z/OS Security Server RACF Diagnosis Guide.
    Example:
      SLIP SET,IF,ACTION=TRACE,LPAMOD=(ICHRFR00,xxxxx),J=jobname,
      TRDATA=(STD,REGS,zzzzzz),ML=100,END

    _______________________________________________________________

  5. Because this SLIP produces GTF records, you must start GTF. Be sure that you specify PARM TRACE=SLIP. Then use IPCS to format the data with the GTFTRACE IPCS command. You will see output similar to the following:
    SLIP S+U          ASCB.... 00FAF580 CPU..... 0001     JOBN.... INETD8
                      .....
                      GENERAL PURPOSE REGISTER VALUES
                      0-3..... 7FFEB744 7FFEB748 00000000 007F2978
                      4-7..... 0000000C 007F0738 00000004 007F24D8
                      8-11.... 00000000 7FFEB6A8 80E2323E 007F2978
                      12-15... 00000000 7FFEB6A8 80E23616 0000000C
                      ...
    
    SLIP USR          CPU..... 0001     EXT..... 0001     CNTLN... 00
                0008  C3C5C5C2 C9D5C9E3                   | CEEBINIT
                002C  C3C5C54B E2C3C5C5 D9E4D540 40404040 | CEE.SCEERUN
                      40404040 40404040 40404040 40404040 |
                      40404040 40404040 40404040          |
                0006  D6D7F2D9 E2F1                       | OP2RS1

    _______________________________________________________________

  6. Look for a SLIP S+U entry where R15 has a value of 0000000C. Then look at that entry to identify the module and library that needs to be defined to program control.

    _______________________________________________________________

You know you are done when you have identified the module and library that needs to be defined to program control.

Tip: To define the module to program control, issue:
 RDEFINE PROGRAM CEEBINIT ADDMEM -
 ('CEE.SCEERUN'/OP2RS1/NOPADCHK) UACC(READ)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014