Oce PRISMAproduction User manual

Océ
PRISMAproduction
ROUTER V1.0
Reference Guide

...and Training?
Our training centers hold seminars
on the printing system described in
this manual. We can also conduct
operator workshops on your premises
or in various locations on request.
Information:
Phone [phone]
Océ Printing Systems USA, Inc.
5600 Broken Sound Blvd
Boca Raton, FL 33487
January 2002 Edition
Copyright Océ Printing Systems GmbH 2000, 2002
All rights reserved, including rights of translation, reprinting,
reproduction by coying or any other method.
Offenders will be liable for damages. All rights, including rights created
by patent grant or registration of a utility model or design, are reserved.
Delivery subject to availability; right of technical modifications reserved.

Preface
U20944-J-Z247-6-7600
Preface
This document explains how to install, maintain, and report problems in PRISMAproduction-ROUTER
for all supported MVS & VSE based operating systems. In general these functions can be performed
without any detailed knowledge of SPS or its parameters. The intended audience for this document is
anyone responsible for these functions in an installation.
Version 1.0 of PP-ROUTER includes support for the SPS base product (spool interface) and the PP-
ROUTER print distribution driver.
Use this manual to install PP-ROUTER version 1.0, and all subsequent releases, until the manual is
superseded.

Summary of Amendments
U20944-J-Z247-6-7600
Summary of Amendments
Summary of Amendments
PP/ROUTER Version 1.0

Contents
U20944-J-Z247-6-7600
Contents
1 SPS and PP/ROUTER Overview................................................................................... 9
OS/390 (MVS)..................................................................................................................... 9
FSI Interface ...................................................................................................................9
Operating System Requirements ............................................................................... 10
VSE ................................................................................................................................... 10
POWER DDS Interface................................................................................................. 10
Operating System Requirements ............................................................................... 11
ROUTER Support Summary........................................................................................... 11
User Input ..................................................................................................................... 11
Installation Specifications .......................................................................................... 12
Reliability, Availability, Serviceability (RAS)............................................................. 12
2 SPS/LI Installation and Customization OS/390 (MVS) ................................................ 14
Installation Overview ...................................................................................................... 14
Model Jobs ................................................................................................................... 15
Basic Machine Readable Material .............................................................................. 16
CREATE the SMP environment .................................................................................. 17
RECEIVE the Product .................................................................................................. 18
Allocate the SPS/MVS Install Data Sets..................................................................... 18
Adjust JCLIN for LPALIB Installation (OPTIONAL) .................................................. 20
Adjust JCLIN for LINKLST Installation (OPTIONAL) ................................................ 21
APPLY the Product ...................................................................................................... 22
Authorize SPS Libraries in the System ..................................................................... 23
Establish SPS Program Properties ............................................................................ 24
Specify LSQA dumping for SPS................................................................................. 25
Define the SPS Printers to JES .................................................................................. 26
Install the SPS Start-up Procedure ............................................................................ 27
Allocate the SPS Execution Libraries........................................................................ 28
Create the SPS Parameter Library Members ............................................................ 29
Define SPS Start-up Procedures and Data Sets to RACF ....................................... 30
ACCEPT the Product ................................................................................................... 30
3 PP/ROUTER Installation and Customization OS/390 (MVS) ...................................... 32
Installation Overview ................................................................................................... 32
Basic Machine Readable Material .............................................................................. 33

Contents
U20944-J-Z247-6-7600
CREATE the SMP environment ...................................................................................33
RECEIVE the Product ...................................................................................................34
PP/ROUTER Install Data Sets ......................................................................................34
APPLY the Product .......................................................................................................34
Define the PP/ROUTER Printers to JES .....................................................................36
Install the PP/ROUTER Start-up Procedure ...............................................................39
Virtual and Real Storage Considerations...................................................................39
SPS Execution Data Sets .............................................................................................40
DDnames .......................................................................................................................40
Create the PP/ROUTER Parameter Library Members ..................................................42
Control Statement Format and Parameter Syntax for files SPSPRINT / SETUPxxx /
MSGSUxxx / LSCOxxxx................................................................................................43
SPSPRINT / SETUPxxx supported parameters..........................................................44
MSGSUxxx member parameters .................................................................................45
Create the PP/ROUTER Router control table.............................................................45
Install the PP/ROUTER License Key...........................................................................48
Test the PP/ROUTER Installation ...................................................................................49
ACCEPT the Product OS/390 (MVS)...............................................................................49
4 SPS/LI Installation and Customization VSE .................................................................51
Installation Overview ....................................................................................................51
Basic Machine Readable Material ...............................................................................51
Restore Sublibrary from Tape .....................................................................................52
Define JECL Parms in AUTOSTART ...........................................................................54
SPS Reentrant Phases .................................................................................................55
5 PP/ROUTER Installation and Customization VSE .......................................................55
Installation Overview .......................................................................................................55
Basic Machine Readable Material ...............................................................................57
Install product from Tape.............................................................................................57
PP/ROUTER printer definitions in VSE and VM.........................................................58
POWER JECL defines in AUTOSTART.......................................................................58
Define the PP/ROUTER TCPIP target servers............................................................59
Install the PP/ROUTER Start-up Job...........................................................................59
Create the PP/ROUTER Parameter Library Members ..................................................62
Control Statement Format and Parameter Syntax for files SPSPRINT / SETUPxxx /
MSGSUxxx / LSCOxxxx................................................................................................62
SPSPRINT / SETUPxxx supported parameters..........................................................63
MSGSUxxx member parameters .................................................................................65
Create the PP/ROUTER Router control table.............................................................65
Install the PP/ROUTER License Key...........................................................................68
Test the PP/ROUTER Installation ...................................................................................69
SPS/MVS related topics...................................................................................................72
Trace..................................................................................................................................72

Contents
U20944-J-Z247-6-7600
6 REXX requirements ..................................................................................................... 73
OS/390 (MVS)................................................................................................................... 74
IRXFLOC ....................................................................................................................... 74
IRXPARMS .................................................................................................................... 76
VSE ................................................................................................................................... 76
ARXFLOC...................................................................................................................... 76
ARXPARMS .................................................................................................................. 78
7 OPERATION................................................................................................................ 79
OS/390 (MVS)................................................................................................................... 79
MVS Commands........................................................................................................... 79
JES Commands............................................................................................................ 79
FSS Commands ........................................................................................................... 80
Printer Commands....................................................................................................... 80
VSE ................................................................................................................................... 83
VSE Commands ........................................................................................................... 83
DDS Commands........................................................................................................... 84
8 JCL parameters ........................................................................................................... 87
OS/390 (MVS)................................................................................................................... 87
VSE Extended Output Features..................................................................................... 89
Extended JECL Keywords .......................................................................................... 89
9 Print Parameter Exit..................................................................................................... 97
OS/390 (MVS)................................................................................................................... 97
VSE ................................................................................................................................... 98
10 Maintenance ................................................................................................................ 99
Temporary Fixes ............................................................................................................. 99
11 Performance Considerations ..................................................................................... 101
Memory ..........................................................................................................................101
PP/ROUTER Storage Estimates ............................................................................... 101
Libraries ......................................................................................................................... 102
Trace Files .....................................................................................................................102
12 Diagnosis ................................................................................................................... 103
Error Reporting ............................................................................................................. 103
Associated Documentation.......................................................................................... 103
When to Dump............................................................................................................... 104
When to Trace ............................................................................................................... 104
Trace Generation .......................................................................................................... 104
ITF Trace Tape Generation........................................................................................... 105

Contents
U20944-J-Z247-6-7600
13 Messages and Codes ................................................................................................ 107
Conventions .................................................................................................................. 107
PP/ROUTER Messages................................................................................................. 109
SPS Messages............................................................................................................... 121
OS/390 (MVS).............................................................................................................. 121
VSE 121
SPS Abend Codes......................................................................................................... 121
Appendix A OS/390 REXX Alternate Library Installation................................................ 122
Appendix B Problem Documentation.............................................................................. 129
List of Tables................................................................................................................... 131
Bibliography ....................................................................................................................133
Index ............................................................................................................................... 135

Installation and Customization
U20944-J-Z247-6-7600
1 SPS and PP/ROUTER Overview
SPS accepts spool print data streams and passes them to the ROUTER client for
distribution via TCPIP to socket serving spool systems such as PRISMAproduction-APA.
There is no conversion performed on the data. The target server destination is based on
ROUTER routing table parameters which are selected based on the SPOOL dataset
charactersistcs of CLASS, DEST and FORMS.
SPS uses only standard documented interfaces. No modifications are introduced in the
operating system environments. SPS uses the Functional Subsystem Interface (FSI) to
communicate with the Job Entry subsystem (JES) installed in the host MVS system SPS
uses the Device Driving System (DDS) interface to communicate with the spooling
application (POWER) in the host VSE system.
PP/ROUTER is a REXX/370 application that adheres to the SAA standards and therefore
uses only standard interfaces within the operating system.
OS/390 (MVS)
FSI Interface
The FSI is an IBM supported customer interface permitting an address space to
communicate with the spooling and operator facilities of the installed JES. The FSI
supports such functions as connecting and disconnecting Functional Subsystems (FSS‘s)
and Functional Subsystem Applications (FSA's) to JES (establishing and terminating
communication), opening and closing spool output files, reading spool records, receiving
operator or JES initiated orders, receiving posts from JES, and sending responses to JES.
SPS is defined to JES in the JES initialization parameters at installation time as one or
more FSS's, each with one or more FSA's, which are printer drivers. These FSA's run as
subtasks of the FSS they are associated with. One FSS and its active FSA's reside in one
address space.
When the operator issues a start printer to any SPS controlled device, if the FSS for this
printer has not been started, an address space is created and the FSS is loaded into the
address space and initialized. This is followed by an FSA driver being associated with the

Installation and Customization
U20944-J-Z247-6-7600
printer and attached as a subtask. If the FSS for the printer already exists in an address
space, just the FSA subtask attach takes place. The FSA subtask initializes and loads the
appropriate printer driver, and then requests a spool file from JES. Spool files are
processed until the printer is drained, at which time the FSA controlling the printer is
detached. Other FSA's driving different printers continue to process. When the printer is
again started by the operator a new copy of the FSA is attached and initialized, and the
process continues as before.
On process completion a spool file is returned to the JES system, which either deletes or
keeps the spool file depending on the initial spool file disposition. If an error occurs during
the processing of a spool file the spool file is returned to JES with a request to save it on
the spool. All operator printer requests are processed by SPS. A cancelled file will be
purged.
Operating System Requirements
SPS Version 3.8 will run without restrictions on MVS systems at the release levels listed
below. Any specifically required PTF's are documented by the ++IF REQ statements of
the supplied installation deck.
OS/390 Version 2 Release 7.0, or higher (Program Number 5647–A01)
TCP/IP
TSO/E Version 2 Release 4, or higher with REXX feature
Oce SPS/MVS V3.8 Ptf SY09021
VSE
POWER DDS Interface
SPS uses the Device-driving System (DDS) to communicate with VSE/POWER under
VSE. The DDS is an IBM supported customer interface permitting a partition to
communicate with the spooling and operator facilities of VSE/POWER. The DDS supports

Installation and Customization
U20944-J-Z247-6-7600
such functions as establishing and terminating communication, opening and closing spool
output files, reading spool records, receiving orders and sending responses.
SPS must be started manually in a partition on its own. When the operator issues a start
device command to any SPS controlled device, SPS will start this device for processing
spooled output. The Device-driving system initializes and loads the printer driver and then
requests a spool file from POWER. Spool files are processed until the printer is stopped.
On process completion a spool file is returned to POWER, which either deletes or keeps
the spool file depending on the initial spool file disposition. If an error occurs during the
processing of a spool file, the spool file is returned to POWER with a request to save it on
the spool. All operator printer requests are processed by SPS. A cancelled file will be
purged.
Operating System Requirements
VSE/ESA Versions 5 and higher
TCPIP V1.4
VSE/REXX
Oce SPS/VSE V3.4.1 Ptf SD30007
ROUTER Support Summary
PRISMAproduction(SPS) processing support for ROUTER, TCPIP connected printer
clients can be divided into three major categories: user input, installation specifications,
and RAS facilities. The main elements of these functions are listed in the following
sections.
User Input
Input Data Stream Processing: This processing accepts from the spooling system any
user generated data stream that is supported by the Spooling system. These data
streams may include line data, composed text data etc..

Installation and Customization
U20944-J-Z247-6-7600
Job Control Language (JCL): See PRISMAproduction/ROUTER Administration Guide
for a detailed clarification of the parameters supported.
Message Generation: SPS generates operator and user related messages concerning
all phases of data stream processing. User messages are printed at the end of the user
output or may be spinned off to a spool file.
Checkpointing: Processing checkpoints may be requested by the user, or installation, on
a time basis. This facility permits the restart of a data stream interrupted by transmission
errors.
Installation Specifications
System parameters: SPS supports a variety of initialization parameters and processing
defaults.
Accounting:
MVS: SPS generates the standard SMF type 6 accounting record compatible to other
ROUTER/DOWNLOAD systems, for all input data streams processed. If MVS is not able
to write an SMF record, SPS informs the operator, allowing retry or ignore actions. Even
when SPS abends or the MVS system crashes, SPS writes SMF records for the printing
files (either at clean-up or at re-selection time) assuring a 100% reliable accounting
system for the printing jobs.
VSE: No accounting support.
User exits: The following exit points are defined:
Print Parameter Exit; PSF exit 15
This exit inserts records to be appended to the Header string, -opa section, that is
transmitted to the server. Each printer may have its own unique exit.
Reliability, Availability, Serviceability (RAS)
Dumping: Diagnostic dumps are automatically taken in the event of program or
unexplained errors. For direct printing applications, SPS must be RACF authorized in
order to be able to write SYSUDUMPs.
Tracing: An SPS trace facility is defined which permits the collection of information on all
phases of SPS processing. The level of detail of the trace information collected may be
selected by the installation and varies from flow trace to all control blocks, input and
output data.
Error recovery: In error situations print datasets are returned to the spool, following an
attempt to recover the situation based on retry counts and intervals that have been
defined in the ROUTER control table, in a hold status therefore allowing the

Installation and Customization
U20944-J-Z247-6-7600
retransmission of the dataset following correction of the network error that has caused the
problem. If checkpointing was active then a restart of the dataset will be attempted from
the checkpoint restart point, if the restart from the checkpoint fails then the print will be
restarted from the beggining.

Installation and Customization
U20944-J-Z247-6-7600
2 SPS/LI Installation and Customization OS/390
(MVS)
Installation Overview
The following tasks must be performed to install SPS:
1. Create the SMP environment
2. Receive SPS base and features
3. Allocate the DLIB's and target libraries
4. Adjust JCLIN for LPALIB installation (optional)
5. Adjust JCLIN for LINKLST installation (optional)
6. Apply SPS
7. Authorize SPS libraries in the system
8. Establish SPS program Properties
9. Exclude SPS printers from SMS processing
10. Specify LSQA dumping for SPS
11. Set RACF authorization for SYSUDUMP processing
12. Define the SPS printers to JES
13. Install the start-up procedure(s)
14. Allocate the execution libraries
15. Create the SPS parameter library members
16. Copy installed message suppression routine to SPSPARM lib
17. Define SPS Start-up Procedures and Data Sets to RACF
18. Test the SPS installation
19. Accept SPS

Installation and Customization
U20944-J-Z247-6-7600
Model Jobs
SPS is distributed with model jobs and examples for all installation functions. The version,
release and modification levels (vrm) in the fmids referenced in these jobs will need to be
updated with the version, release and modification levels in the SPS release letter. After
installation, you can find the examples in SPS.SPSSAMP. The examples are in
SPSvrm0.F3 on the distribution tape. After performing the receive, you can access the
examples under ISPF in the SPS.SPSvrm0.F3 data set, where vis the version, ris the
release, and mis the modification level of the distribution tape. The member names are
the same in this data set as they are when moved to the target library. They can be used
from SPS.SPSvrm0.F3 for installation purposes and their member names will be
mentioned throughout this document whenever models or examples are available.
The library model members for parameters have names ending in XXX for APA printers,
YYY for LIP printers, and ZZZ for MOD2 printers. Throughout this document the member
names in the text ending in xxx are examples of APA printer parameter requirements,
members ending in yyy are LIP parameter requirements, members ending in zzz are
MOD2 parameter requirements and members ending in nnn indicate the statement
applies to APA, LIP and MOD2 parameter requirements.
Sample member names for special forms processing end in FFFF, GGGG, and HHHH for
APA, LIP and MOD2 forms respectively. Throughout this document the form member
names in the text ending in ffff refer to APA forms, form member names ending in gggg
refer to LIP forms, form member names ending in hhhh refer to MOD2 forms and form
member names ending in aaaa indicate that the statement applies to APA, LIP and MOD2
forms.

Installation and Customization
U20944-J-Z247-6-7600
Basic Machine Readable Material
SPS is shipped as 2 FMIDs, a base product and one printer driver feature. The
distribution media for SPS is one standard label tape for the base FMID and one
additional tape for each printer driver feature ordered. The tapes have standard labels
with volume serials PSvrm0 and PSvrm8, where the volume serials are the right 6
characters of the current FMID's of the product, with v, r, and m being the version,
release, and modification levels provided in the release letter.
The tapes are formatted as SMP compatible relative file tapes. SPS is packaged as
functional sysmods and should be installed in the operating system using SMPE. The 5
tape files delivered on the SPS base product installation tape can be found in Table 1 on
page 16. The tape file format for the PP-ROUTER driver feature and be found in the
relevant MVS or VSE install sections.
FILE NAME DSORG BLKSIZE DESCRIPTION
1 SMPMCS PS 80 SMPPTFIN
2 SPSvrm0.F1 PO 3120 JCLIN
3 SPSvrm0.F2 PO 6144 Module Library
4 SPSvrm0.F3 PO 3120 Sample Library
5 SPSvrm0.F4 PO 5020 Message Library
Table 1: Distribution Tape Files for SPS Base Product

Installation and Customization
U20944-J-Z247-6-7600
CREATE the SMP environment
To install SPS, you may use an SMP environment that already exists, (CSI and other
SMP data-sets, zones, etc...) or you may create a complete new SMP environment
(inclusive CSI). The sample job SPSISSMP creates a complete SMP environment for all
SPS FMIDs. You may run the whole job or just the steps you are interested in. Some
installation related updates should be done in this job as specified in the job itself.
You should use the IEBCOPY job listed below (SPSJ00 sample) in order to load job
SPSISSMP from the SPS base product tape (volume serial PSvrm01). This IEBCOPY
also loads the members SMPPROC (a sample SMP/E procedure which may be
customized by the installation) and SPSISRE0 (sample SMP/E receive job). After the
receive is done, all other samples may be found in the SAMPLE library relfile loaded.
//SPSJ00 JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1)
//SPSJ00C EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//PSvrm0 DD DSN=SPSvrm0.F3,UNIT=tape,LABEL=(4,SL),DISP=SHR,
// VOL=SER=PSvrm0
//USERLIB DD DSN=USER.USERLIB,DISP=SHR
//SYSIN DD *
COPY O=USERLIB,I=PSvrm0
S M=(SPSISSMP,SPSISRE0,SMPPROC)
/*
Figure 1: Sample job to load SPSISSMP from tape (SPSJ00)
The following table shows the disk space used by the SMP files allocated by job
SPSISSMP, assuming you use a 3380 disk.
DATA SET RECFM LRECL BLKSIZE CYLS DIR
CSI.DATA KSDS 143 4096 8,1 -
CSI.INDEX KSDS - - 1,1 -
SMPLOG VB 260 3200 3 -
SMPLOGA VB 260 3200 3 -
SMPPTS FB 80 23440 30,5 46
SMPMTS FB 80 23440 1,1 46
SMPSTS FB 80 23440 1,1 46
SMPSCDS FB 80 23440 1,1 46
Table 2: SMP Data Set Allocations (job SPSISSMP)
1Where vis the version, ris the release, and mis the modification level of the delivered
version.

Installation and Customization
U20944-J-Z247-6-7600
RECEIVE the Product
Perform a standard receive of SPS, which is shipped as functional sysmods. The model
job in Figure 14 can be modified to suit installation requirements and used to receive the
product. To receive the printer driver features, the fmid SPSvrm0 and volser PSvrm0 in
the model should be changed to the corresponding values for the driver(s) ordered.
//RECEIVE JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1)
//RECEIVE EXEC SMPPROC
//SMP.SMPPTFIN DD DSN=SMPMCS,DISP=(OLD,PASS),
// VOL=SER=PSvrm0,LABEL=(1,SL),
// UNIT=(tape,,DEFER)
//SMP.SYSIN DD * (SMPCNTL)
SET BDY(GLOBAL) .
RECEIVE S(SPSvrm0) SYSMOD .
/*
Figure 2: Sample SMP Receive Job (SPSISRE0)
Allocate the SPS/MVS Install Data Sets
SPS OD2 requires 3 DLIB data sets and 3 target libraries. These libraries have been
named for distribution purposes as shown in Table 10. The names of the data sets are
arbitrary, as all references to libraries by SPS and SMP are by ddname. The systems
programmer may choose any names convenient to the installation. However, throughout
this document all references to these data sets will be by the names used in the table.
DATA SET SMP DDNAME FUNCTION
SPS.ASPSDLIB ASPSDLIB DLIB module library
SPS.ASPSSAMP ASPSSAMP DLIB sample library
SPS.ASPSMESS ASPSMESS DLIB message library
SPS.SPSLINK SPSLINK Target load library
SPS.SPSSAMP SPSSAMP Target sample library
SPS.SPSMESS SPSMESS Target message library
Table 3: SPS Libraries
Table 4 on page 19 documents the space and record format requirements of SPS. If disk
space is to be minimized, then large secondary allocations should be used. All block sizes
may be increased if desired.
The SPS install data sets may be allocated and catalogued with the model job
SPSIALOC. This job contains the suggested space allocations and record formats. The
DLIB and target library volumes must be set to the installation requirements. The data set
prefix may also be changed.

Installation and Customization
U20944-J-Z247-6-7600
The SPS install data sets should be protected by whatever security product the installation
uses.
DDDEF's should be defined for each of the ddnames in Table 5 on page 20. The
suggested attributes will simplify maintenance procedures. If you have run the sample job
SPSISSMP, these DDDEF's are already defined.
DATA SET RECFM LRECL BLKSIZE BLOCKS DIR
SPS.ASPSDLIB U - 6144 900,100 42
SPS.ASPSSAMP FB 80 3120 1200,120 40
SPS.ASPSMESS VB 251 5020 50,10 5
SPS.SPSLINK U - 6144 1800,200 16
SPS.SPSSAMP FB 80 3120 1200,120 40
SPS.SPSMESS VB 251 5020 50,10 5
Table 4: SPS Data Set Allocations

Installation and Customization
U20944-J-Z247-6-7600
DDDEF ZONE DATA SET INITIAL FINAL WAITFORDSN
ASPSDLIB DLIB SPS.ASPSDLIB OLD KEEP YES
ASPSSAMP DLIB SPS.ASPSSAMP OLD KEEP YES
ASPSMESS DLIB SPS.ASPSMESS OLD KEEP YES
SPSLINK TARGET SPS.SPSLINK SHR KEEP YES
SPSSAMP TARGET SPS.SPSSAMP SHR KEEP YES
SPSMESS TARGET SPS.SPSMESS SHR KEEP YES
Table 5: SPS DDDEF Allocations
Adjust JCLIN for LPALIB Installation (OPTIONAL)
This step is only necessary if you want to install the re-entrant parts of SPS in the
LPA/ELPA instead of in SPS.SPSLINK. To determine whether it is useful to install SPS in
the installation LPA/ELPA, please read "Virtual and Real Storage Considerations" on page
71 and "Memory" on page Error! Bookmark not defined.. This function can also be
performed with UCLIN if the installation prefers.
Duplicate the JCLIN for the link-edits of base product modules SPSMFSS, SPSMLI (alias
SPSMFSSM), SPSMDOPN, IGG019WM and IGG019WS (these 2 last modules may have
another, user specified name. Please see section 0 on page 55). Duplicate the JCLIN as
needed for link-edits of LINE modules SPSPLINE, SPSPLIP and SPSPEPM, or APA
module SPSPAPA2. The modules SPSMPDEF, SPSMGDA and all the header, separator,
message, and trailer page load modules cannot be moved to LPALIB as they are actually
non-reentrant data areas. The direct printing modules SPSMDCAU, SPSMDLCN,
SPSMDLOP and SPSMDSSI should not be installed in LPALIB. They will only waste LPA
space when installed in LPALIB.
The JCLIN may be found in the respective SPS.fmid.F1 library and may be altered using
the ISPF editor. Change the copies from the distribution coded library name
SPS.SPSLINK to SYS1.LPALIB. Any library that is used in the building of LPA during
initialization may be selected instead of SYS1.LPALIB. The list of libraries in the
installation that are used to build LPA can be found in LPALST00 of SYS1.PARMLIB.
Additionally an installation may use libraries in LPALSTxx members that are selected by
the LPA parameter in IEASYS00.
The duplication of the link-edits is recommended so that the entire SPS product is in one
library that can be used as a steplib. This is useful for testing and after maintenance is
applied. When LPALIB is used for the re-entrant SPS modules and the modules are also
in SPSLINK, SPSLINK must be in linklst. If SPSLINK is used as a steplib, the LPA copies
will be ignored.