                           PJS(r) 2.1.4  Readme



                         PJS 2.1.4 Installation



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.



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
    EXPAND     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.



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

After expanding 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.  For more information about the GNU GPL see
the Free Software Foundation website at
http://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.



Task 4:  Extract the PJS Installation Files

The EXTRACT member of the PJS Installation Package PDS contains a
sample job to expand 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



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.



Continuing the Installation

From this point you should follow the instructions in Chapter 2 of the PJS Installation Guide.



                      PJS 2.1.4 Summary of Changes


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.


Changes for PJS(r) 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.


                        Comments and Suggestions


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


                        PJS Documenation License


Copyright (c) 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 no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
copy of the license is included in the file $LICPUB.


                               Trademarks


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.
