Prev | Table of Contents | Next

2. How to Install PJS

To install PJS, you must perform the following tasks:

| Task # | Step Description
| 1 | Obtain the PJS Installation Package
| 2 | Extract the PJS Installation Package PDS
| 3 | Review the $README, $COPYRT, and $LICENSE files
| 4 | Extract the PJS installation files
| 5 | Extract the PJS documentation files
| 6 | Allocate the PJS data sets
| 7 | Install the PJS software (with or without SMP/E)
| 8 | Add PJS to the Link List or the LPA (Optional)
| 9 | Authorize the PJS load libraries
| 10 | Initialize the PJS Request Queue
| 11 | Allocate the PJS JCL Spool (Optional)
| 12 | Create the PJS system task procedure
| 13 | Set up the PJS/TSO interface
| 14 | Set up the PJS/ISPF Interface
| 15 | Start the PJS System Task

Sample JCL is provided where appropriate. However, please check all sample jobs before you use them to ensure that site requirements are met.

2.1 Task 1: Obtain the PJS Installation Package

The PJS Installation Package is a single sequential file that contains all the elements of PJS. This file may be obtained as part of a public software distribution tape, such as the MVS CBT Tape, or downloaded from the Internet. If you obtained PJS from the MVS CBT Tape, or another distribution tape, you should refer to the documentation for the distribution tape for specific details of how to extract the PJS Installation Package.

If you download PJS it from the Internet, it may be contained within a Zip file. If this is the case you will need to extract the PJS Installation Package file from the Zip file. In any case whenever the PJS Installation Package, or the Zip file that contains it, is transmitted, typically with FTP, it must be done as BINARY data.

When the PJS Installation Package file (unzipped if necessary) is finally loaded to the OS/390 or z/OS host it is to be installed on, it must be allocated as a physical sequential data set (DSORG=PS), fixed-length records (RECFM=FB), with a logical record length of 80 bytes (LRECL=80), and any appropriate block size. When FTP is used these data set characteristics are typically set using the FTP ‘SITE’ command. Your installation may also require additional parameters on the ‘SITE’ command to specify how and where the data set should be allocated. For a complete list of all the options available see the IBM Communications Server: IP User’s Guide for your release of OS/390 or z/OS.

The following example shows the FTP commands that can be used to send the PJS Installation Package from a PC to an OS/390 or z/OS host:

C:\>FTP hostname Connected to hostname. 220-FTPD1 IBM FTP CS V1R4 at hostname, 16:34:20 on 2004-02-10. 220 Connection will close if idle for more than 20 minutes. User (hostname:(none)): userid 331 Send password please. Password: password 230 userid is logged on. Working directory is "userid.". ftp> CD 'qual' 250 "qual." is the working directory name prefix. ftp> LCD C:\dir Local directory now C:\dir. ftp> QUOTE SITE RECFM=FB LRECL=80 BLKSIZE=0 TRACKS PRI=300 SEC=75 200 SITE command was accepted ftp> BINARY 200 Representation type is Image ftp> PUT PJS214.XMIT 200 Port request OK. 125 Storing data set qual.PJS214.XMIT 250 Transfer completed successfully. ftp: 10371120 bytes sent in 9.26Seconds 1119.51Kbytes/sec. ftp> QUIT 221 Quit command received. Goodbye.

2.2 Task 2: Extract the PJS Installation Package PDS

The PJS Installation Package contains a partitioned data set that has been formatted as a TSO TRANSMIT file. This PDS, called the PJS Installation Package PDS may be extracted with the TSO ‘RECEIVE’ command with the ‘INDATASET’ parameter.

The following example shows the TSO ‘RECEIVE’ command that can be used to extract the PJS Installation Package PDS:

READY RECEIVE INDATASET('qual.PJS214.XMIT') INMR901I Dataset qual.DDNAME.PACKAGE from TCH03 on SYSTEME INMR906A Enter restore parameters or 'DELETE' or 'END' + DATASET('qual.PJS214.PACKAGE') NEW INMR001I Restore successful to dataset 'qual.PJS214.PACKAGE' READY

Your installation may also require additional parameters on the ‘RECEIVE’ command prompt response to specify how and where the data set should be allocated. For a complete list of all the options available see the TSO/E Command Reference for your release of OS/390 or z/OS.

The following table lists the members of the PJS Installation Package PDS:

Member Name | Description | Format
$COPYRT | PJS Copyright Notice | Text
$LICENSE | GNU General Public License | Text
$LICPUB | GNU Free Documentation License | Text
$README | “Getting Started” Instructions | Text
EXTRACT | Sample job to extract the PJS installation files | Text
PJSDOC | PJS Documentation | Zip
INSTALL | Installation JCL Library | PDS
SMPMCS | SMP/E MCS Statements | Seq
JCLIN | SMP/E JCLIN | PDS
MACLIB | PJS Macro Library | PDS
SRCLIB | PJS Source Library | PDS
MODLIB | PJS Modules Library | PDS
TSOHELP | PJS TSO Help Library | PDS
ISPFPNL | PJS ISPF Panels Library | PDS
ISPFMSG | PJS ISPF Messages Library | PDS
ISPFTBL | PJS ISPF Tables Library | PDS
SAMPLIB | PJS Samples Library | PDS
UCRLIB | PJS User Contributed Routines | PDS

Text = Text file

Zip = Zip file in TSO XMIT format

Seq = Sequential Data Set in TSO XMIT format

PDS = Partitioned Data Set in TSO XMIT format

The $COPYRT, $LICENSE, $LICPUB, and $README members are text files that contain important information about PJS that should be reviewed before completing the installation. The EXTRACT member contains a sample job that can be used to create the PJS installation files from the PJS Installation Package. Each of the other members contains one of the PJS installation files that has been formatted as a TSO TRANSMIT file.

2.3 Task 3: Review the $COPYRT, $LICENSE, and $README Files

After extracting the PJS Installation Package you should carefully read the $COPYRT and $LICENSE members. These contain the copyright notice and license terms for using PJS. If you do not agree to these terms you will not be authorized to use PJS.

PJS is licensed under the GNU General Public License version 2, or (at your option) any later version, as published by the Free Software Foundation. This license is widely used for many open-source software products, including Linux. A copy of the GNU GPL is also included in an appendix of this book. For more information about the GNU GPL see the Free Software Foundation website at http://www.gnu.org/licenses/.

You should also read the $README member. This contains the latest information that might not have been included in the documentation.

2.4 Task 4: Extract the PJS Installation Files

The EXTRACT member of the PJS Installation Package PDS contains a sample job to extract the PJS installation data sets. This job will run TSO as a background job and use the TSO ‘RECEIVE’ command with the ‘INDATASET’ parameter to extract each of the PJS Installation Files.

This job should be tailored to suit your installation standards, paying particular attention to the job card, and the allocation parameters on the TSO ‘RECEIVE’ command prompt responses. For a complete list of all the options available see the TSO/E Command Reference for your release of OS/390 or z/OS.

The extract process will create the following PJS Installation Files:

Data Set Name | Description | Format
qual.PJS214.PJSDOC | PJS Documentation | Zip
qual.PJS214.INSTALL | Installation JCL Library | PDS
qual.PJS214.SMPMCS | SMP/E MCS Statements | Seq
qual.PJS214.NPJ2104.F1 | SMP/E JCLIN | PDS
qual.PJS214.NPJ2104.F2 | PJS Macro Library | PDS
qual.PJS214.NPJ2104.F3 | PJS Source Library | PDS
qual.PJS214.NPJ2104.F4 | PJS Modules Library | PDS
qual.PJS214.NPJ2104.F5 | PJS TSO Help Library | PDS
qual.PJS214.NPJ2104.F6 | PJS ISPF Panels Library | PDS
qual.PJS214.NPJ2104.F7 | PJS ISPF Messages Library | PDS
qual.PJS214.NPJ2104.F8 | PJS ISPF Tables Library | PDS
qual.PJS214.NPJ2104.F9 | PJS Samples Library | PDS
qual.PJS214.UCRLIB | PJS User Contributed Routines | PDS

2.5 Task 5: Extract the PJS Documentation Files

If you download PJS it from the Internet as a Zip file, the PJS documentation may have been included as a separate file within that Zip file. If this is not the case you will need to get the PJS documentation from the PJS Installation Package.

In Task 4 you should have created a file named ‘qual.PJS214.PJSDOC’. This is a variable-length record sequential data set that is a Zip file containing the PJS documentation files. To extract and view these files you will need to download them to a workstation, typically with FTP. This transfer must be done in BINARY mode.

The following example shows the FTP commands that can be used to receive the PJS documentation Zip file to a PC from an OS/390 or z/OS host:

C:\>FTP hostname Connected to hostname. 220-FTPD1 IBM FTP CS V1R4 at hostname, 16:34:20 on 2004-02-10. 220 Connection will close if idle for more than 20 minutes. User (hostname:(none)): userid 331 Send password please. Password: password 230 userid is logged on. Working directory is "userid.". ftp> CD 'qual.PJS214' 250 "qual.PJS214." is the working directory name prefix. ftp> LCD C:\dir Local directory now C:\dir. ftp> BINARY 200 Representation type is Image ftp> GET PJSDOC PJSDOC.ZIP 200 Port request OK. 125 Storing data set qual.PJS214.PJSDOC 250 Transfer completed successfully. ftp: 783588 bytes received in 1.12Seconds 699.01Kbytes/sec. ftp> QUIT 221 Quit command received. Goodbye.

Once the file is on your workstation you will need to extract the documentation files using WinZip, or any other program that extracts Zip files. Once the documents have been extracted the following documents will be available:

File Name | Description | Format
PJSINST.PDF | PJS Installation Guide | PDF
PJSMSG.PDF | PJS Messages and Codes | PDF
PJSUSER.PDF | PJS User’s Guide | PDF

PDF = Adobe Acrobat Portable Document File. To view these files you will need the free Adobe Acrobat Reader, available at http://www.adobe.com/products/acrobat/readstep2.html.

2.6 Task 6: Allocate the PJS Data Sets

Minimum allocation requirements for the PJS distribution and target libraries are listed in the following tables. To allow for maintenance and expansion, add extra space to each data set.

The member ALLOC in the INSTALL library contains a sample job to allocate these data sets. This job should be tailored to suit your installation standards, paying particular attention to the job card, volume serial numbers, and unit names.

PJS Distribution Libraries

File Name | Data Set Name | File Description | RECFM | LRECL | # of 3390 Tracks | # of Dir Blks
APJSMAC | qual.PJS.APJSMAC | PJS Macro DLIB | FB | 80 | 39 | 2
APJSSRC | qual.PJS.APJSSRC | PJS Source DLIB | FB | 80 | * | *
APJSMOD | qual.PJS.APJSMOD | PJS Module DLIB | U | 0 | 107 | 16
APJSHELP | qual.PJS.APJSHELP | PJS TSO Help DLIB | FB | 80 | 38 | 5
APJSPLIB | qual.PJS.APJSPLIB | PJS ISPF Panels DLIB | FB | 80 | 256 | 22
APJSMLIB | qual.PJS.APJSMLIB | PJS ISPF Messages DLIB | FB | 80 | 36 | 7
APJSTLIB | qual.PJS.APJSTLIB | PJS ISPF Tables DLIB | FB | 80 | 2 | 1
APJSSAMP | qual.PJS.APJSSAMP | PJS Samples DLIB | FB | 80 | 114 | 2

If you do not plan to use SMP/E to install PJS, just allocate the APJSMOD data set. Because this library is required only during the installation process, you can delete APJSMOD after you install PJS.

If you use SMP/E to install PJS, allocate all of these data sets. Do not delete APJSMOD after you complete the PJS installation.

PJS Target Libraries

File Name | Data Set Name | File Description | RECFM | LRECL | # of 3390 Tracks | # of Dir Blks
PJSMAC | qual.PJS.MACLIB | PJS Macro Library | FB | 80 | 39 | 2
PJSSRC | qual.PJS.SRCLIB | PJS Source Library | FB | 80 | * | *
PJSCMD | qual.PJS.CMDLIB | PJS TSO Command Library | U | 0 | 43 | 11
PJSLINK | qual.PJS.LINKLIB | PJS Link Library (Common Routines) | U | 0 | 21 | 3
PJSLOAD | qual.PJS.LOADLIB | PJS Load Library (System Task and Utilities) | U | 0 | 9 | 2
PJSHELP | qual.PJS.TSOHELP | PJS TSO Help Library | FB | 80 | 38 | 5
PJSPLIB | qual.PJS.ISPFPNL | PJS ISPF Panels Library | FB | 80 | 256 | 22
PJSMLIB | qual.PJS.ISPFMSG | PJS ISPF Messages Library | FB | 80 | 36 | 7
PJSTLIB | qual.PJS.ISPFTBL | PJS ISPF Tables Library | FB | 80 | 2 | 1
PJSSAMP | qual.PJS.SAMPLIB | PJS Samples Library | FB | 80 | 114 | 2

You can combine the PJSCMD, PJSLINK, and PJSLOAD data sets, or combine these data sets with other data sets by changing the appropriate JCL DD statements and SMP/E DDDEFs. For example, the PJSCMD and PJSLINK DD names can reference SYS1.LPALIB, and the PJSLOAD DD name can reference a common APF authorized non‑link‑list data set.

The load modules contained in the PJSCMD and PJSLINK libraries are reentrant, so they can be included in the system Link Pack Area (LPA). If you decide to include these reentrant load modules in the LPA, you must perform an IPL with CLPA after the installation to load the modules into the LPA. These modules use about 12K of LPA (below the 16M storage line), and about 192K of ELPA (above the 16M storage line).

2.7 Task 7: Install the PJS Software

If you are using SMP/E to install PJS, complete the set of subtasks in Subsection 2.7.1. If you are not using SMP/E to install PJS, complete the set of subtasks in Subsection 2.7.2.

2.7.1 Installation with SMP/E

You can use the SMP/E ISPF Dialogs or the sample jobs to help finish the following subtasks:

2.7.1.1 SMP/E Subtask 1: Prepare the SMP/E zones

PJS can be installed into an existing SMP/E zone, if there are no name conflicts. It can also be installed into a separate zone. If you wish to install PJS into an existing zone, the member SMPDDDEF in sthe INSTALL library provides a sample job to define the DDDEFs required by PJS. If you wish to install PJS into a new zone, the member DEFCSI in the INSTALL library provides a sample job to create and define a new SMP/E CSI for PJS.

2.7.1.2 SMP/E Subtask 2: Receive, Apply, Accept PJS Function SYSMOD

Use the following procedure to receive, apply, and accept the PJS function SYSMOD:

1. Receive the PJS function SYSMOD (FMID NPJ2104) into the SMP/E Global Zone. The member SMPRECF in the INSTALL library provides a sample job to receive the PJS function SYSMOD. This job should be tailored to suit your installation standards, paying particular attention to the job card, and the SMP/E CSI data set name.

2. Apply the PJS function SYSMOD (FMID NPJ2104) to the SMP/E Target Zone. The member SMPAPLYF in the INSTALL library provides a sample job to apply the PJS function SYSMOD. This job should be tailored to suit your installation standards, paying particular attention to the job card, the SMP/E CSI data set name, and the Target Zone name.

3. Accept the PJS function SYSMOD (FMID NPJ2104) into the SMP/E Distribution Zone. The member SMPACPTF in the INSTALL library provides a sample job to accept the PJS function SYSMOD. This job should be tailored to suit your installation standards, paying particular attention to the job card, the SMP/E CSI data set name, and the Distribution Zone name.

2.7.1.3 SMP/E Subtask 3: Receive and Apply User Exit USERMODs (Optional)

Note: User exits provide the means to tailor PJS to better fit site requirements. Even if you do not plan to change user exits and skip this subtask it is a good idea to read the information contained in Chapter 4.

Chapter 4 contains information on the PJS Installation Data Format Exit, the PJS Options Exit, the PJS Security Exit, and the PJS Installation Submit Exit. If you plan to make use of any of these user exits, you can use the sample exits provided or use the information in Chapter 4 to write your own exit routines.

If PJS is being upgraded from an earlier release, the exit source should be reviewed for any required changes, then reinstalled. Do not attempt to use an existing object or load module.

The module source should be placed into an appropriate USERMOD and received into the SMP/E Global Zone. Apply the USERMODs to the SMP/E Target Zone.

The member USERMOD in the INSTALL library provides a sample SMP/E USERMOD for modifying a PJS module. This member should be used as a base, by copying it to another data set and/or member, editing the SYSMOD ID, and adding the source code for the module being modified.

The member SMPRECU in the INSTALL library provides a sample job to receive a USERMOD for PJS. This job should be tailored to suit your installation standards, paying particular attention to the job card, and the SMP/E CSI data set name.

The member SMPAPLYU in the INSTALL library provides a sample job to apply a USERMOD for PJS. This job should be tailored to suit your installation standards, paying particular attention to the job card, the SMP/E CSI data set name, and the USERMOD ID.

Note: We recommend that you do not accept the USERMODs for user exits into the SMP/E Distribution Zone. If you need more information, please refer to the SMP/E User's Guide.

2.7.1.4 SMP/E Subtask 4: Receive and Apply the PJSOPT USERMOD

Create a USERMOD for the PJS Options Module, which is contained in the PJSOPT module. Information on how to create source code for this module is contained in Chapter 3.

If PJS is being upgraded from an earlier release, the PJSOPT source should be reviewed for any required changes, then reinstalled. Do not attempt to use an existing object or load module.

The module source should be placed into an appropriate USERMOD and received into the SMP/E Global Zone. Apply the PJSOPT USERMOD to the SMP/E Target Zone.

The member USERMOD in the INSTALL library provides a sample SMP/E USERMOD for modifying a PJS module. This member should be used as a base, by copying it to another data set and/or member, editing the SYSMOD ID, and adding the source code for the module being modified.

The member SMPRECU in the INSTALL library provides a sample job to receive a USERMOD for PJS. This job should be tailored to suit your installation standards, paying particular attention to the job card, and the SMP/E CSI data set name.

The member SMPAPLYU in the INSTALL library provides a sample job to apply a USERMOD for PJS. This job should be tailored to suit your installation standards, paying particular attention to the job card, the SMP/E CSI data set name, and the USERMOD ID.

Note: We recommend that you do not accept the USERMOD for PJSOPT into the SMP/E Distribution Zone. If you need more information, please refer to the SMP/E User's Guide.

After you finish this subtask, please refer to Section 2.8 to continue installing PJS.

2.7.2 Installation without SMP/E

Perform the following subtasks:

2.7.2.1 Non-SMP/E Subtask 1: Copy PJS from the PJS Installation Files

The member COPYPJS in the INSTALL library provides a sample job to copy PJS from the PJS Installation Files to the PJS target data sets using IEBCOPY.

2.7.2.2 Non-SMP/E Subtask 2: Link-Edit the PJS Software

The TSO command procedures are link‑edited into the PJSCMD library, the common reentrant subroutines are link‑edited into the PJSLINK library, and the non‑reentrant utilities and the PJS System Task programs are link‑edited into the PJSLOAD library. The member LINKPJS in the INSTALL library provides a sample job to link‑edit the PJS software.

2.7.2.3 Non-SMP/E Subtask 3: Assemble and Link-Edit User Exits (Optional)

Note: User exits provide the means to tailor PJS to better fit site requirements. Even if you do not plan to change user exits and skip this subtask it is a good idea to read the information contained in Chapter 4.

Chapter 4 contains information on the PJS Installation Data Format Exit, the PJS Options Exit, the PJS Security Exit, and the PJS Installation Submit Exit. If you plan to make use of any of these user exits, you can use the sample exits provided or use the information in Chapter 4 to write your own exit routines.

If PJS is being upgraded from an earlier release, the exit source should be reviewed for any required changes, then reassembled and link-edited. Do not attempt to use an existing object or load module.

The member ASMEXIT in the INSTALL library provides a sample job to assemble and link‑edit an exit routine for PJS. This job should be tailored to suit your installation standards, paying particular attention to the job card, and the data set names.

2.7.2.4 Non-SMP/E Subtask 4: Assemble and Link-Edit PJSOPT

Create a PJS Options Module (PJSOPT). Details on how to create the source code for the PJSOPT module are contained in Chapter 3.

If PJS is being upgraded from an earlier release, the PJSOPT source should be reviewed for any required changes, then reassembled and link-edited. Do not attempt to use an existing object or load module.

The member ASMOPT in the INSTALL library provides a sample job to assemble and link‑edit the PJS Options Module. This job should be tailored to suit your installation standards, paying particular attention to the job card, and the data set names.

2.8 Task 8: Add PJS to the Link List or the LPA (Optional)

It's a good idea to place the PJSCMD library and the PJSLINK library either in the system link list or the link pack area. You can place the PJSLOAD library in the system link list, but there's no good reason to do so; you cannot place PJSLOAD in the LPA.

For more information and instructions, refer to the MVS Initialization and Tuning Reference. An IPL (with CLPA) may be required to make this change effective.

2.9 Task 9: Authorize the PJS Load Libraries

The PJS System Task should run APF authorized. The main routines used by the PJS System Task are in the PJSLOAD library; it also uses several routines from the PJSLINK (common routines) library. These libraries should be APF authorized. If these libraries are placed on the system link list, and the system link list is authorized, they may acquire authorization from that fact. If the PJSLINK library is placed in the LPA, those routines will be considered authorized. Otherwise, the data sets in which these libraries are placed, must be listed in the IEAAPFnn member of SYS1.PARMLIB. If PJS runs without authorization, PJS cannot send messages to its users. In addition, the PJS Security Exit must be authorized if you plan to use it.

Refer to the MVS Initialization and Tuning Reference for detailed instructions. An IPL may be required to make this change effective.

2.10 Task 10: Initialize the PJS Request Queue

Note: If you are upgrading PJS, you can omit this step. If this is a new installation, you must complete this task.

The PJS Request Queue contains records defining the Job Requests, Calendars, and Events specified by PJS users, as well as other control records.

The PJS Request Queue is a VSAM KSDS. The PJS Request Queue must be defined with RECSZ(144,4084), KEYS(17,0), and SHR(2). Most other data set attributes may be changed to optimize VSAM processing. For most installations, 1 or 2 cylinders of space should be sufficient.

The PJS Request Queue is defined with IDCAMS and initialized with the PJSQINIT program. PJSQINIT is a utility program that initializes the PJS Request Queue. It has no input parameters. A DD statement with a DDNAME of PJSQ is required, and should point to the PJS Request Queue data set. A DD statement with a DDNAME of SYSOUT is also required, and should point to the message data set; in most cases you can specify SYSOUT=*.

The member DEFPJSQ in the INSTALL library provides a sample job to define and initialize the PJS Request Queue data set. This job should be tailored to suit your installation standards, paying particular attention to the job card, the PJS Request Queue data set name, the volume serial number, and the allocation quantity.

For more information on PJSQINIT, please refer to Chapter 7.

2.11 Task 11: Allocate the PJS JCL Spool (Optional)

Note: If this is a maintenance installation (the same release), you can omit this task.

If the PJS JCL Save feature is to be used, the PJS JCL Spool data set must be allocated. The JCL to be saved will be copied to the PJS JCL Spool by the PJS TSO commands and the PJS ISPF interface.

The PJS JCL Spool is a partitioned data set. The PJS JCL Spool must be defined with RECFM=FB, LRECL=80, and any suitable blocksize. Each JCL member saved has a PDS directory entry. Since each directory entry has 22 bytes of user data, 7 directory entries will fit in each directory block.

The member DEFSPOOL in the INSTALL library provides a sample job to allocate the PJS Spool data set. This job should be tailored to suit your installation standards, paying particular attention to the job card, the PJS JCL Spool data set name, the unit name, the volume serial number, and the allocation quantity.

2.12 Task 12: Create the PJS System Task Procedure

Note: If PJS is already installed, you can omit this task. If this is a new installation, you must complete this task.

Place the start‑up procedure for the PJS System Task into a system procedure library. A sample procedure is in member PJSPROC in the INSTALL library. This procedure should be tailored to suit your installation standards.

The PJSLOAD library should be included in the STEPLIB concatenation. (Although it is possible to include the PJSLOAD library in the system link list, this is not generally recommended.) The PJSLINK library must be concatenated to the STEPLIB data set, included in the system link list, or placed in the system link pack area.

A DD statement with a DDNAME of SYSOUT is required, and should point to the message data set; in most cases you can specify SYSOUT=*.

2.13 Task 13: Set Up the PJS/TSO Interface

The PJS/TSO interface must be made available to the user. The PJSCMD library and PJSLINK library must be concatenated to the STEPLIB data set, included in the system link list, or placed in the system link pack area. The PJSHELP library should be concatenated to the SYSHELP data set.

If you have a security system that restricts TSO commands (like ACF2), you may need to define the PJS TSO commands to your security system. The PJS TSO commands that must be defined are listed in Appendix A.

For more information, please refer to TSO/E Customization and your security system documentation.

2.14 Task 14: Set Up the PJS/ISPF Interface (Optional)

Note: If you do not plan to use the ISPF interface, skip this task.

The PJS ISPF panels, messages, and tables must be made available to ISPF, and a means of selecting PJS must be provided to the user. Each of these may be accomplished in several ways. The best way depends on how your installation manages ISPF. Detailed and authoritative information on each method can be found in the ISPF Dialog Management Guide and Reference. The particular documents required may depend on your release of ISPF.

There are several ways to make the PJS ISPF panels, messages, and tables available to ISPF:

- Install the PJS panels, messages and tables in existing ISPF libraries (such as SYS1.ISPPLIB, SYS1.ISPMLIB, and SYS1.ISPTLIB).

- Concatenate the PJS libraries to the data sets already allocated to the ISPF libraries (ISPPLIB, ISPMLIB, and ISPTLIB). This could be done either in the TSO procedure, or by a CLIST or REXX exec that executes prior to ISPF.

- Allocate the PJS libraries using the ISPF LIBDEF service. This may require a CLIST or REXX exec to execute prior to the ISPF SELECT for PJS.

Generally, to call the PJS ISPF interface, the following ISPF SELECT is required:

SELECT PGM(PJSISPF) PARM(option) NEWAPPL(PJS) NOCHECK

where option is the initial PJS option to be selected.

To modify an ISPF menu to call the PJS/ISPF interface, the following statements should be included in the )PROC section of the menu panel definition:

&ZQ = TRUNC(&ZCMD,'.') &ZTRAIL = .TRAIL &ZSEL = TRANS( &ZQ . . . n,'PGM(PJSISPF) PARM(&ZTRAIL) NEWAPPL(PJS) NOCHECK' . . . *,'?')

2.15 Task 15: Start the PJS System Task

Once the PJS system is installed and customized, the PJS System Task can be started. Procedures for starting, stopping, and controlling the PJS System Task are in Chapter 6.

It is recommended that the start command for the PJS System Task be placed in the MVS automatic start‑up commands list (member COMMNDxx of SYS1.PARMLIB). For detailed information on how to do this, see the MVS Initialization and Tuning Reference.

Prev | Table of Contents | Next

Copyright © Northrop Grumman, 1990, 2004. All rights reserved.