z/OS ISPF Planning and Customizing
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Installation considerations

z/OS ISPF Planning and Customizing
GC19-3623-00

Consider these points before you configure your system:

  • A RACF® OMVS segment (or equivalent) that specifies a valid non-zero uid, home directory, and shell command must be defined for each user of the interface.
  • Set MAXPROCUSER in BPXPRMxx parmlib member to a minimum of 50. This can be checked and set dynamically (until the next IPL) with the following commands (as described in z/OS MVS™ System Commands, SA22-7627):
    DISPLAY OMVS,O
    SETOMVS MAXPROCUSER=50.
    Setting a value that is too low can cause the interface to fail.
  • Table 1 describes the load modules that comprise the gateway:
    Table 1. Load modules comprising the gateway
    Name Library Description
    ISPZINT ISP.SISPLPA Gateway initialization - routes processing to ISPZINO or ISPZINL.
    ISPZINO ISP.SISPLPA Gateway initialization - manages spawned TSO sessions, routes command requests to these sessions.
    ISPZINL SYS1.SIEALNKE Gateway and TSO initialization - uses CEA TSO/E address spaces services to start and stop TSO sessions.
    ISPZTSO SYS1.LINKLIB TSO initialization - attaches a TSO session to run a command. ISPZTSO must run APF-authorized.
    ISPZCNT ISP.SISPLOAD ISPF initialization - allocates data sets and starts an ISPF session.
    ISPZCMD ISP.SISPLOAD ISPF command interface - invokes an ISPF command and, if required, keeps the ISPF session active.
    ISPZTMO ISP.SISPLOAD Reusable session time-out processor.

    These load modules must be available to run under the server used to communicate between the client and z/OS® host.

    A PROGRAM class profile that identifies ISPZINT as being a controlled program should be defined using the command:
    RDEFINE PROGRAM ISPZINT  ADDMEM('ISP.SISPLPA'//NOPADCHK) UACC(READ)
    (Refer to your security server's documentation for details.) Failure to define ISPZINT as being controlled might result in messages, such as CSV042I or ICH422I, being issued.
  • Table 2 describes the gateway files installed into the z/OS UNIX file system:
    Table 2. Gateway files installed into the z/OS UNIX file system
    Name Description
    /usr/lpp/ispf/bin/ISPZINL A stub file with the sticky bit set on to enable invocation of the gateway and TSO initialization load module ISPZINL.
    /usr/lpp/ispf/bin/ISPZINO A stub file with the sticky bit set on to enable invocation of the gateway initialization load module ISPZINO.
    /usr/lpp/ispf/bin/ISPZINT A stub file with the sticky bit set on to enable invocation of the gateway initialization load module ISPZINT.
    /usr/lpp/ispf/bin/ISPZTSO A stub file with the sticky bit set on to enable invocation of the TSO initialization load module ISPZTSO.
    /usr/lpp/ispf/bin/ISPZXENV A REXX routine called by the gateway XML API routine, ISPZXML, to set up environment variables.
    /usr/lpp/ispf/bin/ISPZXML A REXX routine that is the XML API for the gateway.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014