prismaproduction router...

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 561-997-3100 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



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


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


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


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


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.


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


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 v is the version, r is the release, and m is 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.


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


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)

1 Where v is the version, r is the release, and m is the modification level of the delivered

version.


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.


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


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.


U20944-J-Z247-6-7600

If you change the SPS JCLIN at installation time, you must also change any JCLIN update received in future PTFs.

Adjust JCLIN for LINKLST Installation (OPTIONAL)

You need to do this step if you will use SPS in direct printing mode and the SPSLINK is in the lnklst concatenation. You may also do this step just to put all direct printing modules in the SPSLINK, even if you do not use direct printing mode. When an installation is installing SPS as part of the linklst concatenation, the direct printing modules that are normally directed to LINKLIB by the supplied JCLIN can be linked into SPS.SPSLINK. This will keep the SPS load modules in one library, which can facilitate testing of new releases of SPS. To install the direct printing modules in SPS.SPSLINK, change the target library on the JCLIN link step for SPSMDCAU, SPSMDLCN, SPSMDLOP and SPSMDSSI to SPS.SPSLINK from SYS1.LINKLIB.

If you change the SPS JCLIN at installation time, you must also change any JCLIN update received in future PTFs.


U20944-J-Z247-6-7600

APPLY the Product

Perform a standard apply check for functional sysmods and then apply SPS. The model job in Figure 14 can be modified to suit installation requirements and used to apply the SPS base product and any requested drivers. Model apply jobs tailored to the ordered fmid are shipped with each fmid in their SPS.fmid.F3 libraries in member names SPSISAP0, SPSISAP1 and SPSISAP2 respectively. The model jobs are supplied with commented out DD cards for SVCLIB and LINKLIB, where appropriate. For SMPE processing, if the installation does not have DDDEF's defined for these data sets, these cards should be updated to suit installation requirements.

Warning message GIM44402W issued for SPSIX23, SPSIXMSG, SPSIX45, SPSMDSFC, SPSMDS10, SPSMRE10 and SPSMRR10 can be ignored.

//APPLY JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //APPLY EXEC SMPPROC //SMP.SYSIN DD * (SMPCNTL) //*SMP.SVCLIB DD DSN=SYS1.SVCLIB,UNIT=XXXX,DISP=SHR, //* VOL=SER=NNNNNN //*SMP.LINKLIB DD DSN=SYS1.LINKLIB,UNIT=XXXX,DISP=SHR, //* VOL=SER=NNNNNN SET BDY(SPSvrmT) . APPLY CHECK S(SPSvrm0) . /*

Figure 3: Sample SMP Apply Job (SPSISAP0)

SPS base has two appendage routines that are placed in SVCLIB: startio and abnormal end. As distributed, these appendages are named IGG019WS and IGG019WM respectively. If either of these appendage names has been used in the installation, an alternate name may be chosen by changing the last two characters of the name and updating the JCLIN link-edit of this module to the new name. The JCLIN can be found in SPS.SPSvrm0.F12 after receiving the product. An example of changing the appendage name IGG019WM to IGG019ZZ is shown in Figure 4. The use of this new name should be indicated in the SIOAPG or ABENDAPG parameter of the setup member for each printer when the SPS parameters are filled out.

Please see SIOAPG or ABENDAPG parameter in the SPS/MVS-APA, SPS/MVS-LIP or the SPS/MVS-MOD2 Administrator's Guide for further information.

2 Where v is the version, r is the release, and m is the modification level of the delivered

version.


U20944-J-Z247-6-7600

//STEP5 EXEC PGM=IEWL,REGION=512K, // PARM='MAP,RENT,NCAL,LIST,LET,XREF,AC=0' //SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(4,1)) //SYSPRINT DD SYSOUT=A //SYSLMOD DD DSN=SYS1.SVCLIB,DISP=SHR //ASPSDLIB DD DSN=SYS1.ASPSDLIB,DISP=SHR //SYSLIN DD * INCLUDE ASPSDLIB(IGG019WM) ENTRY IGG019WM NAME IGG019ZZ(R)

Figure 4: Sample JCLIN Modification for Appendage Named ZZ

Authorize SPS Libraries in the System

The SPS target load library must be authorized. SPS can be run as an authorized steplib, as a member of LINKLST or loaded from LPA.

When run as an authorized steplib, the SPS load library name must be added to the IEAAPF00 member of SYS1.PARMLIB.

When run as a member of linklst, the SPS load library name must be added to linklst, and if the installation linklst is not authorized then it must also be added to IEAAPF00.

When loaded from the LPA, no special action is necessary as modules loaded from LPA are normally authorized. Model statements for these procedures can be found in members SPSIAPF and SPSILNK of SPS.SPSSAMP.


U20944-J-Z247-6-7600

Establish SPS Program Properties

SPS must be non-swappable and execute in program key 1. These properties are given to a program in the SCHED00 member of SYS1.PARMLIB.

SCHED00 update is simply coding the PPT statement (see Figure 5). A model statement can be found at the beginning of SPSIPPT in SPS.SPSSAMP.

PPT PGMNAME(SPSMFSS) /* PROGRAM NAME */ NOSWAP /* NON-SWAPPABLE */ KEY(1) /* PROTECTION KEY */ AFF(NONE) /* NO PROCESSOR AFFINITY */ NODSI /* NO DATA SET INTEGRITY */

Figure 5: Sample PPT statement for SCHED00 in SYS1.PARMLIB


U20944-J-Z247-6-7600

Specify LSQA dumping for SPS

SPS uses an internal trace table when TRACELEV(0) is specified. In this trace table are recorded events from the DIE exit, JES X-memory routines and direct printing open/close routines. For this reason, the trace table needs to be fixed in the LSQA. To have the trace table dumped in case of an abend, your dump options member in SYS1.PARMLIB (i.e. IEADMP00 for SYSUDUMP) should specify SDATA=(LSQA) or SDATA=(ALLSDATA).


U20944-J-Z247-6-7600

Define the SPS Printers to JES

Each SPS start-up procedure is one functional subsystem. The printers defined in the procedure are the printers that the functional subsystem controls. The SPS functional subsystems, and the printers they control, must be defined to the JES subsystem that the installation is using.

See ROUTER install section for the JES defintions required.


U20944-J-Z247-6-7600

Install the SPS Start-up Procedure

Start-up procedures to control the SPS driven printers must be defined and placed in the installation proclib.

See ROUTER install section for a clarification of the start-up procedure.


U20944-J-Z247-6-7600

Allocate the SPS Execution Libraries

The SPS execution data sets defined in the start-up procedures must be allocated. Table 6 shows the suggested data set allocation parameters. A sample allocation for the dump data set is shown in the event the installation prefers a dump data set to a file. It is suggested that the trace data set suffix jjjj be the number of the JES printer expanded to 4 digits (jjjj in SPSIEXDS sample) and the dump data set suffix ssss be the start-up procedure step name (see "Data Set Names" on page Error! Bookmark not defined.). When twin printers are installed, an external storage data set may be optionally used. It is suggested that the suffix for this data set be the number of the JES printer expanded to 4 digits (jjjj in SPSIEXDS sample). A model allocation job for the SPS execution data sets can be found in member SPSIEXDS of SPS.SPSSAMP. This job also copies the SPSPARM sample members from the SPSSAMP to the SPSPARM library. Please customize the iebcopy control statements in order to copy only the members needed for the printer types that you have (APA, LIP or MOD2).

DATA SET RECFM LRECL BLKSIZE BLOCKS DIR DISP SPS.SPSPARM FB 80 3120 100,50 15 SHR

SPS.SPS1jjjj VB 284 4096 3000,0 - SHR

SPS.SPS2jjjj VB 284 4096 3000,0 - SHR

SPS.DUMPssss VB 125 1632 660,330 - MOD

SPS.ESDjjjj F 8192 8192 3000,0 - OLD Table 6: SPS Execution Data Set Allocations


U20944-J-Z247-6-7600

Create the SPS Parameter Library Members

Each time a printer is started, SPS accesses several members of SPS.SPSPARM to determine the installation selected printer defaults and options. These members must be coded for each printer and moved to SPS.SPSPARM. This job is usually performed by the SPS administrator, because it requires a knowledge of SPS processing options and how the installation is planning on using the product.

The SPS parameter library members need not be coded before completing the installation of SPS. If the installer is also going to code these members, the SPS/MVS-APA, SPS/MVS-LIP or the SPS/MVS-MOD2 Administrator's Guide should be consulted for an overview of SPS processing and details on coding the parameters.

The delivered SPSPARM sample members are copied from the SPSSAMP to the SPSPARM when the installation job SPSIEXDS is executed. You may use these samples as a base for your SPSPARM member coding.


U20944-J-Z247-6-7600

Define SPS Start-up Procedures and Data Sets to RACF

If the installation has RACF or some other security product that controls access to the system and resources, the SPS start-up procedures and data sets will have to be defined to this product. This manual only discusses RACF requirements, for other security products please consult the product's documentation.

There are several approaches that an installation may have implemented to handle started tasks and system data sets under RACF. SPS has no special requirements or restrictions, so it may be defined to RACF using whatever scheme an installation has chosen. The important considerations are:

1. Each SPS start-up procedure must be defined as a started task, valid for execution in the system.

2. Each SPS data set or library must be protected against unauthorized change.

3. Each SPS started task must be authorized to use the SPS data sets defined in its start-up procedure.

4. Each SPS started task must be authorized to use any control data sets defined in its control key data set list member of SPS.SPSPARM.

5. Each control data set user must be authorized to update the assigned control data set.

For a full discussion of defining SPS to RACF please see "RACF Considerations" on page Error! Bookmark not defined..

ACCEPT the Product

A new release of SPS should be allowed to run for a reasonable period of time in production before doing an SMP accept. When the installation is confident that all print jobs supported by the previous release of SPS run without problems on the new release, SPS should be accepted.

//ACCEPT JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //ACCEPT EXEC SMPPROC //SMP.SYSIN DD * (SMPCNTL) SET BDY(SPSvrmD) . ACCEPT S(SPSvrm0) . /*

Figure 6: Sample SMP Accept Job (SPSISAC0)

The model job in Figure 17 can be modified to suit installation requirements and used to accept the SPS base product and any requested drivers.


U20944-J-Z247-6-7600

The fmids in the figure should be changed to the drivers ordered.3 If only one of the SPS drivers has been ordered, the accept card should be changed to include only the fmid's that are to be installed.

3 Where v is the version, r is the release and m is the modification level of the delivered version.


U20944-J-Z247-6-7600

3 PP/ROUTER Installation and Customization OS/390 (MVS)

Installation Overview

The following tasks must be performed to install PP/ROUTER:

1. Install REXX Alternate run-time library, IF REQUIRED (See Appendix A)

2. Receive PP/ROUTER feature

3. Apply PP/ROUTER

4. Exclude PP/ROUTER printers from SMS processing (see SPS/MVS Installation manual)

5. Define the PP/ROUTER TCPIP target servers

6. Define the PP/ROUTER printers to JES

7. Install/extend the start-up procedure(s)

8. Create the PP/ROUTER parameter library members, SPSPRINT/SETUPxxx/MSGSUxxx/LSCOxxxx

9. Create the PP/ROUTER router control table

10. Define SPS Start-up Procedures and Data Sets to RACF (see SPS/MVS Installation manual)

11. Install the PP/ROUTER License Key

12. Test the PP/ROUTER installation

13. Accept PP/ROUTER


U20944-J-Z247-6-7600


PP/ROUTER is shipped as 1 FMID. If you are ordering the ROUTER feature, as an additional printer driver to an already installed SPS a PTF tape for the SPS base components will also be delivered.

PRISMAproduction/ROUTER feature. PTF tape for SPS base component.

If you are a new customer to Océ the following tapes will be delivered.

SPS base product. PRISMAproduction/ROUTER feature. PTF tape for SPS base component.

The tapes have standard labels with volume serials PSvrm0, 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. All components are packaged as functional sysmods and should be installed in the operating system using SMPE.

FILE NAME DSORG BLKSIZE DESCRIPTION 1 SMPMCS PS 80 SMPPTFIN

2 PSvrm8.F1 PO 3120 JCLIN

3 PSvrm8.F2 PO 6144 Module Library

4 PSvrm8.F3 PO 3120 Sample Library

5 PSvrm8.F4 PO 5020 Message Library Table 7: Distribution Tape Files for PP/ROUTER Printer Driver

CREATE the SMP environment

To install PP/ROUTER feature, the SMP environment that already exists for the SPS base product is used (see SPS/MVS Installation Guide).


U20944-J-Z247-6-7600

RECEIVE the Product

Perform a standard receive of the PP/ROUTER feature, 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.

//RECEIVE JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //RECEIVE EXEC SMPPROC //SMP.SMPPTFIN DD DSN=SMPMCS,DISP=(OLD,PASS), // VOL=SER=PSvrm8,LABEL=(1,SL), // UNIT=(tape,,DEFER) //SMP.SYSIN DD * (SMPCNTL) SET BDY(GLOBAL) . RECEIVE S(SPSvrm8) SYSMOD . /*

Figure 7: Sample SMP Receive Job

PP/ROUTER Install Data Sets

PP/ROUTER uses the libraries that are already in use for the SPS base product. 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.ASPSMESS ASPSMESS DLIB message library

SPS.SPSLINK SPSLINK Target load library

SPS.SPSMESS SPSMESS Target message library Table 8: SPS Libraries

APPLY the Product

Perform a standard apply check for functional sysmods and then apply PP/ROUTER. The model job in Figure 14 can be modified to suit installation requirements.


U20944-J-Z247-6-7600

//APPLY JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //APPLY EXEC SMPPROC //SMP.SYSIN DD * (SMPCNTL) //*SMP.SVCLIB DD DSN=SYS1.SVCLIB,UNIT=XXXX,DISP=SHR, //* VOL=SER=NNNNNN //*SMP.LINKLIB DD DSN=SYS1.LINKLIB,UNIT=XXXX,DISP=SHR, //* VOL=SER=NNNNNN SET BDY(SPSvrmT) . APPLY CHECK S(SPSvrm8) . /*

Figure 8: Sample SMP Apply Job


U20944-J-Z247-6-7600

Define the PP/ROUTER Printers to JES

Each SPS start-up procedure is one functional subsystem. The printers defined in the procedure are the printers that the functional subsystem controls. The SPS functional subsystems, and the printers they control, must be defined to JES2.

Any combination of APA single, APA twin, LIP, MOD2, and ROUTER printers may be controlled by one functional subsystem. Each ROUTER printer is addressed by the functional subsystem as a single JES printer number. These printer definitions make it possible for the operator to control the printers separately.

In JES2, SPS ROUTER printers should be coded as remote printers (please see Figure 14 on page 55 for coding examples). No device number parameter should be coded. If a device number is included in the PRT(nnnn) or DEVICE statement, SPS does not complete its initialization phase.

Figure 9: Example JES2 Initialization Statements for PP/ROUTER client printers

A brief explanation of each parameter in the JES initialisation statements follows. For a detailed description of these parameters (see IBMs documentation relating to JES definitions).

PROC=procedure_name Procedure for starting this FSS.

(Required)

AUTOSTOP={YES | NO} Whether the FSS address space is stopped when all FSAs have been stopped.

(Optional, default is NO).

PRT(nnnn) This statement defines an FSA and has the following sub-parameters.

CKPTMODE={PAGE | SEC} whether checkpointing is based on PAGES or SECONDS.

(Optional, default is YES).

FSSDEF (PPROUTER) ........ PROC=PPROUTER

PRT(nnnn) MODE=FSS,FSS=PPROUTER,CKPTMODE=SEC,CKPTSEC=60,

PRMODE=(LINE,PAGE,SOSI1,SOSI2,SOSI3), SETUP=NOHALT,DRAIN,QUEUE=4,UCS=0,TRKCELL=YES, PRESELECT=YES,WS=(Q/F)


U20944-J-Z247-6-7600

CKPTSEC={nnnnn | 0} elapsed time between checkpoints.

{CLASS | QUEUE}=(classes) Output classes that will be selected by this FSA.

FCB=pagedef_name 1-4 character name of a pagedef.

FORMS=(form_names) 1-8 character form name, up to 8 form names can be specified.

(Optional, no default).

FSS=fss_name

Gives the name of the FSS that controls this FSA.

(Required).

MODE=FSS Indicates the FSA is controlled by an FSS. (Optional, default is FSS, when FSS= is coded).

PRESELCT={YES | NO} whether data sets are preselected for FSA.


PRMODE=(processing_modes) Sets the dataset processing modes for this FSA:

LINE line-data.

PAGE MO:DCA-P.

SOSIn SOSI1, SOSI2, or SOSI3 for double-byte fonts are selected.

installation-defined Any mode that your installation has defined.


U20944-J-Z247-6-7600

(Optional, default is LINE).

ROUTECDE=(destinations) Destinations processed by this FSA. 1-4 destinations that this FSA will select.

(Optional, no default).

START={YES | NO} whether JES2 starts the FSA automatically whenever JES2 starts.


TRKCELL={YES | NO} whether track-cell despooling is to be used for this FSA.

(Optional, default is NO).

UCS={font_name | 0} 1-4 character default font name. 0 specifies that no default font

(Optional).

WS=(work_selection_criteria) Establishes the spool selection criteria for this FSA:

CL | Q selects only datasets with the same class as stated in CLASS parameter.

R selects only those datasets with a destination name that matches one in the ROUTECDE parameter.

F selects only those datasets with a form name that matches one in the FORMS parameter.

(Optional).


U20944-J-Z247-6-7600

Install the PP/ROUTER Start-up Procedure

Start-up procedures to control the PP/ROUTER driven printers must be defined and placed in the installation proclib. Shown below is a model start-up procedure illustrating the coding for two ROUTER client printers.

//********************************************************************/ 00016000

//* */ 00020000

//* SPS: START UP PROCEDURE FOR PP/ROUTER */ 00030029

//* */ 00040000

//********************************************************************/ 00400000

//* 00410000

//PPROUTER PROC PREFIX='SPS.V380' 00421000

//* 00430000

//S3800 EXEC PGM=SPSMFSS,TIME=1440,REGION=8M 00512000

//* 00550000

//* STEPLIB ONLY NEEDED IF SPS MODULES ARE NOT INSTALLED 00570000

//* IN LINK LIST. 00580000

//STEPLIB DD DSN=&PREFIX..SPSLINK,DISP=SHR 00603500

//* 00620000

//RTRTABDD DD DSN=SPS.SMIC.SPSPARM(RTRTAB02),DISP=SHR (REQUIRED) 00661200

//* 00661300

//SYSUDUMP DD SYSOUT=X R/W 00663000

//* 00670000

//* A DATA SET MAY ALSO BE USED IN WHICH CASE THE SYSOUT 00680000

//* STATEMENT SHOULD BE REPLACED BY: 00690000

//* 00700000

//* //SYSUDUMP DD DSN=&PREFIX..DUMPSPS1,DISP=MOD 00710000

//* 00720000

//* 00930000

//SPSMSGDD DD DSN=SMIC.SPS.MESSAGES.V030800.SY09014(ENGLISH),DISP=SHR 00971000

// DD DSN=SMIC.SPS.MESSAGES.V030800.SY09014(ENGLISH8),DISP=SHR 01000100

//* 01010000

//SPSPARM DD DSN=SPS.SMIC.SPSPARM,DISP=SHR R 01072000

//* 01080000

//* THE LAST 4 CHARS OF THE DDNAME MUST BE THE JES PRINTER 02190000

//* NUMBER (PRT9906 = 9906). 02200000

//* NUMBER (PRT9907 = 9907). 02200000

//* 02210000

//SPS19906 DD DSN=SPS.SMIC.TRA19906,DISP=SHR PRIV 02240100




Figure 10: Example Start-up Procedure

Virtual and Real Storage Considerations

SPS is re-entrant with the exception of its data areas. When only one SPS printer is supported in an installation, only a single copy of SPS will ever be in virtual storage. When


U20944-J-Z247-6-7600

multiple SPS driven printers are supported, multiple copies of SPS will be loaded into virtual storage, when more than one start-up procedure is used. Each of these copies will be backed by different real storage, if the normal installation procedure is followed (STEPLIB or LINKLIB installation) and one start-up procedure is defined for each printer. This duplication can be avoided by directing the link-edits of re-entrant SPS modules to LPALIB (please see "Adjust JCLIN for LPALIB" ) for how to perform this function.

When the SPS re-entrant modules are moved or copied to LPALIB there will be no additional virtual or real storage required for multiple copies due to multiple start-up procedures.

SPS Execution Data Sets

The execution data sets required by SPS depend on the printers installed and the execution options chosen. SPS requires start-up procedure oriented and printer oriented data sets. Start-up procedure data sets have one allocation of each type in the procedure. Printer data sets have one allocation of each type for each printer.

Every procedure requires a message library, a parameter library, a ROUTER control table and may need a steplib and dump data set. The libraries and ROUTER control table may be shared between procedures, but the dump data set must be unique. The trace data sets must be unique for each printer.

User trace data sets are recommended for each printer. However, if the data sets are not present, the trace function will be suppressed and SPS will run normally. An abnormal termination dump data set is not required. However if the data set is provided, abnormal termination dumps will be written to this data set instead of SYSOUT.

DDnames

SPS allocates the data sets defined in the start-up procedure by ddname. The ddnames of the trace files must be of the form SPS1nnnn and SPS2nnnn, where nnnn is the JES printer number expanded to 4 digits (for PRT4 would be SPS10004 and SPS20004).


U20944-J-Z247-6-7600

DDNAME OPT/REQ ACCESS DESCRIPTION

STEPLIB

OPT

R

The load library containing the SPS load modules. This library should be shared between all SPS start-up procedures. This DD is only required if the SPS load library (including information page load modules) is not part of lpalib and/or linklst. An installation using only a steplib is the simplest installation approach.

SYSUDUMP

or

SYSABEND

OPT

R/W

The ddname for any abnormal termination dumps for a single SPS start-up procedure. SYSOUT is recommended for abnormal termination dumps, however adequate spool space must be available. An installation allocated data set may be used by the installation instead of the spool. This data set must be unique for all start-up procedures and must be specified with a disposition of MOD or dumps may be overwritten. The alternate ddname SYSABEND may be used if this is more convenient to the installation dump parameter definitions in SYS1.PARMLIB.

SPSMSGDD

REQ

R

This DD is a concatenation of the message data set members for the products installed. Up to 5 members may be selected: the base product messages, the SPS sort messages, APA printer messages, LINE printer messages and ROUTER messages. Different languages may be selected by member name if ordered. The message library should be shared between all start-up procedures. The message file is read from this file into storage when the SPS procedure is started. The same copy is used by all printers under the same procedure.

SPSPARM

REQ

R

The data set containing the SPS initialization parameter members. These members define the printers controlled by SPS and their processing options. This library should be shared between all start-up procedures. Please see PP/ROUTER Administrator's Guide for further information on these members. Only one parameter library is required for an installation, however if an installation prefers to have one for each start-up procedure, this is possible. Use of the naming conventions recommended in this manual make it more convenient to have only one parameter library.

Table 9: SPS Procedure Oriented DDNAME Descriptions


U20944-J-Z247-6-7600

DDNAME

OPT/REQ

ACCESS

DESCRIPTION

RTRTABDD REQ R This dataset contains the PP/ROUTER routing table which with a given combination of the JCL parameters DEST,FORMS & CLASS determin the target server for print distribution.

SPS1nnnn

and

SPS2nnnn

OPT

R/W

The data sets used to collect diagnostic trace information generated by SPS, where nnnn in the ddname is the number of the JES printer expanded to 4 digits. Both these ddnames must be present if either one is specified. Trace output alternates between each data set, overwriting the oldest entries. Trace data sets are only required if the option TRACEFILE(USER) is selected (please see PP/ROUTER Administrator's Guide for details on trace parameters). It is possible to collect SPS trace records using GTF, in which case these ddnames will not be needed. GTF trace collection will be attempted whenever these ddnames are not present for a printer, even when TRACEFILE(USER) has been specified. Trace data collection will be suppressed when GTF is not active during printer initialization and these ddnames are not present for a printer. GTF trace collection is not recommended (see "Trace Generation" on page 104). The BUFNO subparameter from the DCB parameter may be increased (defaults to 5) to avoid start-stops together with tracing (see "Trace Files" on page 102).

Table 10: SPS Printer Oriented DDNAME and OUTPUT statement descriptions

Create the PP/ROUTER Parameter Library Members Each time a printer is started, SPS accesses several members of SPS.SPSPARM to determine the installation selected printer defaults and options. These members must be coded for each printer and moved to SPS.SPSPARM. This job is usually performed by the SPS administrator, because it requires a knowledge of SPS processing options and how the installation is planning on using the product.

The SPS parameter library members need not be coded before completing the installation of SPS. If the installer is also going to code these members, the PRISMAproduction/ROUTER Administrator's Guide should be consulted for an overview of SPS and ROUTER processing parameters and details on coding these parameters.

SPSPRINT

REQ

SETUPxxx

Opt

LSCOxxx

REQ

MSGSUxxx

REQ

SETUP() LSCODE() MSGSU()


U20944-J-Z247-6-7600

Figure 11: SPSPARM library members

Control Statement Format and Parameter Syntax for files SPSPRINT / SETUPxxx / MSGSUxxx / LSCOxxxx

Each member is a collection of one or more control statements related to a printer or form. Each control statement contains one or more parameters defining some facet of the processing. A control statement is coded in positions 1-71 of the records in the parameter members with any non-blank character in 72 indicating continuation to the next record. A control statement may be a maximum of 10 records long (9 continuation records). Blank lines may appear anywhere between the control statements. Comments may be placed anywhere on or between the control statements except in the middle of a key word parameter. This includes starting on one record of a control statement and ending on any following record in the control statement. A comment on a control statement without parameters is valid and is processed as a null control statement. Comments are introduced by '/*' and terminated with '*/'. The only restriction on the contents of a comment is that a comment terminator (*/) should not be used as text within the comment. Please refer to Figure 8 for allowable syntax examples.

All parameters are keywords. Their general format is KEYWORD(value1,...,valuen). Keyword values must be enclosed by parentheses. Multiple keyword values must be separated by commas. Blanks will be taken as part of the value if present. This means keyword parameters interrupted by a continuation to the next record must be coded through column 71 and begin in column 1 of the next record to avoid unwanted blanks. Keyword parameters may be coded in any order on the control statement, however the order suggested in the parameter descriptions will help to avoid errors and simplify maintenance.

A keyword should not be coded more than once in a member unless specifically allowed.

1 COLUMNS 72 /* This example illustrates all the rules for statements and */ /* keywords. The entire example is valid syntax from the blank */ /* line above this comment to the blank line following the end */ /* of example comment. This comment is 5 null control statements */ /* of 1 line each */ /* Statement 1 */ KEYWORD1(value1,...,valuen) /* Possible comment */C KEYWORD2(value1,...,valuen) /* Possible comment */C KEYWORDn(value1,...,valuen) /* Possible comment */ /* The following statement illustrates key word continuation C situations that are allowed. This comment is 1 null control C statement of 3 lines */


U20944-J-Z247-6-7600

/* Statement 2 */ KEYWORD1(value1,...,valuen) KEYWORC D2(value1,...,valuen) /* Possible comment */ KEYWORDN(valC ue1,...,valuen) /* Possible comment */ /* The following statement illustrates comment continuation */ /* situations. This comment is 1 null control statement of 1 line C and 1 null control statement of 2 lines */ /* Statement 3 */KEYWORD1(value1,...,valuen)/* Possible continued C comment */ KEYWORD2(value1,...,valuen) /C * Possible continued comment */ KEYWORDn(value1,...,valuen) /* End of Statement Syntax Example */

Figure 12: Statement Syntax Examples.

SPSPRINT / SETUPxxx supported parameters

PRT(printer name ) Is the device name defined to the spooling system that ROUTER will control.

(Required)

JES2 - Must correspond to the JES printer name

CUU( RTnn ) Is a unique name within the group of devices defined within this SPSPRINT member.

RTnn – the first 2 characters must be RT nn can be any number between 00-99

(Required)

LSCODE( license code file name )

A „License Key“ is required to function in Production mode. ROUTER has a DEMO mode that is activated when no license key is present.

In DEMO mode a transmission will be terminated and the dataset returned to the spooling system in HOLD status following the transmission of 3500 records.

(Required)

MSGSU( MSGSURTR ) The supplied MSGSU table must be used.

(Required)


U20944-J-Z247-6-7600

SETUP( setup member name )

This file is optional and has the following parameter support. They define the defaults for the FSA that will be used for all jobs transmitted by this FSA when those parameters that are possible to be given at a job level are not given, these parameters are identified by (JCL) following the parameter and have a higher priority as the parameters in the setupxxx member.

Defaults for parameters are underlined.

DRIVER(driver name PPROUTER)

PPRTRPPX(print parm exit name PPRTRPPX)

CMDIF( MODIFY | WTOR )

TRACELEV( 0-4 )

TRACETYPE( ALL | INITERM | REQFLOW | PS | DISPAT | INVRET | PDS | ORDER | SOCKET )

TRACEFILE( GTF | USER )

TRACESET( FF,FF,FF,FF,FF,FF,FF,FF )

DUMP( YES | NO )

CHARS( font name ) (JCL)

FORMDEF( formdef name ) (JCL)

PAGEDEF( pagedef name) (JCL)

MSGSUxxx member parameters

The MSGSUxxx parameter member which is installed into the SAMPLIB must be used for all the PP/ROUTER printers in the installation.

Create the PP/ROUTER Router control table

When a dataset has been selected from the spool system for distribution the router control table is referenced. A matching group entry is sought, the basis being a valid combination of DEST, CLASS and FORMS entries from the datasets output characteristics. Having


U20944-J-Z247-6-7600

found a matching group entry the IPADDR and PORTNUM are used as the target destination. Multiple group statements can exist for a single server destination using different selection criteria. (See ROUTER table section).

In OS/390 (MVS) a routing control file is defined per start procedure(FSS) that has a DD statement of RTRTABDD, this file is then shared by the devices (FSAs) that run under the control of the FSS.

Therefore to introduce changes in a routing table, the changes must be made to the table then the FSS must be stopped and then started again.

Syntax Rules for ROUTER control table

All parameters should be written in uppercase

All parameter values should be coded in uppercase, exception to this being the TCPIP name parameter which can be coded in mixed case.

Each parameter must be coded on a seperate line.

End a group of parameters relevant for a particular destination by a semi colon

Comments should be coded on seperate lines and must begin with /*

ROUTER controls the parameters for syntax as the print device is started, giving messages when errors are found for KEYWORDS, PARAMETERS to keywords and also over GROUP validity.

TCPNAME(TCPIP); /**UNIX BOX IN COMPUTER CENTRE************************ DEST(PRISMA1) CLASS(ABC) FORMS(UNIX) IPADDR(160.120.17.233) PORTNUM(6401) RETRYINT(20) RETRYNUM(2) YEAR_FORMAT(YYYY) SEND_REC_LENGTH(YES); Figure 13: Example Router control table.

TCPNAME(tcpipname); Is the 1-8 character job name of the TCP/IP address


U20944-J-Z247-6-7600

space.

(Optional, default is TCPIP).

This keyword must be terminated with a semicolon.

TCPNAME keyword is required only once within a router control file.

The following keywords make a routing group, as many groups as required can be specified.

CLASS(classes) Up to eight class values. Each class is 1-alphanumeric character.

(Optional).

However when not specified then DEST or FORMS must be given.

DEST(destination names)

Up to eight destination names each being 1-8 characters long, separated by a blank character.

(Optional).

However when not specified then CLASS or FORMS must be given.

FORMS(form names)

Up to eight form names each being 1-8 characters long, separated by a blank character.

(Optional).

However when not specified then CLASS or DEST must be given.

IPADDR(Server ip address)

Is the address of the remote server system. Specify a valid ip address in the format: nnn.nnn.nnn.nnn.

(Required).

PORTNUM(server port number) Is the port number used on the remote server system. This parameter is required.

(Required).

RETRYINT(retry interval | 0)

Is the number of seconds between retries.

Valid range is a number 0-99999

(Optional, default is 0).


U20944-J-Z247-6-7600

RETRYNUM(number of retries | 0)

Is the maximum number of times Router will retry a failed transmission.



SEND_REC_LENGTH(YES | NO)

whether or not each record is prefixed with a length field.

YES a 2 byte record length prefix is included for each record.

NO a 2 byte prefix is not included with each record.


YEAR_FORMAT(YY | YYYY)

Defines format of the year portion of the file name that ROUTER generates.

(Optional, default is YYYY).

; The last keyword within a routing group must be terminated with a semicolon.

e.g. YEAR_FORMAT(YY);

If you specify more than one of the three routing parameters (that is, CLASS,

DEST, or FORMS) on one routing statement, data sets must match all of the

specified parameters to be routed to the associated server.

Install the PP/ROUTER License Key

PRISMAproduction ROUTER requires a license key in order to run in production mode.

Without the license the application runs in DEMO mode, this is indicated as the print device is started and a spool file is processed, the following message will be given:

*SPS0944E PRTnnnn : NO VALID AUTHORIZATION KEY

(CONT.) PROVIDED FOR SPS. RUNNING IN RESTRICTED MODE.

In restricted DEMO mode datasets with a record count greater than 3500 are terminated with message:


U20944-J-Z247-6-7600

RTR0000E PRTnnnn: NO VALID LICENSE KEY, RESTRICTED MODE

ACTIVE LIMITED TO 3500 RECORDS,TRANSFER WILL TERMINATE.

The “License Key” can be obtained from your Océ representative. The CPUID for each processor that PP/ROUTER is to be used on is required for the license key generation.

The CPUID can be displayed as follows:

OS/390 (MVS) MVS sytem command D M=CPU

Test the PP/ROUTER Installation In order to test the installation start the print device that was defined in 2.7. Errors in router table entries will be shown. Any router table groups that have missing required group entries will be disabled.

In order to test the target destinations then test output datasets require to be transmitted.

ACCEPT the Product OS/390 (MVS) A new release of PP/ROUTER should be allowed to run for a reasonable period of time in production before doing an SMP accept. When the installation is confident that all print jobs supported by the previous release of PP/ROUTER run without problems on the new release, PP/ROUTER should be accepted.

//ACCEPT JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //ACCEPT EXEC SMPPROC //SMP.SYSIN DD * (SMPCNTL) SET BDY(SPSvrmD) . ACCEPT S(SPSvrm0) . /*

Figure 14: Example SMP Accept Job


U20944-J-Z247-6-7600

4 SPS/LI Installation and Customization VSE


The following tasks must be performed in order to install SPS:

1. Restore sublibrary from tape using MSHP

2. Define extra JECL parameters in VSE/POWER AUTOSTART if running under POWER 2.3 or later release ( See also PP/ROUTER install section relating to additional POWER defines)

3. Create the SPS system parameters

Additionally, you may do the following optional tasks to customize SPS to your installation needs:

1. Add SPS reentrant phases to SVA


SPS is shipped as 2 products; a base product and a ROUTER print distribution driver. The distribution medium for SPS is one no-label cartdrige for the base product and one cartdrige for the PP-ROUTER driver productThe tapes are in standard MSHP backup/restore format.

The following PRODUCT ID's are used:

SPSvrm base SPS product

PS8vrm SPS driver for PP-ROUTER driver

where vrm is the version, release and modification level of SPS.


U20944-J-Z247-6-7600

Restore Sublibrary from Tape

Restore the base product to a sublibrary whose name is specified in the MSHP job in Figure 27. Each tape is externally identified with the product id of the first or only product on the tape.

* $$ JOB JNM=SPSINST

// JOB SPSINST

// PAUSE ASSGN SYS006 TO INSTALLATION TAPE

// MTC REW,SYS006

// EXEC MSHP

INSTALL PRODUCT FROMTAPE -

PRODUCTION INTO=PRD2.SPSvrm

/*

// MTC RUN,SYS006

/&

* $$ EOJ

Figure 1: Sample MSHP Install Job to install base product (SPSINST.Z)

In Figure 1, the version, release and modification level of the SPS product are designated by the characters vrm. You may override the sublibrary name when running the MSHP restore job. The base and PP-ROUTER products should be installed into the same VSE sublibrary.

The sample job SPSINST.Z from Figure 2 should be used to install the base product and the PP-ROUTER product.


U20944-J-Z247-6-7600

Entries are created in your System History File by these jobs as follows:

5999-SP-S00-vrm - base SPS product

5999-PS-800-vrm - SPS driver for PP-ROUTER


U20944-J-Z247-6-7600

Define JECL Parms in AUTOSTART

You must do this installation task only if you are installing SPS under POWER version 2.3 or a later release, otherwise refere to the SPSZPARM section.

The following statements should be added to the list of the POWER AUTOSTART statements in the startup procedure for the VSE/POWER partition.

See ROUTER install section for the POWER defintions required.


U20944-J-Z247-6-7600

SPS Reentrant Phases

SPS is reentrant with the exception of its data area phases. When SPS drives more than one printer in the same partition only one copy of SPS will be loaded into partition storage. To share the same copy of SPS between multiple partitions, you may load the following phases in the SVA.

SPSDFSS 304.780 bytes

All other phases can not be placed in the SVA.

5 PP/ROUTER Installation and Customization VSE


The following tasks must be performed to install PP/ROUTER:

1. Install the product from tape using MSHP

2. Define extra JECL parameters in VSE/POWER AUTOSTART

3. Define the PP/ROUTER TCPIP target servers

4. Install/extend the start-up procedure(s)

5. Create the PP/ROUTER parameter library members, SPSPRINT/SETUPxxx/MSGSUxxx/LSCOxxxx


U20944-J-Z247-6-7600

6. Create the PP/ROUTER router control table

7. Install the PP/ROUTER License Key

8. Test the PP/ROUTER installation


U20944-J-Z247-6-7600


PP/ROUTER is shipped as 1 Product, If you are ordering the ROUTER feature, as an additional printer driver to an already installed SPS a PTF tape for the SPS base components will also be delivered. PRISMAproduction/ROUTER feature product tape. PTF tape for SPS base component. If you are a new customer to Océ the following tapes will be delivered. SPS base product tape. PRISMAproduction/ROUTER feature product tape. PTF tape for SPS base component. The tapes are in standard MSHP backup/restore format.

The following PRODUCT ID's are used:

SPSvrm SPS base product

PS8vrm PP/ROUTER driver product

where vrm is the version, release and modification level of the product.

Install product from Tape

Install theproduct into a sublibrary whose name is specified in the MSHP job in Figure 1. Each tape is externally identified with the product id of the first or only product on the tape.

* $$ JOB JNM=PPROUTER

// JOB PPROUTER

// PAUSE ASSGN SYS006 TO INSTALLATION TAPE

// MTC REW,SYS006

// EXEC MSHP

INSTALL PRODUCT FROMTAPE -

PRODUCTION INTO=PRD2.SPSvrm


U20944-J-Z247-6-7600

/*

// MTC RUN,SYS006

/&

* $$ EOJ

Figure 2: Example MSHP Install Job to install base product

In Figure 2, the version, release and modification level of the SPS product are designated by the characters vrm. You may override the sublibrary name when running the MSHP restore job. The base and APA products may be installed into the same VSE sublibrary.

The example job in Figure 2 should be used to install the PP/ROUTER product.

An entry will be created in your System History File by this jobs for the following product:

5999-PS-800-vrm - PP/ROUTER driver product

PP/ROUTER printer definitions in VSE and VM

There are no system definitions required for the print devices that will be controlled by the DDS SPS for the PP/ROUTER driver.

POWER JECL defines in AUTOSTART

The following statements should be added to the list of the POWER AUTOSTART DEFINE statements in the startup procedure for the VSE/POWER partition.

DEFINE L,CKPTPAGE,4,1,2,B,1,32767

DEFINE L,CKPTSEC,5,1,2,B,1,32767

DEFINE L,CONTROL,8,1,7,C

DEFINE L,PRMODE,18,1,8,C

DEFINE L,TRC,1A,1,3,C

DEFINE L,FORMDEF,1D,1,6,C

DEFINE L,PAGEDEF,1F,1,6,C

DEFINE L,PIMSG,21,2,3,C


U20944-J-Z247-6-7600

DEFINE L,DATACK,2022,1,8,C

DEFINE L,FORMS,10,1,4,C

DEFINE L,DUPLEX,3D,1,6,C

DEFINE L,INTRAY,3E,1,1,B,1,3

DEFINE L,OFFSETXB,43,1,13,C

DEFINE L,OFFSETYB,44,1,13,C

DEFINE L,OFFSETXF,41,1,13,C

DEFINE L,OFFSETYF,42,1,13,C

DEFINE L,OUTBIN,2023,1,4,B,1,65535

DEFINE L,OVERLAYB,40,1,8,C

DEFINE L,OVERLAYF,3F,1,8,C

DEFINE L,PRTQUEUE,38,1,127,*

DEFINE L,RESFMT,46,1,4,C

DEFINE L,TITLE,2A,1,60,*

Define the PP/ROUTER TCPIP target servers

Definitions for the the PRISMAproduction target TCPIP servers should be made for all the servers that are to be defined in the routing table for PP/ROUTER.

Install the PP/ROUTER Start-up Job

A sample startup job is shown in Figure 3.

* $$ JOB JNM=PPROUTER

// JOB PPROUTER

LIBDEF *,SEARCH=PRD2.SPSvrm

/*

/* trace files for printer nnnn


U20944-J-Z247-6-7600

/*

// DLBL SP1nnnn,'SPSE.DLI.TRA1nnnn',0,SD

// EXTENT SYS001, volser ,1,0, yyy,zzz

// ASSGN SYS001,DISK,VOL=volser ,SHR TRACE FILE 1

// DLBL SP2nnnn,'SPSE.DLI.TRA2nnnn',0,SD

// EXTENT SYS001, volser ,1,0, yyy,zzz

// ASSGN SYS001,DISK,VOL=volser ,SHR TRACE FILE 2

// EXEC SPSDFSS,SIZE=512K,PARM='SPS'

/*

/&

* $$ EOJ

Figure 3: Sample SPS Startup Job

The above example assumes that you wish to create two trace files to be used in a 'flip-flop' fashion should they be required. The labels for the trace files may be placed in the standard label area.


U20944-J-Z247-6-7600

STATEMENT OPT/REQ DESCRIPTION

LIBDEF

REQ

This statement specifies which sublibraries should be searched for the SPS driver phases, printer resources, macros, system parameters and control parameters.

If you loaded the SPS sample resources from tape PS2vrm (240 or 300 dpi) to independent libraries you should specify them also here. See section 0.

LIBDEF DUMP

OPT

This statement specifies which sublibraries may be used to write any abnormal termination dumps for an SPS startup. It is your responsibility to ensure that there is a valid // OPTION PARTDUMP active for this partition.

This statement is required if the required sublibrary is not defined in a permanent LIBDEF statement in the partition startup procedure and you do not want that SPS dumps go to spool.

SP1nnnn and

SP2nnnn

OPT

The files used to collect diagnostic trace information generated by SPS, where nnnn in the filename must be the printer device number expanded to 4 digits as specified in the PRT parameter from the SPSPRINT member. These trace files must be allocated if TRACEFILE(USER) is specified or defaulted in the SETUPcuu system parameter member. Trace output alternates between both data sets.

It is suggested to allocate approximately 20 cylinders of 3380 disk space (or equivalent) per trace file, but you may allocate less space if necessary. Allocate two trace files (1 & 2) per printer.

EXEC

REQ

The EXEC statement calls the main SPS program. The SIZE parameter should be coded as shown. The size parameter should be big enough for the first SPS phase loaded. The rest of the partition is then available for the other phases and for the dynamic areas and buffers. If a lack of storage occurs after SPS starts you should either decrease the SIZE value or increase the partition size. The PARM parameter specifies the subsystem ID for SPS. If more than one SPS job runs in the system at the same time they should have different subsystem IDs. The subsystem ID should be given in the PSTART printer command.

Table 4: SPS Startup Job Statements


U20944-J-Z247-6-7600

Create the PP/ROUTER Parameter Library Members Each time a printer is started, SPS accesses several members of SPS.SPSPARM to determine the installation selected printer defaults and options. These members must be coded for each printer and moved to SPS.SPSPARM. This job is usually performed by the SPS administrator, because it requires a knowledge of SPS processing options and how the installation is planning on using the product.

The SPS parameter library members need not be coded before completing the installation of SPS. If the installer is also going to code these members, the PRISMAproduction/ROUTER Administrator's Guide should be consulted for an overview of SPS and ROUTER processing parameters and details on coding these parameters.

Figure 15: SPSPARM library members

Control Statement Format and Parameter Syntax for files SPSPRINT / SETUPxxx / MSGSUxxx / LSCOxxxx

Each member is a collection of one or more control statements related to a printer or form. Each control statement contains one or more parameters defining some facet of the processing. A control statement is coded in positions 1-71 of the records in the parameter members with any non-blank character in 72 indicating continuation to the next record. A control statement may be a maximum of 10 records long (9 continuation records). Blank lines may appear anywhere between the control statements. Comments may be placed anywhere on or between the control statements except in the middle of a key word parameter. This includes starting on one record of a control statement and ending on any following record in the control statement. A comment on a control statement without parameters is valid and is processed as a null control statement. Comments are introduced by '/*' and terminated with '*/'. The only restriction on the contents of a comment is that a comment terminator (*/) should not be used as text within the comment. Please refer to Figure 8 for allowable syntax examples.

SPSPRINT

REQ

SETUPxxx

Opt

LSCOxxx

REQ

MSGSUxxx

REQ

SETUP() LSCODE() MSGSU()


U20944-J-Z247-6-7600

All parameters are keywords. Their general format is KEYWORD(value1,...,valuen). Keyword values must be enclosed by parentheses. Multiple keyword values must be separated by commas. Blanks will be taken as part of the value if present. This means keyword parameters interrupted by a continuation to the next record must be coded through column 71 and begin in column 1 of the next record to avoid unwanted blanks. Keyword parameters may be coded in any order on the control statement, however the order suggested in the parameter descriptions will help to avoid errors and simplify maintenance.

A keyword should not be coded more than once in a member unless specifically allowed.

1 COLUMNS 72 /* This example illustrates all the rules for statements and */ /* keywords. The entire example is valid syntax from the blank */ /* line above this comment to the blank line following the end */ /* of example comment. This comment is 5 null control statements */ /* of 1 line each */ /* Statement 1 */ KEYWORD1(value1,...,valuen) /* Possible comment */C KEYWORD2(value1,...,valuen) /* Possible comment */C KEYWORDn(value1,...,valuen) /* Possible comment */ /* The following statement illustrates key word continuation C situations that are allowed. This comment is 1 null control C statement of 3 lines */ /* Statement 2 */ KEYWORD1(value1,...,valuen) KEYWORC D2(value1,...,valuen) /* Possible comment */ KEYWORDN(valC ue1,...,valuen) /* Possible comment */ /* The following statement illustrates comment continuation */ /* situations. This comment is 1 null control statement of 1 line C and 1 null control statement of 2 lines */ /* Statement 3 */KEYWORD1(value1,...,valuen)/* Possible continued C comment */ KEYWORD2(value1,...,valuen) /C * Possible continued comment */ KEYWORDn(value1,...,valuen) /* End of Statement Syntax Example */

Figure 16: Statement Syntax Examples.

SPSPRINT / SETUPxxx supported parameters

PRT(printer name ) Is the device name defined to the spooling system that ROUTER will control.

This parameter must be from 1 to 8 alphameric


U20944-J-Z247-6-7600

characters long.

(Required)

CUU( RTnn ) Is a unique name within the group of devices defined within this SPSPRINT member.

RTnn – the first 2 characters must be RT nn can be any number between 00-99

(Required)

LSCODE( license code file name )

A „License Key“ is required to function in Production mode. ROUTER has a DEMO mode that is activated when no license key is present.

In DEMO mode a transmission will be terminated and the dataset returned to the spooling system in HOLD status following the transmission of 3500 records.

(Required)

MSGSU( MSGSURTR ) The supplied MSGSU table must be used.

(Required)

SETUP( setup member name )

This file is optional and has the following parameter support. They define the defaults for the FSA that will be used for all jobs transmitted by this FSA when those parameters that are possible to be given at a job level are not given, those parameters are identified by a (JCL) following the parameter and have a higher priority as the parameters in the setupxxx member.

Defaults for parameters are underlined.

DRIVER(driver name PPROUTER)

PPRTRLIB(sub-library containing router table SPS341.ROUTER)

PPRTRTAB(routing table name ROUTER01)


U20944-J-Z247-6-7600

PPRTRPPX(print parm exit name PPRTRPPX)

TRACELEV( 0-4 )

TRACETYPE( ALL | INITERM | REQFLOW | PS | DISPAT | INVRET | PDS | ORDER | SOCKET )

TRACEFILE( GTF | USER )

TRACESET( FF,FF,FF,FF,FF,FF,FF,FF )

DUMP( YES | NO )

CHARS( font name ) (JCL)

FORMDEF( formdef name ) (JCL)

PAGEDEF( pagedef name) (JCL)

(Optional)

MSGSUxxx member parameters

The MSGSUxxx parameter member which is installed into the SAMPLIB must be used for all the PP/ROUTER printers in the installation.

The member can be expanded with additional supression entries, or merged together with an existing supression file at your installation.

Create the PP/ROUTER Router control table

When a dataset has been selected from the spool system for distribution the router control table is referenced. A matching group entry is sought, the basis being a valid combination of DEST, CLASS and FORMS entries from the datasets output characteristics. Having found a matching group entry the IPADDR and PORTNUM are used as the target destination. Multiple group statements can exist for a single server destination using different selection criteria. (see PP/ROUTER Administration Guide).

In VSE a routing control file is specified per device, in the SETUP member.

The router table is read by each device as it is started. Therefore to introduce changes in a routing table, the changes must be made to the table and any device that is to use the table can then be started, or if already active the device must be stopped and then started again.


U20944-J-Z247-6-7600

Syntax Rules for ROUTER control table

All parameters should be written in uppercase

All parameter values should be coded in uppercase, exception to this being the TCPIP name parameter which can be coded in mixed case.

Each parameter must be coded on a seperate line.

End a group of parameters relevant for a particular destination by a semi colon

Comments should be coded on seperate lines and must begin with /*

ROUTER controls the parameters for syntax as the print device is started, giving messages when errors are found for KEYWORDS, PARAMETERS to keywords and also over GROUP validity.

TCPNAME(TCPIP); /**UNIX BOX IN COMPUTER CENTRE************************ DEST(PRISMA1) CLASS(ABC) FORMS(UNIX) IPADDR(160.120.17.233) PORTNUM(6401) RETRYINT(20) RETRYNUM(2) YEAR_FORMAT(YYYY) SEND_REC_LENGTH(YES); Figure 17: Example Router control table.

TCPNAME(tcpipname); Is the 1-8 character job name of the TCP/IP address space.

(Optional, default is TCPIP).

This keyword must be terminated with a semicolon.

TCPNAME keyword is required only once within a router control file.


U20944-J-Z247-6-7600

The following keywords make a routing group, as many groups as required can be specified.

CLASS(classes) Up to eight class values. Each class is 1-alphanumeric character.

(Optional).

However when not specified then DEST or FORMS must be given.

DEST(destination names)

Up to eight destination names each being 1-8 characters long, separated by a blank character.

(Optional).

However when not specified then CLASS or FORMS must be given.

FORMS(form names)

Up to eight form names each being 1-8 characters long, separated by a blank character.

(Optional).

However when not specified then CLASS or DEST must be given.

IPADDR(Server ip address)

Is the address of the remote server system. Specify a valid ip address in the format: nnn.nnn.nnn.nnn.

(Required).

PORTNUM(server port number) Is the port number used on the remote server system. This parameter is required.

(Required).

RETRYINT(retry interval | 0)

Is the number of seconds between retries.



RETRYNUM(number of retries | 0)

Is the maximum number of times Router will retry a failed transmission.



SEND_REC_LENGTH(YES | NO)

whether or not each record is prefixed with a length field.

YES a 2 byte record length prefix is included for each record.


U20944-J-Z247-6-7600

NO a 2 byte prefix is not included with each record.


YEAR_FORMAT(YY | YYYY)

Defines format of the year portion of the file name that ROUTER generates.

(Optional, default is YYYY).

; The last keyword within a routing group must be terminated with a semicolon.

e.g. YEAR_FORMAT(YY);

If you specify more than one of the three routing parameters (that is, CLASS,

DEST, or FORMS) on one routing statement, data sets must match all of the

specified parameters to be routed to the associated server.

Install the PP/ROUTER License Key

PRISMAproduction ROUTER requires a license key in order to run in production mode.

Without the license the application runs in DEMO mode, this is indicated as the print device is started and a spool file is processed, the following message will be given:

*SPS0944E PRTnnnn : NO VALID AUTHORIZATION KEY

(CONT.) PROVIDED FOR SPS. RUNNING IN RESTRICTED MODE.

In restricted DEMO mode datasets with a record count greater than 3500 are terminated with message:

RTR0000E PRTnnnn: NO VALID LICENSE KEY, RESTRICTED MODE

ACTIVE LIMITED TO 3500 RECORDS,TRANSFER WILL TERMINATE.

The “License Key” can be obtained from your Océ representative. The CPUID for each processor that PP/ROUTER is to be used on is required for the license key generation.

The CPUID can be displayed as follows:


U20944-J-Z247-6-7600

VSE VSE system command SIR

Test the PP/ROUTER Installation In order to test the installation start the print device that was defined in 2.7. Errors in router table entries will be shown. Any router table groups that have missing required group entries will be disabled.

In order to test the target destinations then test output datasets require to be transmitted.

SPS Start-up Procedures

U20944-J-Z247-6-7600

SPS Start-up Procedures

U20944-J-Z247-6-7600

SPS/MVS related topics For further information on the following topics (see SPS/MVS Administration Guide, sections are named as the topics listed below).

SPS Started Task Authorization

SPS Data Set Authorization

Sample Procedure for Defining SPS to RACF

Execution Data Set Allocations

Trace SPS provides the capability of collecting extensive trace information on processing errors. Two trace data sets may be allocated for each printer for collecting this information. The allocation of these data sets for each printer in a start-up procedure, although optional, is highly recommended. GTF can be used instead of the user trace data sets. However, GTF often loses many trace records depending on the activity of the system. The user trace facility provides a wrap around trace table on disk that does not lose trace records. The data may also be directed to tape. SPS defaults, as delivered, generate a comprehensive trace to disk.

The use of trace data collection to disk or tape after installation checkout of the SPS product is only required when a problem has been detected and a trace needs to be generated. This will generally be done at the request of a service representative. The installation should therefore specify the start-up parameter TRACEFILE(NO) and TRACELEV(0) in the setup member for the printer after SPS is running satisfactorily (please see PP/ROUTER Administrator's Guide for trace parameter information).

Maintenance

U20944-J-Z247-6-7600

6 REXX requirements

As PP/ROUTER is written in REXX/370 there are a couple of control modules that are required in order to allow PP/ROUTER to function correctly in the system. These modules are supplied on the PP/ROUTER product tape.

During the installation of the PP/ROUTER product the REXX control modules IRXFLOC and IRXPARMS where installed into the standard SPS libraries.

Maintenance

U20944-J-Z247-6-7600

OS/390 (MVS)

IRXFLOC

This modules defines the external functions that are called by the central REXX ROUTER program, which is defined as a local function package. The supplied IRXFLOC is the standard REXX module with the required external functions for ROUTER.

IRXFLOC CSECT ,

IRXFLOC AMODE 31

IRXFLOC RMODE ANY

TITLE 'IRXFLOC - REXX LOCAL FUNCTION PACKAGE DIRECTORY '

DC CL8'IRXFPACK' /* INITIALIZE THE ID FIELD */

DC FL4'24' /* LENGTH OF HEADER */

DC FL4'7' /* NUMBER OF FUNCTIONS IN PACK. */

DC FL4'0' /* RESERVED FIELD */

DC FL4'32' /* LENGTH OF EACH FUNC. ENTRY */

*

DC CL8'PPRL01' /* PP/ROUTER LI INTERFACE ROUT. */

DC V(PPRL01) /* LOAD ADDRESS OF FUNCTION */

DC FL4'0' /* RESERVED */

DC CL8'PPRL01' /* INITIALIZE THE ID FIELD */

DC CL8' ' /* RESERVED */

*

DC CL8'PPRPDSB' /* PP/ROUTER LI INTERFACE ROUT. */

DC V(PPRPDSB) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRPDSB' /* INITIALIZE THE ID FIELD */


Maintenance

U20944-J-Z247-6-7600

*

DC CL8'PPRTRPPX' /* PP/ROUTER PRINT PARMS EXIT */

DC V(PPRTRPPX) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRTRPPX' /* INITIALIZE THE ID FIELD */


*

DC CL8'PPRTAB ' /* PP/ROUTER ROUTER TABLE LOAD */

DC V(PPRTAB) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRTAB ' /* INITIALIZE THE ID FIELD */


*

DC CL8'SOCKET ' /* PP/ROUTER ROUTER TABLE LOAD */

DC V(SOCKET) /* LOAD ADDRESS OF FUNCTION */


DC CL8'SOCKET ' /* INITIALIZE THE ID FIELD */


*

DC CL8'STORAGE ' /* PP/ROUTER ROUTER TABLE LOAD */

DC V(STORAGE) /* LOAD ADDRESS OF FUNCTION */


DC CL8'STORAGE ' /* INITIALIZE THE ID FIELD */


*

END IRXFLOC

Maintenance

U20944-J-Z247-6-7600

IRXPARMS

The supplied IRXPARMS module is the standard REXX module enabled for LOCAL FUNTION PACKAGES with the PARMBLOCK flags field set as follows.

VSE

ARXFLOC

This modules defines the external functions that are called by the central REXX ROUTER program, which is defined as a local function package. The supplied IRXFLOC is the standard REXX module with the required external functions for ROUTER.

ARXFLOC CSECT ,

ARXFLOC AMODE 31

ARXFLOC RMODE ANY

TITLE 'ARXFLOC - REXX LOCAL FUNCTION PACKAGE DIRECTORY '

DC CL8'ARXFPACK' /* INITIALIZE THE ID FIELD */

DC FL4'24' /* LENGTH OF HEADER */

DC FL4'7' /* NUMBER OF FUNCTIONS IN PACK. */

DC FL4'0' /* RESERVED FIELD */

DC FL4'32' /* LENGTH OF EACH FUNC. ENTRY */

*

DC CL8'PPRL01' /* PP/ROUTER LI INTERFACE ROUT. */

DC V(PPRL01) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRL01' /* INITIALIZE THE ID FIELD */


PARMBLOCK_FLAGS DC X'0146C000' /* Issue alternate messages and ......

Maintenance

U20944-J-Z247-6-7600

*

DC CL8'PPRPDSB' /* PP/ROUTER LI INTERFACE ROUT. */

DC V(PPRPDSB) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRPDSB' /* INITIALIZE THE ID FIELD */


*

DC CL8'PPRTRPPX' /* PP/ROUTER PRINT PARMS EXIT */

DC V(PPRTRPPX) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRTRPPX' /* INITIALIZE THE ID FIELD */


*

DC CL8'PPRTAB ' /* PP/ROUTER ROUTER TABLE LOAD */

DC V(PPRTAB) /* LOAD ADDRESS OF FUNCTION */


DC CL8'PPRTAB ' /* INITIALIZE THE ID FIELD */


*

DC CL8'SOCKET ' /* PP/ROUTER ROUTER TABLE LOAD */

DC V(SOCKET) /* LOAD ADDRESS OF FUNCTION */


DC CL8'SOCKET ' /* INITIALIZE THE ID FIELD */


*

DC CL8'STORAGE ' /* PP/ROUTER ROUTER TABLE LOAD */

DC V(STORAGE) /* LOAD ADDRESS OF FUNCTION */


DC CL8'STORAGE ' /* INITIALIZE THE ID FIELD */

Maintenance

U20944-J-Z247-6-7600


*

END ARXFLOC

ARXPARMS

The supplied ARXPARMS module is the standard REXX module enabled for LOCAL FUNTION PACKAGES with the PARMBLOCK flags field set as follows.

PARMBLOCK_FLAGS DC X'0146C000' /* Issue alternate messages and ......

Maintenance

U20944-J-Z247-6-7600

7 OPERATION In addition to the JES printer related commands supported by SPS (like $PPRTx,$SPRTx, $CPRTx, etc...) there are also some commands given directly to SPS (not via JES) to achieve some other functions.

OS/390 (MVS)

MVS Commands

STOP (P) Command

This MVS command allows the operator to terminate one SPS procedure when no printers are started.

The format of this command is:

P procid

where:

procid is the procedure id used to start the SPS procedure and corresponds to the FSS id specified in the JES2PARM.

When any printer is started for the specified procedure and the STOP command is issued SPS rejects the command with a message indicating that printer(s) are still active. Another STOP command has to be given later, after all FSS related printers are drained.

JES Commands

The following JES commands are supported by SPS & PP/ROUTER:

$S Start device command


$P Stop device command


Maintenance

U20944-J-Z247-6-7600

$C Cancel device command


FSS Commands

FSS commands are issued to the SPS main task and not to a specific printer (FSA) subtask. These commands are always issued via the MVS MODIFY (F) command. FSS commands are not available in direct printing mode.

The general format of an FSS command is:

F procid,command

where:


command is the SPS FSS command.

CANCEL Command

This command is issued to the SPS main task in order to request the immediate termination of one SPS printer task running under this FSS. The canceled task will terminate with a system abend code 33E (termination because of detach macro). This command should be used only if the ROUTER printer is hanging (wait) or looping and you are not able to drain it (for JES2, $PPRTx). The advantage of this command to a simple MVS CANCEL command is that other printers running under the same procedure are not affected. If you have just one printer running under this FSS you may also issue the MVS CANCEL command.

The format of the CANCEL command is:

F procid,PRTx,CANCEL

where:


PRTx is the JES printer name as specified in the JES2PARM and SPSPRINT SPSPARM member.

Printer Commands

Printer commands are executed by the corresponding printer subtask. There are 2 ways to issue such commands depending on the specification of the CMDIF parameter from the

Maintenance

U20944-J-Z247-6-7600

SETUPxxx member (SPSPARM). If CMDIF(WTOR) is specified the printer subtask issues a message with answer (WTOR) just after its initialization (message SPS0260A). You enter printer commands just answering this message. In this case, the format of any printer command is:

R xx,command

If CMDIF(MODIFY) is specified or defaulted no pending message is issued by the printer subtask. You have to enter printer commands via the MVS MODIFY (F) command. The SPS main task receives these commands, checks if the requested printer subtask is active and passes the command to the printer subtask. In this case, the format of any printer command is:

F procid,PRTx,command

where:


PRTx is the JES printer name as specified in the JES2PARM and SPSPRINT SPSPARM member.

SPS always uses the WTOR interface for printer commands in direct printing mode.

TOPE Command

This command requests that SPS open the trace files. Any previous information contained in the trace files is lost after they are opened. If the trace files are already open this command is ignored. After successfully opening the trace files, SPS writes a trace record indicating the dynamic open operation.


F procid,PRTx,TOPE for CMDIF(MODIFY)

or

R xx,TOPE for CMDIF(WTOR)

TCLO Command

This command requests that SPS should close the trace files. After successfully closing the trace files, they may be unloaded to a tape or formatted using the FPTRACE sample job (see SPSSAMP library). When the unload/formatting job terminates the trace files may be opened again via the TOPE command. If the trace files are already closed this command is ignored. Before closing the trace files SPS writes a trace record indicating

Maintenance

U20944-J-Z247-6-7600

the dynamic close operation and automatically issues the TINT command to write the internal trace table into the trace files.


F procid,PRTx,TCLO for CMDIF(MODIFY)

or

R xx,TCLO for CMDIF(WTOR)

TDIS Command

This command requests that SPS should display the status of the trace environment via message SPS0266I.


F procid,PRTx,TDIS for CMDIF(MODIFY)

or

R xx,TDIS for CMDIF(WTOR)

Please see the description of message SPS0266I in the SPS/MVS-APA Messages Guide for more information about this command.

TINT Command

This command requests that SPS write its internal trace table into the trace file (trace level 2 is required).

Events from some special components of SPS are only traced in the internal trace table (JES X-memory routines, open/close/put routines). The TINT command is automatically executed at normal and abnormal termination time and before the trace files are closed via the TCLO command.


F procid, PRTx, TINT for CMDIF(MODIFY)

or

R xx, TINT for CMDIF(WTOR)

TLEV Command

This command requests that SPS change the trace level specification (see TRACELEV keyword from SETUPxxx). The trace level controls the amount of information traced.

Maintenance

U20944-J-Z247-6-7600

Level 0 corresponds to the minimum trace and level 4 to the maximum of trace information.


F procid,PRTx,TLEV n for CMDIF(MODIFY)

or

R xx,TLEV n for CMDIF(WTOR)

where:

n is a digit between 0 and 4 specifying the new trace level.

TSET Command

This command requests that SPS change the trace set specification (see TRACESET keyword from SETUPxxx). The traceset controls which components from the PS (print server) FMID of SPS are traced. The traceset specifications should be changed only on request from an Océ representative.


F procid,PRTx,TSET xxxxxxxxxxxxxxxx

or

R xx,TSET xxxxxxxxxxxxxxxx

where:

xxxxxxxxxxxxxxxx is a 16 character hex string specifying the new traceset value. Each digit may be 0 - 9 or A - F (one hex digit representation). All 16 digits must be specified each time this command is 6

VSE

VSE Commands

SPS supports the necessary additional VSE/POWER operator commands for controlling the printer/s. These are:

S DEV,devname,SPS,class(es)[,PARM='logdest, ...']

devname Specifies the device name. This parameter must correspond to the name specified for the printer in the PRT keyword of the SPSPRINT system parameter member.

Maintenance

U20944-J-Z247-6-7600

SPS Specifies the subsystem id of the SPS job. The default value of the subsystem id is SPS. If you have more than one SPS job running in your VSE system at the same time you need to have a unique subsystem id for each of them. You specify the subsystem id in the PARM parameter of the EXEC statement which calls the SPS program (see the SPSTART.Z sample in your SPS sublibrary).

class(es) Specifies from one to four output classes used by POWER to select output to be printed. Enter up to four alphabetic characters not separated by commas. The order in which the classes are entered determines the order in which POWER selects output for SPS.

logdest Specifies the names of up to eight logical destinations (separated by commas and enclosed in apostrophes) to be used by VSE/POWER for the printer being started.

Default logdest for local printers is LOCAL.

Default logdest for remote printers is the devname.

PSTOP DEV,devname<,EOJ|,RESTART|,FORCE>

PFLUSH DEV,devname<,HOLD>

DDS Commands

The operator may change the class or logical destination of a printer using the following POWER operator command:

PXMIT DEV,devname,ALTER {[CLASS=c...][,][LOGDEST=(cccc,...)]}

DEV Code this operand as shown

devname Specifies the device name. This parameter must correspond to the name specified for the printer in the PRT keyword of the SPSPRINT system parameter member.

ALTER Permits the operator to alter the output classes or the logical destinations used to select output for the printer. This is done without stopping and restarting the printer.

CLASS=c... Specifies from one to four output classes used by POWER to select output to be printed. Enter up to four alphabetic characters not separated by commas. The order in which the classes are entered determines the order in which POWER selects output for SPS.

LOGDEST=(ccccc,..) Specifies from one to eight logical destination names used by POWER to select output. Enter a list of up to eight names, separated by commas. Each name is from one to eight alphameric characters in length.

Maintenance

U20944-J-Z247-6-7600

The PXMIT command may be also used to obtain status information from the printer. The following 3 subcommands are allowed:

PXMIT DEV,devname,STAT

PXMIT DEV,devname,FORM

PXMIT DEV,devname,JOBS

STAT Requests SPS to display the printer status via message SPS0270I (main line), the status of the jobs being printed via message SPS0270I (continuation lines) and the status of the trace environment via message SPS0266I. Please see the description of the mentioned messages for an explanation of the status information displayed.

FORM Requests SPS to display the printer status via message SPS0270I (main line) and the status of the user and real forms mounted on the printer via messages SPS0256I. Please see the description of the mentioned messages for an explanation of the status information displayed.

JOBS Requests SPS to display the printer status via message SPS0270I (main line) and the status of the jobs being printed via message SPS0270I (continuation lines). Please see the description of the mentioned messages for an explanation of the status information displayed.

The PXMIT command may be also used to display and change the trace environment. The following 5 subcommands are allowed:

PXMIT DEV,devname,TDIS

PXMIT DEV,devname,TOPE

PXMIT DEV,devname,TCLO

PXMIT DEV,devname,TLEV n

PXMIT DEV,devname,TSET hhhhhhhhhhhhhhhh

TDIS Requests SPS to display the status of the trace environment via message SPS0266I. This message shows if the trace files are open or closed, shows the current trace level (see TRACELEV parameter from the SETUPcuu sublibrary member) and shows the current trace set (see TRACESET parameter from the SETUPcuu sublibrary member).

TOPE Requests SPS to open and start using the trace files. If the trace files are already open this subcommand has no effect. While the trace files are open you may not run the trace formatter program. See the TRACEFILE parameter from the SETUPcuu sublibrary member.

TCLO Requests SPS to close and stop using the trace files. If the trace files are already closed this subcommand has no effect. While the trace files are closed you may run the trace formatter program to copy or format the trace records. After the formatter run

Maintenance

U20944-J-Z247-6-7600

you may open the trace files again via the TOPE subcommand. See the TRACEFILE parameter from the SETUPcuu sublibrary member.

TLEV Requests SPS to change the trace level being used. The trace level controls the amount of information traced by SPS. See the TRACELEV parameter from the SETUPcuu sublibrary member.

Is the new trace level to be used by SPS. You should specify a value between 0 and 4. Trace level 0 means no trace. Trace level 1 is a flow trace. Trace level 2 is a flow and status trace. Trace level 3 is a flow, status and control block trace. Trace level 4 is a flow, status, control block and data trace. The specified trace level remains active until the next TLEV subcommand is successfully processed or the printer is stoped and started. See the TRACELEV parameter from the SETUPcuu sublibrary member.

If you start SPS with trace level 0 or traceset (00,00,00, ...) and PSDYNTRA (NO) you are not able to activate the trace of the PS/APA componet of SPS via this command. On the other hand, when running with this options a smaller and optimized version of the PS/APA driver is used.

When you specify trace level 0 in this command or in the SETUPcuu sublibrary member SPS forces an in-storage only trace level 1 of the L### (base) component of SPS.

This reduced trace has a minimum performance impact and may help when only a dump is available to solve a problem.

TSET Requests SPS to change the trace set being used. The trace set controls the type of information traced by the SPS printer driver. Each driver (one for each printer type) may use the trace set bits in a different way and its use is not documented in this manual. A change of the trace set bits should be done only when requested from your Océ systems representative. See the TRACESET parameter from the SETUPcuu sublibrary member.

hhhhhhhhhhhhhhhh Is the new trace set to be used by SPS. You should specify 16 contiguous hexadecimal digits (0-9,A-F). The specified trace set remains active until the next TSET subcommand is successfully processed or the printer is stoped and started. See the TRACESET parameter from the SETUPcuu sublibrary member.

Maintenance

U20944-J-Z247-6-7600

8 JCL parameters

OS/390 (MVS) You specify the JCL parameters described in this section on one or both of the

following JCL statements:

DD statement

OUTPUT statement

If you specify the same parameter on both the DD and

the OUTPUT JCL statements, the parameter on the DD statement is used.

These JCL parameters are used to build a header file that is transmitted to the ROUTER server together with the spool data. The server stores this header file in reference to the print data for later printing.

The following JCL parameters are supported:

ADDRESS=(address_lines)

BUILDING=building

CHARS=(font_names)

CKPTSEC=seconds

CLASS=class

COPIES=nnn

DATACK={BLOCK | UNBLOCK | BLKCHAR | BLKPOS }

DCB=OPTCD=J

DCB=RECFM={A | M}

Maintenance

U20944-J-Z247-6-7600

DEST=[node.]name

DEST=’[node.]IP:ip_address’

DUPLEX={NO | NORMAL | TUMBLE}

FCB=pagedef_name

FORMDEF=formdef_name

FORMS=form_name

INTRAY=nnn

NAME=name

NOTIFY=([node.]userid)

OFFSETXB=nnnn[.mmm]unit

OFFSETXF=nnnn[.mmm]unit

OFFSETYB=nnnn[.mmm]unit

OFFSETYF=nnnn[.mmm]unit

OUTBIN=bin_number

OVERLAYB=overlay_name

OVERLAYF=overlay_name

PAGEDEF=pagadef_name

PRMODE={SOSI1 | SOSI2 | SOSI3 |aaaaaaaa}

PRTQUEUE=’print_queue_name’

RESFMT={P240 | P300}

ROOM=room

SEGMENT=page_count

SYSOUT=(class,,form_name)

TITLE=title

UCS=font_name

TRC={YES | NO}

For a detailed clarification of the parameters above refer to the relevant OS/390 (MVS) and JES documentation.

Maintenance

U20944-J-Z247-6-7600

VSE Extended Output Features Many output features necessary for the Océ printers cannot be specified via normal JECL parameters from the * $$ LST statement. For example, when printing on an APA printer, the user cannot specify the required FORMDEF via a normal LST parameter.

The Extended JECL Keywords are an extension to the $$ LST POWER statement. During SPS installation, these keywords are defined to power via DEFINE statements in the startup procedure for the POWER partition. To use these keywords you just need to code them in your LST statement. The Extended JECL Keywords are the primary way that should be used to specify the Extended Output Features.

There are some more sources from where the data-set characteristics may be obtained. The print data stream, APA resources PAGEDEF, FORMDEF, CHARS can also be specified in the SETUPxxx member for the ROUTER device. The JECL has priority over the SETUPxxx member parameters.

Extended JECL Keywords

The following keywords may be specified in the POWER $$ LST statement. You should take care; some syntax errors in the coding of these keywords may be detected only as it is attempted to print the corresponding output file at the final destination.

In the following figure the parameters are prefixed with (APA) and (RTR) indicating whether the parameter is supported by the relevant product. If your installation has SPS/VSE installed then those parameters prefixed with (APA) may already be defined to your POWER system.

Maintenance

U20944-J-Z247-6-7600

Figure 5: Format of the Extended JECL Keywords

Keyword Parameter Description

CKPTSEC specifies the number of seconds of elapsed time after which a checkpoint will be taken. Specify an integer from 1 to 32767. CKPTSEC should not be specified together with CKPTPAGE.

CKPTPAGE/SEC If both CKTPAGE and CKPTSEC are specified in the LST statement SPS uses the type of checkpoint value (ie, CKTPAGE or CKPTSEC) specified in the SETUPcuu member. The value of the keyword, however, is that specified in the LST statement.

If no default was specified in SETUPcuu then SPS uses the CKPTSEC keyword from the LST statement.

If the output to be printed has fewer pages than the checkpoint value specified here, then no checkpointing will be done.

Do not take checkpoints too frequently as for each checkpoint the printer has to provide the operating system with certain control information.

* $$ LST [,CKPTPAGE=sheets] (APA)

[,CKPTSEC=seconds] (APA)(RTR) [,CONTROL=SINGLE|DOUBLE|TRIPLE|PROGRAM ] (APA) [,DATACK=BLOCK|UNBLOCK|BLKCHAR|BLKPOS ] (APA)(RTR) [,FORMDEF=name] (APA)(RTR) [,PAGEDEF=name] (APA)(RTR) [,PIMSG=(YES|NO[,nnn] ) ] (APA) [,PRMODE=SOSI1|SOSI2 ] (APA)(RTR) [,TRC=YES|NO ] (APA)(RTR)[,FORMS=name (APA)(RTR) [,DUPLEX=NORMAL|TUMBLE|NO (RTR) [,INTRAY=nnn (RTR) [,OFFSETXF=nnnn[.ppp]units (RTR) [,OFFSETXB=nnnn[.ppp]units (RTR) [,OFFSETYF=nnnn[.ppp]units (RTR) [,OFFSETYB=nnnn[.ppp]units (RTR) [,OUTBIN=nnn (RTR) [,OVERLAYF=name (RTR) [,OVERLAYB=name (RTR) [,PRTQUEUE=’print queue name’ (RTR) [,RESFMT=P240|P300 (RTR) [,TITLE=title (RTR)

Maintenance

U20944-J-Z247-6-7600

If no checkpoints have been taken printing restarts from the first page.

DATACK Specifies what action is to be taken in the event of a data-check error occurring.

There are two types of data-check errors; invalid-character errors and print-position errors. Invalid-character errors occur when an attempt is made to use a code point that is not assigned to a character. Print-position errors occur when an attempt is made to print outside the valid printable area. These errors also cause an error message to be sent unless PIMSG=NO is also specified.

If error processing for an error type is BLOCK'ed the error is not reported to SPS. This may cause a loss of output data.

If error processing for an error type is UNBLOCK'ed the error is reported on the message page at the end of the print file in which it occurs. See also the PIMSG parameter for related information.

BLOCK specifies that no data-check error types should be reported to SPS.

UNBLOCK specifies that all data-check error types should be reported to SPS.

BLKCHAR specifies that invalid-character data errors will not be reported to SPS.

BLKPOS specifies that print-position errors will not be reported to SPS.

The default for this parameter is UNBLOCK. This parameter can be also specified in the printer parameter phase (SPSZPARM), in the control file, or in the DTF.

FORMDEF Specifies the one to six character name of the form definition that will be used in this print job.

Note: The complete phase name in the library consists of a two-character prefix (F1) followed by the name specified here. SPS concatenates the two parts of the name for you.

PAGEDEF Specifies the one to six character name of the page definition that will be used for a line print job.

Note: The complete phase name in the library consists of a two-character prefix (P1) followed by the name specified here. SPS concatenates the two parts of the name for you.

PRMODE Specifies that the print job contains embedded EBCDIC shift-out (SO) and shift-in (SI) controls used for switching between single-byte and double-byte fonts. At least two fonts must be specified, the

Maintenance

U20944-J-Z247-6-7600

first of which must be a single-byte font and the second of which must be a double-byte font.

Please see of the ENDBCS parameter from SETUPcuu/control file for an explanation of the different ways of using SOSI characters (IBM compatible way and enhanced SOSI processing).

SOSI1 specifies that the SO or SI code invokes the font switch and causes a blank (X'40') to replace the SOSI code.

SOSI2 specifies that the SO or SI code invokes the font switch only. No blank is inserted to replace the SOSI code.

Note: Each input line of the print job must start with a single-byte font. If the line starts with a double-font you must start the line with an SO control, irrespective of how the last line ended.

TRC Specifies whether the print records contain embedded font table reference characters (TRC's) to identify the font to be used to print each record.

DUPLEX={NO | NORMAL | TUMBLE}

Specifies whether printing is to be done on one or both sides of each sheet.

NO Requests printing on the front side of each sheet.

NORMAL

Requests printing on both sides of the sheet such that the sheets can be

bound on the long edge of the paper.

TUMBLE

Requests printing on both sides of the sheet such that the sheets can be

bound on the short edge of the paper.

FORMS=form_name

Specifies the 1- to 4-character form name.

ROUTER might use the form name you specify, along with the

class and destination values, to route the data set to a particular remote system.

Notes:

Maintenance

U20944-J-Z247-6-7600

1. Although this parameter is optional, you must specify either a class, form

name, or destination name to direct the output to a remote system and

server.

INTRAY=nnn Specifies a number from 1 to 255, which identifies the tray from which paper is

to be selected. To determine the input tray identifiers for your printer, refer to

your printer documentation.

OFFSETXB=nnnn[.mmm]unit

Specifies the offset in the x direction of the logical page origin from the media

origin for the back side of each sheet. For unit, specify one of the following

values. ROUTER converts all values to millimeters

IN Specifies a unit of inches

CM Specifies a unit of centimeters

MM Specifies a unit of millimeters

PELS Specifies a unit of picture elements (1/240 inch)

POINTS Specifies a unit of points (1/72 inch)

OFFSETXF=nnnn[.mmm]unit

Specifies the offset in the x direction of the logical page origin from the media

origin for the front side of each sheet. For unit, specify one of the following

values. ROUTER converts all values to millimeters.






OFFSETYB=nnnn[.mmm]unit

Specifies the offset in the y direction of the logical page origin from the media

Maintenance

U20944-J-Z247-6-7600

origin for the back side of each sheet. For unit, specify one of the following







OFFSETYF=nnnn[.mmm]unit

Specifies the offset in the y direction of the logical page origin from the media

origin for the front side of each sheet. For unit, specify one of the following







OUTBIN=bin_number

Specifies the number of the output bin.

OVERLAYB=overlay_name

Specifies the name of a medium overlay to be placed on the back side of each

page. The complete name of the overlay must be given inclusive of the prefix O1 if that is being used to identify overlays.

OVERLAYF=overlay_name

Specifies the name of a medium overlay to be placed on the front side of each

page. The complete name of the overlay must be given inclusive of the prefix O1 if that is being used to identify overlays.

PRTQUEUE=’print_queue_name ’

Specifies the name of a print queue for printing the data set. Specify any printable character string from 1 to 127 characters enclosed in single quotes.

RESFMT={P240 | Specifies the resolution at which the output was formatted.

Maintenance

U20944-J-Z247-6-7600

P300}

TITLE=title Specifies a 1- to 60-character description of the output data set.

Maintenance

U20944-J-Z247-6-7600

Maintenance

U20944-J-Z247-6-7600

9 Print Parameter Exit

OS/390 (MVS) The Print Parameter Exit allows the customer to extend the -opa parameter string which is used to pass relevant job information in the header file that is built for every job that PP/ROUTER transmits to target router servers.

The exit is called for each output data set that PP/ROUTER processes. The returned string, if any, is then appended to the standard -opa parameter string in the header for the data set.

The ROUTER server administrator may have to amend exits or scripts in order to support additional parameters that are appended by the sending system

A Sample source exit is loaded into the sample library from the install tape – PPRTRX01.

This sample exit builds an –opa string of device_name=PRTnnnn ,outgrp_name=nn

The input buffer that is passed to the exit contains access points to the following OS/390 (MVS) control blocks:

JSPA

SWB Text Units

Refer to the sample exit for a full explanation of the INPUT/OUTPUT requirements of the exit.

To install the Print Parameter Exit complile and link edit the suplied sample into a library that is available to the PP/ROUTER FSS.

Maintenance

U20944-J-Z247-6-7600

If the name used is not PPRTRPPX which is the default, then the SETUPxxx parameter entry PPRTRPPX(exitname) must be coded.

VSE A Sample source exit is loaded into the sample library from the install tape – PPRTRX01.

This sample exit builds an –opa string of device_name=PRTnnnn ,outgrp_name=nn

The input buffer that is passed to the exit contains access points to the following VSE fields:

JECL statements

OPTB parameters

Refer to the sample exit for a full explanation of the INPUT/OUTPUT requirements of the exit.

To install the Print Parameter Exit complile and link edit the suplied sample into a library that is available to the PP/ROUTER partition.

If the name used is not PPRTRPPX which is the default, then the SETUPxxx parameter entry PPRTRPPX(exitname) must be coded.

Maintenance

U20944-J-Z247-6-7600

10 Maintenance

Temporary Fixes Temporary fixes will be supplied by Océ, when necessary, in the form of module replacements packaged as PTF's on a standard label tape. The tape will consist of a single file containing 1 or more PTF's and associated control cards. All PTFs will be adequately documented in the comments and processable by SMPE. The standard IBM utility program SMPE should be used to install the correction(s). Figure 18, Figure 19, and Figure 20 are example jobs to receive, apply and accept a PTF tape.

The PTF processing jobs should be modified to suit installation requirements. The receive job requires the volume serial number of the PTF tape. If the SMPPTS is not dynamically allocated, this DD card must be activated and modified to show its name and location. The jobs also assume that all SPS data sets have been defined to SMPE for dynamic allocation as was suggested in the SPS installation procedures (see "SPS/MVS Installation Guide, section Allocate the SPS/MVS Install Data Sets"). If this is not the case, DD cards for each data set required must be added to the model jobs.

//RECEIVE EXEC SMPPROC //SMP.SMPPTFIN DD DSN=SMPMCS,DISP=(OLD,PASS), // VOL=SER=NNNNNN,LABEL=(1,SL), // UNIT=(TAPE,,DEFER) //SMP.SYSIN DD * (SMPCNTL) SET BDY(GLOBAL) . RECEIVE SYSMODS . /*

Figure 18: Example SMP PTF Receive Job

An apply check job should be run before an actual apply is performed. In the event a PTF applies to the SPS startio or abnormal end appendage and svclib is not dynamically allocated by SMPE, this DD card must be activated and updated to reflect the location of svclib. If linklib is used, this DD card must also be activated and updated to reflect the library location.

Maintenance

U20944-J-Z247-6-7600

//APPLY JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //APPLY EXEC SMPPROC //*SMP.SVCLIB DD DSN=SYS1.SVCLIB,UNIT=XXXX,DISP=SHR, //* VOL=SER=NNNNNN //*SMP.LINKLIB DD DSN=SYS1.LINKLIB,UNIT=XXXX,DISP=SHR, //* VOL=SER=NNNNNN //SMP.SYSIN DD * (SMPCNTL) SET BDY(SPSvrmT) . APPLY CHECK . /*

Figure 19: Example SMP PTF Apply Job

An accept should be performed only after SPS has been run with the new sysmods for a while without problems. A good approach is to accept old sysmods when new sysmods are to be applied.

//ACCEPT JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //ACCEPT EXEC SMPPROC //SMP.SYSIN DD * (SMPCNTL) SET BDY(SPSvrmD) . ACCEPT . /*

Figure 20: Example SMP PTF Accept Job

Messages

11 Performance Considerations

Memory The memory requirements of an SPS procedure varies depending on the number of printers that are to be run under one procedure and the size and number of buffers allocated for each printer. Another consideration is whether SPS re-entrant parts are in lpalib, linklib or a steplib. Storage estimates are given below for PP/ROUTER printers

Substantial real storage savings can be achieved when multiple printers are being driven, by SPS depending on how it is installed. The use of linklib or steplib will cause a copy of SPS to be loaded into each SPS address space. Each SPS address space will use a separate real storage copy of SPS. An installation that has the re-entrant portions of SPS in lpalib will only require one copy of SPS for the entire system regardless of the number of SPS procedures. Therefore, if a steplib or linklib approach has been used, it is better to have multiple printers driven by each SPS procedure. If an lpalib approach has been used, there is little advantage in having more than one printer per SPS procedure.

Most SPS code and dynamic areas are located above the line. Just some code and areas must remain below the line because of system restrictions and compatibility reasons. Data management buffers and control blocks ( trace files, system resource libraries) are located below the line and may take quite a large amount of storage. Trace files have 20 IO-buffers per default. The region estimation below is always given in the form xxx(yyy), where xxx are the requirements below the line and yyy are the requirements above the line.

PP/ROUTER Storage Estimates

When PP/ROUTER is located in a linklib or steplib and the default buffer allocations are used, an installation should allocate 200K(1.3M) of virtual storage for the first driver in a procedure and 200K(800K) for each additional driver to run under that procedure. Using these estimates an installation using steplib or linklib driving 2 printers with one procedure and 1 printer with another procedure would require 400K(2.1M) in one procedure and 200K(1.3M) in the other.

Messages

U20944-J-Z247-6-7600

When the re-entrant portions of SPS are located in lpalib and default buffer allocations are used, an installation should allocate 200K(800K) of virtual storage for each driver to be run under a procedure. Using these estimates an installation using lpalib driving 2 printers with one procedure and 1 printer with another procedure would require 400K(1.6M) in one procedure and 200K(800K) in the other.

Libraries SPS can be installed by using a steplib, linklib or lpalib. The simplest approach is to use a steplib. When an installation has only one PP/ROUTER printer, this method will have little performance impact on the system. The use of linklib instead of a steplib will reduce search time and possibly load time.

If an installation requires more than one start-up procedure, it is desirable to place SPS in lpalib to avoid multiple copies of SPS in the system (see "Memory" on page Error! Bookmark not defined.). This approach also keeps search and load time to a minimum. When all the SPS printers in the system can be driven by one procedure, little advantage will be gained through the use of lpalib. Only search and load time will be reduced, real memory requirements will remain the same.

Trace Files If you need to run PP/ROUTER collecting trace data to the trace files and you are experiencing poor transmission times, you may try to increase the number of buffers used by the access method to write to the trace files. You may do that via the BUFNO subparameter from the DCB parameter specified in both DD statements from the trace files.

Messages

U20944-J-Z247-6-7600

12 Diagnosis

Error Reporting All SPS message and abend code descriptions include instructions concerning what should be done about the problem. When suggested system programmer actions do not resolve a problem, it should be submitted to the Océ service representative with the appropriate documentation as described in this chapter.

Associated Documentation All problems reported to Océ should be accompanied by the following documentation, if possible:

The JCL and output listings of the job that encountered the error,

A listing or copy of the SPS.SPSPARM data set. If more convenient, a listing of all members used in the initialization of the printer and execution of the job. This should include the following members for printer nnn and form aaaa4 if they are used:

Member Contents

SPSPRINT Printer table

SETUPnnn SPS initialization parameters

MSGSUnnn Message table

A SYSLOG listing.

Tape copy of the PP/ROUTER trace data set(s) covering the time when the problem occurred. The trace data set should be generated by the FPTRACE job in ITF5 format (see "ITF Trace Tape Generation" in SPS/MVS Installation Guide).

4 Where nnn is either an APA or LINE printer device number and aaaa is either an APA

or LINE printer form name. 5 SPS ITF (Internal Trace Format) tapes have no relationship to the ITF (Internal Trace

Facility) delivered with Océ printers for hardware diagnostics from a PC.

Messages

U20944-J-Z247-6-7600

If an ABEND has resulted in a dump, the dump should be sent on tape.

When to Dump SPS will always take a diagnostic dump for any conditions in which it would be useful. Even when SPS is cancelled by the operator due to a wait or loop condition, no dump should be requested. The SPS ESTAE routine will receive control from the cancel command and take a user 222 dump. If a dump is requested by the operator, a second dump will be taken by the operating system.

In all situations where SPS is capable of recovering from an error and a dump would be useful for diagnostic purposes, SPS takes a dump unless the DUMP(NO) option in the SETUPnnn member for the ROUTER printer has been selected. This option is generally not recommended. In the event of an error while running with the DUMP(NO) option, the option should be changed to YES and SPS reinitialized. Then the problem should be recreated, so a dump is available to the Océ service representative.

If one SPS printer is hanging and you have other printers running under the same procedure, you should cancel the hanging printer via the F SPSx,PRTx,CANCEL command. See the SPS Administrator's Guide for more information.

When to Trace The SPS internal trace facility is one of the most useful tools for diagnosing system or SPS internal problems. The product should always be run with trace level 3 for testing, maintenance, installation, and trace level 0 for normal production. For all reproducible problems, trace data should be collected in the trace data sets at trace level 4. The trace specification may be dynamically changed via SPS commands (close and open the trace files, change the trace level and set). See the SPS Administrator's Guide for more information.

Trace Generation The suggested normal running mode for PP/ROUTER is trace level 0 and no trace data sets (TRACEFILE(NO) in SETUPnnn). This will produce a flow trace of reasonable size in an abend dump with very little system overhead and no impact on transmission time.

Messages

U20944-J-Z247-6-7600

However, if an installation is experiencing problems, PP/ROUTER should be run with large user trace data sets at trace level 4. This trace level will impact the transmission performance and place an I/O overhead on the system. GTF tracing is not recommended because GTF suppresses records when trace activity is too high. The PP/ROUTER user trace files will always contain all the trace records.

The use of the TRACETYPE and TRACESET options requires a knowledge of the internals of SPS. These options are mainly to be used as requested by an Océ service representative when special diagnostic traces are needed. Using the defaults for these options will produce all information possible. This is the suggested mode when no special request has been made by an Océ service representative.

The trace generation related parameters are TRACEFILE, TRACELEV, TRACESET and TRACETYPE. For coding information please see the respective parameters under "Printer Execution Parameters" in the PRISMAproduction ROUTER Administrator's Guide.

For all reproducible problems, in the absence of any special instructions from an Océ service representative, the trace information should be:

At trace level 4

Directed to large user trace data sets or to tape (TRACEFILE(USER))

Run with options TRACETYPE(ALL) and TRACESET(FFFFFFFFFFFFFFFF) for these parameters in the SETUPnnn member for the printer. These are the defaults when TRACETYPE and TRACESET are not specified.

ITF Trace Tape Generation Trace data generated to the PP/ROUTER trace data sets must be formatted into an ITF6 trace tape for submission to Océ. This is accomplished by running the trace formatting job FPTRACE supplied in SPS.SPSSAMP. The job can also be used to generate trace reports on site by Océ service representatives.

A example job with the correct control cards for generating an ITF trace tape can be found in Figure 23. The TROUT dd card should be adjusted to installation requirements and the input trace data sets must be set to their correct names before running.

6 SPS ITF (Internal Trace Format) tapes have no relationship to the ITF (Internal Trace

Facility) delivered with Océ printers for hardware diagnostics from a PC.

Messages

U20944-J-Z247-6-7600

//SUSER JOB 'ACCOUNT #','NAME',MSGLEVEL=(1,1) //* //* FPTRACE – UNLOAD SPS TRACE RECORDS //* //******************************************************** //* EXAMPLE JOB TO GENERATE ITF TAPE //******************************************************** //* //S1 EXEC PGM=SPSMPTRC //STEPLIB DD DSN=SPS.SPSLINK,DISP=SHR //TRMSG DD SYSOUT=* //TROUT DD DSN=ITF.desc.data,VOL=SER=volser,UNIT=TAPE, // DISP=(NEW,KEEP) //TRIN1 DD DSN=SPS.TRA1nnnn,DISP=SHR //TRIN2 DD DSN=SPS.TRA2nnnn,DISP=SHR //SYSIN DD * OUTPUT(ITF) /*

Figure 23: Example Trace Generation Job

Messages

U20944-J-Z247-6-7600

13 Messages and Codes

Conventions All messages issued by PP/ROUTER are in the following format:

RTRnnnnt PRTn: TEXT

where:

RTR Prefix identifier of all PP/ROUTER messages. nnnn Serial number of the message. t Type of message:

A Action message. This message needs an operator action or reply.

E Error message. This message occurred because of a severe error.

I Informational message.

W Warning message. Some unusual situation occurred.

PRTn JES printer name for the printer to which the message refers. The printer name is not repeated in each of the message descriptions below, but will be present in all messages that are associated with a particular printer.

All messages issued by SPS are in the following format:

SPxnnnnt PRTn: TEXT

where:

SP Prefix identifier of all SPS messages. x The component identifier of the messages. S Base fmid of SPS

nnnn Serial number of the message. t Type of message: A Action message. This message needs an operator action or reply.

Messages

U20944-J-Z247-6-7600

E Error message. This message occurred because of a severe error.

I Informational message.

W Warning message. Some unusual situation occurred.

PRTnJES printer name for the printer to which the message refers. The printer name is not repeated in each of the message descriptions below, but will be present in all messages that are associated with a particular printer.

All SPS messages are issued with routing code 7 and no descriptor code. If NOTIFY(user-list) is specified in the SETUPxxx member 'A' and 'E' type messages are sent to the requested userids also.

Messages

U20944-J-Z247-6-7600

PP/ROUTER Messages RTR0000E PRTnnnn: NO VALID LICENSE KEY, RESTRICTED MODE ACTIVE

LIMITED TO 3500 RECORDS, TRANSFER WILL TERMINATE.

Explanation There is either no valid license key for this cpu for product PP/ROUTER V3.8 in the LSCODE parameter file member for this printer (PRTnnnn) or the LSCODE parameter is missing in the SPSPRINT paramater file for this printer

SPS Action The transmission of the current print file will terminate and the print file will return to the spool in HOLD.

Operator Response

None.

Programmer Response

Either make the required parameter file entries to include a valid License Key for this CPU for product PP/ROUTER V3.8 or contact you Océ Representative in order to obtain one.

RTR0002E PRTnnnn: J=(jobname),JID=(jobnumber). NO MATCHING ROUTER TABLE ENTRY FOUND.

Explanation There was no valid routing group found in the router control table for the job.

This selection criteria is based on the jobs CLASS/DEST/FORMS values.

SPS Action The transmission is terminated and the dataset returns to the spool in HOLD.

Operator Response

None.

Programmer Response

Check that the routing table has valid entries to mach the jobs requirements.

Messages

U20944-J-Z247-6-7600

RTR0003W PRTnnnn: J=(jobname),JID=(jobnumber). ROUTER CHECKPOINT VALUE DOES NOT MATCH SERVERS BYTES RECEIVED S=ipaddress , DATASET WILL BE HELD.

Explanation Checkpointing is active for the current dataset and the checkpoint value that would be used by ROUTER for the current checkpoint does not match the servers value of the number of bytes received since the start of the job or from the last checkpoint value.

SPS Action The transmission is terminated and the dataset is returned to the spool in HOLD.

Operator Response

Release and retransmit the dataset if the problem persists then inform the Network Administrator.

Programmer Response

None.

RTR0004W PRTnnnn: J=(jobname),JID=(jobnumber). ROUTER EOF VALUE DOES NOT MATCH SERVERS BYTES RECEIVED S=ipaddress, DATASET WILL BE HELD.

Explanation The EOF byte count from ROUTER does not match the number of bytes received by the server for the current dataset.

SPS Action The transmission is terminated and the dataset is returned to the spool in HOLD.

Operator Response

Release and retransmit the dataset if the problem persists then inform the Network Administrator.

Programmer Response

None.

Messages

U20944-J-Z247-6-7600

RTR0005I PRTnnnn: J=(jobname),JID=(jobnumber). CHECKPOINT RESTART FAILED, FILE NO LONGER EXISTS ON THE SERVER S=ipaddress , DATASET WILL BE RESTARTED FROM THE BEGINNING.

Explanation The current dataset has a valid ROUTER checkpoint record. However when a restart was attempted to the specified server it was found that the partially transmitted file no longer exists on that server.

The transmission will restart from the beginning of the file.

SPS Action None.

Operator Response

None.

Programmer Response

None.

RTR0006I PRTnnnn: J=(jobname),JID=(jobnumber). CHECKPOINT RESTART FAILED, ROUTER CHECKPOINT VALUE DOES NOT MATCH SERVERS S=ipaddress , DATASET WILL BE RESTARTED FROM THE BEGINNING.

Explanation The current dataset has a valid ROUTER checkpoint record. However when a restart was attempted from the checkpoint restart position the server rejected the restart as the checkpoint values did not match.

The transmission will restart from the beginning of the file.

SPS Action None.

Operator Response

None.

Programmer Response

None.

RTR0007I PRTnnnn: J=(jobname),JID=(jobnumber).COMMAND JEScommand NOT SUPPORTED, TRANSFER WILL CONTINUE.

Explanation The JES command that was issued is not supported by the ROUTER driver.

SPS Action None. The command is rejected.

Messages

U20944-J-Z247-6-7600

Operator Response

None.

Programmer Response

None.

RTR0008W PRTnnnn: ERROR IN ROUTER TABLE, INVALID KEYWORD, ENTRY IGNORED LINE=line_number DATA=keyword_value

Explanation The keyword identified in DATA at the line number identified by LINE in the ROUTER control table is incorrect the entry is ignored. If the keyword is not a required keyword then processing will continue with the default value for the keyword. If the keyword is a required keyword then the group will be disabled.

SPS Action Processing continues with the next keyword entry.

Operator Response

When the keywords that where in error are corrected then STOP and START the printer in order to activate the corrected ROUTER control table.

Programmer Response

Correct the keyword entries that are in error.

RTR0009W PRTnnnn: ERROR IN ROUTER TABLE, GROUP=group_number ALL REQUIRED KEYWORDS ARE NOT DEFINED THE GROUP IS DISABLED.

Explanation The Group entry number group_number is failing or has incorrectly defined, required, keywords. The Group entry is disabled.

SPS Action Processing continues with the Group entries that are correct.

Operator Response


Programmer Response


Messages

U20944-J-Z247-6-7600

RTR0010W PRTnnnn: ERROR IN ROUTER TABLE, KEYWORD=keyword_name, LINE=line_number, MORE THAN maximum_number _parms PARAMETERS DEFINED. KEYWORD IGNORED.

Explanation A ROUTER control table keyword was found identified by KEYWORD at line LINE with more that the allowed maximum_number_parms for that keyword.

SPS Action The keyword entry is ignored. Processing continues with the next keyword.

Operator Response


Programmer Response


RTR0011W PRTnnnn: ERROR IN ROUTER TABLE, KEYWORD=keyword_name, LINE=line_number, PARAMETER LENGTH ERROR, > maximum_length_parm CHARACTERS. KEYWORD IGNORED.

Explanation A ROUTER control table keyword was found identified by KEYWORD at line LINE with a parameter that has a length greater than the allowed maximum_length_parm for that keyword.


Operator Response


Programmer Response


RTR0012W PRTnnnn: ERROR IN ROUTER TABLE, KEYWORD=keyword_name, LINE=line_number, PARAMETER OUTSIDE OF ALLOWED RANGE OF maximum_number_parms. KEYWORD IGNORED.

Explanation A ROUTER control table keyword was found identified by KEYWORD at line LINE with a set of parameters greater than the allowed maximum_number_parms for that keyword.


Operator Response


Messages

U20944-J-Z247-6-7600

Programmer Response


RTR0013W PRTnnnn: ERROR IN ROUTER TABLE, KEYWORD=keyword_name, LINE=line_number INVALID IP ADDRESS FORMAT given_ipaddress. KEYWORD IGNORED.

Explanation A ROUTER control table keyword was found identified by KEYWORD at line LINE with an ipaddress entry given_ipaddress that does not conform to the format of ip addresses.


Operator Response


Programmer Response


Explanation

SPS Action None.

Operator Response

None.

Programmer Response

None.

RTR1000E PRTnnnn: Print Parameter Exit exitname not found.

Explanation A print parameter exit was specified in the SETUPxxx member for the printer PRTnnnn. This member was not found in the active library chain.

Messages

U20944-J-Z247-6-7600

SPS Action Following message RTR1000E a user abend 512 is performed without a dump and the printer is terminated.

Operator Response

Report this error to your ROUTER administrator.

Programmer Response

Correct the PPRTRPPX keyword entry in the SETUPxxx member for the printer.

Explanation

SPS Action None.

Operator Response

None.

Programmer Response

None.

Messages

U20944-J-Z247-6-7600

RTR8001E PRTnnnn: UNABLE TO INITIALIZE SOCKET SET. RC=socket_rc

Explanation ROUTER was unable to establish a socket set for the reason indicated by socket_rc.

SPS Action The current dataset is returned to the spool in HOLD.

Operator Response

Check that the TCPIP application is active that ROUTER uses. If the application is active then stop the device and report the problem to the System Administrator.

Programmer Response

Ensure that the router control table has the correct TCPIP application defined in the TCPNAME keyword and that the application is active.

Problem Determination

Report this problem to your Océ Representative with the following.

Console output

SPS trace level 3 (SETUP member)

Dump if produced

TCPIP trace if required.

RTR8002E PRTnnnn: UNABLE TO CREATE SOCKET. RC=socket_rc

Explanation ROUTER was unable create a socket in the current active socket set for the reason indicated by socket_rc.


Operator Response

Check that the TCPIP application is active that ROUTER uses. If the application is active then stop the device and report the problem to the System Administrator.

Programmer Response

Ensure that the router control table has the correct TCPIP application defined in the TCPNAME keyword and that the application is active.



Console output


Dump if produced


Messages

U20944-J-Z247-6-7600

RTR8003E PRTnnnn: UNABLE TO CONNECT TO S=server_ip_address P=server_port_number. RC=socket_rc

Explanation ROUTER was unable make a socket connection to server identified by server_ip_address at port server_port_number for the reason indicated by socket_rc.

SPS Action The connection attempt will be retried. The number of retry attempts and the time interval between these attempts are specified in the router control table.

If ROUTER is still unable to connect to the server the current dataset is returned to the spool in HOLD.

Operator Response

Ensure that the server is active and that the TCPIP application used is also active.

Programmer Response

Ensure that the correct server and port destination are defined.



Console output


Dump if produced


RTR8004E PRTnnnn: UNABLE TO CONNECT TO S=server_ip_address,P=server_port_number. RC=socket_rc. ATTEMPT=(attempt_number OF retry_count), RETRY INTERVAL=(retry_interval:SECONDS).

Explanation Following a network error ROUTER is retrying a connection to the server,

SPS Action The connection has failed again for the reaseon in socket_rc. A further retry attempt may or may not be made based on the retry count and interval as specified in the ROUTER control table and also indicated in the message text.

Operator Response

Ensure that the server is active and that the TCPIP application used is also active.

Programmer Response

Ensure that the correct server and port destination are defined.

Messages

U20944-J-Z247-6-7600



Console output


Dump if produced


RTR8006E PRTnnnn: ERROR WITH ROUTER CONNECTION UNABLE TO SEND DATA. RC=socket_rc

Explanation ROUTER is unable to send data to the server due to a socket error.


Operator Response

Check the socket_rc, that the server is available and that the download application is active on the server.

Programmer Response

Check the network connection to the server and that the download application on the server is functioning correctly.



Console output


Dump if produced


RTR8008E PRTnnnn: ERROR WHEN CLOSING SOCKET CONNECTION. S=server_ip_address,P=server_port_number, USING SOCKET=socket_rc

Explanation ROUTER received a bad return code when attempting to cloase the socket connection to the server.

SPS Action None.

Operator Response


Programmer Response


Messages

U20944-J-Z247-6-7600



Console output


Dump if produced


RTR8009E PRTnnnn: ERROR SERVER IS NOT IN A RECEIVING STATE. S=server_ip_address,P=server_port_number

Explanation ROUTER is attempting to send data to the server and the server has indicated that it is not in a state to be able to receive data.

SPS Action ROUTER will attempt to send the data following the retry interval specified in the router control table for the specified connection.

Operator Response

Check that the server is active and that the download application on the server at the specified port is active.

Programmer Response

Check for network errors to the specified server.



Console output


Dump if produced


RTR8010E PRTnnnn: ERROR SERVER IS NOT RESPONDING. S=server_ip_address,P=server_port_number

Explanation ROUTER is awaiting confirmation from the server from a transmission. The server has not responded.


Operator Response


Messages

U20944-J-Z247-6-7600

Programmer Response




Console output


Dump if produced


Explanation

SPS Action None.

Operator Response

None.

Programmer Response

None.

Messages

SPS Messages

OS/390 (MVS)

Insert the SPSnnnnn messages from the MVS message guide

VSE

Insert the SPSnnnnn messages from the VSE message guide

SPS Abend Codes Please report the problem and abend termination code information to your Océ support representative.

Messages

U20944-J-Z247-6-7600

Appendix A OS/390 REXX Alternate Library Installation The REXX Alternate Library should be installed into the relevant SPS CSI as the REXX Alternate Library is part of the SPS/MVS-ROUTER shipment.

This section contains the instructions for the installation of the Alternate Library.

These instructions must be provided by the software developer when the Alternate

Library is included as part of an application. To prevent installation problems, they

must be sent exactly as they are given here.

1. Determine if the IBM Library for SAA REXX/370 Release 3 (FMID HWJ9130) or

the Alternate Library (FMID HWJ9133) is installed. If either one is installed, you

need take no further action.

If Release 1 (FMID HWJ9110) or Release 2 (FMID HWJ9120) of the Library is

installed, you must install Release 3. Once Release 3 is installed, you need

take no further action.

2. Use SMP/E to RECEIVE the Alternate Library (FMID HWJ9133).

3. Allocate these data sets:

Note: In these instructions, we refer to high level qualifiers 1 and 2 of the

Alternate Library as follows:

High level qualifier 1: SPS

High level qualifier 2: V380

Messages

U20944-J-Z247-6-7600

High level qualifier 3: REXX

High level qualifier 4: V1R3M0

In your installation these two qualifiers could be different.

To perform the allocations, you can use the sample EAGKALLO, which is in data

set SPS.V380.HWJ9133.F4, which was created by the RECEIVE step.

4. Add data definitions (DDDEFs) for the following ddnames:

SEAGALT

AEAGMOD1

SEAGMENU

AEAGMENU

SEAGSAM

AEAGSAM

SEAGJENU

AEAGJENU

You can do it with this UCLIN:

5. Alternate Library Data Set Characteristics

Data Set Name Space RECFM LRECL BLKSIZE

SPS.V380.REXX.V1R3M0.SEAGALT (32760,(12,12,4)) U 32760

SPS.V380.REXX.V1R3M0.AEAGMOD1 (32760,(20,190,32)) U 32760

SPS.V380.REXX.V1R3M0.SEAGMENU (27998,(10,10,2)) VB 255 27998

SPS.V380.REXX.V1R3M0.AEAGMENU (27998,(10,10,2)) VB 255 27998

SPS.V380.REXX.V1R3M0.SEAGSAM (27920,(10,10,2)) FB 80 27920

SPS.V380.REXX.V1R3M0.AEAGSAM (27920,(10,10,2)) FB 80 27920

Messages

U20944-J-Z247-6-7600

SPS.V380.REXX.V1R3M0.SEAGJENU (27920,(5,5,2)) FB 80 27920

SPS.V380.REXX.V1R3M0.AEAGJENU (27920,(5,5,2)) FB 80 27920

SET BDY(TGTZONE).

UCLIN.

ADD DDDEF(SEAGALT) DA(SPS.V380.REXX.V1R3M0.SEAGALT) SHR.

ADD DDDEF(AEAGMOD1) DA(SPS.V380.REXX.V1R3M0.AEAGMOD1) SHR.

ADD DDDEF(SEAGMENU) DA(SPS.V380.REXX.V1R3M0.SEAGMENU) SHR.

ADD DDDEF(AEAGMENU) DA(SPS.V380.REXX.V1R3M0.AEAGMENU) SHR.

ADD DDDEF(SEAGSAM) DA(SPS.V380.REXX.V1R3M0.SEAGSAM) SHR.

ADD DDDEF(AEAGSAM) DA(SPS.V380.REXX.V1R3M0.AEAGSAM) SHR.

ADD DDDEF(SEAGJENU) DA(SPS.V380.REXX.V1R3M0.SEAGJENU) SHR.

ADD DDDEF(AEAGJENU) DA(SPS.V380.REXX.V1R3M0.AEAGJENU) SHR.

ENDUCL.

SET BDY(DLIBZONE).

UCLIN.

ADD DDDEF(AEAGMOD1) DA(SPS.V380.REXX.V1R3M0.AEAGMOD1) SHR.

ADD DDDEF(AEAGMENU) DA(SPS.V380.REXX.V1R3M0.AEAGMENU) SHR.

ADD DDDEF(AEAGSAM) DA(SPS.V380.REXX.V1R3M0.AEAGSAM) SHR.

ADD DDDEF(AEAGJENU) DA(SPS.V380.REXX.V1R3M0.AEAGJENU) SHR.

ENDUCL.

The UCLIN can be found in the sample EAGKDDD, which is in data set

SPS.V380.HWJ9133.F4, which was created by the RECEIVE step.

6. Now you can install the Alternate Library using APPLY/ACCEPT. Sample JCL for

the next steps is provided in data set REXX.V1R3M0.HWJ9133.F4, which was

created by the RECEIVE step.

Messages

U20944-J-Z247-6-7600

a. Use the JCL sample EAGKAPQ to verify that SMP/E is ready to perform the

APPLY step. If the job finishes with a return code of zero, use the JCL

sample EAGKAPP to perform the APPLY.

b. Use the JCL sample EAGKACQ to verify that SMP/E is ready to perform the

ACCEPT step. If this job finishes with a return code of zero, use the JCL

sample EAGKACC to perform the ACCEPT.

6. Install the Compiler Programming Table.

The Compiler Programming Table (CPT) IRXCMPTM is the TSO/E module that

identifies one or more alternate exec processors and their corresponding

interface routines to TSO/E. When a program is compiled by the REXX/370

Compiler, the compiled exec contains the name of the REXX/370 Library as the

alternate exec processor. The CPT must be updated to include the Alternate

Library. Your installation uses either the default table in SYS1.LINKLIB shipped

with TSO/E, or an installation-defined CPT.

To replace the default IRXCMPTM shipped with TSO/E, use the SMP/E usermod

example EAGKUMOD, which is in data set REXX.V1R3M0.SEAGSAM. This

prevents inadvertent updates of the CPT. If IRXCMPTM is updated by program

service, SMP/E issues a warning. If the ++SRC statement in EAGKUMOD is:

++SRC (EAGKCPT) SYSLIB(SEAGSAM) DISTLIB(AEAGSAM)

Change it to:

++SRC (IRXCMPTM) SYSLIB(SAMPLIB) DISTLIB(ASAMPLIB)

Messages

U20944-J-Z247-6-7600

If you are installing the Alternate Library in the same zone as TSO/E, this

replaces the default IRXCMPTM in the SYS1.LINKLIB with the updated

IRXCMPTM. If you are installing the Alternate Library in a different zone to

TSO/E, you must manually replace IRXCMPTM in SYS1.LINKLIB after running

EAGKUMOD.

To replace an installation-defined IRXCMPTM, perform the following steps:

a. Get the source for the installation-defined IRXCMPTM.

b. Copy the installation-defined statements for the Alternate Library into the

usermod example EAGKUMOD in REXX.V1R3M0.SEAGSAM.

c. Set the number of entries in the table to the number of entries in the

installation-defined CPT plus 1. This ensures that the Alternate Library can

be used concurrently with the other runtime libraries specified in the

installation-defined CPT.

d. Assemble and link-edit the updated IRXCMPTM.

e. Replace the existing IRXCMPTM.

f. Update the REXX/370 program directory. The program directory changes

are handled via PSP bucket updates and program directory replacement. If

you are a vendor, you must change the EAGKUMOD sample that you deliver

to your customers. Change:

++SRC (EAGKCPT) SYSLIB(SEAGSAM) DISTLIB(AEAGSAM)

To:

++SRC (IRXCMPTM) SYSLIB(SAMPLIB) DISTLIB(ASAMPLIB)

7. Install REXX.V1R3M0.SEAGALT, the Alternate Library, in the system LINKLIST.

Messages

U20944-J-Z247-6-7600

Do not place the Alternate Library either in the LPA or in a STEPLIB for the

application

Messages

Appendix B Problem Documentation

This section provides a list of information useful to the Océ representative in diagnosing an SPS problem reported by the APA print driver (messages beginning with SPI or ATC's from the APA driver). All of the information may not be available. Try to provide as much of the information as possible taking into consideration the utility of the item in relationship to the error message or abend termination code issued. The list below includes the collection of some diagnostic data items that will require the help of your Océ representative.

HISTORY and ENVIRONMENTAL data is helpful for the analysis of any problem

1. Description of the sequence or process that produced the message or abend termination code

2. List of any special system components

3. System log output

4. Output from the PTFI, PRTI, SDIS and FDIS SPS commands (or PRINTSET and PRINTOPT SPSPARM options)

PRINT DATA producing the problem

1. Print file

2. JCL used

3. Resources requested (form definition, page definition, overlays, page segments, code pages, coded fonts, font character sets)

PRINTOUT is useful for a quick overview

1. Faulty print

2. Reference print (if available)

TRACE is needed for any time dependent and abend analysis.

1. SPS standard trace data (run FPTRACE procedure)

2. Silent trace (will require FE help in collection)

3. Functional code trace (will require FE help in collection)

Messages

U20944-J-Z247-6-7600

4. "Sniffy" trace (will require FE help in collection)

SYSTEM DUMP is always required to diagnose abend conditions

1. DUMP(s) produced by SPS termination routines

Any other dumps produced during the failure

List of Tables

U20944-J-Z247-6-7600

List of Tables Fehler! Es konnten keine Einträge für ein Abbildungsverzeichnis gefunden werden.

U20944-J-Z247-6-7600

Bibliography

U20944-J-Z247-6-7600

Bibliography • SPS/MVS-APA Administrator's Guide U21020-J-Z247-X-7600

• SPS/MVS-APA Messages Guide U21745-J-Z247-X-7600

Index

U20944-J-Z247-6-7600

Index

accepting PP/ROUTER 71, 107

accepting SPS 52

applying SPS 28, 56, 87

ASPSDLIB 25, 56, 87

ASPSMESS 25, 56, 87

ASPSSAMP 25, 56, 87

authorising SPS libraries See RACF

Blocking data checks 139

Carriage control

forced space 139 40, 41, 42

Checkpoint interval 139

CKPTPAGE 139

CKPTSEC 139

Classes

altering 128 commands, SPS 123

component id 75, 94

CONTROL 139

50

50 Control File

concept 133 control statement format 65, 99

customization 73

data sets

allocation 49, 50 50 execution 49, 62, 109, 113 install 24, 56, 87

DATACK 139

34 35, 81, 82

35, 39, 58, 89 81, 82

descriptor codes 156

DEVICE statement (JES) 39

diagnosis 150

distribution tapes

format 20, 55, 86, 94 volume serial 20, 55, 86, 94

dumps 151

Index

136 U20944-J-Z247-6-7600

Error message supression 140

error reporting 150

See operating system requirements

examples 19

execution data sets 49, 62, 109, 113

Extended JECL

CKPTPAGE 139 CKPTSEC 139 concept 133 CONTROL 139 DATACK 139 description of parameters 133 FORMDEF 140 PAGEDEF 140 PIMSG 140 PRMODE 140 TRC 140

extended output features 133

41 FMID's (SPS) 19

Font selection 140

FORM subcommand

of PXMIT command 129 FORMDEF 140

FSA See functional subsystem application

FSI See functional subsystem interface

FSS See functional subsystem

FSSDEF statement (JES) 39, 58, 89

functional subsystem 13, 39, 58, 89

functional subsystem application 13

functional subsystem interface 13

IEAAPF00 30

IEFSD060 31

IEFSDPPT 31 See also program properties table

install

POWER JECL defines in AUTOSTART 95 TCPIP server definitions 97

install jobs 19

accept 52, 71, 107 apply 28, 56, 87 LPA installation 26, 27 receive 24, 56, 87 31

Installation 73

installation parameters 49

installation tapes 73

34

JOBS subcommand

of PXMIT command 129

libraries 149

LINKLST installation 27

Logical destination

altering 128 LPALIB installation 26

maintenance 146

Index

U20944-J-Z247-6-7600

maintenance jobs

accept 147 memory requirements 148

message format 154

messages 154–69

descriptor codes 156 format 154 routing codes 156

31 31 31

model jobs 19 See also maintenance jobs See also install jobs

MSHP install 75, 94

naming considerations

ddnames 62, 110, 113

operating system requirements

15, 16 MVS/XA 15

operation 123

Output features

extended 133

42, 43 overviews

install 18, 85, 93 PP/ROUTER install 54 processing 13

PAGEDEF 140

parameter library members 49

performance 148

libraries 149 memory 148

PIMSG 140

PPT See program properties table

Printer status

obtaining 129 PRINTERnn statement (JES) 39

PRMODE 140

problem reporting 150

product id 75, 94

program properties table 31

PRTnnnnn statement (JES) 39, 58, 89

PXMIT command 128

FORM subcommand 129 JOBS subcommand 129 STAT subcommand 129 TCLO subcommand 129 TDIS subcommand 129 TLEV subcommand 129 TOPE subcommand 129 TSET subcommand 129

RACF

control data sets 51 SPS libraries 51 SPS started tasks 51 start-up procedures 51

receiving SPS 24, 56, 87

reentrant phases 83

rexx requirements 117

routing codes 156

Index

138 U20944-J-Z247-6-7600

SCHED00 See program properties table

Shift-in controls 140

Shift-out controls 140

spool file parameters 15

SPS

installation tapes 73 31

SPSLINK 25, 56, 87

SPSMESS 25, 56, 63, 87, 111, 114

SPSMPTRC 153

SPSPARM 63, 111, 114

SPSSAMP 25, 56, 87

SPST1ddd 115

SPST2ddd 115

SPSWnnnn 115

startio appendage 28

start-up procedures 107–16

authorization 51 ddnames 62, 110, 113 execution data sets 62, 109, 113 109 installing 46, 61, 92 real storage considerations 61, 109, 112 virtual storage considerations 61, 109, 112

STAT subcommand

of PXMIT command 129 statement syntax 65, 99

Status of printer

obtaining 129 STEPLIB 63, 111, 114

support summary

APA 16

syntax 65, 99

SYSABEND 63, 111, 114

system parameter members

control statement format 65, 99 system parameters

syntax 65, 99 SYSUDUMP 63, 111, 114

tapes

of SPS product 73 TCLO subcommand

of PXMIT command 129 TDIS subcommand

of PXMIT command 129 TLEV subcommand

of PXMIT command 129 TOPE subcommand

of PXMIT command 129 trace 116

example formatting job 153 formatting job 153 how to 151 ITF tape generation 152 when to 151

Trace environment

display of 129 Trace files

dynamic open close 129

Trace level

changing 129 Trace set

changing 129 TRC 140

Index

U20944-J-Z247-6-7600

TSET subcommand

of PXMIT command 129

VSE & VM printer definitions

install 95 VSE start-up job

installing 97

VSE/POWER

AUTOSTART 80 AUTOSTART statement 80 DEFINE statement 80

35, 81

XA See operating system requirements See operating system requirements

prismaproduction router...

Documents