PJS®
Personal Job Scheduler 
Installation Guide
Release 2.1
Related PJS Technical Documentation
Personal Job Scheduler (PJS®) User Guide
Personal Job Scheduler (PJS®) Messages and Codes
Personal Job Scheduler (PJS) 2.1.1 was released for distribution in April, 1992.
Personal Job Scheduler (PJS) 2.1.2 was released for distribution in November, 1992.
Personal Job Scheduler (PJS) 2.1.3 was released for distribution in October, 2002.
Personal Job Scheduler (PJS) 2.1.4 was released for distribution in February, 2004.
PJS is a registered trademark of Northrop Grumman.
MVS is a trademark and IBM®, OS/390®, RACF®, and z/OS® are registered trademarks of International Business Machines Corporation.
Copyright © Northrop Grumman, 1990, 2004. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being "PJS Software Copyright and License" and "GNU General Public License", with no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
PJS Software Copyright and License
2.1 Task 1: Obtain the PJS Installation Package
2.2 Task 2: Extract the PJS Installation Package PDS
2.3 Task 3: Review the $COPYRT, $LICENSE, and $README Files
2.4 Task 4: Extract the PJS Installation Files
2.5 Task 5: Extract the PJS Installation Files
2.6 Task 6: Allocate the PJS Data Sets
2.7 Task 7: Install the PJS Software
2.7.1.1 SMP/E Subtask 1: Prepare the SMP/E Zones
2.7.1.2 SMP/E Subtask 2: Receive, Apply, Accept PJS Function SYSMOD
2.7.1.3 SMP/E Subtask 3: Receive and Apply User Exit USERMODs
2.7.1.4 SMP/E Subtask 4: Receive and Apply the PJSOPT USERMOD
2.7.2 Installation without SMP/E
2.7.2.1 Non-SMP/E Subtask 1: Copy PJS from the PJS Installation Files
2.7.2.2 Non-SMP/E Subtask 2: Link-Edit the PJS Software
2.7.2.3 Non-SMP/E Subtask 3: Assemble and Link-Edit User Exits (Optional)
2.7.2.4 Non-SMP/E Subtask 4: Assemble and Link-Edit PJSOPT
2.8 Task 8: Add PJS to the Link List or the LPA (Optional)
2.9 Task 9: Authorize the PJS Load Libraries
2.10 Task 10: Initialize the PJS Request Queue
2.11 Task 11: Allocate the PJS JCL Spool (Optional)
2.12 Task 12: Create the PJS System Task Procedure
2.13 Task 13: Set Up the PJS/TSO Interface
2.14 Task 14: Set Up the PJS/ISPF Interface (Optional)
2.15 Task 15: Start the PJS System Task
3.1 PJSOPT Macro Format and Operands
4.1 The PJS Installation Data Format Exit (PJSIDFX)
4.1.1 PJSIDFX Input Parameters
4.2 The PJS Installation Options Exit (PJSOPTX)
4.2.1 PJSOPTX Input Parameters
4.3 The PJS Installation Security Exit (PJSSECX)
4.3.1 PJSSECX Input Parameters
4.4 The PJS Installation Submit Exit (PJSSUBX)
4.4.1 PJSSUBX Input Parameters
4.4.3 How to Use the PJSSUBX Exit
5.2 Securing the PJS Data Sets
5.3 Securing the PJS Request Queue Records
5.4 Securing Batch Jobs Submitted by PJS
7.1 The PJS Request Queue Initialization (PJSQINIT) Utility
7.2 The PJS Request Queue Maintenance (PJSQMNT) Utility
B.3 The PJS Request Queue Entry
B.4 The PJSQ Queue Control Record
B.6 The PJSQ Job Request Record
GNU Free Documentation License
This manual describes how to install and customize Release 2.1 of the Personal Job Scheduler (PJS).
The person who installs and customizes PJS should have the skills and experience of a Site Administrator or Systems Programmer. Installation requires knowledge of IBM mainframes, the OS/390 environment, JCL, site standards, and site conventions.
During the installation procedure, you can use SMP/E to help install PJS, set prebuilt panels to run under ISPF, or use a security system such as RACF. If you choose any of these options, the manual assumes familiarity with relevant software systems.
If you need more information on how to use this product, please refer to the Personal Job Scheduler (PJS®) User Guide. If you need information on error messages and abend codes encountered during PJS use, please refer to the Personal Job Scheduler (PJS®) Messages and Codes manual.
The following conventions are used in command formats throughout this manual:
BOLD UPPERCASE is used to display commands or keywords you must code exactly as shown, for example, SEND FILENAME.TXT.
italic lowercase is used to display information you must supply, for example, SEND filename.txt.
Underscores either show a default value in a command description, display a default value in a screen image, or represent a highlighted word in a screen image.
Brackets [ ] mean that you can select one of the items enclosed by the brackets; none of the enclosed items is required.
Braces { } mean that you must select one of the items enclosed by the braces.
Vertical Bar | separates options. One vertical bar separates two options, two vertical bars separate three options, and so on. You can select only one of the options.
Ellipsis . . . means that you can repeat the word or clause that immediately precedes the ellipsis.
PJS was written by Tim Henness
The original version of this manual was written by Matthew ???? and Tim Henness.
Extensive revisions have been made by Tim Henness
PJS Software Copyright and License
All PJS software is Copyright © Northrop Grumman, 1990, 2004. All rights reserved.
PJS is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
PJS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
A copy of the GNU General Public License is included in the back of this book.
The author welcomes your comments and suggestions. He can be contacted at:
Tim Henness
Northrop Grumman IT
Internal Information Services
Bldg. 521-2
4101 Washington Ave.
Newport News, VA 23607
E-mail: Tim.Henness@ngc.com