Appendix C.  Summary of Changes

 

 

C.1  Changes for PJS Release 2.1.4

 

Functional Changes ‑

 

·         The CPU authorization checking has been removed.

 

·         Commands to display copyright and license information have been added to the ISPF menu.

 

 

Installation Changes ‑

 

·         PJS is now distributed as a single file that can be distributed as part of a public software distribution tape, such as the MVS CBT Tape, or downloaded from the internet.

 

·         PJS is now installed with full source code.  All macros required for reassembling PJS (other than IBM macros that are shipped with MVS) are included.

 

·         The sample installation JCL has been moved from the SMP/E JCLIN PDS to a separate PDS.

 

·         The PJS documentation is now shipped as a zip file that can be downloaded to a workstation and expanded.  The documentation is shipped in Microsoft Word, Adobe Acrobat PDF, and HTML files.

 

·         The PJS Request Queue Conversion Utility (PJSQCONV) has been removed.

 

 

C.2  Changes for PJS® Release 2.1.3

 

Functional Changes ‑

 

·         The default century for 2-digit years is changed from 19xx to 20xx.

 

 

Installation Changes ‑

 

·         PJS Documentation is now included on the installation tape in PDF (Adobe Acrobat Reader) format.

 

 

Additional PJS R2.1 PTF’s and APAR’sIncorporated ‑

 

PPJ0029 ‑ ISPF Help for Delete Job Request panel (PJSPJDEL) gives “Panel not found” dialog error.

 

PPJ0030 ‑ PJS Security Exit (PJSSECX) not called from PJSTASK for “Begin System Task” and “End System Task”.

 

PPJ0031 ‑ Documentation for sample PJS Installation Security Exits (PJSSECX) is incorrect.

 

OPJ0034 ‑ List Events for Owner does not list Events when the corresponding Owner record does not exist.

 

PPJ0035 ‑ Scope of enqueue on PJS Request Queue changed from SYSTEM to SYSTEMS.

 

PPJ0036 ‑ Scope of dequeue on PJS Request Queue changed from SYSTEM to SYSTEMS.

 

 

C.3  Changes for PJS® Release 2.1

 

Functional Changes ‑

 

·         PJS can process dates in the dd/mm/yyyy format (commonly used in Europe), in addition to the mm/dd/yyyy format (commonly used in the U.S.).  The format used is controlled by the new DATEFMT parameter of the PJSOPT macro.

 

·         PJS ISPF commands may be abbreviated to 2 characters.

 

·         A PJS Tutorial Index is provided.

 

·         The name of the Batch Event Post Utility is changed from ‘PJSEVENT’ to ‘PJSPOST’.  The old name, ‘PJSEVENT’, is still supported as an alias of ‘PJSPOST’.

 

·         A new Batch Event Reset Utility (PJSRESET) is available. This utility complements the Batch Event Post Utility (PJSPOST).

 

·         The Batch Event Post Utility (PJSPOST) and the Batch Event Reset Utility (PJSRESET) are described in the PJS ISPF Tutorial.

 

 

Installation Changes ‑

 

·         A User Contributed Routines library is provided on file 11 of the installation tape.  These routines are provided by PJS users and distributed on an ‘as‑is’ basis.  They are not supported by NNS Information Services, nor have they been tested by NNS.  Use of these routines is at the customers own risk.

 

·         The installation options are checked for validity at program initialization time.  In addition, the PJS System Task will display the current option values.

 

·         The default for the TSOAUTH parameter of the PJSOPT macro is changed from ‘NO’ to ‘YES’.  ‘NO’ is rarely needed, while ‘YES’ is frequently required.

 

·         The PJS Request Queue Maintenance Utility (PJSQMNT) will treat a zero value for the CMPTIME, DISTIME, or ERRTIME options as indicating ‘no limit’.

 

·         A sample PJS Options Exit (PJSOPTX1) is provided that will allow an installation to run multiple copies of PJS on a single system.
(PJS 2.0 PTF PPJ0017)

 

·         The internal formats of the PJS Options Table (PJSOPT) and the PJS Vector Table (PJSVT) have changed.  The PJS Options Table and any user exits must be reassembled.

 

 

Problems Fixed ‑

 

·         When the PJS System Task attempted to submit a job, and the JCL data set was in use by another task, the job request was failed with message PJS401E, and the job request was placed in the ‘ERROR’ status.

The PJS System Task is changed to requeue the job request and retry the submission at a later time.  The maximum number of attempts and the interval between each attempt is controlled by the new RETRY parameter of the PJSOPT macro.

 

·         When the PJS System Task attempted to submit a job, and no internal readers were available, the job request was failed with message PJS401E, and the job request was placed in the ‘ERROR’ status.

The PJS System Task is changed to wait until an internal reader is available. These is no limit to how long PJS will wait.

 

·         After the PJS TSO commands (including those used by the PJS ISPF interface) terminated, the PJS Request Queue data set remained allocated.

The PJS Request Queue data set is automatically deallocated when the TSO commands terminate.  The PJS System Task will continue to leave the PJS Request Queue data set allocated.

 

·         When the PJS Queue Maintenance Utility (PJSQMNT) was run, and the PJS JCL Spool was not used by the installation, message PJS401E and abend 2103 resulted.

PJSQMNT determines if the PJS JCL Spool is in use by testing PJSVT_JCLSDSN for nulls, but the PJSOPT macro sets the PJS JCL Spool Data Set Name to spaces.  PJSQMNT is changed to check the PJSVT_OPT_JSAVES bit of PJSVT_OPT_FLAGS (set by the JCLSAVE option), instead of PJSVT_JCLSDSN to determine if the JCL Spool data set is in use.
(Supercedes PJS 2.0 PTF PPJ0023)

 

·         The PJS System Task did not correctly check the Ready Request Table Entry against the current system time to determine if a request was ready to be submitted.  Also, after a job request was successfully processed, its Ready Request Table Entry was not updated.  The result was that every minute PJSTASKJ was called to process each job request in the Ready Request Table.  Although PJSTASKJ performed its own check, the result was a great deal of unnecessary activity against the PJS Request Queue.

The PJS System Task is fixed to correctly check the Ready Request Table Entry againes the current system time.  Also, PJSTASKJ is fixed to update the Ready Request Table Entry to reflect the new submit date (if any) of the job request.

 

·         The use of attributes in the PJS ISPF panels was not always consistant.  Also, for some panels, the use of the ‘skip’ attribute after some input fields is desireable.

The use of attributes in the PJS ISPF panels has been standardized.  Input fields with no existing value will be filled with underscores (‘_’).  The attribute terminating most input fields will have the ‘noskip’ attribute.  Some selection fields will have ‘skip’, where this facilitates data entry.

 

·         When the PJS Tutorial was entered using the ‘T’ option on the PJS Main Menu panel, at the end of the tutorial, the IBM ISPF tutorial was entered, instead of returning to the PJS Tutorial main panel.

The PJS ISPF Interface is changed to correctly set the ISPF Tutorial control variables ZHTOP and ZHINDEX in the shared variable pool.

 

 

Additional PJS R2.0 PTF’s Incorporated ‑

 

PPJ0018 ‑ Message PJS749I incorrectly displayed by PJS Queue Maintenance Utility (PJSQMNT).

 

PPJ0020 ‑ ISPF List panels do not display national characters ($, #, or @) in dynamic area.

 

PPJ0021 ‑ ISPF Copy Calendar function does not set the new Calendar‑ID.

 

PPJ0022 ‑ ISPF List panels are being formatted with nulls (X’00’) imbedded in the lines.

 

PPJ0024 ‑ Message PJS234E issued by PJS System Task with sample security exit PJSSECX or PJSSECX2.

 

PPJ0025 ‑ Abend U2706 issued by PJS TSO commands PJREQADD and PJREQMOD.

 

PPJ0026 ‑ Invalid years displayed by PJS ISPF calendar dialogs.

 

PPJ0027 ‑ Message PJS254E issued by PJS TSO command PJEVRSET.

 

PPJ0028 ‑ System console messages have the wrong route and descriptor codes.