DJP User's Guide - Welcome to Support On Line...

DJP

User's Guide

DPS

7000/XTA

NO

VASC

ALE

7000

Communications: Applications

REFERENCE47 A2 14UC 05

DPS7000/XTANOVASCALE 7000

DJPUser's Guide

Communications: Applications

January 1998

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE47 A2 14UC 05

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 1995, 1998

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

Intel® and Itanium® are registered trademarks of Intel Corporation.

Windows® and Microsoft® software are registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is a registered trademark of Linus Torvalds.

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

47 A2 14UC Rev05 iii

Preface

OBJECTIVE OF THIS MANUAL

This document describes the Distributed Job Processing facility within a DSA networkbetween two DPS 7/7000s and between a DPS 7/7000 and a DPS 6.

It explains the sequence of events for job submission and execution, and how to obtainthe results of the job.

UFT (Unified File Transfer) must be present on the DPS 7/7000 for DJP to function. Forcommands specific to UFT operations, see the GCOS 7 V7 UFT User's Guide.

On the DPS 6, remote processing is performed by the Extended UFT function. Refer tothe DPS 6 UFT User's Guide.

INTENDED READERSHIP

The manual is intended as a user guide and reference manual for system engineers,analyst/programmers, users and console operators who send jobs to be processed onremote systems.

DJP User's Guide

iv 47 A2 14UC Rev05

STRUCTURE OF THE MANUAL

Section 1 introduces the functions of DJP.

Section 2 describes job submission and execution between twoDPS 7/7000s, and how to obtain the results of the job.

Section 3 describes job submission and execution between theDPS 7/7000 and the DPS 6, and vice versa, and how toobtain the results of the job.

Appendix A gives the syntax and parameter description of jobprocessing commands.

Appendix B explains network generation and the job processingcapability in relation to the file transfer capability of thesystem according to its profile.

Appendix C describes the rules affecting the security and access inthe DJP environment.

Appendix D describes cataloging projects, users, stations andsystems in the DPS 7/7000 site catalog.

Appendix E details the parameters WHEN, EVERY and RRESTART.

Appendix F lists JOR and operator messages, and status codes.

ASSOCIATED DOCUMENTS

The following publications may be referred to for further details on topics mentioned in thismanual:

DSA: Development of Distributed Applications ................................................ 39 A2 9731

GCOS 7-V7 UFT User Guide......................................................................... 47 A2 13UC

Networks: Overview and Concepts................................................................ 47 A2 92UC

IOF Terminal User's Reference Manual Vol 1................................................. 47 A2 38UJIOF Terminal User's Reference Manual Vol 2................................................. 47 A2 39UJIOF Terminal User's Reference Manual Vol 3................................................. 47 A2 40UJ

System Operator's Guide Release V7 .............................................................47 A2 47US

System Operator's Guide Release V8 .............................................................47 A2 53US

DPS 6 UFT User's Guide .................................................................................69 A2 CZ92

GTWriter User's Guide.................................................................................... 47 A2 55UU

Preface

47 A2 14UC Rev05 v

REMARKS FORM

Suggestions and criticisms concerning the form, content and purpose of this manual areinvited. A Remarks Form is provided at the end of the manual for this purpose.

NOTATION CONVENTIONS FOR SYNTAX FORMS

The following notation conventions are used in the GCL in this manual:

UPPERCASE The keyword or system message is written exactly asshown.

lowercase Indicates a user-supplied parameter.

[item] An item with square brackets is optional.

{item1}{item2}{item3}

A column of items within braces means that one valuemust be selected if the associated parameter is specified.If the parameter is not specified the underlined item istaken as the default value.

( ) Parentheses must be used if they enclose more than oneitem.

... An ellipsis indicates that the preceding item may berepeated one or more times.

DJP User's Guide

vi 47 A2 14UC Rev05

47 A2 14UC Rev05 vii

Table of Contents

1. Distributed Job Processing ............................................................................ 1-1

1.1 TERMINOLOGY ......................................................................................................... 1-1

1.2 DESCRIPTION OF DJP .............................................................................................. 1-2

1.2.1 DJP Functions ........................................................................................................... 1-21.2.2 DJP Prerequisites ...................................................................................................... 1-21.2.3 DJP Services .............................................................................................................. 1-21.2.4 Job Submission ........................................................................................................ 1-3

2. Distributed Job Processing DPS 7/7000 <--> DPS 7/7000 ................. 2-1

2.1 JOB SUBMISSION ..................................................................................................... 2-1

2.2 DESTINATION OF JOB OUTPUT .............................................................................. 2-5

3. Distributed Job Processing DPS 7/7000 <--> DPS 6 ............................ 3-1

3.1 DJP WITH DPS 6 ........................................................................................................ 3-1

3.2 DPS 7/7000 --> DPS 6 ................................................................................................ 3-2

3.2.1 Job Submission ........................................................................................................ 3-23.2.2 Obtaining the Results of the Job ............................................................................. 3-3

DJP User's Guide

viii 47 A2 14UC Rev05

3.3 DPS 6 --> DPS 7/7000 ................................................................................................ 3-5

3.3.1 Job Submission ........................................................................................................ 3-53.3.2 Obtaining the JOR and SYSOUT ............................................................................. 3-6

Table of Contents

47 A2 14UC Rev05 ix

Appendices

A. Job Processing Commands ........................................................................... A-1

A.1 CO (CANCEL_OUTPUT) ............................................................................................ A-3

A.2 CUR (CANCEL_USER_REQ) .................................................................................... A-6

A.3 DC (DISPLAY_CONFIGURATION) ............................................................................ A-8

A.4 DDJP (DISPLAY_DJP) ............................................................................................... A-11

A.5 DJ (DISPLAY_JOB) ................................................................................................... A-15

A.6 DLD (DISPLAY_LOAD) .............................................................................................. A-19

A.7 DO (DISPLAY_OUTPUT) ........................................................................................... A-23

A.8 DSO (DISPLAY_SECURITY_OPTIONS) ................................................................... A-26

A.9 DUR (DISPLAY_USER_REQ) .................................................................................... A-29

A.10 ENTER_JOB_REQ (EJR, EJ) .................................................................................... A-32

A.11 FO (FORCE_OUTPUT) .............................................................................................. A-41

A.12 FUR (FORCE_USER_REQ) ....................................................................................... A-42

A.13 HUR (HOLD_USER_REQ) ......................................................................................... A-43

A.14 MDC (MODIFY_CONFIGURATION) .......................................................................... A-44

DJP User's Guide

x 47 A2 14UC Rev05

A.15 MDDJP (MODIFY_DJP) ............................................................................................. A-46

A.16 MODIFY_OUTPUT (MDO, MO) ................................................................................. A-49

A.17 MDOP (MODIFY_OUTPUT_PARAMETERS) ............................................................ A-53

A.18 MDST (MODIFY_STATION)....................................................................................... A-56

A.19 MDUR (MODIFY_USER_REQ) .................................................................................. A-59

A.20 RUR (RELEASE_USER_REQ) .................................................................................. A-62

A.21 SIR (START_INPUT_READER) ................................................................................. A-64

A.22 SOW (START_OUTPUT_WRITER) ........................................................................... A-65

A.23 TIR (TERMINATE_INPUT_READER) ........................................................................ A-70

A.24 TOW (TERMINATE_OUTPUT_WRITER) .................................................................. A-71

B. Network Generation ........................................................................................... B-1

B.1 SYSTEM PROFILES .................................................................................................. B-1

B.2 DPS 7/7000 FILE TRANSFER CAPABILITIES .......................................................... B-2

B.2.1 Transfer DPS 7/7000 <---> DPS 7/7000 .................................................................... B-2B.2.2 Transfer DPS 7/7000 <---> non-DPS 7/7000 ............................................................ B-3B.2.3 Profiles and RFA Capabilities .................................................................................. B-4

B.3 NETWORK GENERATION ON THE DPS 7/7000 ...................................................... B-6

B.3.1 Network Schematic Description .............................................................................. B-7B.3.2 Low-Level Directives ................................................................................................ B-8B.3.3 High-Level Directives ................................................................................................ B-10

Table of Contents

47 A2 14UC Rev05 xi

C. DJP Security and Access Control Rules ................................................... C-1

C.1 PRINCIPLES OF GCOS 7 SECURITY ....................................................................... C-3

C.1.1 USER, PROJECT, BILLING, APPLICATION, STATION and SITE .......................... C-3C.1.2 Identities of JOB Submitter and JOB Owner .......................................................... C-4

C.2 DJP SECURITY CHECKS .......................................................................................... C-5

C.2.1 Checks Always Performed ....................................................................................... C-5C.2.2 Additional Checks when CHKPW=NO ..................................................................... C-6C.2.3 Additional Checks when CHKPW=YES ................................................................... C-6C.2.4 Remote JOB Execution Request from GCOS 7 V5 Site to V6 or V7 Site ............. C-6C.2.5 Remote JOB Execution Request from GCOS 7 V6 or V7 Site to V5 Site ............. C-6C.2.6 Computation Rules for JOB Owner Identity ........................................................... C-7C.2.7 Summary of DJP Security Checks ........................................................................... C-7

C.3 EXAMPLE OF SITE.CATALOGS AT REQUESTING AND EXECUTING SITES ...... C-10

C.3.1 Example when CHKPW=NO ..................................................................................... C-10C.3.2 Example when CHKPW=YES ................................................................................... C-11

D. Site Catalog ........................................................................................................... D-1

D.1 CATALOGING A PROJECT ....................................................................................... D-2

D.1.1 Defining the List of Applications for a Project ....................................................... D-2D.1.2 Defining the List of Stations for a Project .............................................................. D-3

D.2 CATALOGING A STATION AND DEFINING THE ASSOCIATED LIST OF SITES .. D-4

E. WHEN, EVERY and RRESTART .................................................................... E-1

E.1 WHEN ......................................................................................................................... E-1

E.1.1 Absolute Addressing ................................................................................................ E-1E.1.2 Relative Addressing .................................................................................................. E-3E.1.3 Fast Options .............................................................................................................. E-3E.1.4 FORCE Option ........................................................................................................... E-4

E.2 EVERY ........................................................................................................................ E-5

E.3 RRESTART ................................................................................................................. E-7

DJP User's Guide

xii 47 A2 14UC Rev05

F. Messages and Status Codes .......................................................................... F-1

F.1 REPORTING ............................................................................................................... F-1

F.1.1 JOR at Local and Remote Sites ............................................................................... F-1F.1.2 RFA Messages ........................................................................................................... F-3F.1.2.1 Messages.................................................................................................................... F-4F.1.2.2 Details on RFA Messages........................................................................................... F-18

F.1.3 Messages Coming from Server Site ........................................................................ F-23F.1.3.1 Format and Explanation of Messages......................................................................... F-23F.1.3.2 Type 4 Messages........................................................................................................ F-25

F.2 OPERATOR MESSAGES ........................................................................................... F-30

F.3 LIST OF STATUS CODES ......................................................................................... F-34

Index ................................................................................................................................... i-1

Table of Contents

47 A2 14UC Rev05 xiii

Illustrations

Figures

1-1 Example of Job Submission........................................................................................ 1-32-1 Submission of Local Job at DPS 7/7000 for Remote Processing ............................... 2-22-2 DPS 7/7000 Requestor as Host .................................................................................. 2-32-3 DPS 7/7000 Server as SITE and HOST ..................................................................... 2-42-4 Output of Jobs submitted by DPS 7/7000 requestor................................................... 2-53-1 Job Submission from DPS 7/7000 to DPS 6............................................................... 3-23-2 Obtaining Results of Job Executed by DPS 6 (Method A) .......................................... 3-33-3 Obtaining Results of Job Executed by DPS 6 (Method B) .......................................... 3-43-4 Job Submission from DPS 6 to DPS 7/7000............................................................... 3-53-5 Obtaining Results of Job Executed by DPS 7/7000.................................................... 3-6

DJP User's Guide

xiv 47 A2 14UC Rev05

47 A2 14UC Rev05 1-1

1. Distributed Job Processing

1.1 TERMINOLOGY

Request A command for executing an activity.

Site In the context of job submission, a site is the system inwhich the file resides.

Host A system which executes jobs submitted fromdepartmentalized stations or from other hosts.

Requestor The site where the request is entered and the DJP sessionis initiated.

Server The remote site that dialogs with the requestor. The serverexecutes the transfer initiated by the requestor and reportsto the requestor.

Request Queue Each request is placed in a request queue. A systemmaintains one request queue for each remote site knownto that system.

Station A set of cataloged network resources associated with anoutput queue for sending and receiving data. There is oneoutput queue for each station.For job processing, the term departmentalized station isused to describe the DPS 6 functioning as a satellitesubmitting job requests to the more powerful DPS 7/7000host for execution.

Site Catalog The catalog on the DPS 7/7000 containing information onprojects, users, billings and stations which determine theuse of and access to the DPS 7/7000 system resources.

DJP User's Guide

1-2 47 A2 14UC Rev05

1.2 DESCRIPTION OF DJP

1.2.1 DJP Functions

Distributed Job Processing allows distributing the workload throughout the network byallowing systems to submit jobs to each other for execution and to receive requests toexecute jobs. The user is not aware whether the resources of the network are remote orlocal. In the GCOS 7 V7 release and later, DJP on the DPS 7/7000 host functions withanother DPS 7/7000 or a DPS 6.

The job request involves transferring the input file containing the job to the DPS 7/7000host for execution. Once the host DPS 7/7000 has processed the job, an output filecontaining the results of the job is then spooled back either to the original submittersystem or to another system for printing.

1.2.2 DJP Prerequisites

1. GCOS 7 Releases from V3 through V8 fully support

- SEND and EXECUTE functions of job processing- and SEND and RECEIVE functions for output.

For further details, see B.2.3 Profiles and RFA (Remote File Access) Capabilities.

2. Access rights are granted to the user in the catalogs of both systems.See Appendix C Site Catalog.

3. The UFT application is installed and initialized on both systems. On the DPS 6,remote job processing is done by the Extended UFT function.

1.2.3 DJP Services

The different services offered by DJP are:

• submitting jobs and monitoring them and their outputs on other systems in the network

• defining or modifying the station at which outputs are to be printed

• and submitting jobs for several systems in a single directive known as job spooling.

DJP services are complemented by the UFT service for transferring files to or from othersystems in the network.

Distributed Job Processing

47 A2 14UC Rev05 1-3

1.2.4 Job Submission

The contents of the file or member containing the job or jobs is a sequence of JCL (JobControl Language) statements. At execution time, however, there are many jobs in thejobset; each job is processed separately and a JOR (Job Occurrence Report) is producedfor each one.

Jobs are submitted through the EJR (Enter Job Request) command. For a full list of jobprocessing commands, see Appendix A.

The diagram below shows the roles of DPS 7/7000 systems as SITE and HOST.

In both cases, System A is the SITE where the file containing the job resides. The role of the HOST depends on which system executes the job request. 1) The EJR command entered at A to execute A's jobset at B: EJR INFILE=AJCL HOST=B; System B is the HOST executing the job contained in a file on System A at the request of System A. System A is the SITE while System B is the HOST.

DPS 7/7000 DPS 7/7000

AJCL system A system B

2) The EJR command entered at B to execute A's jobset at A:

EJR INFILE=$A:AJCL HOST=A;

System A is the HOST executing its own job at the request of System B. System A is both SITE and HOST.

Figure 1-1. Example of Job Submission

DJP User's Guide

1-4 47 A2 14UC Rev05

47 A2 14UC Rev05 2-1

2. Distributed Job ProcessingDPS 7/7000 <--> DPS 7/7000

2.1 JOB SUBMISSION

Between DPS 7/7000s, each system can function as:

• Requestor or Server, while the other system functions as the opposite

• Site or Host, or Site and Host.

DP71 is the requestor in Figures 2-1, 2-2, 2-3, functioning respectively as follows:

• as the site containing the job LIB1.JOB1..JCL1 to be submitted for execution on DP72(submission of local job for remote processing).

• as the host executing either its own local job LIB1.JOB1..JCL1 or a remote jobLIB2.JOB2..JCL2 (requestor as host)

• as server functioning both as site and host.

In all three cases the destination of the resulting job report is indicated.

The sequence of DJP Procedures as shown in Figures 2-1, 2-2, 2-3 is as follows:

• The requestor DP71 submits the EJR command.

• The job file identified for execution by INFILE (see note) is accessed at the siteconcerned and transferred, if required, to the server or to the requestor for processing.

• The job is executed.

• The server outputs the resulting job report to the destination implicit to DP71 orexplicitly specified by DEST.

NOTE: Where the requestor is both site and host, INFILE need not be specified.Instead, MEMBERS specifying the member and LIB specifying the library can beused.

DJP User's Guide

2-2 47 A2 14UC Rev05

STNcataloged

stationon

DP72LIB1.JOB1..JCL1

GTP

DP71 DP72

GTP

GSP

Step 3 : DP72 processes the job.

Step 4 : The resulting report is enqueued on STN.

STEP 2 : DP71 submits its job in LIB1.JOB1..JCL to DP72.

2

3

2

4

LIB1.JOB1..JCL1

GTP

DP71 DP72

GTP

GSP

3

2

4

SCHEMA 1

EJR INFILE=LIB1.JOB1..JCL1 HOST=DP72 DEST='DP72.STN' ;

Step 1 : The EJR command is issued at DP71.

GSP2

Step 2 : DP71 submits its job in LIB1.JOB1..JCL1 to DP72.


Step 4 : Since DEST is omitted, the resulting report is enqueued on DP71's implicit station.

SCHEMA 2

EJR INFILE=LIB1.JOB1..JCL1 HOST=DP72;


1

1

Figure 2-1. Submission of Local Job at DPS 7/7000 for Remote Processing

Distributed Job Processing DPS 7/7000 <--> DPS 7/7000

47 A2 14UC Rev05 2-3

LIB1.JOB1..JCL1

GTP

DP71

GTP

GSP

4

1

3

4ANYS

2Step 3 : DP72 processes the job.

Step 4 : DEST specifies the results of the job will appear on the STN cataloged on site ANYS.

STEP 2 : DP71 submits its job in LIB1.JOB1..JCL to itself.

STNcataloged

stationon

ANYS

SCHEMA 1

EJR MEMBERS=JCL=LIB1.JOB.1 DEST='ANYS.STN' ;


GTP

DP71

GSP

1

3

4

2

STNcataloged

stationon

DP71

2

SCHEMA 2

EJR INFILE=$DP72:LIB2.JOB2..JCL2 DEST='STN' ;


Step 2 : DP72 submits the job in LIB2.JOB2..JCL2 to DP71.


Step 4 : DEST specifies that the job results will appear on STN.

LIB2.JOB2..JCL2

DP72

Figure 2-2. DPS 7/7000 Requestor as Host

DJP User's Guide

2-4 47 A2 14UC Rev05

GTP

DP71

GTP

GSP

1

3

1

LIB2.JOB2..JCL2

GSPGSP

2

SCHEMA 1

EJR INFILE=$DP72:LIB2.JOB2..JCL2 HOST=DP72 ; ;


DP72

LIB2.JOB2..JCL2

2

Step 2 : DP72 is both site and host executing its own job in LIB2.JOB2..JCL2.


Step 4 : The results of the job destined for DP71 are enqueued on its implicit station.

SCHEMA 2

EJR INFILE=$DP72:LIB2.JOB2..JCL2 HOST=DP72 DEST='STN' ;


GTP

DP71

GTP

GSP

3

2DP72

2

4

4

STNcataloged

stationon

DP72

Step 2 : DP72 is both site & host executing its own job in LIB2.JOB2..JCL2.


Step 4 : The job results destined for DP72 are enqueued on its cataloged STN.

GSP

Figure 2-3. DPS 7/7000 Server as SITE and HOST

Distributed Job Processing DPS 7/7000 <--> DPS 7/7000

47 A2 14UC Rev05 2-5

2.2 DESTINATION OF JOB OUTPUT

Although a file transfer or a job submission can only be requested on a participating site,the results of the executed job can be sent to any connected site. This is done by creatinga station, with the same name as the non-participating site in question, in the site catalogof one or both of the participating sites.

The station is operated on by DJP station management.

The diagram below shows how the DEST parameter is used to identify the station atwhich the results are to appear.

DPS 7/7000

site B host C

DPS 7/7000

AJCL

System B is a site since the file AJCL resides in it.

System C is a host since it executes the job submitted at B.

System A represents any station in the network which is cataloged on either Site B or host C.

Case 1 : Where B is the requestor, the format of EJR is:

EJR INFILE=AJCL HOST=C DEST=A; A is station on C or

EJR INFILE=AJCL HOST=C DEST=B.A; A is station on B Case 2 : Where C is the requestor, the format of EJR is:

EJR INFILE=$B:AJCL DEST=A; A is station on C or

EJR INFILE=$B.AJCL DEST=B.A; A is station on B

Figure 2-4. Output of Jobs submitted by DPS 7/7000 Requestor

DJP User's Guide

2-6 47 A2 14UC Rev05

47 A2 14UC Rev05 3-1

3. Distributed Job ProcessingDPS 7/7000 <--> DPS 6

3.1 DJP WITH DPS 6

In the current DJP environment, the roles of the DPS 7/7000 and the DPS 6 areasymmetric. This is a restriction of the available GCOS 7 and GCOS 6 software, in that :

• the print format of the GCOS 6 report file is not recognized by GCOS 7 as a standardformat to render intelligible printing.

• there is no GCOS 7 utility to convert the GCOS 6 report file print format to anequivalent GCOS 7 standard format.

The DPS 6 can take one of two roles according to the context in which it operates.

1. It functions with other DPS 6s as a departmentalized station.

In this role it submits jobs to the more powerful DPS 7/7000 and receives theresulting reports. The DPS 7/7000 serves as a centralized system and does notsubmit job requests to the DPS 6s. It is there to provide a service for the DPS 6departmentalized stations.

2. The DPS 6 is a system in its own right. It acts as a remote host, executing jobssubmitted by the DPS 7/7000 requestor.

DJP User's Guide

3-2 47 A2 14UC Rev05

3.2 DPS 7/7000 --> DPS 6

In the diagrams following the DPS 7/7000 is named for convenience DPS 7, similarly theterm DPS 6 is the name given to the DPS 6.


GTP

1

3

DPS6

ExtendedUFT

FTPS

DPS7

H_GTP

^DIR>JOB>JCL.EC

^DIR>JOB>JCL.AO

EJR INFILE=$DPS6:^DIR>JOB>JCL.EC HOST=DPS6;

Step 1 : The EJR command is issued at DPS7.

DPS6 is the host and site of the job processing request even if the command is entered at DPS7.

4

2

Step 2 : The job >JCL.EC in ^DIR>JOB is read in by the GCOS 6 input reader.

Step 3 : The DPS 6 executes the job.

Step 4 : The results of >JCL.EC are written to >JCL.AO in ^DIR>JOB.

Figure 3-1. Job Submission from DPS 7/7000 to DPS 6

1. The DPS 7/7000 user enters the EJR command that specifies the job residing in siteDPS 6, to be executed by the DPS 6.

2. The job >JCL.EC in ^DIR>JOB at site DPS 6 is read in by the GCOS 6 input reader.

3. The DPS 6 executes the job.

4. The results of >JCL.EC are written to >JCL.AO in ^DIR>JOB.

Distributed Job Processing DPS 7/7000 <--> DPS 6

47 A2 14UC Rev05 3-3

3.2.2 Obtaining the Results of the Job

There are two methods of recovery, outlined in steps 5 to 7.

GTP

DPS7

H_GTP

7

DPS6

ExtendedUFT

FTPS

6

Step 6 : FTPS at DPS6 accesses file >JCL.AO to transmit to DPS7.

Step 7 : UFT transfers the contents of ^DIR>JOB>JCL.AO to LIB.REPORTS.

5

Method A

EFTR INFILE=$DPS6:^DIR>JOB>JCL.AO OUTFILE=LIB.REPORTS;

Step 5 : The EFTR command is issued at DPS7.

LIB.REPORTS ^DIR>JOB>JCL.AO

Figure 3-2. Obtaining Results of Job Executed by DPS 6 (Method A)

5. The DPS 7/7000 user telephones the DPS 6 center for information on the progressof the job submitted under the user name supplied at logon. The DPS 6 consoleoperator monitors the job by entering the LQR -BATCH command. When the jobterminates, the DPS 6 center telephones the DPS 7/7000 user. The DPS 7/7000user enters the EFTR command, specifying that the file containing the results of thejob must be repatriated to the DPS 7/7000.

6. The file >JCL.AO in ^DIR>JOB is accessed by the server FTPS for transmission.

7. UFT transfers the contents of ^DIR>JOB>JCL.AO to the DPS 7/7000 fileLIB.REPORTS. DPS 7/7000 requires a DPS 6 system at its site, to which it transfersthe contents of LIB.REPORTS for printing.

DJP User's Guide

3-4 47 A2 14UC Rev05

GTP

DPS7

H_GTP

7

DPS6

ExtendedUFT

FTPS

6

Step 6 : FTPS at DPS6 accesses file >JCL.AO to transmit to DPS7.

Step 7 : UFT transfers the contents of ^DIR>JOB>JCL.AO to LIB.REPORTS.

5

LIB.REPORTS ^DIR>JOB>JCL.AO

Method B

-TR -OP ^DIR>JOB>JCL.AO -DN DPS7 -DP LIB.REPORTS

Step 5 : The TR command is entered at DPS6.

Figure 3-3. Obtaining Results of Job Executed by DPS 6 (Method B)

5. The DPS 7/7000 user telephones the DPS 6 center giving the following informationon the job submitted:

- user-name at logon,

- the name of the DPS 7/7000 system and the name of the file to receive the jobreport.

The DPS 6 console operator monitors the job by entering the LQR -BATCHcommand. When the job, identified by its user-name, terminates, the resulting reportis created in^DIR>JOB>JCL.AO.

The DPS 6 console operator enters the -TR command specifying that the results ofthe job are to be repatriated to the DPS 7/7000.

6. The file >JCL.AO in ^DIR>JOB is accessed by the requestor FTPR for transmission.

7. UFT transfers the contents of ^DIR>JOB>JCL.AO to the DPS 7/7000 fileLIB.REPORTS. DPS 7/7000 requires a DPS 6 system at its site, to which it transfersthe contents of LIB.REPORTS for printing.

Distributed Job Processing DPS 7/7000 <--> DPS 6

47 A2 14UC Rev05 3-5

3.3 DPS 6 --> DPS 7/7000


DPS6

ExtendedUFT

-EX -EN DPS7 -EP LIB.JOB..JCL

Step 1 : The EX command is issued at DPS6.

DPS7 is the host and site of the job processing request even if the command is entered at DPS6.

FTPS

DPS7

H_SERVER2

LIB.JOB..JCL

GTP

2

4

SYS.OUT

Step 2 : The job JCL in LIB.JOB at DPS7 is read in by the GCOS 7 input reader.

Step 3 : The DPS7 executes the job.

Step 4 : The results of JCL are written to the DPS7 public SYS.OUT file and enqueued on DPS6's station.

1

3

Figure 3-4. Job Submission from DPS 6 to DPS 7/7000

1. The DPS 6 operator enters the -EX command that specifies the job residing on siteDPS 7/7000, to be executed by the DPS 7/7000.

2. The job JCL in LIB.JOB at site DPS 7/7000 is read in by the GCOS 7 input reader.

3. The DPS 7/7000 executes the job.

4. The results of the job JCL written to the DPS 7/7000 public SYS.OUT file belong tothe DPS 6 station queue.

DJP User's Guide

3-6 47 A2 14UC Rev05

3.3.2 Obtaining the JOR and SYSOUT

DPS7

H_GTP

7

DPS6

ExtendedUFT

6

5

GTPFTPS

SOW ON=$DPS6:SPOOL ST=DPS6

Step 5 : The SOW command is issued at DPS7. to transfer SYS.OUT contents to DPS6.

Step 6 : GTP in DPS7 starts to transfer outputs.

>UDD>REPORTS>DPS7>FILES SYS.OUT

Step 7 : The job results are spooled to DPS6 for printing. The spooling directory on DPS6 is named:

>UDD>REPORTS>DPS7>QUEUE

Figure 3-5. Obtaining Results of Job Executed by DPS 7/7000

5. The DPS 7/7000 main or station operator monitors the progress of jobs by enteringthe DLD command, followed by a DO Xnnn command, for the specific job run. Theoperator then enters the SOW command to repatriate the resulting job report to theDPS 6.

6. The results of the selected queued job in the DPS 7/7000 public SYS.OUT filebelong to the DPS 6 station queue and are accessed by the GTP for transmission.

7. The job results are written to a DPS 6 file, implicitly named>UDD>REPORTS>DPS7>FILES. The implicit name of the spooling directory inwhich the results are queued is >UDD>REPORTS>DPS7>QUEUE.

The results are printed at the DPS 6 through the command UNSP (unspool).

47 A2 14UC Rev05 A-1

A. Job Processing Commands

The DJP commands treated here are those applicable to the DPS 7/7000 functioning asthe requestor of the job submission with another DPS 7/7000 or DPS 6.

Commands which are reserved for the MAIN operator and those which apply to thestation operator are clearly indicated in their function descriptions.

Meaning of Abbreviations in Syntax

GCL is a typed language. Parameters include variables and expressions which takearguments in specific recognizable forms of assignments and references.

The following is a list of argument types:

bool: boolean binary condition, 0 or 1

digit: any numeric value

dec: decimal value

hexa: hexadecimal value

name: any string of alphanumeric characters

char: any string of alpha characters

The following is a list of parameter types:

lib: library

file: file

rfile: remote file

fset: fileset

volume: volume

output: output

DJP User's Guide

A-2 47 A2 14UC Rev05

The following commands are available for DJP and UFT. The first column gives thenumber of the command applicable to DJP, the last column gives the number of the pagein the Appendix. Where the entry UFT appears for the command, refer to the GCOS 7-V7UFT User's Guide. Abbreviations against the command entry are u for user, m for MAINoperator and s for Station operator.

A.1 CO CANCEL_OUTPUT u A-3A.2 CUR CANCEL_USER_REQ u A-6A.3 DC DISPLAY_CONFIGURATION u A-8A.4 DDJP DISPLAY_DJP u A-11A.5 DJ DISPLAY_JOB u A-15A.6 DLD DISPLAY_LOAD u A-19A.7 DO DISPLAY_OUTPUT u A-23A.8 DSO DISPLAY_SECURITY_OPTIONS u A-26A.9 DUR

EFTRDISPLAY_USER_REQENTER_FILE_TRANSFER_REQ

uu

A-29UFT

A.10 EJRELTREXFTEXDLRFEXMDRF

ENTER_JOB_REQENTER_LIBTRANS_REQEXECUTE_FILE_TRANSFEREXECUTE_DELETE_REMOTE_FILEEXECUTE_MODIFY_REMOTE_FILE

uuuuu

A-32UFTUFTUFTUFT

A.11 FO FORCE_OUTPUT m A-41A.12 FUR FORCE_USER_REQ m A-42A.13 HUR HOLD_USER_REQ u A-44A.14 MDC MODIFY_CONFIGURATION m A-45A.15 MDDJP MODIFY_DJP m A-47A.16 MDO MODIFY_OUTPUT u A-49A.17 MDOP MODIFY_OUTPUT_PARAMETERS u A-53A.18 MDST MODIFY_STATION s A-56A.19 MDUR MODIFY_USER_REQ u A-59A.20 RUR RELEASE_USER_REQ u A-62A.21 SIR START_INPUT_READER m A-64A.22 SOW START_OUTPUT_WRITER s A-65A.23 TIR TERMINATE_INPUT_READER m A-70A.24 TOW TERMINATE_OUTPUT_WRITER s A-71

Job Processing Commands

47 A2 14UC Rev05 A-3

A.1 CO (CANCEL_OUTPUT)

Purpose

Cancels the request that an output or set of outputs be printed. The outputs cannot berecovered after they have been cancelled.

IMPORTANT

This command applies only to the outputs on which the submitterhas access rights

Syntax

{ CANCEL_OUTPUT } { CO }

[ { (output14 [ output14 ] ...) } ] [ OUTPUT = { output14-output14 } ] [ { * | ALL } ]

[ SELCLASS = a [-a] ]

[ STRONG = { bool | 0 } ]

[ { STATION } { * } ] [ { } = { ALL } ] [ { ST } { name8 } ]

[ { SELECT } { user/project } ] [ { } = { */project } ] [ { } { */* } ] [ { SEL } { * } ]

[ { JOBNAME } ] [ { } = name8 ] [ { JNM } ]

DJP User's Guide

A-4 47 A2 14UC Rev05

Parameters

OUTPUT Output(s) to be cancelled. The following formats are allowed:

1. a list of the names of up to 16 outputs:

- Xnnnn:nnnn } to refer to a specific output } (Xnnnn:name means the first output- Xnnnn:name } so named)

- Xnnnn to refer to all outputs of a job.

2. a range of outputs delimited by a lower and an upperboundary. This may take the following form only:

- Xnnnn-Xnnnn to refer to all outputs of a range of jobs; the first ron must be lower than the second.

3. to refer to all outputs of all jobs, specify:

- * or ALL (default when JOBNAME is specified)

SELCLASS (meaningful only for output names in the form Xnnnn)restricts the scope of the command to those outputs thatbelong to a certain class or range of classes. This may beexpressed as:

class for a single classclass-class for a range of classes

where class is a letter in the range A to Z.

When omitted, all classes are assumed (A-Z).

STRONG if 1, cancel even if outputs are being printed. Default is 0.

STATION restricts the scope of the command to outputs attached to thestation specified. When omitted or when * or ALL is specified,there is no station restriction.

SELECT restricts the scope of the command to outputs belonging to aspecified user and/or project. Not meaningful when OUTPUTspecifies a list of outputs (format 1). By default, only theoutputs belonging to the command submitter are selected.

JOBNAME restricts the scope of the command to the outputs of jobs withthe name specified. If JOBNAME is specified, the defaultvalue for OUTPUT is *.


47 A2 14UC Rev05 A-5

Rules

• SELCLASS is ignored for names of specific outputs (Xnnnn: nnnnn or Xnnnn :name).

• If several outputs of the same job are given the same name, CO Xnnnn: name onlyaffects the first output with that name encountered by the system.

• CANCEL_OUTPUT does not apply to outputs in the KNOWN state.

Examples:

CO X123 {cancel all outputs of job X123}

CO (X123 X124) {cancel all outputs of jobs X123 and X124}

CO X123 H {cancel all outputs of job X123 that are of class H}

CO X123 A-S {cancel all outputs of job X123 that are of classes A to S}

CO X123:2 {cancel specified outputs of job X123}CO X123: SPRCO (X123:1 X123:RES)

CO X123 STRONG {cancel all outputs of job X123, even if being printed}

CO X123-X2167 {cancel all outputs, belonging to the command submitter, ofthe jobs whose RON is in the range X123 to X2167

CO * Z {cancel all class Z outputs, belonging to the commandsubmitter}

CO * SELECT=U1/P1 {cancel all the outputs belonging to user U1 of project P1}

CO * STATION=BC10 {cancel all outputs, belonging to the command submitter, thatare attached to the station BC10}

CO X123-X2167 A ST=BC10 SEL=U1/P1{cancel all class A outputs of jobs in the range X123 to X2167that are attached to station BC10 and belong to user U1 ofproject P1}

CO JOBNAME=JOB1 {cancel outputs, belonging to the command submitter, of thejobs named JOB1}

DJP User's Guide

A-6 47 A2 14UC Rev05

A.2 CUR (CANCEL_USER_REQ)

Function

Cancels (RELEASE=0) or releases (RELEASE=1) waiting and submitted request(s).

Syntax

{ CANCEL_USER_REQ }{ }{ CUR }

{ { Jddddddd [ Jddddddd ... ] } }{ REQUEST = ( { } ) }{ { name8 [ name8 ... ] } }{ }{ ALL = ( bool | 0 ) }{ }{ ALL_USERS = { bool | 0 } ]

[ RELEASE = { bool | 0 } ]

Parameters

REQUEST: a list up to 16 requests of the format (request [,request...])where request is one of the following forms:

Jddddddd: Jobset Occurrence Number (JON) resulting fromthe EJR command

name-8: the symbolic name of a request as specified by theNAME parameter of the EJR or EFTR command.

ALL: all requests of the submitter of the command.

ALL_USERS: If MAIN Operator, all requests of all users.If Station Operator, all requests on the station.

RELEASE: if 1, the request(s) waiting for the completion of the cancelledrequests are released, just as if the cancelled requests hadcompleted normally.if 0 (default), the request(s) is to be cancelled; RELEASE=0 isignored for jobset request(s).

Example:

If the jobs J38 and J39 are submitted, the command CURJ38 RELEASE has the effect of cancelling J38 and thereforemaking J39 eligible for execution. For more details, seeExamples.


47 A2 14UC Rev05 A-7

Messages

The following message is displayed as the result of successful execution of the command:

<time> <request id> CANCELLED

Examples:

S: CUR (J27 F32 RQP)cancels 3 requests, J27 as a job request, F32 being a file transfer request and RQP asany submission.

S: CUR J44 RELEASEcancels job processing request J44 and releases waiting requests

S: CUR J110results in the message: 18.45 J110 CANCELLED

For each request which depends on the execution of the cancelled request, a message"<fon> CANCELLED/RELEASED" is displayed:

S: CUR J35 RELEASE 16.44 J39 RELEASED 16.44 J35 CANCELLED

DJP User's Guide

A-8 47 A2 14UC Rev05

A.3 DC (DISPLAY_CONFIGURATION)

Purpose

Displays the status of selected elements of the hardware or software configuration.

Syntax

{DISPLAY_CONFIGURATION}{DC }

[ {* }] [ DEVICE = {device-id }] [ {device-class }] [ {device-type }]

[{OUTCLASS} {* }] [{ } = { }] [{OC } {a[-a]}]

[ {* }] [OUTDV = {PR[nn] }] [ {T[nnn] }] [ {W[nnn] }]

[{STATION} {* }] [{ } = {ALL }] [{ } = {CURRENT}] [{ST } {a[-a] }]

[ {* }] [ PLM = { }] [ {[lib-nm..] lm-nm [:volnm :dvc]}]

[BS = name6]

{ VOLUME } [{ } = volume-name:device-class ] { VOL }

------------------------------------------------

[ LIB = lib78 ]

Parameters

DEVICE display the status of the devices. This may be specified as:

*: all devicesdevice-nn: a specified device (e.g., MS03)device-class: all devices of a class (e.g., MS/B10)


47 A2 14UC Rev05 A-9

OUTCLASS display the configuration of the output classes (priority, outputmedia) and output activities for these classes. These may bespecified as:

*: all classes -class: a specified classclass-class: a range of classes

where class is a letter in the range A to Z. A list of up to10 classes or ranges of classes may be specified.

OUTDV display the output currently being processed or waiting for thespecified device (PRnn, Tnnn, or Wnnn), device class (PR, Tor W), or all writers (*, i.e. PR + T + W).

STATION specifies one of the following: an explicit station name,CURRENT (for currently attached stations) or ALL or * (for allstations). When used in conjunction with OUTCLASS orOUTDV, the information shown is restricted to the stationconcerned (values ALL and * are then ignored). When neitherOUTCLASS nor OUTDV is specified, information about theconfiguration of the named stations is displayed.

PLM display information (name, location and number of units)about all (*) or a designated preinitialized load module (PLM).A single PLM is designated as follows:

[lib-name..] Im-name [:volnm :dvc]

where:

- lib-name is the library name (default SYS.HLMLIB)- Im-name is the name of the load module- volnm is the volume name (uncataloged library)- dvc is the device class of volnm (uncataloged library)

BS display the status of the required elements of backing store.This may be specified as:

SYS backing store occupation for system,ALL backing store occupation for system and all jobs,MAP which backing stores are used and on which volumes,SM loaded shareable modules,CKPT active checkpoints,VMF active Virtual Memory Files,IO average number of I/Os per second,Xnnnn space used by the named job,volume-name jobs that use the volume as backing store.

VOLUME display the status of a volume. The volume must be standard.For cartridge, the Full Device Class is needed if severalmodels are present on the site.

LIB display loaded shareable modules in backing store for thespecified library. Used only with BS=SM.

DJP User's Guide

A-10 47 A2 14UC Rev05

Rules

None.

Examples:

DC MT {display status of all magnetic tape drives}

DC ST=* {display all stations information}

DC OC=* {display characteristics and activities for all output classes}

DC PLM=* {display all preinitialized load modules}

DC BS=ALL {display status of backing stores}

DC OUTDV=W {display the characteristics and the output activities of allmagnetic writers (W001, W002, ..)}

DC OUTDV=T001 {display the output activities of the GTP T001}

DC OUTCLASS=A OUTDV=*{display the configuration of outclass A (priority, output media,size), and the characteristics and output activities of allwriters}

NOTES: 1. It is recommended that you use theDISPLAY_HARDWARE_CONFIGURATION command (DHW) todisplay the status of a hardware resource.

2. To display information about CPU priorities, dimensions ormemory, use the DISPLAY_XL_CLASS or DISPLAY_DIMENSIONcommands.

3. For more information about transfers (OUTDV=T[nnn], use thecommand DISPLAY_DJP (DDJP).


47 A2 14UC Rev05 A-11

A.4 DDJP (DISPLAY_DJP)

Function

Displays the current status of system files, system processors and request attributes inremote sites. DDJP does not, however, report on file transfer activities launched with theJCL statement FILTFR. In a file transfer environment, this command is used to displayinformation on a given site or sites.

SITE does not apply to the transferrer's own state. This state will be ACTIVE, IDLE,WAITING ON TELECOM or SITE. If the transferrer is active, the display includes therequest currently being processed, giving the number of records transferred.

Syntax

{ DISPLAY_DJP }{ }{ DDJP }

[ { { ALL [ JOBNAME = bool ] } ][ { { --- } ][ { { Tddd } ][ { { } ][ { { { EX } { } } ][ { { { } { } } ][ { OPTION={ { HOLD } { { } } } ][ { { { } { { ALL } } } ][ { { { QUEUE } { SITE={ --- } } } ][ { { { } { { name-4 } } } ][ { { { TFR } { { } } } ][ { { { } { } } ][ { { { WAIT | WDTM | WTFL | WTFR } { } } ][ { } ][ { YEAR = year } ]

[ DETAILED = bool ][ UFTWAIT = bool ]

Parameters

OPTION: specifies the type of information for display:

ALL (default): all known requests, SITE not applicableTddd: transfer identifier, SITE not applicableEX: requests being processedHOLD: requests heldQUEUE: requests enqueuedTFR: files, jobsets and outputsWAIT: requests waiting to be processedWDTM: requests waiting for date/time conditionWTFL: requests waiting for filesWTFR: requests awaiting completion of other

transfers

DJP User's Guide

A-12 47 A2 14UC Rev05

SITE: specifies the system to which OPTION applies; notapplicable to Tddd options :

ALL (default): all systemsname-4: a particular system declared at network

generation by the LSYS or RSYS orSYSTEM directive

YEAR: specifies the year for which both non-working days andholidays are to be displayed.YEAR is mutually exclusive to OPTION and SITE.

JOBNAME: used with DDJP OPTION=ALL.if 1, the name of the file or the subfile containing the job is tobe displayed:- 31 characters maximum for subfile- 44 characters for file.

if 0, no display.JOBNAME is mutually exclusive to SITE and YEAR.

UFTWAIT: when set to 1, this parameter gives the waiting time, in hoursand/or minutes, between two data transfers.

DETAILED: when set to 1, this parameter gives the public holidays indetailed mode for year specified in YEAR parameter.

Messages

S: DDJP ALL

<time> NO TRANSFER ACTIVITY

S: DDJP Tddd

<time> UNKNOWN TRANSFER ACTIVITY = Tddd

S: DDJP SITE=<site-name>

one of the following messages is displayed:

<time> NO TRANSFER ACTIVITY FOR SITE= <site name>

<time> UNKNOWN SITE= <site name>

<time> SITE=<site-name> ACTIVITIES= {n | p} [PROTOCOL=RFA]

Tddd SITE=<site-name> <status> GTP | IR =<ron> . . .

Tddd SITE=<site-name> <status> GTP | IR =<ron> . . .


47 A2 14UC Rev05 A-13

where:

n/p: defines the number of active (n) GTPs out of the number ofpossible (p) GTPs

status: refers to the status of the transferrer, namely IDLE, ACTIVE,IN ABORT, IN TERM, WAIT ON TELECOM, or WAIT ONSITE

{GTP | IR}: identifies the RON of the GTP or Input Reader

<time> Tddd SITE=<site-name> <status> {GTP |IR} =<ron> STATION = <station-name> <devclass> <output-class> WORKING ON: {<output-name> REMAINING LINES : <nnn> } {<fon> TRANSFERRED RECORDS :<nnn>} {<jon> } . . .

where:

STATION: designates the target station

WORKING ON: designates the type of operation, namely:REMAINING LINES for transfer of output fileTRANSFERRED RECORDS for normal file transfer

Examples:

S: DDJP OPTION=T1

14.22 T1 SITE=HD01 IDLE GTP RON=X128

S: DDJP SITE=HD01

14.22 SITE=HD01 ACTIVITIES=0/5 PROTOCOL=RFA T1 SITE=HD01 IDLE GTP RON=X128

S: DDJP OPTION=TFR SITE=HD01

The results below show different states of TFR.

Case 1

14.24 SITE=HD01 ACTIVITIES=0/5 PROTOCOL=RFA T1 SITE=HD01 IDLE GTP RON=X128 STATION=HD01 PR A-Z STATION=RBFQ PR A-Z

Case 2

14.36 SITE=HD01 ACTIVITIES=1/5 PROTOCOL=RFA T1 SITE=HD01 ACTIVE GTP RON=X128 STATION=HD01 PR A-Z STATION=RBFQ PR A-Z WORKING ON: X0345:3 REMAINING LINES : 108

DJP User's Guide

A-14 47 A2 14UC Rev05

Case 3

14.39 SITE=HD01 ACTIVITIES=1/5 PROTOCOL=RFA T1 SITE=HD01 ACTIVE GTP RON=X128 STATION=HD01 PR A-Z STATION=RFBQ PR A-Z WORKING ON: F17 TRANSFERRED RECORDS : 2

S: DDJP YEAR=1991

09.15 NOT WORKING DAYS FOR:BPE4 ARE: SATURDAY,SUNDAY 09.15 FOR 1991,HOLIDAYS ARE: 1,86,121,128,195,227,305,315,359

S: DDJP ALL JOBNAME;

7.2 F318 C 3 RDY SITE=BP50 OPERATORF324 C 3 RDY SITE=BP50 DUPONTF326 C 3 RDY SITE=BP50 DUBOISF360 C 3 WTFL SITE=BP50 OPERATORF365 C 3 RDY SITE=BP50 OPERATORJ366 C 3 HOLD SITE=BP42 HOST=BP42 JOB=TDMVHF367 C 3 WTFL SITE=BP50 OPERATORF368 C 3 RDY SITE=BP50 OPERATORF375 C 3 WTFL SITE=BP50 OPERATORJ378 C 3 EX SITE=BP42 HOST=BP42 JOB=SPOOLF380 C 3 WTFL SITE=BP50 OPERATORF383 C 3 RDY SITE=BP50 OPERATORF386 C 3 RDY SITE=BP50 OPERATORJ418 C 3 RDY SITE=BP42 HOST=BP42 JOB=WATCHDOG

Command (1) displays the information (2):

DDJP UFTWAIT (1)

UFT WAITING TIME : 20 minutes (2)

Command (1) displays the information (2):

DDJP YEAR=2000 DETAILED (1)

NOT WORKING DAYS FOR:BC06 ARE: SATURDAY,SUNDAY } FOR 2000,HOLIDAYS ARE: } JULIAN DAY NUMBER JULIAN DAY } 1 JAN 1 } (2) 3 JAN 3 } 36 FEB 5 } 252 SEP 8 }


47 A2 14UC Rev05 A-15

A.5 DJ (DISPLAY_JOB)

Function

Displays the current status of selected jobs.

Syntax

{ DISPLAY_JOB }{ DJ }

[ { jstate } ][ { jtype } ][ JOBID = {(jstate jtype) } ][ { Xnnnn } ][ { name8 } ]

[ { SELECT } { jclass} [ { usenm* } [ { projnm } ] ] ][ { } = { } [ , { } [ , { } ] ] ][ { SEL } { } [ { * } [ { * } ] ] ]

[ { STATION } { * } ][ { } = { ALL } ][ { ST } { name8} ]

[ JOBNAME = name8]

[ = 200 ] }][ LIMIT = 20 ] }] (See parameter description for default value)[ = dec4] }]

[{ SYSTEM } ][{ } = name4][{ SYS } ]

[ { SEQUENCE } { PRIORITY | DECR_ITIME | INCR_ITIME }][ { } = { | | }][ { SEQ } { | DIT | IIT }]

[ { DETAILED } ][ { } = { bool | 0 } ][ { DTLD } ]

DJP User's Guide

A-16 47 A2 14UC Rev05

Parameters

JOBID: the jobs to be displayed are designated by their:- Run Occurrence number (Xnnnn);- name (name8);- current state (jstate); and/or- job type (jtype)or current state and job type.

jstate must be one of the following:ALL, SCH, EX, SUSP, OUT, IDLE, IN, HOLDjtype must be one of the following:ALL, BATCH, IOF, SERVICE, NSERVICEif NSERVICE is specified, all jobs except the service jobs aredisplayed.When JOBID is unspecified, ALL is assumed.

SELECT: restricts the directive to the jobs that belong to the specifiedcombination of class/user-name/project. * is all jobs. Whenomitted, all jobs for which USER is the terminal user areassumed.

STATION: restricts the list of jobs displayed to those that are attached tothe named station (* or ALL stand for any station). Whenomitted, the current working station of the submitter isassumed.

JOBNAME: the job or jobs to be displayed by name (name-8).

LIMIT: maximum number of jobs to be displayed. Beyond that limit,only the number of jobs per class is displayed.The default value and maximum values are:When DETAILED=1, default 20, maximum 100.When DETAILED=0, default 200, maximum 850.

SYSTEM: indicates the system where the command is to be executed.

SEQUENCE: specifies the order in which jobs are to be displayed for eachjob state. The sort criterion can be the scheduling priority(keyword PRIORITY) or the introduction time (keywordsDECR_ITIME and INCR_ITIME). The display order for eachjob state is determined by:

- the scheduling priority (PRIORITY), from highest tolowest. The introduction time is used for second levelsorting within each priority level. This is the defaultdisplay criterion.

- or the introduction time alone, (PRIORITY not specified):DECR_ITIME = from most recent to oldestINCR_ITIME = from oldest to most recent.


47 A2 14UC Rev05 A-17

DETAILED: (abbreviation DTLD) specifies whether detailed jobinformation is to be displayed. The information returneddepends on the job state:

HOLD Hold countIntroduction time

EX/SUSP Introduction timeSwitchesFull load module name or step stateSystem internal identifier associated with the stepCPU and elapsed times for the current stepNumber of processesBacking storeUsed and fixed instantaneous memory sets.

It is not always possible to provide all of the aboveinformation for jobs in state EX or SUSP. In particular theARM dimension (e.g., IOF, BATCH) and the step-specificinformation (load module name, step CPU and elapsed time,number of processes, backing store, memory sets). This isthe case at step initialization (if the step is waiting for aresource statically assigned by a JCL statement or forresources in a dimension), and at step termination.

OUT The introduction and termination times.These times may be unknown if the job is in the OUT stateand if they were kept after SYS.OUT recovery at systemRESTART.

IN, SCH, IDLE The introduction time.

When DETAILED=1, LIMIT may not exceed 100 and thedefault value is 20.

Rules

When JOBID is in the form Xnnnn, SELECT and STATION and LIMIT are ignored.JOBID and JOBNAME are mutually exclusive.

Examples:

S: DJ {Display the status of all jobs for which USER is thecommand submitter and that are attached to his currentworking station.}

S: DJ EX {Display the status of all executing jobs for which USER is thecommand submitter and that are attached to his currentworking station.}

S: DJ SCH {Display the status of all scheduled jobs for which USER isthe command submitter and that are attached to his currentworking station.}

S: DJ X222 {Display the status of job with RON X222.}

DJP User's Guide

A-18 47 A2 14UC Rev05

S: DJ EX * {Display the status of all executing jobs that are attached tothe current working station of the command submitter.}

S: DJ ALL */JONES {Display the status of all jobs for which the USER is JONESand that are attached to the current working station of thecommand submitter.}

S: DJ EX */*/PROJ/ {Display the status of all executing jobs submitted underproject PROJ.}

S: DJ PAYROLL {Display the status of all the jobs named PAYROLL for whichUSER is command submitter and that are attached to hiscurrent working station.}

S: DJ BATCH C {Display the status of all batch jobs in class C attached to thecurrent working station of the command submitter.}

S: DJ EX ST=ST1 {Display the status of all executing jobs for which USER is thecommand submitter and that are attached to station ST1.}

S: DJ JOBID=(EX NSERVICE) *{Display the status of all executing jobs that are not servicejobs and that are attached to the current working station ofthe command submitter.}

S: DJ SEQUENCE=INCR_ITIME DTLD{Display detailed information about jobs for which USER isthe command submitter and that are attached to his currentworkstation. Within each state, display the oldest jobs first.}


47 A2 14UC Rev05 A-19

A.6 DLD (DISPLAY_LOAD)

Purpose

Display selected information on the current system load

Syntax

{ DISPLAY_LOAD }{ DLD }

[ {BRIEF }] [ {LOAD }] [ {CLASS [[SELECT=]{* | jclass | jclass-jclass}] }] [ {CLDTLD | CD [[SELECT=]{* | jclass | jclass-jclass}] }] [OPTION={CONNECT | CN [[SELECT=]{* | jclass | jclass-jclass}] }] [ {ALLOUT [[SELECT=]{* | ALL | name8 } }] [ {OUTPUT [[SELECT=]{* | ALL | name8 | SPACE } }] [ {MEM [[SELECT=] Xnnnn] }]

Parameters

OPTION a name selecting the information to be displayed. These aresummarized in the following table. When the parameter isomitted, BRIEF is assumed.

SELECT a name or a star (*) that further specifies the scope of theinformation selected by OPTION. Applicable values andauthorized combinations are summarized in the followingtable.

NOTE: jclass [-jclass] is entered in the form aa [-aa] .

DJP User's Guide

A-20 47 A2 14UC Rev05

Rules

OPTION SELECT Information displayed Examples

BRIEF - Brief information on the job load. DLDDLD BRIEF

LOAD - Job load by classes. DLD LOAD

CLASS aa[-aa] Current load of the specified class orrange of classes (all classes if * or noclass specified).

DLD CLASS XDLD CLASS A-ZDLD CLASS *DLD CLASS

CONNECT aa[-aa] Current connection of specified class orrange of classes (all classes if * or noclass specified).

DLD CONNECT XDLD CN AA-ZZDLD CONNECT *DLD CONNECT

ALLOUT *ALL

name_8

All jobs of the named station withoutputs in READY, WAIT, HOLD orOUT states (see section 5). All stationsif ALL or *.

DLD ALLOUTDLD ALLOUT ST01DLD ALLOUT*

OUTPUT *ALL

name_8

The number of outputs in the queues ofthe named station (all if ALL or *).

DLD OUTPUTDLD OUTPUT ALLDLD OUTPUT *

OUTPUT SPACE The percentage of free space in theSYS.OUT file.

DLD OUTPUTSPACE

MEM Xdddd Memory used by job Xdddd. DLD MEM X2222

CLDTLD(abbr.CD)

aa[-aa]*

Detailed information on specified jobclass or range of job classes (allclasses if * or no class specified).

DLD CLDTLD ADLD CD BB-MM

NOTE: (-) means that SELECT is not allowed.

In response to the command using the CLDTLD option, messages SH40, SH41 andSH32 are sent:

• SH40 gives information on the job load and the multiprogramming level in the job class,

• SH41 gives the various limits linked to the job class (priority, step CPU, and elapsedtime),

• SH32 gives the connection of the job class(i.e. if it is a job class group or if it isattached to one).


47 A2 14UC Rev05 A-21

Examples:

See the right-hand of the table above.

Normal replies to certain DLD commands are as follows:

1. DLD or DLD BRIEF

SH21 hh.mm IN=in-nb HOLD=hold-nb SCH=sch-nb EX=ex-nb SUSP=susp-nb OUT=out-nb IDLE=idle-nb

Which indicates the number of jobs in each of the possible states:

IN HOLD SCHEDULED EXECUTING SUSPENDED OUT IDLE.

2. DLD CLASS [ . . . . ]

jclass [NOT] STARTED LOAD=class-ld/clmult-lmt SPR=spr XPR=xpr

Which indicates, for each class specified in the command, the following information:

- whether the class is started or not.- the current number of executing jobs of that class (class-ld) over the class

multiprogramming level (clmult-lmt).- the default scheduling (spr) and execution (xpr) priorities.

3. DLD LOAD

SH16 LOAD : STARTED=started-nb/current-nb BATCH=ex-nb+susp-nb IOF=iof-nb SERVICE=service-nb (01) LOAD : jclass1=load_1/multi_1 (02) LOAD : jclass1=load_1/multi_1...jclass2=load_2/multi_2 (03) LOAD : jclass1=load_1/multi_1...jclass3=load_3/multi_3 (04) LOAD : jclass1=load_1/multi_1...jclass4=load_4/multi_4 (05) LOAD : jclass1=load_1/multi_1...jclass5=load_5/multi_5 (06)

These messages are the response to DISPLAY_LOAD:

(01) This message displays the following:

- the total number of STARTED jobs over the maximumnumber of jobs

- the number of executing batch jobs plus suspendedbatch jobs

- the number of IOF jobs started- the number of SERVICE jobs started.

(02)-(06) These messages display the class load over the current classmulti-programming limit for each class.

DJP User's Guide

A-22 47 A2 14UC Rev05

4. NO JOBS RUNNING

If no jobs are currently running in the system, the following message is displayed:

(SH17) hh.mm NO JOBS

5. DLD ALLOUT SELECT=ST01

Displays all jobs with outputs in READY, WAIT, HOLD, or OUT state in the queue ofthe station ST01.

6. DLD ALLOUT SELECT=*

Displays all jobs with outputs in READY, WAIT, HOLD, or OUT state in the queue ofall stations.

7. DLD CD P

Displays detailed information about the job class P.

Response:

SH40 P START EX+SUSP=20 SCH=5 OTHER=67 MULTI=20 MDMULTI=NO SPR=7 SPRLIM=7 XPR=9 XPRLIM=5 ELAPTIME=30 GROUP:CLASS:PS PP PO PN PM PL PK PJ PI PH PG PF PE PD CLASS:PC PB PA


47 A2 14UC Rev05 A-23

A.7 DO (DISPLAY_OUTPUT)

Purpose

Displays the current status of outputs. Outputs may be selected according to the job towhich they belong (OUTPUT parameter) or to their current state in the system (STATEparameter). The display shows for each output its name, priority, class, device (PR =printer, state, station, size and number of copies.

Syntax

{ DISPLAY_OUTPUT } { DO }



[ { QUEUE } ] [ STATE = { WAIT } ] [ { HOLD } ] [ { OUT } ]

[ { STATION } { * } ] [ { } = { ALL } ] [ { ST } { name8 } ]


[ { JOBNAME } ] [ { } = name8 ] [ { JNM } ]

[ SIZE = { bool | 0 } ]

DJP User's Guide

A-24 47 A2 14UC Rev05

Parameters

OUTPUT Output(s) to be displayed. The following formats are allowed:


- Xnnnn:nnnn } to refer to a specific output } (Xnnnn:name means the first output - Xnnnn:name } so named)



- Xnnnn-Xnnnn to refer to all outputs of a range of jobs. The first ron must be lower than the second.



If neither OUTPUT nor STATE are specified, the scope of thecommand is restricted to only the outputs of the OPERATORjob (or of the IOF job corresponding to the IOF usersubmitting the command).

SELCLASS (meaningful only for output names in the form Xnnnn)restricts the scope of the command to those outputs thatbelong to a certain class or range of classes. This may beexpressed as:



When omitted, all classes are assumed (A-Z).

STATE the current state of the outputs to be listed. This may beexpressed as OUT (for currently being output), HOLD (forheld), WAIT (for waiting to be output), or QUEUE (for any ofthe preceding).

STATION (with STATE) further qualifies the outputs to be listed bynaming the station to which they are attached (* and ALLstand for any station). When omitted, the default station isassumed.(with OUTPUT) restricts the scope of the command to thespecified station. When omitted, or when * or ALL isspecified, there is no station restriction.


47 A2 14UC Rev05 A-25

SELECT restricts the scope of the command to outputs belonging to aspecified user and/or project. Not meaningful when OUTPUTspecifies a list of outputs (format 1) or when STATE isspecified. By default, only the outputs belonging to thecommand submitter are selected.


SIZE when 1 (meaningful only when STATE is specified), thenumber of lines and pages of the queued outputs isdisplayed. Default is 0.

Rules

• SELCLASS is ignored for names of specific outputs (Xnnnn:nnnn or Xnnnn:name).

• OUTPUT and STATE are mutually exclusive.

• If neither OUTPUT or STATE is specified, command only concerns outputs ofOPERATOR job (or IOF job corresponding to the IOF user submitting the command).

Examples:

DO {display only the outputs of the OPERATOR or IOF job. Seeconstraints above.}

DO STATE=QUEUE {display all outputs, belonging to the command submitter, inthe queue of the current or specified station}

DO STATE=HOLD STATION=ST1{display all held outputs, belonging to the commandsubmitter, that are attached to station ST1}

DO X2345 {display all outputs of X2345}

DO X2345 Z {only those in class Z}

DO X2345 P-Z {only those of classes P to Z}

DO X2345:2 {display specified output}

DO (X2345:1 X2345:RES) {display two specified outputs}

DO STATE=QUEUE SELCLASS=W SIZE=1{display the queued, class W outputs with their number oflines and pages}

DO STATE=WAIT {display all queued outputs in the WAIT state}

DO X123-X2617 SELECT=U1/P1{display the outputs, belonging to user U1 of project P1, ofthe jobs whose RON is in the range X123 to X2617}

DO JOBNAME=JOB1 {display all the outputs, belonging to the command submitter,of all jobs named JOB1}

DJP User's Guide

A-26 47 A2 14UC Rev05

A.8 DSO (DISPLAY_SECURITY_OPTIONS)

Function:

Displays the security options for the site

• declared by the SECOPT and SADMOPT statements of CONFIG

• and recorded in the SITE.CATALOG.

Syntax:

{ DISPLAY_SECURITY_OPTIONS }{ }{ DSO }

Parameters: None

Constraints: None

Description of Message Entries:

PROTECTED SYSTEM(ACCESS RIGHTS): defines the access rights recorded in the SITE.CATALOG

(see C.3.1 Access Rights and Security).

=YES: access to files is checked according to the rightsdefined for the project in the GCOS 7 site catalog.

=NO: access to files is unrestricted for all users.

CHKJSADM(SADMOPT parameter): defines the restriction of job submission under SYSADMIN.

=YES: GCOS 7 checks that users running jobs forSYSADMIN are cataloged under the SYSADMINproject.

=NO: Job submission under SYSADMIN is unrestricted.

CHKPW(SECOPT parameter): defines if the password is to be checked; applicable where

the project of the user submitting the request has beendefined with either UFT, DJP or SPOOL in the catalog.

=NO: default: password is not checked.=YES: the site receiving the request checks the

password of the user submitting the job (thepassword can be provided when the command issubmitted).


47 A2 14UC Rev05 A-27

ERASE(SECOPT parameter): specifies if the entire data space allocated to all files to be

deleted is to be overwritten with binary zeros.

=NO: default: the disk is not physically erased unlessthe system is configured with mandatory defaulterasing.

=YES: the disk is physically erased.

GCLKPROJ(SADMOPT parameter): defines the user access to GCL procedures specifying LOCK

in the PROC statement.

=YES: access is available to any user under the sameproject as the user compiling these procedures.

=NO: access is limited only to the user compiling theseprocedures.

GCLKSADM(SADMOPT parameter): defines the SYSADMIN access to GCL procedures specifying

LOCK in the PROC statement.

=YES: users under the SYSADMIN project have thesame rights of access as the user compilingthese procedures.

=NO: users under the SYSADMIN project have noadditional access rights.

GCSADMOP(SADMOPT parameter): defines the SYSADMIN access to Main Operator commands

through EXDIR.

=YES: users under the SYSADMIN project have thesame rights as the Main Operator.

=NO: users under the SYSADMIN project are normalIOF users.

MIRROR(SADMOPT parameter): defines if MIRRORED disks are used.

=YES: duplicate WRITEs on 2 disks.=NO: no MIRRORED disks.

NETSEC(SECOPT parameter): defines how connections are to be checked.

=YES: connections always go through the front-endprocessor which performs security checks usingLACS software.

=NO: local connections are checked by GCOS 7.

SA7ADMIN(SECOPT parameter): defines how the user administration of the site is performed.

=YES: administration is performed by SECUR'ACCESS.=NO: administration is performed by SYSADMIN

through catalog management (MNCAT).

DJP User's Guide

A-28 47 A2 14UC Rev05

SA7LOGON(SECOPT parameter): defines how the user's access rights are to be checked.

=YES: user rights to access TDS/IOF applications arechecked by SECUR'ACCESS at connection time.

=NO: access rights are checked by GCOS 7.

SA7NOCSL(SECOPT parameter): defines if SECUR'ACCESS checks the identity of the user

logging on to the local system console.

=NO: the user's identity is checked by SECUR'ACCESS;meaningful only if SA7LOGON=YES .

=YES: the user's identity is checked by GCOS 7.

Example:

S: DSO;

14.16 SECURITY OPTIONS FOR : BPA6 ON: OCT 10, 1995 ARE: PROJECT/USER CHECKS = YES PROJECT/BILLING CHECKS = NO PROTECTED SYSTEM (ACCESS RIGHTS) = YES

SA7LOGON = YES SA7ADMIN = NO SA7NOCSL = NO NETSEC = NO CHKPW = YES ERASE = YES

SYSADMIN OPTIONS ARE: CHKJSADM = NO GCLKPROJ = NO GCLKSADM = NO GCSADMOP = YES MIRROR = YES

S:


47 A2 14UC Rev05 A-29

A.9 DUR (DISPLAY_USER_REQ)

Function

Displays the status of file transfer requests.

Syntax

{ DISPLAY_USER_REQ }{ }{ DUR }

[ { {[{SUBMITTER} {submitter-name} }}][ { {[{ }={--------------}[.project-name]]}}][ { ALL {[{SELECT } {user-name } }}][ { --- { }}][ REQUEST={ { JOBNAME = bool }}][ { }][ { { Jddddddd [ Jddddddd ... ] } }][ { ( { } ) }][ { { name8 [ name8 ... ] } }]

[ { { SUBMITTER } } ][ { { } = submitter-name [ .project-name ] } ][ { { SELECT } } ][ { } ][ { USER = secondary-user-name [ .project-name ] } ]

[ DETAILED = { 0 | bool }]

Parameters

REQUEST: identifies the request(s)ALL (default): all requestsrequest-list: a list up to 16 requests of the format (request[,request...]) where request is one of the following forms:Jddddddd: Jobset Occurrence Number (JON) resulting fromthe EJR commandname8: the symbolic name of a request as specified by theNAME parameter of the EJR command.

SUBMITTERalias SELECT: When specified with ALL, restricts the display to the named

user. Default is the name of the submitter of the command.When specified without ALL, identifies the submitter of therequest(s).SUBMITTER alias SELECT can be optionally specified for agiven project.

JOBNAME: if 1, displays the name of the job.

USER: identifies the name supplied for USER in the EJR or EFTRcommand.

DJP User's Guide

A-30 47 A2 14UC Rev05

DETAILED: is meaningful only when REQUEST=ALL.if = 1: displays all information as for REQUEST=name8(request name).if = 0 (default value): displays only the list of requests.

Messages

DUR request

<time> <request> <class> <priority> <state> <p-user> <s-user>

INFILE = <infile-description> OUTFILE = <outfile-description> HOST = <execution-host-name>

The following messages will be included depending on how the jobrequest has been submitted:

1) OUTVAL INFORMATION DESTINATION=<station-name> CLASS=<class> PRIORITY=<priority>

2) REQUEST WDTM WILL BE EXECUTED: AT:<time> <date> REPEAT=<n> TIMES EVERY=<interval>

3) REQUEST WTFR WAITING FOR COMPLETION OF <list of up to 8 requests>

4) VALUES OF JOB REQUEST <values passed to job>

where:

request: file transfer occurrence number

class: one alphabetic character in the range A through Z

priority: one numeric character in the range 0 through 7

state: {RDY |HOLD |WAIT |EX}

p-user: primary user, the submitter of the request, designated withthe USER keyword

s-user: secondary submitter name, designated with the SSI(Secondary Submitter Identity) keyword; given only if differentfrom p-user


47 A2 14UC Rev05 A-31

Examples:

S: DUR or S: DUR ALL

displays all the terminal user's current requests.

S: DUR ALL; 17.47 F318 C 3 RDY SITE=BCLE OPERATOR F324 C 3 RDY SITE=BCLE DUPONT F326 C 3 RDY SITE=BCLE DUBOIS F360 C 3 RDY SITE=BCLE OPERATOR F365 C 3 RDY SITE=BCLE OPERATOR F366 C 3 RDY SITE=BCLE OPERATOR F368 C 3 RDY SITE=BCLE OPERATOR F375 C 3 RDY SITE=BCLE OPERATOR F380 C 3 RDY SITE=BCLE OPERATOR F383 C 3 RDY SITE=BCLE OPERATOR F386 C 3 RDY SITE=BCLE OPERATOR J387 C 3 HOLD SITE=BCLE HOST=D9 DUPONT J404 C 3 EX SITE=BCLE HOST=D9 DUBOIS F418 C 3 RDY SITE=BCLE DURAND

S: DUR ALL JONES

displays all the current requests submitted by JONES.

S: DUR SELECT = JONES.PREP

displays all the current requests submitted by the user JONES under the project PREP.

S: DUR (F22 J44 RQP)

displays the three named requests.

S: DUR F145;

14.48 F145 C 3 EX USER=JONES INFILE=FIL SQ SL:TSU216:MS/D500 OUTFILE=$BCLE:FIL SQ SL REMOTE:TSU217:MS/D500

S: DUR J1288

15.00 J1288 C 3 WAIT TOTO USER=JONES SSI=SMITH INFILE=MYJOB1:MYLIB:K185:MS/D500 HOST=PICD

S: DUR ALL DETAILED

display the list of all terminal user's requests with detailed information.

DJP User's Guide

A-32 47 A2 14UC Rev05

A.10 ENTER_JOB_REQ (EJR, EJ)

Purpose

Requests the execution of one or more jobs or submits a jobset request (see Section 8,Part 1, for jobs and Section 9, Part 1, for jobsets).

Syntax

{ ENTER_JOB_REQ }{ EJR }{ EJ }

[ MEMBERS = star62 ]

[ PROC = name31 ]

[ LIB = lib78 ]

[ CLASS = aa ]

[ PRIORITY = { 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 } ]

[ HOLDOUT = bool ]

[ DEST = [name8.]name8 ]

[ HOLD = bool ]

[ SWITCHES = { ( dec2 [ dec2 ] ... ) | 32 } ]

{ VALUES } [ { } = ( value-expressions ) ] { VL }

[ USER = name12 ]

[ PROJECT = name12 ]

[ BILLING = name12 ]

[ REPEAT = bool ]

[ HOST = name8 ]

[ RHOLD = bool ]

[ RCLASS = a ]

[ RPRIORITY = { 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 } ]

[ NAME = name8 ]


47 A2 14UC Rev05 A-33

{ IMMED } { mm.dd.yy. hh.mm } [ WHEN = { } ] { +nnnn{W|D|H|M} } { when-clause }

{ W | WEEK } { D | DAY } { H | HOUR } [ EVERY = ( [ dec5 ] { M | MIN } [ dec5 ] ) ] { MONTH } { WKD } { NWKD }

{ CANCEL | NO } { IMMED } [ RRESTART = { } ] { delay } { delayE }

[ WAIT = ( name8 [ name8 ] ... ) ]

[ JOBLANG = { JCL | GCL } ]

[ DEBUG_GCL = { bool | 0 } ]

[ TRACE_GCL = { bool | 0 } ]

[ PRTFILE = file78 ]

- - - - - - - - - - - - - - - - - - -

{ VALUES2 } [ { } = ( value-expressions ) ] { VL2 }



{ INFILE } [ { } = rfile78 ] { INF }

[ STARTUP = bool ]

{ HOLDCOUNT } [ { } = dec2 ] { HOLDCNT }

[ DELETE = { NO | YES | FORCE } ]

[ FROM = name12 ]

[ TO = name12 ]

[ BANINF = ( char12 [ char12 [ char12 [ char12 ] ] ] ) ]

DJP User's Guide

A-34 47 A2 14UC Rev05

[ BANNER = bool ]

[ LIST = { SOURCE | ALL | NO } ]

[ JOR = { NORMAL | NO | ABORT } ]

[ SEV = { 1 | 2 | 3 | 4 | 5 } ]

[ ENVT = name12 ]

[ JOBNAME = name8 ]

{ TRACE } [ { } = { bool | 0 } ] { TR }

[ BRIEF = { bool | 0 } ]

[ EXPVAL = { bool | 0 } ]

Parameters

MEMBERS a star-name denoting the member(s) containing the job(s) tobe submitted.

PROC the name of the GCL procedure to be submitted as anabsentee job (see Section 8, Part 1).

LIB the library containing the members or the procedure to besubmitted. It must not be a temporary library. If the parameteris omitted, the default SL output library (#SLIB), forMEMBERS, or the current binary input search path(#BINLIB), for PROC, is assumed, unless it refers totemporary libraries. If #SLIB or #BINLIB is temporary orunassigned, a system default library is assumed.

CLASS the class of the submitted jobs, expressed as one or twoletters in the range A to RZ.

PRIORITY the priority of the submitted jobs, expressed as a digit in therange 0 to 7. The lower the priority, the higher the urgency.

HOLDOUT if 1, jobs' outputs are to be held. The directiveRELEASE_OUTPUT can subsequently be used to releasethem.

DEST destination of output expressed as [host-name.]station-name.See Section 9, Part 1, for discussion.

HOLD if 1, jobs are held. The directive RELEASE_JOB can be usedin order to make them eligible for execution.

SWITCHES a list of the switches (expressed as numbers in the range 0 to31) to be set in the submitted jobs. Value 32 denotes thatcurrent values for the switches are passed.


47 A2 14UC Rev05 A-35

VALUES a list of one or more values, enclosed in parentheses, to bepassed to the submitted job (MEMBERS), or denoting theparameters of the submitted absentee job (PROC). If thevalues exceed 254 characters, "hidden" parametersVALUES2, VALUES3, and VALUES4 may be used.

USER/PROJECT/BILLINGif submitting jobs on behalf of another user, project, or billing.

REPEAT if 1, repeat the job if it is cancelled or if there is a systemfailure or abort.

HOST the name of the host where the jobs are to execute.

RHOLD if 1, hold the jobset request. The directiveRELEASE_USER_REQ can subsequently be used to releasethe request.

RCLASS the jobset request class, expressed as a letter in the range Ato Z.

RPRIORITY the priority of the jobset request, expressed as a number inthe range 0 to 7. The lower the number, the higher theurgency.

NAME the symbolic name to be given to the request for furtherreferences in dedicated directives. Syntaxes in the formJnnnnnnn and Fnnnnnnn are not allowed. When omitted,the request may only be referred to by its Jobset OccurrenceNumber (JON in the form Jnnnnnnn) returned by thisdirective.

WHEN when the request is to be taken into account, expressed as:

IMMED now (default) [mm.dd.yy.]hh.mm a date +nnnnn{W|D|H|M} a number of weeks, days, hours, minutes when-clause a range of expressions

The WHEN parameter offers a rich selection of options. For adetailed discussion, refer to the Help texts and to the GCOS 7System Operator's Guide. When omitted, IMMED isassumed.

EVERY the interval and number of times the request is to beexecuted, expressed as:

(interval [ number-of-times ])

If number-of-times is omitted, an infinite number of times isassumed. Interval can be expressed as a number of weeks,days, hours, or minutes; month (MONTH), working days(WKD), or non-working days (NWKD). The minimum intervalis defined by the CONFIG statement DJPCTL (default =15 minutes, lowest is 1 minute). The maximum interval is45 days, 12 hours, and 15 minutes (65535 minutes).

DJP User's Guide

A-36 47 A2 14UC Rev05

The working days (WKD) are the days that belong neither tothe list of non-working days nor to that of holidays. WhenNWKD is used, the request is enqueued on non-working daysand holidays. For a more detailed discussion, refer to theHelp texts and Appendix E of the GCOS 7 System Operator'sGuide.

RRESTART specifies how an EFTR request should be handled, if therequest is not executed because of a system failure or normalshutdown. Valid options are:

IMMED request enqueued immediatelyCANCEL/NO request is cancelleddelay delay added to normal enqueing time.delayE elapsed delay, the maximum delay allowed for

placing request in queue.

For more detailed information, refer to the Help texts andAppendix E of the GCOS 7 System Operator's Guide.

WAIT a list of up to 8 request names (FON, JON, or symbolic). Thecurrent request will not be executed until the WAIT requestshave completed execution. In the case of the JON, if theissued job is executed:- locally the current request waits until completion. If the

first job terminates with a severity greater than or equalto 3, the waiting request is cancelled. If the severity isless than 3, the request is released.

- on a remote site the current request waits untilcompletion of the JCL file transfer.

JOBLANG command language used in the job description. It isrecommended that the command language of the jobbespecified in the statement $JOB. (Refer to the GCLProgrammer's Manual.)

GCL GCOS 7 Command LanguageJCL GCOS 7 Job Control Language

The default value for the parameter JOBLANG is the valueset in the system variable #JOBLANG of the user profile.The variable #JOBLANG has no default value. WhenJOBLANG is specified in EJR and in the statement $JOB, thevalue specified in $JOB overrides the value specified in EJR.

DEBUG_GCL if 1, debug GCL procedures. Each time a line is executed, itis displayed with evaluated variables prefixed by procedurename and line number. The default value is 0. Thisparameter may only be used when the job descriptionlanguage is GCL. DEBUG_GCL=1 is equivalent to thedirective MODIFY_PROFILE DEBUG.

TRACE_GCL if 1, trace all CALL statements executed on the current outputdevice. The default value is 0. This parameter may only beused when the job description language is GCL.TRACE_GCL=1 is equivalent to the directiveMODIFY_PROFILE TRACE.


47 A2 14UC Rev05 A-37

PRTFILE the report file, used when the job description language isGCL. If omitted (and if PRTFILE is not specified in the$OPTIONS statement), the report is directed to the standardsystem file SYS.OUT.

The value specified for PRTFILE in EJR overrides the valuespecified in $OPTIONS.

VALUES2/VALUES3/VALUES4may be used when the values exceed 254 characters (seeparameter VALUES). VALUES2, VALUES3, and VALUES4,though "hidden parameters", appear on the menu directlyafter VALUES when "EJR+" is entered.

INFILE the file or remote file containing the jobs to be submitted.

STARTUP if 0, do not execute the STARTUP sequences in thesubmitted jobs.

HOLDCOUNT the submitted jobs are held. They will be released only whenthe specified number of RELEASE_JOB directives have beenissued.

DELETE if YES, delete the subfile after submission. If FORCE, thesubfile is deleted, even if submission is unsuccessful.

FROM/TO (with INFILE only) select the first and last jobs to besubmitted in INFILE. Default values are the first job forFROM, and the last one for TO.

BANINF up to four 12-character texts to appear on the output banner.The banner is built from bottom to top, with each succeedingline pushing up the previous one(s).

BANNER if 0, no output banner is generated.

LIST permits the user to select the type of information to be printedwhen listing the JCL on the Job Occurrence Report.

SOURCE the source JCL or GCL, inserted StreamReader statements, records inserted using a$SWINPUT statement with the CONSOLEparameter, and error messages are listed.

ALL the source JCL or GCL, records inserted usinga $SWINPUT statement, and all expansionsof JCL sequences which are entered usingINVOKE, and project start-up are listed, alongwith error messages.

NO only Stream Reader statements, comments,and error messages are listed.

If Access Rights have been implemented and the user doesnot have the READ right over the file(s) containing theinformation to be printed, then LIST is ignored.

DJP User's Guide

A-38 47 A2 14UC Rev05

JORNORMAL a Job Occurrence Report will be produced at

the end of job execution.

NO no Job Occurrence Report will be produced.

ABORT a Job Occurrence Report will be producedwhen job execution aborts. For a GCLprocedure submitted as an absentee job, thedefault value is ABORT.

SEV with PROC: defines the session severity level at which a GCLprocedure submitted as an absentee job will be aborted at theend of the current step. The default value is 4.

with JOBLANG=GCL: defines the severity level at which thebatch job will be aborted at the end of the current step ifDEFAULT is the current value for ON_ERROR.

SEV is ignored when JOBLANG=JCL.

ENVT (with PROC only) defines the alternate environment fromwhich a GCL procedure submitted as an absentee job isaccessible by the user's project. When omitted, the defaultenvironment of the user's project is assumed.

JOBNAME (with PROC only) the symbolic name to be given to theabsentee job. When omitted, the name ABSENTEE isassumed.

TRACE if 1, the RFA (Remote File Access) trace is displayed on thescreen. The default value is 0.

EXPVAL if 1, expansion of the values in the JCL of the job is requiredin the Job Occurrence Report. The default value is 0. Whenthe level of embedded values is grater than 2, the expansionmay give unpredictable results (without any effect in thesubstitution mechanism at translation time.)

BRIEF if 1 and if the parametere HOST is used, only the messagesissued at the beginning and end of the job execution aredisplayed. If the parameter HOST is not used, BRIEF isignored. The default value is 0.


47 A2 14UC Rev05 A-39

Constraints:

• BANNER=0 and BANINF are mutually exclusive.

• A jobset (see Section 9, Part 1) is created if:

either INFILE is used and denotes a remote fileor one of the following parameters is used: HOST, RHOLD,

WHEN, EVERY, WAIT.

• Either MEMBERS, PROC, or INFILE must be specified.

• INFILE is exclusive of LIB, MEMBERS, PROC, and DELETE.

• JOBLANG (explicit or default value), PRFILE, DEBUG-GCL, TRACE-GCL may not beused when HOST is specified or when a remote file is specified in INFILE.

• HOLD and HOLDCOUNT are mutually exclusive.

• STARTUP has meaning only when MEMBERS is specified.

• FROM and TO can only be used when INFILE is used.

• ENVT and JOBNAME are meaningful only when PROC is used.

• SEV is meaningful only when PROC or JOBLANG=GCL is used.

• File transfer and job requests may be mixed, but the mixture of JONs/FONs andsymbolic names is not allowed. WAIT=(F18,F25,J38) or WAIT=(A,B,C,D) is allowed;WAIT=(F18,A,J38,B) is not allowed.

• Chaining between requests is limited to 1 level.EJ MYJOB1 NAME=REQ1EJ MYJOB2 NAME=REQ2 WAIT=REQ1 is allowedEJ MYJOB3 WAIT=REQ2 will be rejected because REQ2 already waits on REQ1

• If JOBLANG=GCL, EXPVAL and HOST must not be specified

• The Keywords specified in VALUES must be less or equal to 8 characters in GCLbatch.

DJP User's Guide

A-40 47 A2 14UC Rev05

Examples:

EJR PROC=LSV VALUES=MYV:MS/D500 {submit absentee job to list a volume}

EJR MYJOBS CLASS=D {submit jobs in output library}

EJR JOBS LIB=PROJ.LIB {submit jobs within specified library}

EJR JOBS WAIT=(F18 F19) {submit after completion of two file transfer requests}

EJR MYJOB1 NAME=REQ1 WAIT=(F12,J67) {submit after completion of file transfer F12 and job J67}

EJR MYJOB2 WAIT=(A,B,C,D) {submit after completion of jobs or file transfers A, B, C, and D}

EJR PROC=MYPROC BINLIB=MYLIB.BIN ENVT=PREP {submit absentee job using alternate environment PREP}

EJR PROC=MYPROC BINLIB=MYLIB.BIN JOBNAME=MYPROC {submit absentee job with symbolic name MYPROC}

EJR JOBS LIB=PROJ.LIB HOST=LYON NAME=PAYROLL WAIT=(FP1 FP2) {execution on remote host, wait for two file transfer requests}

EJR INFILE=$LYON:P1.REMLIB..REMSF WHEN=+20H {submit jobs from remote file in 20 hours time}

EJR PROC=MYPROC VALUES=(A,B,C) {submit absentee job with specified values}

LET A1 A; LET B1 B; LET C1 CEJR PROC=MYPROC VALUES=#CAT(%A1,',',%B1,',',%C1) {same as above with calculated values}

EJR MYJOB EVERY=(2H 3) {submit job MYJOB; execution every two hours and repeated three times}


47 A2 14UC Rev05 A-41

A.11 FO (FORCE_OUTPUT)

Purpose

Forces an output. The output is started as soon as an output device of the correct typebecomes available. If a forced output was held, it is released.

Syntax

{ FORCE_OUTPUT } { FO }

OUTPUT = output14

[ STRONG = bool ]

Parameters

OUTPUT the name of the output to be forced. It may take one or thetwo following forms:

Xnnnn:nnnnXnnnn:name

STRONG if 1, the output is forced even if the output is in the READYstate.

Rules

Only one output may be forced on a station at any one time. Any subsequentFORCE_OUTPUT command on a given station is rejected, until the forced output is held,or until it no longer exists in the queue of a station. The operator must either wait until theprevious forced output is completed, or else cancel it, or hold it, or transfer it to anotherstation before trying again.

Examples:

FO X1234:2 {force the named output}

FO X1234:REPORT {force the output of job X1234 named REPORT}

FO X45:3 STRONG {force the specified output even if in the READY state}

DJP User's Guide

A-42 47 A2 14UC Rev05

A.12 FUR (FORCE_USER_REQ)

Function: reserved for the MAIN operator

Forces the execution of a request whatever its state. The request will be selected beforeany other request of the same queue. For a given site, only one request can be forced.

The WHEN and/or WAIT conditions (if any) are ignored and the request is put in queue inthe WAIT state with the highest priority.

Syntax

{ FORCE_USER_REQ }{ }{ FUR }

{ Jddddddd }REQUEST = { } { name8 }

Parameters

REQUEST: the name of the request to be forced in one of the followingforms:


name8: the symbolic name of a request as specified by theNAME parameter of the EJR command.

Constraints

Only one user request may be forced at a time, on any given station. If a second one isforced before the first has started:

• the second user request is forced• the first user request is placed in the WAIT state.

A forced user request may be held, by using the HUR (HOLD_USER_REQ) command.

Messages

The following message is displayed if the command is successful:

<time> <request-id> FORCED

Examples:

S:FUR J12

11.55 J12 FORCED

forces the job processing request J12 with the following message displayed.


47 A2 14UC Rev05 A-43

A.13 HUR (HOLD_USER_REQ)

Function

Prevents a file transfer from being executed or interrupts a file transfer currentlyprocessed by placing it in the HOLD state.

HUR is only effective on the submitter's own requests and no one else's.

The effect of HUR is symmetric with the RUR (Release User Request) command .

Syntax

{ HOLD_USER_REQ }{ }{ HUR }

{ Jddddddd [ Jddddddd ... ] }REQUEST = ( { } ) { name8 [name8 ... ] }

Parameters

REQUEST: identifies a list of up to 16 requests to be held, the name ofthe request being in one of the following formats:


name8: the symbolic name of a request as specified by theNAME parameter of the EJR command.

Messages

The following message is displayed, if the command is successful:<time> <request-name> HELD

Examples:

S: HUR F12 16.08 J12 HELD

places the job processing request J12 in HOLD.

S: HUR (J3 HQR J2) 16.10 J3 HELD HQR HELD J2 HELD

places the three requests J3, HQR and J2 in HOLD.

DJP User's Guide

A-44 47 A2 14UC Rev05

A.14 MDC (MODIFY_CONFIGURATION)

Function: reserved for the MAIN and Station operators

Modifies the default output priority and the default output media associated with an outputclass.

For the MAIN operator, the additional parameters of the command (shown in BOLD in thesyntax ) allow modifying the station and preinitializing or cancelling load modules affectingresident system functions and memory dimensions.

Syntax

{ MODIFY_CONFIGURATION }{ }{ MDC }

{ [ { PRIORITY } ] } { [ { } = dec1 ] } { [ { PRTY } ] } { }{ OUTCLASS } { [ { MEDIA } ] }

{ } = ( a [ a ... ] ) { [ { } = name6 ] }{ OC } { [ { MD } ] } { } { [ { STATION } ] } { [ { } = name8 ] } { [ { ST } ] }

[ PLM = [ libname.. ] lm-name [ :volume :dvc ] ]

[ CLM = [ libname.. ] lm-name [ :volume :dvc ] ]

[ LINES = {* | char-7} ]

Parameters in BOLD apply only to the MAIN operator.

Parameters

OUTCLASS: the output class whose characteristics are to be modified,expressed as a letter (A to Z).

PRIORITY: the new default output priority for the output class, expressedas a digit in the range 0 to 7.

MEDIA: the new default output media for the output class.


47 A2 14UC Rev05 A-45

LINES: the maximum number of lines of an output in a given class.If LINES is equal to * or 9999999: the number of lines is notlimitted in the given class.If the parameter is not specified, the current value is notchanged. The values of LINES is greater than 0 (zero).In the concerned class, if a job creates an output greater thanthe quota of lines: this job aborts with the Return Code:ERLMOV.

NOTES:1. Dumps are not concerned by the parameter LINES.2. The value of the LINES parameter is independant of the

bufferization of the OW command.

Examples:MDC OC=B LINES=100000The maximum size of each output in class B is 100 000 lines.MDC OC=Z LINES =*The number of lines is illimitted in each output of class Z.

STATION: applicable only to the MAIN operator.the name of the unattended station for which the outclassattributes are to be changed.When Station is omitted, the default is the MAIN station.

PLM: applicable only to the MAIN operator.identifies the load-module to be preinitialized.

CLM: applicable only to the MAIN operator.identifies the preinitialized load-module to be cancelled.

Constraints

Station Operator: PRIORITY or (MEDIA or LINES or both) must be specified.

MAIN Operator: If PRIORITY and/or MEDIA and/or STATION and/or LINESare specified, OUTCLASS must be specified.

Examples:

S: MDC Z MD=I12B45default media for class Z is I12B45}

S: MDC Z 3 I12B45set both the default priority and media for output class Z.

S: MDC OC=(A,B) 3 ST=STNmodify output classes A and B default priority for station STN.

DJP User's Guide

A-46 47 A2 14UC Rev05

A.15 MDDJP (MODIFY_DJP)

Function

Sets the maximum number of simultaneous transfer activities between the local site and aremote site according to the criteria affecting such connections. As with all modifycommands, the default will be whatever value had been previously selected:

Syntax

{MODIFY_DJP}{ }{MDDJP }

SITE = name-4

TFRNB = dec-2

[ STRONG = bool ]

[ WAITIME = dec-2 ]

[ NWKD = ( dayname [ ,dayname ... ] ) ]

[ YEAR = year ]

[ HOLIDAYS = (year, day-nbr [ ,day-nbr ... ] ) ]

[ HOLIDAYS_MODE = RPL | ADD | DL ]

[ UFTWAIT = HH.MM]

Parameters

SITE: the name of the site at which transfer activity is to bemodified.

TFRNB: the number of transfers that can take place simultaneouslybetween the local site and the one specified by SITE.When 0, no transfer is possible.

STRONG: meaningful only when TFRNB is less than the current numberof transfers in progress. If 0 (default) or not specified, thesystem waits for the normal completion of transfers in excessof TFRNB. If 1, excess transfers are immediately aborted.

NOTE: To obtain the sites attached to stations, the DC command is used, with the STparameter.

WAITIME: the time in minutes between two consecutive attempts atestablishing connections towards the same site when the firstconnection fails.Default is 5 minutes.


47 A2 14UC Rev05 A-47

NWKD: Non Working Days specifying the following values:NO: all days (of the week) are working daysThe name of the day (of the week) is identified by its first3 letters, for example, Sunday is SUN.

NOTE: After a COLD/CLEAN restart, NWKD values are lost.

The days actually not worked are NWKD and Holidays.

YEAR: the year to consider

HOLIDAYS: ( year, day-nbr [ ,day-nbr ... ] ) where the first argumentintroduces the year followed by a list of up to 20 daysexpressed in numbers.

Example:HOLIDAYS=(1995,1,106,121)This means that the days 1, 106 and 121 of the year 1992 areholidays.

HOLIDAYS_MODE: Specifies how public holidays given in HOLIDAYS are used:

- RPL: Replace public holidays in the current list ofspecified year

- ADD: Add public holidays in the current list of specifiedyear

- DL: Delete public holidays in the current list of specifiedyear

UFTWAIT: Waiting time, in hours and/or minutes, between two datatransfers (min = 1 minute, max = 72 hours).)

NOTE: After a COLD/CLEAN restart, Holidays values are lost. The days actually notworked are NWKD and Holidays.

Examples:

S: MDDJP SIT3 1010 transfer activities with site SIT3 for which job class Y must be at least equal to 10 inorder to launch 10 GTPs.

S: MDDJP SIT3 5 STRONGreduce transfer activity and abort excess transfers.

S: MDDJP UFTWAIT=00.20the connection to a remote site will be aborted if during 20 minutes no data transferoccurs.

S: MDDJP YEAR=2000 HOLIDAYS=(1,366) HOLIDAYS_MODE=ADDfor the year 2000, add the public holidays: January 1st, December 31th.

S: MDDJP YEAR=2000 HOLIDAYS=(1,365) HOLIDAYS_MODE=DLfor the year 2000, delete the public holidays: January 1st, December 30th.

S: MDDJP YEAR=2000 HOLIDAYS_MODE=RPLfor the year 2000, there are no public holidays.

DJP User's Guide

A-48 47 A2 14UC Rev05

NOTE: MDDJP applies also to the local site, that is, the command allows regulating thenumber of READERs and local GTPs.

If TFRNB is set to 0 for the local site, no further jobs can be submitted; however,EJR requests will be accepted but not executed. To execute jobs, set TFRNB toa non-zero value.


47 A2 14UC Rev05 A-49

A.16 MODIFY_OUTPUT (MDO, MO)

Purpose

Modifies the characteristics of outputs.

IMPORTANT

This command applies only to the outputs on which the submitter hasaccess rights

Syntax

{ MODIFY_OUTPUT } { MDO } { MO }



[ CLASS = a ]

[ PRIORITY = {0|1|2|3|4|5|6|7} ]

[ DEST = [ name8.] name8 ]

[ COPIES = nn ]

[ { STATION } ] [ { } = stnnm ] [ { ST } ]


[ { JOBNAME } ] [ { } = name8 ] [ { JNM } ]

DJP User's Guide

A-50 47 A2 14UC Rev05

Parameters

OUTPUT a list of the names of up to 16 outputs whose characteristicsare to be modified. These may take the following forms:


- Xnnnn:nnnnn} to refer to a specific output } (Xnnnn:name means the first output - Xnnnn:name } so named)



- Xnnnn-Xnnnn to refer to all outputs of a range of jobs. The first ron must be lower than the first.



SELCLASS (meaningful only for output names in the form Xnnnn)restricts the scope fo the directive to those outputs thatbelong to the specified class or range of classes. This may beexpressed as:



When SELCLASS is omitted, all existing and future outputs ofthe job are selected.

CLASS the new class for the selected outputs: a letter in the range Ato Z.

PRIORITY the new priority for the selected outputs: a digit in the range 0to 7 (the lower the priority number, the higher the urgency).

DEST the new destination of the output(s) in the form:

[host-name.] station-name

COPIES the new number of copies (see DPRINT command).

STATION restricts the scope of the command to outputs attached to thestation specified. When omitted or when * or ALL is specified,there is no station restriction.


47 A2 14UC Rev05 A-51

SELECT restricts the scope of the command to outputs belonging to aspecified user and/or project. Not meaningful when OUTPUTspecifies a list of outputs (format 1). By default, only theoutputs belonging to the command submitter are selected.


Rules

• SELCLASS is ignored for names of specific outputs (Xnnnn:nnnnn or Xnnnn:name).

• At least one of CLASS, DEST, PRIORITY, or COPIES must be used.

• DEST parameter must begin with a letter.

• If several output of the same job are given the same name, MDO Xnnnn :name onlyaffects the first output with that name encountered by the system.

• When SELCLASS is omitted, the modified CLASS, PRIORITY, and DEST (but not theCOPIES) apply to all existing and future outputs of the job. When SELCLASS=A-Z, onlycurrently known outputs are modified.

• While the output is being printed, no modification in the number of copies can be takeninto account before the start of the next copy. For example, if MDO COPIES=3 isentered during the printing of the third copy, the printer prints a fourth copy before itstops.

• CLASS, DEST and PRIORITY are ignored if output is already being printed.

• MDO COPIES=nn takes into account the number of copies already printed. Forexample, if 6 copies were requested and 3 have been printed, MDO Xron COPIES=8does not change the number of copies already printed. Five more are printed for a totalof 8. However, MDO Xron COPIES=4 results in just one more copy for a total of 4.

Examples:

MDO X123 DEST=MAIN {print all outputs of X123 on one of the main site printers}

MDO X123 C D 5 {set outputs of X123 of class C to class D and priority 5}

MDO (X123:2 X123:RES) CLASS=C{set two selected outputs of job X123 to class C}

MDO X123:1 CLASS=C DEST=HST1.STN2{modify class of one output and print it on a remote site}

MDO X123:RES COPIES=6{provide six copies of named output}

MDO * DEST=MAIN {reroute all outputs belonging to the command submitter andattached to the current station, to the MAIN station}

DJP User's Guide

A-52 47 A2 14UC Rev05

MDO * DEST=MAIN ST=STN{reroute all outputs belonging to the command submitter andattached to station STN, to station MAIN}

MDO X123 PRIORITY=6 {modify the priority of all current and future outputs of jobX123}

MDO X123 A-Z PRIORITY=1{modify only the priority of currently existing outputs}

MDO X123-X2167 CLASS=G{modify the class of all outputs, belonging to the commandsubmitter, of the jobs whose RON is in the range X123 toX2167}

MDO X34-X382 SELCLASS=A-E PRIORITY=2{modify the priority of all outputs, belonging to the commandsubmitter, of the jobs whose RON is in the range X34-X382and whose output classes are in the range A to E}

MDO * P Q {modify all class P outputs belonging to the commandsubmitter, to class Q}

MDO * SELECT=U1/P1 CLASS=A COPIES=2{modify the class and number of copies of all outputsbelonging to user U1 of project P1}

MDO * JOBNAME=JOB1 PRIORITY=1{modify the priority of all outputs, belonging to the commandsubmitter, of all jobs named JOB1}


47 A2 14UC Rev05 A-53

A.17 MDOP (MODIFY_OUTPUT_PARAMETERS)

Function

Sets the default output handling and output editing values for printouts issued during thecurrent session. These default values apply to the DPRINT directive.

Syntax

{ MODIFY_OUTPUT_PARAMETERS }{ }{ MDOP }

[ CLASS = a ]

[ PRIORITY = { 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 } ]

[ { END | JOB } ][ { } ][ { STEP } ][ WHEN = { } ][ { IMMED } ][ { } ][ { DEFER } ]

[ DEST = [ name8. ] name 8 ]

[ NAME = name8 ]

[ BANINF = ( char12 [ char12 [ char12 [ char12 ] ] ] ) ]

[ COPIES = ddd ]

[ { DEVCLASS } ][ { } = dvc ][ { DVC } ]

[ { MEDIA } ][ { } = char6 ][ { MD } ]

[ DELETE bool ]

[ HOLD = bool ]

[ { NO } ][ { YES } ][ { JOB } ][ BANNER = { } ][ { OUTPUT } ][ { COPY } ][ { MEMBER } ]

[ KEEP = bool]

DJP User's Guide

A-54 47 A2 14UC Rev05

Parameters

CLASS: the output class (a letter in the range A to Z). The default isinstallation defined.

PRIORITY: the priority as a number in the range 0 to 7. The lower thenumber, the higher the urgency.

WHEN: END or JOB: enqueueing of the output request when thesession is ended. This is the default option.

IMMED: enqueueing of the request as soon as the file isclosed.

STEP: enqueueing of the request at the end of programexecution.

DEFER: no enqueueing is done; a later DPRINT directive willcause the request to enqueued.

DEST: the destination of the output expressed as [host-name.]station-name. See Section 9, Part 1 for discussion.

NAME: a symbolic name to be given to outputs and to appear in theDISPLAY_OUTPUT directive.

BANINF: up to 4 12-character texts to appear on the output banner.

COPIES: the number of copies in the range 1 to 99.

DEVCLASS: the type of the device to be used. The default is installationdependent.

MEDIA: the belt to be used (if not the default).

DELETE: if 1, delete subfiles after printing (meaningful only for apermanent SYSOUT library).

HOLD: when 1, outputs are held by default. The directiveRELEASE_OUTPUT must be used to cancel the effect of thisparameter.

BANNER: whether a banner is to be generated (YES) or not (NO) andwhere: between jobs (JOB), deliveries (OUTPUT), copies(COPY) or members (MEMBER).

KEEP: when specified, the current values of the parameters notmodified by the command are kept, i.e., the standard systemparameters don't replace the current values; the default is 0.

Constraints:

MEDIA may not be specified if DEVCLASS is not.


47 A2 14UC Rev05 A-55

Examples:

MDOP Z {the default output class is Z}

MDOP DEST=SIT1.STN3 {define the default output station}

MDOP Z WHEN=IMMED {class is Z, immediate enqueueing}

MDOP Z BANINF=('MY OUTPUT', JONES) {class is Z, the last two lines of the banner are redefined}

MDOP CLASS = D DEST = STATION1

MDOP COPIES = 4 KEEP=1 {After these two commands, the output parameters will be:Class = D, DEST = STATION1 and COPIES = 4}

DJP User's Guide

A-56 47 A2 14UC Rev05

A.18 MDST (MODIFY_STATION)

Function: reserved for the MAIN or Station operator

Modifies the characteristics of a local (station operator) or remote (main operator) station.

Syntax

{ MODIFY_STATION }{ }{ MDST }

{ [ {DEVCLASS} {PR[/attr]} {DEVICE} ] } { [ { }={ } { }=rfile-78 ] } { [ {DVC } {CD[/attr]} {DV } ] }ADDLDV = name4 { } { [ SELCLASS = a [ -a ] ] } { } { [ LCASE = bool ] }

[ { * } ] [ { PRTDEST } ][ CLRLDV = { } ] [ { } = name 8 ][ { name4 } ] [ { PCHDEST } ]

[ EBANNER = bool ] [ FBANNER = n ] [ BANCHAR = char2 ]

[ { RESCUE_ON } ] [ { RESCUE_OFF } ][ { } = name8 ] [ { } = name8 ][ { RCON } ] [ { RCOFF } ]

[ { RESCUED_CLASS } ] [ { STATION } ][ { } = a [ -a ] ] [ { } = name8 ][ { RCCLASS } ] [ { ST } ]

Parameters

ADDLDV: the four-character name of a logical device to be defined andmade known to GCOS 7.

DEVCLASS: DEVCLASS is used with DEVICE and is applicable onlywith ADDLDV.the device class of the logical device: printer, card reader orcard punch.

DEVICE: DEVICE is used with DEVCLASS and is applicable onlywith ADDLDV.the DPS 6 path name (possibly including the site name)identifying the file or device to act as the named logicaldevice.Since the DPS 6 system file is considered foreign, 'rfile-78'must be protected by single quotes, as shown.


47 A2 14UC Rev05 A-57

SELCLASS: applicable only with ADDLDV.the default output class(es) attached to the logical deviceexpressed as a letter (A to Z), namely:- class for a single classclass-class for a range of classes.When omitted, all classes are assumed.

LCASE: applicable only with ADDLDV.If 1, the logical device can handle small letters.If 0, the logical device cannot handle small letters and thesystem translates small letters into capitals beforetransmitting to the device.

CLRDV: the name of a logical device whose definition is to be erased.CLRDV=* erases all device definitions and options attachedto the station.

PRTDEST/PCHDEST: the name of a station to which outputs will be directed:- printouts (PRTDEST)- punchouts (PCHDEST).

EBANNER: If 1, an end banner is required for outputs.

FBANNER: the number of front banners (0, 1, 2) for outputs.

BANCHAR: a two-character string to be used first as a banner separator,and the second one to print the large characters on thebanner.

RESCUE_ON/RESCUE_OFF:the name of another station to be used for rescuing(RESCUE_ON) or stopping the rescue (RESCUE_OFF) thestation. The output delivered and intended for a rescuedstation will be redirected to the rescuing station whenSTART_OUTPUT_WRITER is issued.

RESCUED_CLASS: meaningful only with RESCUE_ON or RESCUE_OFF.specifies the list of output classes (A to Z) which are theobject of the rescue or the termination of the rescue.The default is all output classes.

STATION: applicable only for the MAIN operator.the name of the unattended station to which the modificationsapply.

Constraints:

• If ADDLDV is used, then both DEVCLASS and DEVICE must be used.

• If DEVCLASS, DEVICE, SELCLASS or LCASE is used, then ADDLDV must be used.

DJP User's Guide

A-58 47 A2 14UC Rev05

Examples:

S: MDST PR99 /H160 $YORK :>SPD>LPT00 A-Idefines PR99 as the name of a printer at DPS 6 site YORK where it is known as>SPD>LTP00.

When SOW PR99 is issued, the writer will process classes A to I.

S: MDST CLRLDV=PR99erases the command above.

S: MDST RCON=ST3 ST=ST2Station ST2 is to be rescued by station ST3.

This command can only be issued by the MAIN operator.

S: MDST RCON=ST3 RCCLASS=A-QStation ST3 is to rescue output classes A through Q.

This command can only be issued by the Station operator.


47 A2 14UC Rev05 A-59

A.19 MDUR (MODIFY_USER_REQ)

Function

Modifies job processing requests submitted by the terminal user.

Requests submitted by other users may not be modified.

Syntax

{ MODIFY_USER_REQ }{ }{ MDUR }

[ { Jddddddd [ Jddddddd ... ] } ][ REQUEST=( { } ) ] [ RCLASS = alpha ][ { name8 [ name8 ... ] } ]

[ RPRIORITY = 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 ]

[ HOST = host ]

{ [ { {W | WEEK } }]}{[ {IMMED }] [ { { } }]}{[ {----- }] [ { {D | DAY } }]}{[ {[mm.dd.yy.]hh.mm}] [ {({ }[dec-5])}]}{[WHEN={ }] [EVERY={ {{H | HOUR } }]}{[ {+dddd{ W|D|H|M }}] [ { { } }]}{[ { ] [ { {dddd{ W|D|H|M }} }]}{[ {when-clause }] [ { }]}{ ] [ { every-clause }]}{ }{ [ TIMEOFF = bool ] }

{ [ WAIT = ( name-8 [ ,name-8 ] ... ) ] }{ }{ [ NOWAIT = bool ] }

[ { IMMED } ][ { ----- } ][ { NO } ][ RRESTART = { } ][ { delay[E] } ][ { } ][ { rrestart-clause } ]

DJP User's Guide

A-60 47 A2 14UC Rev05

Parameters

REQUEST: identifies a list of up to 16 requests to be modified, the nameof the request being in one of the following formats:Jddddddd: Jobset Occurrence Number (JON) resulting fromthe EJR command

name-8: the symbolic name of a request as specified by theNAME parameter of the EJR command.

RCLASS: the new class for the request, expressed as a letter in therange A to Z.

RPRIORITY: the new priority for the request, expressed as a number in theinclusive range 0 to 7. The lower the number, the higher theurgency.

HOST: the name of the site at which the request other than filetransfers is to be executed.For file transfers, HOST is ignored.

WHEN: when the job processing request is to start:IMMED (default): now[mm.dd.yy.]: a date+ddddd{W|D|H|M|}: a number of weeks, days, hours,minutes."when-clause" introducing the syntax treated in Appendix E.

EVERY: the interval and number of times the request is to besubsequently enqueued for execution, in the form: (frequencynumber-of-times) or "every-clause"; introducing the syntaxtreated in Appendix E.If number of times is omitted, an infinite number of times isassumed. Frequency can be expressed as a number ofweeks, days, hours, minutes, months, working days, or non-working days.If EVERY = (0,0) is specified, the repeat condition iscancelled and other enqueuing parameters left unchanged.

TIMEOFF: 1: cancels WHEN and EVERY conditions.0: WHEN and/or EVERY apply.

WAIT: a list of up to 8 request names (symbolic or JON or FON).The current request will not be executed until the WAITrequests have completed execution.

NOWAIT: 1: cancels the WAIT condition.0: the WAIT condition applies.


47 A2 14UC Rev05 A-61

RRESTART: specifies how the job processing request should be handledin the case of system failure or shutdown.IMMED: Default , the request is enqueuedNO or CANCEL: the request is cancelled<delay>:expressed as <decimal>{M|H|D|W} being the delay added tothe normal enqueuing time where, M=month, H=hour, D=day,W=week.E: option to <delay>, being the elapsed delay before thesystem restarts, the request is then enqueued and executed.the rrestart-clause introducing the syntax treated inAppendix E.

WHEN, EVERY and RRESTART, see Appendix E for details.

Constraints

• WAIT and NOWAIT are mutually exclusive.

• TIMEOFF is exclusive of WHEN and EVERY.

Messages

If the WAIT condition has not been performed successfully, the following message isdisplayed:

<time> WAIT CONDITION NOT FULFILLED: REQUEST MODIFIED [AND HELD]

The following message is displayed, for each request which cannot be chained on themodified request:

Examples:

S: MDUR J18 Zchange class of J18 to Z.

S: MDUR J36 RPRIORITY=0change priority of J36 to 0.

S: MDUR J37 TIMEOFFignore time condition for J37.

S: MDUR J5 WAIT=(J3 J4)make J5 begin only when both J3 and J4 have completed.

S: MDUR J1234 WHEN=03.01.92.00.00 EVERY=4Wexecute request on March 1, 1992 and repeat it every 4 weeks.

DJP User's Guide

A-62 47 A2 14UC Rev05

A.20 RUR (RELEASE_USER_REQ)

Function

Cancels an HUR request, by removing a job processing request from the HOLD state toWAIT to make it eligible for execution.

Syntax

{ RELEASE_USER_REQ }{ }{ RUR }

{ Jddddddd [ Jddddddd ... ] }REQUEST = ( { } ) { name8 [ name8 ... ] }

[ START = dec-5 ]

Parameters

REQUEST: identifies a list of up to 16 requests to be modified, the nameof the request being in one of the following formats:Jddddddd:Jobset Occurrence Number (JON) resulting from the EJRcommand name8:the symbolic name of a request as specified by the NAMEparameter of the EJR command.

START: not applicable for job processing.specifies the rank of the logical record (starting with 1) fromwhich the transfer is resumed.

Messages

The following message is displayed, if the command is successful:

<time> <request> RELEASED

Examples:

S: RUR (F4 J7 FREQ) 1.54 F4 RELEASED J7 RELEASED FREQ RELEASED

releases the three requests F4, J7 and FREQ from HOLD.

S: RUR F33 START= 600 1.55 F33 RELEASED

releases the file transfer request F33 from HOLD, to be restarted from record number600.


47 A2 14UC Rev05 A-63

NOTE: When the parameter WAIT is used in EJR and EFTR, the normal way to ensurecorrect execution is:

to submit the first request with HOLD state

to introduce requests subsequent to the first

then to release the first one.

Example 1:

EJR J1,,LIB RHOLD NAME=JOB1; EJR J2,,LIB WAIT=JOB1; RUR JOB1;

Job J2 will execute when job J1 has terminated.

Example 2:

EFTR $SITE:A..MB1 B..MB2 BINARY RHOLD NAME=TF1; EJR J2,,LIB WAIT=TF1; RUR TF1;

Job J2 will execute when file transfer TF1 has terminated.

DJP User's Guide

A-64 47 A2 14UC Rev05

A.21 SIR (START_INPUT_READER)

Function: reserved for the MAIN operator only

Specifies that job readers/JTRA started after an EJR command remain active for theduration of the GCOS 7 session so that performance is improved.

Syntax

{ START_INPUT_READER }{ }{ SIR }

PERM = bool

Parameters

PERM: If 1, any job reader started by the EJR command remainsactive.


47 A2 14UC Rev05 A-65

A.22 SOW (START_OUTPUT_WRITER)


Purpose

Starts a writer on a specified device or file for specified output classes. When used by astation operator, this command starts a remote writer which sends to a station the outputsqueued for it.

Syntax

{ START_OUTPUT_WRITER } { SOW...} { SO }

{ ALLDV } { PRxx } ON = { name4 } { $site:SPOOL } { rfile78 }

[ SELCLASS = (a[-a] {a[-a] ...]) ]

[ { DEVCLASS } { } ] [ { } = { PR [/dvattr] } ] [ { DVC } { } ]

{ STATION } { } = stnnm { ST }

[ PERM = { bool | 0 }]

[ { DOF } ] [ { SARF} ] [ DATAFORM = { VPF } ] [ { ASA } ] [ { SSF } ]

[ LCASE = bool ]

[ USER = name12 [ PASSWORD = name12 ]]

[ PROJECT = name12 ]

[ BILLING = name12 ]

[ JOR = NORMAL | ABORT | NO ]

[ BANNER_WIDTH = banner_width ]

[ SILENT = bool ]

[ OPTIMIZE = bool ]

DJP User's Guide

A-66 47 A2 14UC Rev05

Parameters

ON on which device or file the writer is to be started, expressedas:

ALLDV: all devices

PRxx: the named printer

name4: the station's logical device identification

$site: SPOOL the standard SYSOUT file of the named site

rfile78: the named local or remote (GCOS 7 or DPS 6) file.

rfile78 defines a local or remote file name. Syntax is: [$SITE:]file-name. When defining a foreign system file (DPS 6), thefile-name must be protected by ' '. When defining a DPS 7000file, the file-name format is: efn [..subfile][:media:dvc]. As file-name is not a file-literal, $CAT/$RES or $MFT, etc., are notsupported.

For remote operations refer to the DPS 6 - DPS 7 RemoteFacilities Manual or the DJP User's Guide or the RBF User'sGuide.

If you are using a library, this library must not be cataloged inSITE.CATALOG.

SELCLASS restricts the scope of the command to the outputs that belongto the specified class(es) or range(s) of classes. This may beexpressed as:

class for a single class

class-class for a range of classes

where class is a letter (A to Z). When SELCLASS is omitted,"default classes" attached to the device are assumed. In thecase of SOW on SPOOL or rfile78, "all classes" areassumed.

DEVCLASS (for sequential files) the device to be simulated forpresentation of the report on the file. The file can be laterprocessed by use of the DPRINT command.

STATION Name of the (unattended or rescued) station to which thecommand applies.

PERM (applies only to local writers) when 1, the writer is permanent.The default value is 0.


47 A2 14UC Rev05 A-67

DATAFORM The data format for the output handled by the writer. One ofthe following can be entered:SSF Standard System FormatASA American Standard Assn. formatVPF Virtual Printed FormatSARF Standard Access Record FormatDOF Device Oriented Format

LCASE (for DPS 6 stations) when 1, the remote writer is requested tokeep lowercase when printing.

USER Name of the user to be connected to the remote site. Defaultis the command submitter.

PASSWORD Password of the user to be connected to the remote site.Default is the password of the command submitter.

JOR JOR specifies the JOR option at writer termination. If thevalue is set to:NORMAL: JOR is kept in case of normal or abnormal

termination of the writer.ABORT: JOR is kept in case of abnormal termination of

the writer.NO: The JOR is not kept whatever the termination of

the writer. When JOR is not specified, the defaultvalue assumed depends on the type of the writer:- NORMAL: for local magnetic writers- NO: for other writers.

The JOR parameter is meaningless for SPOOL (see theTOW command).

Examples :

SOW PR01 JOR=NORMALThe JOR is kept in all cases at a writer termination.

SOW MYLIB JOR=ABORTThe JOR is kept only in case of an abnormal writertermination.

PROJECT Project of the user to be connected to the remote site.Default is the project of the command submitter.If only BILLING is specified, PROJECT is left blank toconnect the remote site with the default project of the user onthe remote site (same as the EFTR rules).

BILLING Billing of the user to be connected to the remote site. Defaultis the billing of the command submitter.If only PROJECT is specified, BILLING is left blank toconnect the remote site with the default billing of the specifiedproject on the remote site (same as the EFTR rules).

DJP User's Guide

A-68 47 A2 14UC Rev05

BANNER_WIDTH Specifies the banner width (in columns number) of outputwhen it is printed (the default and upper value is 120; thelower value is 55).Any value < 55 or > 120 is rejected by the command.The value of the parameter given in the SOW commandtakes into account two factors.

The possible characteristics of the banner:- small banner if BANNER_WIDTH is between 55 and 107- big banner with big letters separated by 1 blank if

BANNER_WIDTH is between 107 and 118- big banner with big letters separated by 2 blanks if

BANNER_WIDTH is between 118 and 120

The format of the printer paper:if the format cannot accept the width commanded, thewidth of the printed banner will be the maximum that iscompatible with the format.

SILENT Setting up this parameter leads to the suppression of themessages TW04, TW05 and TW06 sent by GT-WRITER.This parameter is only important in the case of a queuedwriter launched by the station GTW. The default value is:SILENT=0 .

OPTIMIZE Setting up this parameter modifies the selection mechanismof outputs by the writer. These are always chosen accordingto their priority, but inside a priority the writer will choose anoutput which will not trigger a request to load a new medium.The default value is:OPTIMIZE=0 ,in which case the outputs are chosen by priority and FIFOwithin the priority.


47 A2 14UC Rev05 A-69

Rules

• DEVCLASS, PERM, LCASE and DATAFORM are ignored when ON is ALLDV.

• SITE is mandatory in the ON parameter if ON = RFILE and STATION is not the sameas #WSTATION.

• When SITE is omitted in the rfile78 syntax, the default site of the station is assumed.

• SITE is mandatory in the rfile78 syntax if the SOW command is managing an outputqueue other than the default station queue.

• USER, PASSWORD, PROJECT and BILLING are meaningful only for remote writersor SPOOL.

• SOW command on an already started file (local or remote) is rejected. In the case ofSOW on an already started writer device, DEVCLASS, PERM and LCASE are rejected;classlist is updated if the operator's station and output queue match previous ones.

• In the case of SOW..SPOOL, selclass/devclass/STATION queue are added to the GTPselection criteria. Only the operator's right to submit SOW for that STATION ischecked.

• If a file situated on a remote site is used, this file must be sequential, and its RECSIZEmust be greater than or equal to 600.

• When a writer is started on a cataloged file, this file must pre-exist. The output writerwill not create it.

Examples:

SOW ALLDV {Starts all local writers on devices.}

SOW PRL6 Z LCASE {Start a writer on the station's logical device PRL6 with lowercase handling.}

SOW OUTSAV :OUT :MT/T9 X DVC=PR/H160{All outputs of class X are saved on the named tape file,emulating a 160 hammers printer.}

SOW $SETI:MYFILE {Launches a Writer on the site SETI; the outputs are saved inthe file MYFILE.}

SOW $BC03:SPOOL ST=BC03 USER=OP2 PASSWORD=OP{Starts a spool towards the remote site BC03; user OP2 withpassword OP will be connected to this remote site.}

SOW PR01 BANNER_WIDTH=110{The banner width of the outputs processed by this writer willbe 110 columns.}

SOW $MAIN :library STATION=GTW SILENT=1

SOW PO01 SELCLASS=P OPTIMIZE=1

DJP User's Guide

A-70 47 A2 14UC Rev05

A.23 TIR (TERMINATE_INPUT_READER)

Function: reserved for the MAIN operator only

Specifies that job readers and JTRA (JCL Translator) that were set active for the durationof the GCOS 7 session by SIR PERM will become inactive as soon as they haveterminated reading or translating (JTRA) the job(s).

Syntax

{ TERMINATE_INPUT_READER }{ }{ TIR }

PERM = bool

Parameters

PERM: if set to 1, job readers and JTRA started by the EJRcommand will no longer remain active once they haveterminated introducing the jobs.


47 A2 14UC Rev05 A-71

A.24 TOW (TERMINATE_OUTPUT_WRITER)


Purpose

Stops a writer or a remote writer.

Syntax

{ TERMINATE_OUTPUT_WRITER } { TOW }

{ * | ALL } { ALLDV } { PRxx } ON = { name4 } { Wnnn } { $site:SPOOL } { rfile78 }

[ SELCLASS = (a[-a] [a[-a]] ...) ]

[ STATION = stnnm ]

[ STRONG = { bool | 0 } ]

[ { LEAVE } ] [ END = { } ] [ { UNLOAD } ]

Parameters

ON The identification of the writer to be stopped, expressed as:

* or ALL: all writers (both on devices and files)

ALLDV: all writers operating on devices (but not on files)

PRxx: the writer operating on the named printer

name4: the writer operating on the named station's logicaldevice

Wnnn: the writer where identification (as returned by theSTART_OUTPUT_WRITER command) is Wnnn

$site: SPOOL the standard SYSOUT file of the named site

rfile78: the writer operating on the named local or remote(DPS 7000 or DPS 6) file. (See START_OUTPUT_WRITERfor syntax and rules.)

For remote operations, refer to the DPS 6 - DPS 7 RemoteFacilities manual and to the DJP User's Guide.

DJP User's Guide

A-72 47 A2 14UC Rev05

SELCLASS restricts the scope of the command to the outputs that belongto the specified class(es) or range of classes. This may beexpressed as:


where class is a letter (A to Z). When SELCLASS is omitted,all started classes are assumed.

STATION the name of the (unattended) station to which the commandapplies.

STRONG if 1, outputs being printed are stopped immediately; if 0(default), the stop is deferred until the outputs being printedare ended.

END specifies action to be taken at termination of the tape writer:

UNLOAD requests automatic unloading of the tape.LEAVE (default) specifies no automatic unloading.

This parameter is relevant only if the writer was started withPERM=1 (permanent writer) and when all started classes arerequesting termination.

Rules

• When ON is * or ALLDV, STRONG is ignored

• If ON is Wnnn, STATION is ignored.

Examples:

TOW * ST=RSL6 {Stop all writers on station RSL6.}

TOW PRL6 STRONG {Stop immediately the writer on the station's logical devicePRL6.}

TOW $MST1 :SPOOL ST=PUNCH{Stop routing card-punch outputs from station PUNCH tohost's MST1 standard SYSOUT file.}

TOW W007 {Stop writer whose identification is W007.}

TOW <tape-file-description> SELCLASS=A-D END=UNLOAD{Terminate a permanent writer on a magnetic tape file for theoutput classes A-D and asks for an automatic unloading ofthe tape.}

47 A2 14UC Rev05 B-1

B. Network Generation

The NETGEN utility executed on the DPS 7/7000 defines the systems and thecommunications environment in which the host DPS 7/7000 is to operate.

The capability of the remote system in participating in job processing and file transfer,collectively termed in this manual as RFA activities, depends on its hardware support andsoftware release. These two criteria constitute the profile of the remote system.

B.1 SYSTEM PROFILES

In the network generation of the DPS 7/7000, each system is declared with a profile thatidentifies its hardware, its operating system and the release of its system software.

The default profile of all systems, including the DPS 7/7000 host, is their latest hardwareversion, operating system and release of system software. The profile of the localDPS 7/7000 configuring the network generation is therefore 'DPS 7/GCOS 7/V6'.

Other GCOS 7 releases can be declared for the DPS 7/7000 only where it functions as aremote system.

V2 and V3 declared in the profiles DPS 7/GCOS 7/V2 and DPS 7/GCOS 7/V3 correspondto the following respective GCOS 7 releases:

V2 profile means V2, V3A0 and V3B0 GCOS 7 releases

V3 profile means V3A7 and V3B7 GCOS 7 releases.

If the system's profile is not the default, its profile must be explicitly declared in either thelow-level RSYS/RSC pair-set of directives or the high-level SYS directive.

DJP User's Guide

B-2 47 A2 14UC Rev05

B.2 DPS 7/7000 FILE TRANSFER CAPABILITIES

B.2.1 Transfer DPS 7/7000 <---> DPS 7/7000

When the remote system is a DPS 7/7000, its file transfer capability towards the localDPS 7/7000 system depends on its GCOS 7 release:

1. GCOS 7 1E.5 or V1 Profile : 'DPS7/GCOS-7/V1' 'DPS7/GCOS-64/1E.5' 'L64/GCOS-64/1E.5' '64DPS/GCOS-64/1E.5'

No file transfer is possible with the local system.

2. GCOS 7 V2 with technical status < TS25 Profile : 'DPS7/GCOS-7/V2'

No file transfer is possible with the local system.

3. GCOS 7 V2 with technical status >= TS25 (supports protocol V2A of UFT) Profile : 'DPS7/GCOS-7/V2'

Files can be transferred to/from the local system only if the PROFILE is changedfrom V2 into V3. See 5.

4. GCOS 7 V3 and V5 Profile : 'DPS7/GCOS-7/V3'

File transfers to and from the local system are unrestricted. See 5.

5. GCOS 7 V6 and V7 Profile : 'DPS 7/GCOS 7/V6'

Security depends on the access rights implemented for the file transfer applicationon the acceptor DPS 7/7000 system (local or remote).

if locally configured as "protected", the file will be transferred only after the acceptoragrees to the submitter's access rights.

if locally configured as "not protected", there are no restrictions on the file transfer.See 4.

Network Generation

47 A2 14UC Rev05 B-3

B.2.2 Transfer DPS 7/7000 <---> non-DPS 7/7000

If the DPS 7/7000 host has a profile from V3 upwards, it can send files to, and receivefiles from, the following remote systems with their corresponding profiles:

DPS 6:

Releases 2.2, 3.0, 3.1, 4.O and 4.1 of DSS are supported.

The implicit DPS 6 profile is 'DPS6/DSS/4.1 '

DPS 8:

Releases SR2500, SR3000, SR4000 and SR5000 of GCOS 8 are supported.

The implicit DPS 8 profile is 'DPS8/GCOS-8/SR5000 '

Questar 400, DPX/2 x00:

The nomenclatures SID3 and SID4 are accepted as software releases.

The implicit STID profile is 'STID/ISO/SID4 '.

IBM Site:

Since the IBM site is known only by its connection interface, its front-end processor(DN300) and its gateway (JANUS) provide its external profile.

The implicit IBM profile is 'IBM/JANUS/DN300 '.

NOTE: Incompatible profiles cause the transfer to abort, see Appendix E for a completelist of FATAL error messages.

DJP User's Guide

B-4 47 A2 14UC Rev05

B.2.3 Profiles and RFA Capabilities

The following 2 charts resume the capability of the remote system in participating in UFTand DJP activities with the host DPS 7/7000.

System profileRFA index

DJP UFT

DPS7 / GCOS-7 / {V3 to V7} 1 4

DPS8 / GCOS-8 / {SR3000 to SR5000} 6 4

DPS8 / GCOS-8 / SR2500 7 4

DPS6 / DSS / {3.1 to 4.1} see * 2 4

DPS6 / DSS / 3.0 8 4

DPS6 / DSS / {1.1 to 2.2} 3 5

DPS6P / HVS / {1.0 and 2.0} see * 2 4

M400 / DSA / {3.0 to 4.0} 3 5

STID / ISO / {SID3 and SID4} 0 4

IBM / JANUS / DN300 0 4

DJP UFTRFA idx job output

SEND EXEC RECV SEND RQST ACCP PRTC VERS

0 no no no no no no no none

1 ys ys ys ys no no RFA V2A

2 ys ys ys no no no RFA V2A

3 ys no ys no ys no L6 none

4 no no no no ys ys RFA V2A

5 no no no no no ys L6 see *

7 ys no no no no no RFA V2A

8 ys no ys no no no RFA V2A

DPS 6P/HVS and DPS 6/DSS versions from 3.1 onwards support both L6 and RFAprotocols. However, the DPS 7/7000 host will always choose RFA. In order to "force"L6 protocol on the DPS 7/7000 host, these DPS 6 systems should be declared'DPS6/DSS/2.2' whatever their real profiles are.

Network Generation

47 A2 14UC Rev05 B-5

In the second table of B.2.3 giving the capabilities of DJP and UFT, the attributes for bothof the functions have the following definitions:

DJP SEND on job: the system can issue a job request equivalentto the EJR command on the DPS 7/7000.

EXEC on job: the system can execute the job.

RECV on output: The system can receive the job output.

SEND on output: The system can send the job output.

UFT RQST: the system can issue a file transfer requestequivalent to EFTR or EXFT or ELTRcommands on the DPS 7/7000.

ACCP: the system can transfer a file to and from theDPS 7/7000.

PRTC: defines the protocol used in the transfer.

VERS: defines the version of UFT protocol.

DJP User's Guide

B-6 47 A2 14UC Rev05

B.3 NETWORK GENERATION ON THE DPS 7/7000

Network generation on the DPS 7/7000 can be declared in both low-level directives andhigh-level SYS directives. In the following example, the profiles declared are the latestreleases current for the systems and taken as defaults in the DPS 7/7000 NETGEN.

For further information on the DPS 7/7000 Network Generation, see Networks: Overviewand Generation.

In the following example of a network generation, the remote systems connected througheither the CNP 7 or the Datanet are given the same names for the sake of simplicity. In areal network generation, the name of each system should be unique as it is the session-control identifier.

NOTE: The user must declare the appropriate profiles of the systems which actuallycorrespond to their technical status or which are compatible with the file transfercapability of the DPS 7/7000 host.

Network Generation

47 A2 14UC Rev05 B-7

B.3.1 Network Schematic Description

The example shows:

• the local system HOST

• its neighbors:- DPS7 : direct DPS 7/7000-to-DPS 7/7000 link on the ISL- DTNT : passthrough Datanet on the PSI- CNP7 : passthrough CNP 7 on the ISL

• the remote systems RSxx of the primary network connected through either of thepassthroughs functioning as front-end processors and named for simplicity by thefollowing convention:- RS77 : for the DPS 7/7000- RS66 : for the DPS 6- RS88 : for the DPS 8- RSQX : for the QUESTAR 400 and DPX/2 x00- RSIB : for the IBM site.

A system is cataloged as a station or site or both, depending on the access required forindividual users. See C.2 How Systems are Cataloged.

D P S 7 /7000HOST

FEPS TN SD atane t D TN T

P S I

IS L

C N P 7CNP 7

DPS 7rem ote

D P S 7 /7000RSxx

rem o te system rem ote system

RSxx

DJP User's Guide

B-8 47 A2 14UC Rev05

B.3.2 Low-Level Directives

NET HOST;

COMM '+---------------------------------------------+';COMM '| L O C A L S Y S T E M : H O S T |';COMM '+---------------------------------------------+';

LSYS HOST PF='DPS7/GCOS-7/V6';LSC HOST SCID=60:57;SVR feps TYPE=FEPS LCT=CC01;LCT CC01 TYPE=PSI WATCH=2000;SVR TNS;LCT EA11;LPL PLINK_01 LCT=EA11 IADDR=08-00-38-50-3C-39 CB=CBL_01;CP CP_01 LPL=PLINK_01;

COMM '+---------------------------------------------+';COMM '| N E I G H B O R O N I S L : D P S 7 |';COMM '+---------------------------------------------+';

RSYS DPS7 PF='DPS7/GCOS-7/V6';RSC DPS7 RTS=TS_DPS7 SVR=TNS SCID=60:23;RTS TS_DPS7 NR=NR_1;NR NR_1 CP=CP_01 TP=PTPT1 RPL=RPL_DPS7;TP PTPT1 WINDOW=5;RPL RPL_DPS7 IADDR=08-00-38-50-3C-17 RCT=RCT_EA21 CB=CBL_01;RCT RCT_EA21;

COMM '+---------------------------------------------+';COMM '| P A S S T H R O U G H C N P 7 : C N P 7 |';COMM '+---------------------------------------------+';

RSYS CNP7 PF='CNP7/CNS7/A2' RCT=RCT_2;RSC CNP7 RTS=TS_BL13 SVR=TNS SCID=60:19;RTS TS_CNP7 NR=NR_2;NR NR_2 CP=CP_01 TP=PTPT2 RPL=RPL_2;RPL RPL_2 IADDR='08-00-38-50-3C-13' RCT=RCT_2 CB=CBL_01;RCT RCT_2;

COMM '+---------------------------------------------+';COMM '| P A S S T H R O U G H D N 7 1 0 0 : D T N T |';COMM '+---------------------------------------------+';

RSYS DTNT PF='DN7100/DN-C/V4.0' SVR= feps ;RSC DTNT SVR= feps SCID=60:63;

COMM '+---------------------------------------------+';COMM '| REMOTE SYSTEMS CONNECTED THROUGH CNP7 |';COMM '| RS77 RS66 RS88 RSQX RSIB |';COMM '+---------------------------------------------+';

Network Generation

47 A2 14UC Rev05 B-9

RSYS RS77 PF='DPS7/GCOS-7/V6';RSC RS77 SCID=60:61 SVR=TNS RTS=TS_BL2;

RSYS RS66 PF='DPS6/DSS/4.1';RSC RS66 SCID=60:51 SVR=TNS RTS=TS_BL2;

RSYS RS88 PF='DPS8/GCOS-8/SR5000';RSC RS88 SCID=60:41 SVR=TNS RTS=TS_BL2;

RSYS RSQX PF='STID/ISO/SID4';RSC RSQX SCID=60:31 SVR=TNS RTS=TS_BL2;

RSYS RSIB PF='IBM/JANUS/DN300';RSC RSIB SCID=60:21 SVR=TNS RTS=TS_BL2;

COMM '+---------------------------------------------+';COMM '| REMOTE SYSTEMS CONNECTED THROUGH DTNT |';COMM '| RS77 RS66 RS88 RSQX RSIB |';COMM '+---------------------------------------------+';

RSYS RS77 PF='DPS7/GCOS-7/V6';RSC RS77 SCID=60:36 SVR= feps ;

RSYS RS66 PF='DPS6/DSS/4.1';RSC RS66 SCID=60:38 SVR= feps ;

RSYS RS88 PF='DPS8/GCOS-8/SR5000';RSC RS88 SCID=60:07 SVR= feps ;

RSYS RSQX PF='STID/ISO/SID4';RSC RSQX SCID=70:71 SVR= feps ;

RSYS RSIB PF='IBM/JANUS/DN300';RSC RSIB SCID=71:70 SVR= feps ;

ENET;

DJP User's Guide

B-10 47 A2 14UC Rev05

B.3.3 High-Level Directives

COMM '+---------------------------------------------+';COMM '| L O C A L S Y S T E M : H O S T |';COMM '+---------------------------------------------+';

SYS HOST PF=LSYS SCID=60:57 ISL=(50-3C-39,EA11);

COMM '+---------------------------------------------+';COMM '| N E I G H B O R S |';COMM '+---------------------------------------------+';

SYS CNP7 PF=CNP7 SCID=60:19 ISL=(50-3C-13);DEF PTPT1 TYPE=SET WATCH=2000 WINDOW=5;SYS DPS7 PF=DPS7 SCID=60:23 ISL=(50-3C-17);SYS DTNT PF=DN7100 SCID=60:63 PSI=CC01;

COMM '+---------------------------------------------+';COMM '| REMOTE SYSTEMS CONNECTED THROUGH CNP7 |';COMM '| RS77 RS66 RS88 RSQX RSIB |';COMM '+---------------------------------------------+';

SYS RS77 PF=DPS7 SCID=60:61 PT= CNP7;SYS RS66 PF=DPS6 SCID=60:51 PT= CNP7;SYS RS88 PF=DPS8 SCID=60:41 PT= CNP7;SYS RSQX PF=STID SCID=60:31 PT= CNP7;SYS RSIB PF=IBM SCID=60:21 PT= CNP7;

COMM '+---------------------------------------------+';COMM '| REMOTE SYSTEMS CONNECTED THROUGH DTNT |';COMM '| RS77 RS66 RS88 RSQX RSIB |';COMM '+---------------------------------------------+';

SYS RS77 PF=DPS7 SCID=60:36 PT= DTNT;SYS RS66 PF=DPS6 SCID=60:38 PT= DTNT;SYS RS88 PF=DPS8 SCID=60:07 PT= DTNT;SYS RSQX PF=STID SCID=70:71 PT= DTNT;SYS RSIB PF=IBM SCID=71:70 PT= DTNT;

ENET;

47 A2 14UC Rev05 C-1

C. DJP Security and Access Control Rules

This Section describes how the rights to use DJP to start a batch job on a remote systemare checked. Rights to start writer are described in the SOW command.

All functions of DJP V5 are retained in DJP V6. If only the V5 functions of DJP V6 areused, the SITE.CATALOG need not be altered when migrating from V5 to V6. However,as from V6, changes have been made to DJP security checks if the JOB Submitter (theuser requesting the JOB execution) is not the JOB Owner (the user for whom the JOB isexecuted). These two users are different if USER, PROJECT and BILLING, with HOSTare specified in the EJR command.

The effects of these changes when the JOB Submitter is not the JOB Owner are asfollows:

• The service JOB is started on the Server Site under the identity of:- in V6 or V7, under the JOB Submitter: the STATION in the SITE.CATALOG of the

Server Site whose name is the Requestor Site must be attached to the PROJECTof the JOB Submitter

- in V5, under the JOB Owner: the STATION in the SITE.CATALOG of the ServerSite whose name is the Requestor Site must be attached to the PROJECT of theJOB Owner.

• When BILLING is explicitly specified in the EJR command but not USER andPROJECT, the default value for PROJECT has been changed for a remote JOBsubmission:- in V6 or V7, the PROJECT of the JOB Submitter is always assumed to be the

PROJECT of the JOB Owner- in V5, the PROJECT of the JOB Submitter is assumed to be:

the PROJECT of the JOB Owner for a local JOB (EJR without HOST)and the default PROJECT of the JOB Submitter for a remote JOB (EJR withHOST).

DJP User's Guide

C-2 47 A2 14UC Rev05

In V6 and V7, additional improvements have been made to simplify checks:

• DJP PASSWORD checks have been modified to be identical to UFT PASSWORDchecks, namely, when the Server Site is configured with CHKPW=NO (SECOPTCONFIG default) the JOB Submitter PASSWORD is not checked at the Server Site:whereas in V5, the JOB Submitter PASSWORD was checked at the Server Site.

• checks on rights to submit a JOB on the Server Site are the same for a local JOB (EJRwithout HOST) as for a remote JOB (EJR with HOST)

• checks on the relationship between the PROJECT of JOB Owner and the USER of theJOB Submitter have been suppressed.

Additional functions in DJP V6 for which new options are available:

• CHKPW=YES (SECOPT CONFIG parameter for mandatory check on password andapplication) improves Security for a DPS 7/7000 acting as a Server Site since a JOBcannot be remotely started on a system without:- checks on a local PASSWORD of the JOB Submitter- and explicit authorization through the cataloged APPLICATION DJP on the Server

Site where the JOB will be executed.

• Access to DJP on a site configured with CHKPW=YES from a Requestor Site runningunder V5 is only possible if the JOB Submitter is the JOB Owner.

• the ALL_RSYS as a station-name or site-name in the SITE.CATALOG replaces allSTATIONs of a PROJECT or all SITEs of a STATION. ALL_RSYS only affects thelocal system.

DJP Security and Access Control Rules

47 A2 14UC Rev05 C-3

C.1 PRINCIPLES OF GCOS 7 SECURITY

GCOS 7 security management is based on a system file called SITE.CATALOG. ThisSection is a recapitulation of the basic concepts of the objects configured in theSITE.CATALOG. Appendix D treats the commands used to manage these objects.

C.1.1 USER, PROJECT, BILLING, APPLICATION, STATION and SITE

The SITE.CATALOG contains the names of USERs authorized to access certain GCOS 7applications. A PASSWORD is registered in this SITE.CATALOG for each USER. APROJECT is a set of USERs described in the GCOS 7 SITE.CATALOG. There may beone DEFAULT PROJECT.

Each PROJECT is associated with a list of attributes which define the rights andcharacteristics of all USERs of the PROJECT. The attributes which may be used for thepurpose of DJP Security Checks are:

• the type of USER: MAIN Operator, Station Operator or Normal IOF user

• the list of BILLING containing the names used for accounting purposes for aPROJECT; there may be one default BILLING

• the list of cataloged APPLICATIONs available for this PROJECT such as IOF, MML orany TDS name

• the list of STATIONs available for this PROJECT, the first STATION of the list beingthe default STATION.

A STATION is a Queue of Output having a name and attributes such as the defaultoutput class, the default banner and the list of SITEs available for this STATION.

SITEs available for a STATION are Remote Systems. The output enqueued on theSTATION may be forwarded toward these SITEs. The first SITE of the list is the defaultsite.

For an IOF session or a batch JOB, the working STATION is the STATION at whichoutputs are enqueued. This STATION can be changed for commands in which aspecific STATION can be specified. The initial value of the working STATION is thedefault STATION of the PROJECT.

NOTE: The list of available STATIONs for a PROJECT or SITEs for a STATION willcomprise all the remote systems if the keyword ALL_RSYS is specified.

USER, PROJECT and STATION may be created, modified and suppressed by theSystem Administrator through the MAINTAIN_CATALOG GCL utility. For furtherinformation, see the System Administrator's Manual.

DJP User's Guide

C-4 47 A2 14UC Rev05

C.1.2 Identities of JOB Submitter and JOB Owner

These two identities involve USER, PROJECT and BILLING which are associated with abatch job. The Job Submitter identity and the Job Owner identity may be the same.

Role of the JOB Submitter

The Job Submitter is the person who is in charge of monitoring the execution of a JOB.

The Job Submitter identity is that of the person issuing the EJR request from aninteractive session. Job Submitter identity cannot be overridden .

NOTE: When a JOB starts another JOB which in turn spawns other JOBs, the JobSubmitter remains the first interactive user who started the first JOB.

These rules are also valid in a distributed environment where a JOB is requested on a siteand executed on another site.

The messages from a batch JOB such as JOB started and JOB completed, are sent tothe Job Submitter Mailbox of the site where the JOB is executed. To obtain thesemessages, the JOB submitter must be logged on in interactive mode to the system wherethe JOB is executed.

Role of the JOB Owner

The Job Owner is the person for whom the JOB is executed.

The Job Owner identity may be explicitly defined when the following parameters of theEJR request are present: USER, PROJECT and BILLING.

When USER, PROJECT and BILLING parameters are not all present, the rules whichapply for computing the Job Owner identity are described in Paragraph C.2.

The Job Owner may be subsequently modified by means of parameters of the $JOBstatement. The different stages in processing the JOB Owner are in the followingsequence:

A) JOB Submitter identity is processed with USER, PROJECT and BILLING specified inthe EJR command, which is the subject of the Section

B) The result of A is combined with USER, PROJECT and BILLING specified in the$JOB statement, which does not concern DJP and is outside the scope of thepresent document, See the JCL Reference Manual

C) The rights of the user to access files and volumes is checked against the result of B.

NOTE: It is assumed for the rest of this manual that USER, PROJECT and BILLING areomitted in the $JOB statement.


47 A2 14UC Rev05 C-5

C.2 DJP SECURITY CHECKS

Some checks on the Job Submitter and the Job Owner are always performed. Thesechecks are identical to those which are performed when a JOB is submitted locally on asystem.

An option specific to DJP reinforces Mandatory Checks on Password and Application.This option is set by means of the CHKPW keyword of the SECOPT configurationstatement. See the System Installation Configuration and Updating Guide.

C.2.1 Checks Always Performed

The Job Submitter must have at the site at which the EJR command with the HOSTparameter is issued:

• USER, PROJECT and BILLING which identity him cataloged in the SITE.CATALOG• the Executing Site among the SITEs available for his Working STATION in the

SITE.CATALOG• the READ right to the JCL when it is on the Requesting Site• and the station specified by the DEST parameter (when used) among the stations

available for its project.

The Job Submitter must have at the site (specified by HOST of EJR) where the JOB isexecuted:

• USER, PROJECT and BILLING which identity him cataloged in the SITE.CATALOG

• a STATION in the SITE.CATALOG- whose name is the Requesting Site in the list of STATIONs available for his

PROJECT- and on which the report (the Server JOR) of the DJP activity on the Executing Site

will be enqueued.

• and the following rights:- either the EXECUTE right to the JCL when it is on the Executing Site- or the READ right to the GCL domain when the EJR command is issued specifying

the PROC parameter.

The USER, PROJECT and BILLING identifying the Job Owner must be present in theSITE.CATALOG of the site where the JOB is to be executed. The MAIN station and thestation specified by the DEST parameter must be availabe for the PROJECT of the JobOwner. The default value for the DEST parameter is the STATION whose name isthe Requesting Site.

A Site is Protected when the mechanism of checking access rights to files is active. In thiscase, the Job Submitter must be:

• either the Job Owner• or a MAIN or a Station Operator.

This check is performed at the Requesting Site and the Executing Site when both Sitesare protected.

DJP User's Guide

C-6 47 A2 14UC Rev05

C.2.2 Additional Checks when CHKPW=NO

CHKPW=NO means that Mandatory Checks on Password and Application are notapplied:

• when the PASSWORD of the Job Submitter has been checked thereby authenticatinghis identity at the Requesting Site, in which case he may use DJP towards theExecuting Site configured with CHKPW=NO without a new check on PASSWORD

• and no checks are made on authorized APPLICATIONs nor any further checks.

C.2.3 Additional Checks when CHKPW=YES

CHKPW=YES means that Mandatory Checks on Password and Application are to beapplied. The Job Submitter PASSWORD and the access right to the DJP application arechecked at the Executing Site configured with CHKPW=YES.

The Job Submitter must have at the Executing Site:

• the same PASSWORD at the Requesting Site• and the keyword DJP in the list of APPLICATIONs authorized for his PROJECT.

C.2.4 Remote JOB Execution Request from GCOS 7 V5 Site to V6 or V7 Site

When the GCOS 7 V6 or V7 site is configured with CHKPW=NO , most of the securitychecks are identical to those which are performed when both sites are running on V6.

However, the DJP processing on the Executing Site will be started under the identity ofthe Job Owner and not under that of the JOB Submitter. So the STATION whose name isthe Requesting Site must be attached to the PROJECT of the Job Owner and not to thatof the Job Submitter. All the other checks remain unchanged.

When the GCOS 7 V6 or V7 site is configured with CHKPW=YES , the Job Submittermust be identical to the Job Owner. In all the other cases, starting a remote JOB will fail.

When this rule is respected, security checks are identical to those which are performedwhen both sites are running on V6 or V7. All the other checks remain unchanged.

C.2.5 Remote JOB Execution Request from GCOS 7 V6 or V7 Site to V5 Site

Most of the security checks are identical to those which are performed when both sitesare running on V5.

However, DJP processing on the Executing Site will be started under the identity of theJob Submitter and not under that of the Job Owner. So the STATION whose name is theRequesting Site must be attached to the PROJECT of the Job Submitter and not to that ofthe Job Owner.


47 A2 14UC Rev05 C-7

C.2.6 Computation Rules for JOB Owner Identity

The Job Owner identity is computed from:

• the Job Submitter identity

• and the values supplied for USER, PROJECT and BILLING parameters of the EJRcommand, when these parameters are present.

The three cases for establishing the Job Owner identity are:

• if USER is specified, PROJECT and BILLING where omitted are supplied with theirdefault values for the USER at the Executing Site

• if PROJECT is specified but USER is omitted, missing values are supplied as follows:- USER: the Job Submitter identity- BILLING: the default for the PROJECT at the Executing Site

• if USER and PROJECT are omitted, the missing value(s) supplied is thatcorresponding the equivalent(s) in the Job Submitter identity.

NOTE: The identity of the Job Owner may be overridden by means of the USER,PROJECT and BILLING parameters of the $JOB statement, see C.1.2 Role ofthe JOB Owner.

C.2.7 Summary of DJP Security Checks

Rules on STATIONs and access rights to files are described in C.2.1 Checks AlwaysPerformed.

The following tables, DJP executes between two DPS 7/7000 systems running the sameversion and assuming that USER, PROJECT and BILLING are omitted in the $JOBstatement.

The notation used for describing rules on USER, PROJECT, BILLING, PASSWORD andcataloged APPLICATIONs can be summarized as follows:

• DJP is a cataloged APPLICATION which goes under the system-reserved name DJP

• Uo, Po and Bo are abbreviations for USER, PROJECT and BILLING of the USEROwner when these are explicitly specified

• Ur, Pr, Br and PSWr are abbreviations for USER, PROJECT, BILLING andPASSWORD of the JOB Submitter

• Pd and Bd are default values at the Server Site for PROJECT and BILLING.

DJP User's Guide

C-8 47 A2 14UC Rev05

Example 1

Ur/Po/Bd means the relationship between the USER Requestor, the PROJECT Owner(explicitly supplied in the EJR command) and the default BILLING, is checked.

Example 2

Ur/Po/[Bd] is equivalent to:

• Ur/Po/Bd when Bo is omitted

• and Ur/Po/Bo when Bo is explicitly specified.

Checks performed in GCOS 7Condition supplied: Release V5

on Requestor: on Owner:

Uo omitted with one following:

Po omitted :Local Ur/Pr/[Br]

:Remote Ur/Pr/Br/PSWr Ur/Pr/[Br]

Po supplied :Local Ur/Po/[Bd]

:Remote Ur/Pr/Br/PSWr Ur/Po/[Bd]

Uo supplied :Local :Ur is operator Uo/[Pd]/[Bd]

:Ur not operator error

:Remote :Ur is operator Ur/Pr/Br/PSWr Uo/[Pd]/[Bd]and Ur/[Pd]



47 A2 14UC Rev05 C-9




Po omitted :Local Ur/Pr/[Br]

:Remote Ur/Pr/Br Ur/Pr/[Br]


:Remote Ur/Pr/Br Ur/Po/[Bd]



:Remote :Ur is operator Ur/Pr/Br Uo/[Pd]/[Bd]





Uo omitted :Local Ur/Pr/[Br]

:Remote Ur/Pr/Br/PSWr Ur/Pr/[Br]/aDJP


:Remote Ur/Pr/Br/PSWr Ur/Po/[Bd]/aDJP



:Remote :Ur is operator Ur/Pr/Br/PSWr Uo/[Pd]/[Bd]/aDJP


DJP User's Guide

C-10 47 A2 14UC Rev05

C.3 EXAMPLE OF SITE.CATALOGS AT REQUESTING AND EXECUTINGSITES

C.3.1 Example when CHKPW=NO

The example shows the contents of the SITE.CATALOG on the Requesting Site and thatat the Executing Site.

The following command is keyed in by a MAIN operator:

• logged on under USER US, PROJECT PS, BILLING BS• and having MAIN as his working STATION,• to execute from a SITE SIT1, the file MYJOB of the library MYSLLIB on the host SIT2.

EJR MYJOB INFILE=MYSLLIB HOST=SIT2 USER=U0 PROJECT=P0 BILLING=B0;

• MYJOB does not have USER/PROJECT/BILLING in its $JOB statement.

The site SIT2 is configured with CHKPW=NO which means that Mandatory Checks onPassword and Application are not applied.

Job Submitter has:

• at SIT1:- his identity US, PS and BS cataloged in the SITE.CATALOG- the MAIN operator attributes under his PROJECT PS- the keyword IOF in the list of APPLICATIONs associated to his PROJECT PS

(IOF allows the user to log on)- SIT2 or the keyword ALL_RSYS among the SITEs available for this current working

STATION being MAIN- and the READ access right on the library MYSLLIB.

• at SIT2:- his identity US, PS and BS cataloged in the SITE.CATALOG- the MAIN operator attributes under his PROJECT PS- and SIT1 or the keyword ALL_RSYS as a STATION available under the PROJECT

PS.

The Job Owner identity is U0, P0 and B0. This identity must be cataloged in theSITE.CATALOG of SIT2.

The DJP report on SIT2 can be transferred back to SIT1 by means of a remote writer.See the SOW command in Appendix A.


47 A2 14UC Rev05 C-11

When CHKPW=NO on SIT2, the following sequences of MAINTAIN_CATALOGcommands may be used to register the Job Submitter and Job Owner identities on SIT1and SIT2:

On SIT1: CRP PS MAIN APPLIST=IOF STTNLIST=(MAIN,SIT2); MDS MAIN ADDSITE=SIT2; CRB PS.BS; CRU PS.US PASSWORD=PSWS;

On SIT2: CRP PS MAIN STTNLIST=SIT1; CRS SIT1 SITELIST=SIT1; CRB PS.BS; CRU PS.US PASSWORD=YYY; CRP P0 STTNLIST=(SIT1,MAIN); CRB P0.B0; CRU P0.U0 PASSWORD=ZZZ;

C.3.2 Example when CHKPW=YES

When CHKPW=YES on SIT2, the following additional checks are performed:

• PSWS must be the PASSWORD of US at SIT1 and SIT2

• and the keyword DJP must be present in the list of APPLICATIONs associated to PS inSIT2.

The following sequence of MAINTAIN_CATALOG commands may be used to register theJob Submitter and the Job Owner identities at SIT1 and SIT2:

On SIT1: CRP PS APPLIST=IOF STTNLIST=(MAIN,SIT2); MDS MAIN ADDSITE=SIT2; CRB PS.BS; CRU PS.US PASSWORD=PSWS;

On SIT2: CRP PS MAIN APPLIST=DJP STTNLIST=SIT1; CRS SIT1 SITELIST=SIT1; CRB PS.BS; CRU PS.US PASSWORD=PSWS; CRP P0 STTNLIST=(SIT1,MAIN); CRB P0.B0; CRU P0.U0 PASSWORD=ZZZ;

DJP User's Guide

C-12 47 A2 14UC Rev05

47 A2 14UC Rev05 D-1

D. Site Catalog

This Appendix gives a brief description of how to manage projects, users, billings andstations in the SITE.CATALOG through the MAINTAIN_CATALOG utility. For furtherdetails, see the System Administrator's Manual.

GCOS 7 security is based on the SITE.CATALOG. Control checks performed by UFT aredescribed in Appendix C.

DJP User's Guide

D-2 47 A2 14UC Rev05

D.1 CATALOGING A PROJECT

The MAINTAIN_CATALOG commands for a project are:

• CRP (create project) when the project is first created

• and MDP (modify project) when the project is subsequently modified.

The project is associated with:

• a list of applications

• and a list of stations.

D.1.1 Defining the List of Applications for a Project

Each project defined in the SITE.CATALOG can have an application list.

The list of applications is

• defined when the project is created in the SITE.CATALOG through the APPLISTparameter of the CRP (create project) command

CRP project-name... APPLIST=(appl-name[/tdscode] [,appl-name[/tdscode]...])

• or added to when the site catalog is subsequently modified by the ADDAPPL parameterof the MDP command.

MDP project-name... ADDAPPL=(appl-name[/tdscode] [,appl-name[/tdscode]...])

Example:

CRP PROJ APPLIST=( IOF ...)

The list of applications may also include the names of TDS versions and MML.

Site Catalog

47 A2 14UC Rev05 D-3

D.1.2 Defining the List of Stations for a Project

Any number of stations may be included in the station list for each project defined in thesite catalog.

ALL_RSYS used as a station name allows access to:

• all the stations which are explicitly declared in the SITE.CATALOG

• all the stations which have the same name as the Remote System declared in theGCOS 7 NETGEN and the characteristics of a fictitious station ALL_RSYS (When thisstation does not exist; the characteristics of the MAIN station are assumed:

The list of stations is:

• defined when the project is created in the SITE.CATALOG through the STTNLISTparameter of the CRP (create project) command

CRP project-name... STTNLIST= ( station-name [,station-name...] )

or

CRP project-name... STTNLST={ ALL_RSYS | (station-name,ALL_RSYS) }

• or added to when the site catalog is subsequently modified by the ADDSTTNparameter of the MDP (modify project) command.

MDP project-name... ADDSTTN=(station-name [,station-name]...])

Example:

1) CRP PROJ STTNLIST=( HOST,DPS7,RS77,RS66,RS88,RSQX,RSIB)

or

2) CRP PROJ STTNLIST= ( HOST,ALL_RSYS)

HOST is the Default Station for the project PROJ and all Remote Systems declqred in theNETGEN will be considered as available for this project:

Both statements are identical in function:

• The list of stations in 1 includes all the remote systems and the host DPS 7/7000declared in the example in Appendix B. However, the names of the stations can bedifferent from those of the systems.

• The keyword ALL_RSYS in 2 replaces all the stations listed in 1. This command hasthe same effect as 1, but any Remote System added to the NETGEN will automaticallybe available for project.

DJP User's Guide

D-4 47 A2 14UC Rev05

D.2 CATALOGING A STATION AND DEFINING THE ASSOCIATED LIST OFSITES

A station is first created by a CRS command and may be subsequently included in the listof stations associated with the project.

On the DPS 7/7000, all projects created without an explicit station list are linked by defaultto the MAIN station. This means that all users linked to these projects also belong to theMAIN station by default.

The station is associated with a list of sites.

Defining the List of Sites for a Station

Any number of sites may be included in the site list for each station defined in the sitecatalog.

ALL_RSYS used as a site name allows access to all the sites which have the same nameas a Remote System declared in the GCOS 7 NETGEN.

The list of sites is

• defined when a station is created in the SITE.CATALOG through the SITELISTparameter of the CRS (create station) command

CRS station-name... SITELIST= ( site name [,site-name...])

or

CRS station-name... SITELIST={ ALL_SYS | (site-name,ALL_RSYS) }

• or added to when the site catalog is subsequently modified by the ADDSITE parameterof the MDS (modify station) command.

MDS station-name... ADDSITE=(site-name [,site-name]...])

Site Catalog

47 A2 14UC Rev05 D-5

Example:

1) CRS STTN SITELIST= (HOST,DPS7,RS77,RS66,RS88,RSQX,RSIB)

or

2) CRS STTN SITELIST= (HOST,ALL_RSYS)

HOST is the Default Site for the station STTN and all Remote Systems declared in theNETGEN will be considered as available for this station.

Both statements are identical in function:

• The list of sites in 1 includes all remote systems and the host DPS 7/7000 declared inthe Example in Appendix B

• The keyword ALL_RSYS in 2 replaces all the sites listed in 1; This command has thesame effect as 1, but any Remote System added to the NETGEN will automatically beavailable for station STTN without catalog modification.

DJP User's Guide

D-6 47 A2 14UC Rev05

47 A2 14UC Rev05 E-1

E. WHEN, EVERY and RRESTART

E.1 WHEN

Purpose of WHEN is to specify when the request will be enqueued for execution.

E.1.1 Absolute Addressing

WHEN or WHEN=IMMED allows the request to be enqueued immediately.

WHEN=date_time allows the request to be enqueued and executed on the given date atthe specified time. However, if the time is prior to the current time, the request iscancelled with an error message.

Date_time has the format

month.day.yy[yy].hh.mm

where the separators can be . or : or /

month can be a number from 1 through 12 or the first 3 letters of the month such as JANor MAR.

day can be:

• if the month is after the current month and is therefore explicitly specified- either a number from 1 through 31- or LAST-n* where n is a number from 1 through 3 concatenated to the name of the

day, being the first 3 letters such as JAN:LAST-1*MON 1992, meaning the last butone Monday of January 1992

• if the month is current and therefore omitted- either a number from 1 through 31 concatenated to *DAY, meaning the nth day of

the current month- or a number from 1* through 4* concatenated to the name of the day, being the first

3 letters of the day such as 2*TUE, meaning the second Tuesday of the currentmonth

DJP User's Guide

E-2 47 A2 14UC Rev05

- or LAST concatenated to *DAY, meaning the last day of the current month- or LAST-n where n is a number from 1 through 15, meaning n days before the end

of the current month.

• The expression *DAY can also apply to *WKD (working day) or *NWKD (non-workingday). Please see Appendix A.15 for a description of the Main Operator CommandMDDJP.

• if the day is relative to today either in the form of TOM (tomorrow) or NXW (next week),in which case the month can either be current or the month following, see paragraphE.1.3 Fast Options.

• if the day and/or time have lapsed in which case, FORCE enables the request to beimmediately enqueued for execution, see paragraph E.1.4 FORCE Option.

year can be expressed either as 2 digits such as 91 or 4 digits such as 1991.

hours and minutes are expressed as digits in the order indicated.

Examples:

WHEN=20*DAY:10:00request to be enqueued and executed on the 20th day of the current month at 10:00.

WHEN=LAST*DAY/7:00request to be enqueued and executed on the last day of the current month at 7:00.

WHEN=3*MON/18.00request to be enqueued and executed on the third Monday of the current month at18:00.

WHEN=LAST-2:10.34request to be enqueued and executed 2 days before the end of the current month at10:34.

WHEN=JAN.LAST-1*MON.1992.12:30request to be enqueued and executed on the last but one Monday of January 1992 at12:30.

WHEN=12.25.91.6.30request to be enqueued and executed on December 25, 1991 at 6:30.

WHEN, EVERY and RRESTART

47 A2 14UC Rev05 E-3

E.1.2 Relative Addressing

WHEN=+delay gives the interval before the request is enqueued.

Delay is a signed (+) number of:

• weeks (W or WEEK)• days (D or DAY)• hours (H or HOUR)• minutes (M or MIN).

Delay must be greater than 1 minute. The maximum delay period, specified as a numberof up to 5 digits, is 45 days, 12 hours and 15 minutes.

Examples:

WHEN=+H30Menqueuing and execution in 1 hour and 30 minutes.

WHEN=+2Denqueuing and execution in 2 days.

WHEN=+4W2Denqueuing and execution in 4 weeks and 2 days.

E.1.3 Fast Options

Abbreviations are available as acronyms, namely:

• NXD.WKD for next working day

• NXD.NWKD for next non-working day

• NXD for next day

• NXW for next week

• TOM for tomorrow

• and the first 3 letters of the day such as WED for Wednesday.

The default day for next week being Monday and the default time being 00H00.

DJP User's Guide

E-4 47 A2 14UC Rev05

Examples:

WHEN=TOMthe request is enqueued tomorrow at 00H00.

WHEN=TOM:14:30the request is enqueued tomorrow at 14H30.

WHEN=NXDthe request is enqueued next day (tomorrow) at 00H00.

WHEN=NXD/TUEthe request is enqueued next Tuesday at 00H00.

WHEN=NXD.TUE.8.45the request is enqueued next Tuesday at 8H45.

WHEN=NXD.WKDthe request is enqueued next working day at 00H00.

WHEN=NXD.NWKD.10.00the request is enqueued next non-working day at 10H00.

WHEN=NXWthe request is enqueued next week on Monday at 00H00.

WHEN=NXW/TUEthe request is enqueued next week at Tuesday at 00H00.

WHEN=NXW.TUE.8.45the request is enqueued next week at Tuesday at 8H45.

E.1.4 FORCE Option

FORCE is useful when the requested date and/or the requested time have lapsed.

The request is enqueued immediately for execution on the current date and at the currenttime irrespective of the submission date and/or time without an error message beingissued.

Example:

WHEN=FORCE.10.00

submitted today at 11H00, it causes the request to be enqueued today at 11H00.

WHEN=10.00

submitted today at 11H00 without FORCE or EVERY specified, it will result in

• the error message : *** WHEN : ILLEGAL VALUE .

• and the WHEN-clause being rejected .


47 A2 14UC Rev05 E-5

E.2 EVERY

EVERY specifies the interval and the number of times that the request is to besubsequently enqueued for execution.

The interval expressed in EVERY is equivalent to delay in WHEN, see paragraph E.1.2Relative Addressing. However, the value of interval for EVERY must be greater than xminutes but less than 45 days, 12 hours and 15 minutes. x is by default 15 minutes or canbe set to a value between 1 and 14 using the MINEVERY parameter of DJPCTL verb ofCONFIG. (See System Installation, Configuration, and Updating Guide.)

The format of EVERY is:

EVERY = ( interval [times] ), where

interval is limited to 12 characters and is a number qualified by:• weeks (W or WEEK)• days (D or DAY)• hours (H or HOUR)• minutes (M or MIN)• months (MONTH)• working days (WKD)• non-working days (NWKD).

times is the number of times up to a maximum of 65535 that the request is to beenqueued. When omitted, the request will continue to be enqueued until the userintervenes or the request is ultimately executed.

If MONTH is specified, the request will be handled on the same day as the submissionday next month. If the submission day is 31, the request will be handled on the 1st. of themonth following the next. For example, if the submission day is May 31st., the request willbe handled on July 1st.

working days (WKD) are the days that belong neither to the list of the non-working daysnor to that of the holidays. There are default lists for non-working days and for holidays inthe system. These can be modified using the MODIFY_DJP command.

Examples:

EVERY=5Wrequests are to be enqueued indefinitely every 5 weeks.

EVERY=(1D 2)requests are to be enqueued once every day for 2 days.

EVERY=(20M 72)requests are to be enqueued every 20 minutes, 72 times in total.

EVERY=(4H 6)requests are to be enqueued every 4 hours, 6 times in total.

EVERY=1WKDrequests are to be enqueued indefinitely every working day.

DJP User's Guide

E-6 47 A2 14UC Rev05

WHEN=MAR.31.16.30 EVERY=MONTHrequests will be enqueued at 16H30 on March 31st., May 1st., May 31st., ... until theuser intervenes or the requests are ultimately executed.

WHEN=DEC/21/1995/12/45 EVERY=WKDrequests will be enqueued at 12H45 on December 21st, 22nd, 26th, etc. Saturdays,Sundays and Christmas are considered non-working days.

WHEN=OCT.1*WKD/7.30 EVERY=MONTHrequests will be enqueued each month beginning on the first working day of October at7H30.

WHEN=JAN.LAST*WKD/00.00 EVERY=MONTHrequests will be enqueued each month on the last working day beginning January atmidnight.

WHEN=NXD.NWKD.8.30 EVERY=NWKDrequests will be enqueued at 8H30 every non-working day beginning on the next non-working day.


47 A2 14UC Rev05 E-7

E.3 RRESTART

RRESTART specifies what to do with the requests which normally should have beenhandled at a time when the system was stopped for whatever reason and then restartedby WARM RESTART. RRESTART takes into account all system stoppages whether theyare normal shutdown or hardware and software failures. Requests whose dates aresubsequent to the restarting time are not affected and will be enqueued normally whentheir time is due.

IMMED: the request is immediately enqueued.

CANCEL or NO: the request is cancelled.

delay: delay is added to the normal enqueuing time.Delay is expressed in- minutes (M)- hours (H)- days (- weeks (W).

Delay can be qualified by E to denote elapsed time.

DelayE specifies the maximum delay allowed for enqueueingthe request, on expiration of which the request is cancelled.Maximum elapsed time for delayE is set at 45 days, 12 hoursand 15 minutes.

Examples:

WHEN=10.30 RRESTART=1DThe request is to be enqueued at 10H30 in a day's time. If on the day at 10H30 thesystem is down, the request will be enqueued tomorrow at the same time. If cometomorrow the system is still down, the request is further enqueued for a subsequentdelay and so on, indefinitely.

WHEN=10.30 RRESTART=1DEThe request is to be enqueued at 10H30 in a day's time. If the system was shut down(for whatever reason) and restarted, one of two actions concerning the request will betaken:

- either the request will be enqueued and executed if the system was restartedbefore the elapsed time expired

- or the request will be cancelled if the system was restarted after the elapsed time.

NOTE: If the request is repetitive; the delayE must be less than the delay between twonormal executions of the request specified by EVERY.

DJP User's Guide

E-8 47 A2 14UC Rev05

47 A2 14UC Rev05 F-1

F. Messages and Status Codes

F.1 REPORTING

F.1.1 JOR at Local and Remote Sites

Error messages specific to the file transfer that can appear in the JOR may be generatedeither by the file transfer facility or by RFA (remote file access).

A JOR is normally generated at the local site for every file transfer activity. When theactivity has been initiated by the file transfer command, the JOR is printed only in case ofabort. A JOR is also generated at the remote (Server) site for each Server activity. So thatthe 2 JOR's involved in the same file transfer can be easily related, the JOR at therequestor site indicates the RON of the Server activity, while the JOR at the Server siteindicates the RON of the requestor activity.

Both JORs give summary indications on the file transfer which was requested:

• at the requestor:- file names for local and remote files- processing mode of the remote file- negotiable options such as BINARY, DATA COMPRESSION and RESTART

• at the server:- the server file name- processing mode- the identification of the requestor site.

Because the file transfer is only a special kind of file copy, the file transfer facility usesprocedures of the CREATE utility that performs local file copies in units of records or CIs.

Messages generated by the CREATE utility will appear in the JOR at the Requestor site.For the description of these messages, see the Data Management Utilities.

The error messages specific to the file transfer that can appear in the JOR are given inthis Appendix. They may be generated either by the file transfer facility or by the remotefile access method.

DJP User's Guide

F-2 47 A2 14UC Rev05

All the messages generated by RFA (Remote Access Method) are prefixed by RT.Messages generated by the CREATE utility are prefixed by DU in the JOR but not at theterminal.

RFA generates two kinds of messages:• those for information only, which do not require intervention• those which report a problem encountered for which FATAL or WARNING appears to

the left of the message and which requires the user to perform corrective action.

Information: these messages are for information only concerning thestatus or the condition of the transfer and require nointervention.Action: none

Warning: these messages are in italics and advise the user thatalthough the transfer has executed, an exception conditionhas occurred that may affect the reliability of the datatransferred.Action:If the contents of the data transfer are incorrect, resubmitthe transfer request. If the same anomaly occurs, call theService Center.

Fatal: these messages are in bold and inform the user that thetransfer has been unsuccessful; intervention either by theuser or the service center is required.Action:Try correcting the error condition from the message textgiven, then resubmit the transfer request. If the same errorcondition persists, call the Service Center.

RFA messages appear in the JOR for FILTFR and for the SERVER2 and on the userconsole for EFTR, ELTR and EXFT. These messages are explicit in meaning.

RFA messages appear in JOR for FILTFR and for the SERVER2. They appear on theuser console for EFTR, ELTR or EXFT.

Some of the messages listed below appear only when the TRACE keyword has been setby the user or by the operator STTR command.

When the TRACE command has been set, the SERVER2 produces a JOR whether thetransfer aborts or is successful. This feature can be used by the user to have moreinformation about any problem that occurs on the other site.

Messages and Status Codes

47 A2 14UC Rev05 F-3

F.1.2 RFA Messages

Messages are preceded by code and severity for the convenience of the user, to providethe following information:

• code for finding the UFT function originating the message• severity for determining the degree of intervention required.

Neither code nor severity appear in the message text.

CODES

AC Activate or deactivate work station or mailboxAS Assign the fileCK Checkmark processingCO Connection processingCR Create processingDA Data phase processingDC Delete or Create processingDI DisconnectDL Delete processingFA File assignmentFD File definitionNA Nack of a control recordOP Open of the remote filePR Protocol checkingRDC Rename or DElete or Create processingRD Rename or DElete or Create processingRN Rename processingRV Receive of a remote recordRS Restart processingSD Send a record to the remote siteSR Send or receive of a remote recordTR UFT traceUF UFT managementXX Not defined

SEVERITY

I Information messageW Warning messageF Fatal error

DJP User's Guide

F-4 47 A2 14UC Rev05

Example:

CO F RT212 NO SESSION ANY MORE: REMOTE SITE WAS site+- - +---- +----------------------------------- ---+| | | | || | | | metalanguage terms appear in italics<-+| | | || | | +->message text| | || | +->RTnumber| || | <-------message as it actually appears-------->| || +->severity: a fatal error has occurred|+->code: the UFT function for the message is Connection Processing

F.1.2.1 Messages

CO I RT101 > > > R F A DSA V2A PROTOCOL 40*TR I RT102 MGI= 128xCO I RT103 ESTABLISHED CONNECTION WITH SITE siteCO I RT104 ESTABLISHED CONNECTION WITH SITE site AND ronCO I RT105 > > > RFA PROCESSING STOPPED < < <

TR I RT106 AUTOMAT STATE WAS: aaa aaaTR I RT107 AUTOMAT STATE WAS: ACK aaa aaaDI I RT108 DISCONNECTION DONETR I RT109 < < < END RFATR I RT110 CELL= xx STATE= xx EVENT= xxxx control-record state RQ-> NEW-STATE= state

TR I RT111 RQ-> NEW-STATE= stateTR I RT112 SD-> NEW-STATE= stateTR F RT113 SEND A LEVEL 5 SD-> NEW-STATE= stateTR F RT114 SENDIT VALUE=xx SD-> NEW-STATE= stateTR I RT115 SD MGC=64x

TR F RT116 SEND: ERROR ON SEND SD-> NEW-STATE= stateTR F RT117 SEND: DETECTED LEVEL 5 SD-> NEW-STATE= stateTR I RT118 CELL=xx STATE= aa EVENT= aaa SD-> NEW-STATE= stateTR I RT119 SEND: NOT V-CREDIT RECEIVED SD-> NEW-STATE= stateRV W RT120 INFILE FILE IS EMPTY

TR I RT121 RV MGC = L_64RV I RT122 RECEIVE ERROR RV-> NEW_STATE= stateRV I RT123 DETECTED LEVEL 5 ON RECEIVE RV-> NEW_STATE= stateTR I RT124 CELL= xx STATE= xx EVENT= xxxx record-name state RV-> NEW-STATE= state QUEUE= queueTR I RT125 RV-> NEW-STATE= state

DI I RT126 DISCONNECT ALREADY DONEDI I RT127 SESSION NORMALLY TERMINATEDDI I RT128 ABNORMAL TERMINATION OF SESSIONDI I RT129 EDISC: SEND A CLMSGDI I RT130 EDISC: SEND A NORMAL END OF SESSION, MGC= 64x


47 A2 14UC Rev05 F-5

SD I RT131 RECEIVE EVENT ON SEND. STATUS= xx OPCODE= xxTR I RT132 MGC= 32xCO I RT133 ASKED CONNECTION COMING FROM SITE siteCO I RT134 ASKED CONNECTION COMING FROM SITE site WITH ronCO I RT135 CONNECTION ACCEPTED

TR I RT136 STATUS= statusTR I RT137 STATUS= statusTR I RT138 CELL= xx STATE= xx EVENT= xxxx control-record site SR-> NEW-STATE= stateTR I RT139 SR-> NEW-STATE= new-stateCO I RT140 ESTABLISHED CONNECTION WITH SITE site AND Xcccc. REQUEST= cccc

CO I RT141 ASKED CONNECTION COMING FROM SITE site WITH cccc. REQUEST= cccc.CO F RT201 REASON: TELECOMMUNICATIONS ARE NOT STARTEDCO F RT202 REQUESTOR: REMOTE SITE NAME IS BLANK OR NOT SPECIFIEDCO F RT203 CONNECT: ERROR IN GSYSTI TO FIND REMOTE CHARACTERISTICSCO F RT204 CONNECT CANNOT GET A SEMAPHORECO F RT205 CONNECT, REQUESTOR: SITE IS NOT AVAILABLECO F RT206 CONNECT, REQUESTOR: CONNECTION REJECTED BY DESTINATIONCO F RT207 CONNECT, REQUESTOR: CALLER S MAILBOX SATUREDCO F RT208 CONNECT, REQUESTOR: SYSTEM RESOURCE ALLOCATED FAILURECO F RT209 CONNECT, REQUESTOR: CONNECTION REJECTED BY VCAM

CO F RT210 CONNECT, IMPOSSIBLE TO OPEN MESSAGE GROUPCO F RT211 CONNECT, UNSUCCESSFUL INQUIRE, ABORTCO F RT212 NO SESSION ANY MORE: REMOTE SITE WAS siteCO F RT213 CONNECT: UNABLE TO KNOWN THE SLFICB SIZECO F RT214 CONNECT: SPACE ALLOCATED FOR SLFICB STRUCTURE CANNOT BE PERFORMED

CO F RT215 CONNECT: CANNOT GET THE PROCEDURE ADDRESS OF aaaaaaaaCO F RT216 CONNECT: UNABLE TO SET TIMERCO F RT217 CONNECT: MCEVENT ARGERR. REASON: xxxxxxxxCO F RT218 CONNECT: MCEVENT USE OF WRONG PARAMETERSCO F RT219 CONNECT: INPUT SEMAPHORE MESSAGE OPCODE IS NOT V_EVENT

CO F RT220 CONNECT: ABNORMAL END SHUTDOWNCO F RT221 CONNECT: ABNORMAL EVENT: 0235xxxxCO F RT222 CONNECT: V_DATA ON CONNECTIONCO F RT223 CONNECT: V_INTERRUPT ON CONNECTIONCO F RT224 CONNECT: V_MGCLOSED ON CONNECTION

CO F RT225 CONNECT: V_LCCLOSED ON CONNECTIONCO F RT226 CONNECT: V_SHUTDOWN ON CONNECTIONCO F RT227 CONNECT: ERROR ON MCEVENTCO F RT228 CONNECT: UNKNOWN OPCODE ON MCEVENTCO F RT229 CONNECT: UNABLE TO CREATE A SEGMENT

CO F RT230 CONNECT: UNSUCCESSFUL H_READSB PRIMITIVE BEFORE CONNECTIONCO F RT231 EACONN: SERVER :CHECK WHEN RECEIVED CONNECTIONCO F RT232 EACONN: SPACE ALLOCATION FOR STRUCTURES NOT PERFORMEDCO F RT301 REASON: ABNORMAL INQUIRECO F RT302 REASON: SYSOV ON STARTJ

DJP User's Guide

F-6 47 A2 14UC Rev05

CO F RT303 REASON: TOO LATE ON STARTJCO F RT304 REASON: TOO MANY INTERACTIVE/SERVICE JOBSCO F RT305 REASON: USER MEMORY OVERLOAD ON STARTJCO F RT306 REASON: CLASS OVERLOADED ON STARTJCO F RT307 SERVER ABORTED

CO F RT308 REASON: SITE SERVER DOES NOT HAVE RFA ACCESS METHODCO F RT309 REASON: STARTJ REFUSEDCO F RT310 REASON: DESTINATION MAILBOX SATURATEDCO F RT311 REASON: DESTINATION MAILBOX UNKNOWNCO F RT312 REASON: DESTINATION MAILBOX NOT OPERATIONAL

CO F RT313 REASON: DUPLICATE USER IDENTIFICATIONCO F RT314 REASON: PATH NOT OPERATIONALCO F RT315 REASON: CATALOG VIOLATIONCO F RT316 REASON: DESTINATION NODE UNKNOWNCO F RT317 REASON: DESTINATION NODE IS NOT OPERATIONALCO F RT318 REASON: DLG REJECTCO F RT319 REASON: ABNORMAL REJECTCO F RT320 REASON: TIME OUTCO F RT401 COMPL STATUS: REQUESTED MAILBOX IS LOCAL AND IS SATURATEDCO F RT402 COMPL STATUS: SYNCHRONOUS OPMG VERB AND V_OPENACK MESSAGE NOT RECEIVED BY THE EVENT PROCESSING

CO F RT403 COMPL STATUS: REMOTE INITIATOR CASE AND WRONG NODE CODES ARE DRIVEN IN THE ADDRESS RECORD OF THE ILCRL CONNECTION LETTERCO F RT404 COMPL STATUS: REQUESTED NODE IS LOCAL AND REQUESTED MAILBOX IS NOT DEFINEDCO F RT405 COMPL STATUS: USER UNKNOWNCO F RT406 COMPL STATUS: PROJECT UNKNOWNCO F RT407 COMPL STATUS: BILLING UNKNOWN

CO F RT408 COMPL STATUS: STATION UNKNOWNCO F RT409 COMPL STATUS: APPL UNKNOWNCO F RT410 COMPL STATUS: RLUP UNKNOWNCO F RT411 COMPL STATUS: RLUP UNKNOWNCO F RT412 COMPL STATUS: RLAP UNKNOWN

CO F RT413 COMPL STATUS: COMPL STATUS:RLSP UNKNOWNCO F RT414 COMPL STATUS: PASSWORD VIOLATIONCO F RT415 COMPL STATUS: UNEXPECTED RETURN CODE FROM CATALOGCO F RT416 COMPL STATUS: CATALOG NOT VALIDATED OR SUBMITTER IDENTIFICATION SET NOT GIVEN BY INITIATOR AND DESTINATION MAILBOX SPECIFIES CTL=, OR NCTL=0CO F RT417 COMPL STATUS: WRONG DESTINATION MAILBOX NAME

CO F RT418 COMPL STATUS: DUPLICATE NAME OWNER CREATING A MAIN USER ID IN DICTIONARYCO F RT419 COMPL STATUS: DESTINATION NODE UNKNOWNCO F RT420 COMPL STATUS: NEITHER THE CALLER'S MAILBOX NOR THE DESTINATION'S ONE IS AN APPLICATION MAILBOXCO F RT421 COMPL STATUS: REQUESTED NODE IS REMOTE AND THE CORRESPONDING WORKSTATION IS NOT ACTIVECO F RT422 COMPL STATUS: REQUESTED NODE IS REMOTE AND THE CORRESPONDING WORKSTATION DOESN'T EXIST


47 A2 14UC Rev05 F-7

CO F RT423 COMPL STATUS: DESTINATION MAILBOX IS SATURATED AND HAS REJCT OPTIONCO F RT424 COMPL STATUS: DESTINATION MAILBOX IS IN THE ENDING STATE AND IS DYNAMIC OR IS STATIC AND HAS REJECT OPTIONCO F RT425 COMPL STATUS: SBC ALLOCATION FAILED, REMOTE INITIATION CASECO F RT426 COMPL STATUS: SESSION ENTRY ALLOCATION FAILED,REMOTE INITIATOR CASECO F RT427 COMPL STATUS: RETURN CODE NOT DONE WHEN TRYING TO PUT CONNECTION LETTER IN THE BUFFER POOL

CO F RT428 COMPL STATUS: REMOTE INITIATOR CASE,ILCRL CONNECTION LETTER IS NOT IN AGREMENT WITH DSA PROTOCOLCO F RT429 COMPL STATUS: REMOTE INITIATOR CASEZ, ILCRL CONNECTION LETTER SPECIFIES A EXTENSION, AND THIS PARAMETER IS NOT IMPLEMENTED IN THE CURRENT RELEASECO F RT430 COMPL STATUS: A CONNECTION ARRIVES FROM A REMOTE INITIATOR AND THE SPECIFIED DESTINATION IS NOT THE LOCAL NODECO F RT431 SPECIAL ERROR FROM OTHER SITEUF F RT501 DAP PRIMITIVE CALL ERROR

UF F RT502 PROTOCOL NUMBER ERRORUF F RT503 THE DAP SERVER IS NOT A SUBSET OF THE DAP REQUESTORUF F RT504 SAP PRIMITIVE CALL ERRORUF F RT505 INCORRECT NUMBER OF PROTOCOLSPR F RT506 ERROR WITH THE PROTOCOL

UF F RT507 EXECUTE JOB NOT ALLOWED ON OTHER SITEUF F RT508 FILE TRANSFER NOT ALLOWED ON OTHER SITEUF F RT509 INPUT READER NOT ALLOWED ON OTHER SITEUF F RT510 OUTPUT WRITER NOT ALLOWED ON OTHER SITEUF F RT601 INVALID CHECK DRF CALL

UF F RT602 TRANSFER OR CREATION OF FILES WHOSE FILEORG= NONE IS ONLY AUTHORIZED BETWEEN TWO DPS7 WITH RELEASES >= V6.FD F RT603 INVALID RECFORM FOR DRF TO SENDFD F RT604 INVALID FILEORG FOR DRF TO SENDFD F RT605 INVALID TRANSLATE TIME FOR DRF TO SEND (expiration date not sent)FD F RT606 INVALID LABEL FOR DRF TO SEND (label not sent)

FD F RT607 INVALID LIBTYPE FOR DRF TO SEND (libtype not sent)FD F RT608 CISIZE: ILLEGAL VALUE IF KBYTESFD F RT609 INVALID REQATTR IN RECEIVED DRFFD F RT610 INVALID RECFORM IN RECEIVED DRFFD F RT611 INVALID FILE_ORG IN RECEIVED DRF

FD F RT612 INVALID EXPIRATION DATEFD F RT613 INVALID PARAMETER IN PARAMETER PROCESSING SERVERFD F RT614 INVALID REC LENGTH, COMPUTE_PARAM, DRFFD F RT615 INVALID DFLDEF, DRFFD F RT616 INVALID RETRIEVE SIZE, DRF

FD F RT617 INVALID RFLDEF_OVERRIDE, DRFFD F RT618 INVALID RFLDEF SOURCE, DRFFD F RT619 INVALID RFLDEF-DEFINED IN DRFFD F RT620 EDRF: MISSING RFA SLFICB SECTIONSCR F RT621 ITS FORBIDDEN TO CREATE A FILE

DJP User's Guide

F-8 47 A2 14UC Rev05

DL F RT622 ITS FORBIDDEN TO DELETE A FILERN F RT623 ITS FORBIDDEN TO RENAME A FILEUF F RT624 CALL NOT IN THE SCENARIODA F RT625 TOO LARGE RECORDS: COMPACT IS MODIFIED IN NCOMPACTUF F RT626 ONLY SYSADMIN CAN CREATE,DELETE OR RENAME THIS FILE

CR F RT627 THE ccccc FUNCTION IS NOT SUPPORTED BY REMOTE SITEPR F RT701 PROTOCOL ERROR: RECEIVE WHILE REQUESTOR HAS THE TURNPR F RT702 PROTOCOL ERROR: CONTROL RECORD NUMBER NOT FIRST IN ACKNOWLEGMENT RECORDPR F RT703 EAUTMR, PROTOCOL ERROR: UNKNOWN RECORD TYPE xxxxPR F RT704 PROTOCOL ERROR: TURN NOT RECEIVED ON CONTROL RECORD NUMBER

PR F RT705 AUTOMAT: PROTOCOL ERROR. DAP MUST GIVES THE TURNPR F RT706 PROTOCOL ERROR: ILLEGAL PROTOCOL TYPEPR F RT707 AUTOMAT: PROTOCOL ERROR. PROTOCOL cccPR F RT708 AUTOMAT: PROTOCOL ERROR. TURN NOT RECEIVED AFTER A(SAP)PR F RT709 AUTOMAT: PROTOCOL ERROR. TURN RECEIVED WHILE THE STATE QUEUE IS NOT EMPTY

PR F RT710 EAUTMR: PROTOCOL ERROR: TURN RECEIVED AND STATES QUEUE NOT EMPTYPR F RT711 PROTOCOL ERROR: UNKNOWN LAST CONCATENATE CONTROL RECORDPR F RT712 PROTOCOL ERROR: NEXT CONTROL RECORD UNKNOWNPR F RT713 PROTOCOL ERROR: INVALID CONCATENATION.LAST= xx NEXT= yyPR F RT714 PROTOCOL ERROR, ACK HAS NOT TYPE1 AHEADPR F RT715 ERROR IN STATES QUEUE MANAGEMENTPR F RT716 OVERFLOW IN QUEUE STATE TABLEPR F RT717 PROTOCOL ERROR DETECTED BY REQUESTORPR F RT718 PROTOCOL ERROR: RECEIVED TURN WHILE WAITING FOR ACKNOWLEDGEMENTUF F RT719 REQAUTOMAT: MISSING RFA SLFICB SECTIONSUF F RT720 PUT: NOT ALLOWED OUT OF DATA PHASE PROCESSINGUF F RT721 PUT: CONTROL RECORD NOT AUTHORIZEDUF F RT722 IWRITE CALL ERRORUF F RT723 REASON: TELECOMMUNICATIONS ARE NOT STARTEDUF F RT724 PROTOCOL ERROR: UNKNOWN EVENT xxUF F RT725 SEND: PROTOCOL ERRORUF F RT726 SEND: ATTENTION ERRONEOUS LENGTHSD F RT727 SEND: COMPACTION ERRORSD F RT728 procedure: CANNOT GET THE PROCEDURE ADDRESS OF OTHER procedureSD F RT730 PUT/SEND: TIMEOUT ON SEMAPHORE

PR F RT731 PROTOCOL ERROR: AUTOMAT-STATE= 0DA F RT732 THE INPUT RECORD IS > OUTPUT MAXIMUM RECORD SIZEDA F RT733 RECEIVE: DECOMPACTION ERRORRV F RT734 RECEIVE: TIMEOUT ON SEMAPHORERV F RT735 RECEIVE: NOT V_DATA ON SEMAPHORE

RV F RT736 RECEIVE: MISSING SECTIONS IN RFA SLFICBUF F RT801 INVALID DISCONNECT: REQUEST IDENTIFIER DOESNT MATCH WITH PRESENT CONNECTIONUF F RT802 DISK: MISSING RFA SLFICB SECTIONSUF F RT803 INVALID DISCONNECT: REQUEST IDENTIFIER= 0DI F RT804 DISC: ERROR ON CLOSE MESSAGE GROUP

DI F RT805 EDISC: NO TURN, SO ABNORMAL END OF SESSIONDI F RT806 ABNORMAL TERMINATION OF SESSIONUF F RT807 DISCONNECT CANNOT DELETE THE TIMERUF F RT808 DISCONNECT CANNOT DELETE THE SEMAPHORECO F RT809 CONNECT: UNABLE TO SET TIMER


47 A2 14UC Rev05 F-9

NA F RT901 NACK OF RECORD: aaa SEVERITY= severity CLASS= classUF F RT904 COMMON ERROR REASON CODE OUT OF V2A PROTOCOLNA F RT905 REASON TEXT: textNA F RT906 SUPPL.DIAG.CODE= aaUF F RT909 SPECIFIC ERROR ccc REASON CODE OUT OF V2A PROTOCOL

NA F RT912 RECORD TYPE: cccc RESTART RANK: ccccc LAST_ACTIVITY: cccc RELATIVE_RECORD_NUMBER: ddddddNA F RT913 RECORD KEY LENGTH: ccc VALUE: dddddNA F RT914 DIAGNOSTIC SUPPLEMENT: SYSTEM= cccc MESSAGE1= messageNA F RT915 DIAGNOSTIC SUPPLEMENT: MESSAGE2= messagePR F RT1001 FIRST GET: ABNORMAL SDT

UF F RT1002 FIRST GET: IMPOSSIBLE TO GET THE GET PROCEDURE ENTRYUF F RT1003 FIRST GET: MISSING RFA SLFICB SECTIONSUF F RT1004 SDT2: IMPOSSIBLE TO GET THE PUT PROCEDURE ENTRYUF F RT1005 SDT2: IMPOSSIBLE TO GET THE GET PROCEDURE ENTRYUF F RT1006 SDT PRIMITIVE CALL ERROR

UF F RT1007 FIRST PUT: ABNORMAL SDTUF F RT1008 FIRST PUT: IMPOSSIBLE TO GET THE PUT PROCEDURE ENTRYUF F RT1009 MISSING RFA SLFICB SECTIONSTR I RT1101 TRACE: UNABLE TO CREATE FDTR I RT1102 TRACE: UNABLE TO OPEN TRACE FILE

UF F RT1201 cccccc: SPACE ALLOCATION FOR STRUCTURES NOT PERFORMEDRV F RT1202 RECVR: RECEIVE TURNVIOLRV F RT1203 RECVR: RECEIVE RESOVRV F RT1204 RECVR: RECEIVE NOCREDITRV F RT1205 RECVR: MGCSTAT VALUE IS xx

RV F RT1206 RECVR: RECEIVE ARGERRRV F RT1207 RECVR: EXCEPTION DURING ACCESS TO LAST BYTES OF WKS PARAMETERSRV F RT1208 RECVR: WRONG VALUE OF WKS-F15WSIDENTRV F RT1209 RECVR: WORKSTATION IS NOT ACTIVERV F RT1210 RECVR: EXCEPTION DURING ACCESS TO LAST BYTE OF MGC PARAMETER

RV F RT1211 RECVR: EXCEPTION DURING ACCESS TO WA IN MCRECV CODERV F RT1212 RECVR: SESSION IN WRONG STATE IN MCSENDRV F RT1213 RECVR: WRONG VALUE OF MGC-L08REQLVL IN MCSENDRV F RT1214 RECVR: CREDIT TO BE RECEIVED BEFORE SENDINGRV F RT1215 RECVR: MGC_L08REQLVL WITH AN INCORRECT VALUE (V_PORTION)RV F RT1216 RECVR: RECORD TYPE GREATER THAN 4095

RV F RT1217 RECORD TYPE SMALLER THAN 18RV F RT1218 EXCEPTION DURING ACCESS TO WA-INDEX=MGC-F15WASIZE IN RECEIVERV F RT1219 SESSION IN WRONG STATE (ACTIVE=1,TERMINATION RUNNING)RV F RT1220 SESSION IN WRONG STATE (NOT ACTIVE WITHOUT TERMINATION)RV F RT1221 NO LETTER TO BE RECEIVED (RECEIVE ASYNCHRONOUS MODE)

RV F RT1222 RECVR: WRONG MESSAGE GROUP IDENTIFIERRV F RT1223 RECVR: V_EVENT DOES NOT RETURN V_INTERRUPTRV F RT1224 RECVR: TOO BIG RECORD TOWARDS TNSRV F RT1225 RECV ERROR : ABNORMAL TERMINATION BY aaaaaaaaaRV F RT1226 TERMINATION REQUESTED ON RECV: IMMEDIATE SHUTDOWN

DJP User's Guide

F-10 47 A2 14UC Rev05

UF F RT1227 DEMAND TURN NOT ALLOWED IN V2 PROTOCOLRV F RT1228 PURGE REQUESTEDRV F RT1229 V-TELEG ON RECV: PROTOCOL ERRORRV F RT1230 V-RECOREQ ON RECV: PROTOCOL ERRORRV F RT1231 V-RECOACK ON RECV: PROTOCOL ERROR

RV F RT1232 RECVR: OTHER FEATURE IS ASKING FOR A SESSION TERMINATIONRV F RT1233 RECVR: RECEIVED V-OPENREQRV F RT1234 RECVR: RECEIVED V-OPENACKRV F RT1235 RECVR: RECEIVED V-MGCLOSEDRV F RT1236 RECVR: RECEIVED V-DATA

RV F RT1237 RECVR: RECEIVED V-STARTUPRV F RT1238 RECVR: RECEIVED V-SHUTDOWNRV F RT1239 RECVR: RECEIVED V-LCCLOSEDRV F RT1240 RECVR: RECEIVED V-RDTNRV F RT1241 RECVR: RECEIVED V-CLG

RV F RT1242 RECVR: RECEIVED V-ACKLTSR F RT1243 ARGERR ON SEND SEMSR F RT1244 EXCEPTION IN LAST BYTES OF WKSSR F RT1245 WRONG VALUE OF WKS-F15WSIDENTSR F RT1246 WORKSTATION NOT ACTIVE

SR F RT1247 EXCEPTION IN LAST BYTES OF MGCSR F RT1248 EXCEPTION IN LAST BYTES OF WA IN MCSENDSR F RT1249 SESSION IN WRONG STATESR F RT1250 WRONG VALUE OF B-MGC-L08REQVL IN MCSENDSR F RT1251 RELEASE MRU TO BE RECEIVED BEFORE SENDINGSR F RT1252 CREDIT TO BE RECEIVED BEFORE SENDINGSR F RT1253 B-MGC-L08REQLVL WITH V-PORTIONSR F RT1254 RECORD TYPE GREATER THAN 4095SR F RT1255 CONTROL RECORD TYPE SMALLER THAN 128SR F RT1256 EXCEPTION DURING ACCESS OF WA (B_MGC_WASIZE) IN RECEIVE

SR F RT1257 SESSION IN WRONG STATE (NORMAL TERMINATION IS RUNNING)SR F RT1258 NO LETTER TO BE RECEIVED (RECEIVE IN ASYNCRONOUS MODE)SR F RT1259 WRONG MGID, MESSAGE GROUP IDENTIFIERSR F RT1260 AFTER INTERNAL POP, V_EVENT DOES NOT RETURN V_EVENTSR F RT1261 IN MUX, NO MORE SIM ENTRYSR F RT1262 TOO BIG RECORD TOWARDS TNSSR F RT1263 AREA RECEIVING THE DEVICE PROC HEADER IS TOO SHORTRV F RT1264 RECVR PROTOCOL ERROR: RECEIVED A CHEKPOINT MARK ACK ATTENTIONRV F RT1301 RECVR PROTOCOL ERROR: RECEIVED AN IMMEDIATE RESTART ATTENTIONRV F RT1302 RECVR PROTOCOL ERROR: RECEIVED A SUSPEND ATTENTION

RV F RT1303 RECVR PRTOCOL ERROR: RECEIVED A CANCEL ATTENTIONSR F RT1304 ATTENTION RECEIVED OUT OF PROTOCOL. VALUE= xxxxSR F RT1305 CONNECT: UNABLE TO SET TIMERRV F RT1306 RECVR: OPCODE VALUE IS xxRV F RT1307 RECVR: INT_TYPE, INT_VALUE ARE xxxxxx

RV F RT1308 ESEMRR: OPCODE VALUE IS xxRV F RT1309 ESEMRR: INT_TYPE, INT_VALUE ARE xxxxxxSD F RT1310 SENDR: OPCODE VALUE IS xxSD F RT1311 SENDR: INT_TYPE, INIT_VALUE ARE xxxxxxSD F RT1312 ESENDR: RECEIVED AN IMMEDIATE RESTART ATTENTION


47 A2 14UC Rev05 F-11

SD F RT1313 ESENDR: RECEIVE A SUSPEND ATTENTIONSD F RT1314 ESENDR: RECEIVED A CANCEL ATTENTIONRV F RT1401 ESEMRR: TIMEOUT ON SEMAPHORESD F RT1402 cccc: UNKNOWN OPCODE IN MESSAGERV F RT1403 RECEIVE ERROR: ABNORMAL TERMINATION BY aaaaaaaaaa

RV F RT1404 ESEMRR: ABNORMAL TERMINATION OF SESSION. VALUE: xxxxSR F RT1405 V_TELEG ON SEM: PROTOCOL ERRORSR F RT1406 V_RECOREQ ON SEM: PROTOCOL ERRORSR F RT1407 V_RECOACK ON SEND: PROTOCOL ERRORSR F RT1408 SEND SEM: OTHER FEATURE IS ASKING FOR A SESSION TERMINATION

SR F RT1409 SEND SEM: RECEIVED V_OPENREQSR F RT1410 SEND SEM: RECEIVED V_OPENACKSR F RT1411 SEND SEM: RECEIVED V_MGCLOSEDSR F RT1412 SEND SEM: RECEIVED V_DATASR F RT1413 SEND SEM: RECEIVED V_STARTUP

SR F RT1414 SEND SEM: RECEIVED V_SHUTDOWNSR F RT1415 SEND SEM: RECEIVED V_LCCLOSEDSR F RT1416 SEND SEM: RECEIVED V_RDTNSR F RT1417 SEND SEM: RECEIVED V_CLGSR F RT1418 SEND SEM: RECEIVED V_ACKLT

RV F RT1419 ESEMRR: RECEIVED AN ATTENTIONSD F RT1502 SENDR: RECEIVE TURNVIOLSD F RT1503 SENDR: RECEIVE RESOVSD F RT1504 SENDR: RECEIVE NOCREDITSD F RT1505 SENDR: MGCSTAT VALUE IS xx

SD F RT1506 SENDR: RECEIVE ARGERRSD F RT1507 SENDR: EXCEPTION DURING ACCESS TO LAST BYTES OF WKS PARAMETERSSD F RT1508 SENDR: WRONG VALUE OF WKS_F15WSIDENTSD F RT1509 SENDR: WORKSTATION IS NOT ACTIVESD F RT1510 SENDR: EXCEPTION DURING ACCESS TO LAST BYTE OF MGC PARAMETERSD F RT1511 SENDR: EXCEPTION DURING ACCESS TO WA IN MCSEND CODE. MGCF15ALN INDEX= indexSD F RT1512 SENDR: SESSION IN WRONG STATE IN MCSENDSD F RT1513 SENDR: WRONG VALUE OF MGC_L08REQLVL IN MCSENDSD F RT1514 SENDR: CREDIT TO BE RECEIVED BEFORE SENDINGSD F RT1515 SENDR: MGC_L08REQLVL WITH AN INCORRECT VALUE (V_PORTION)

SD F RT1516 SENDR: RECORD TYPE GREATER THAN 4095SD F RT1517 RECORD TYPE SMALLER THAN 18SD F RT1518 EXCEPTION DURING ACCESS TO WA_INDEX=MGC_F15WASIZE IN RECSIZESD F RT1519 SESSION IN WRONG STATE (ACTIVE=1,TERMINATION RUNNING)SD F RT1520 SESSION IN WRONG STATE (NOT ACTIVE WITHOUT TERMINATION)

SD F RT1521 NO LETTER TO BE RECEIVED (RECEIVE ASYNCHRONOUS MODE)SD F RT1522 SENDR: WRONG MESSAGE GROUP IDENTIFIERSD F RT1523 SENDR: V_EVENT DOES NOT RETURN V_INTERRUPTSD F RT1524 SENDR: TOO BIG RECORD TOWARDS TNSSD F RT1525 SEND ERROR: ABNORMAL TERMINATION BY xxxx

DJP User's Guide

F-12 47 A2 14UC Rev05

SD F RT1526 TERMINATION REQUESTED ON SEND: IMMEDIAT SHUTDOWNSR F RT1527 DEMAND TURN NOT ALLOWED IN V2 PROTOCOLSR F RT1528 PURGE REQUESTEDSD F RT1529 V_TELEG ON SEND: PROTOCOL ERRORSD F RT1530 V_RECOREQ ON SEND: PROTOCOL ERROR

SD F RT1531 V_RECOACK ON SEND: PROTOCOL ERRORSD F RT1532 SENDR: OTHER FEATURE IS ASKING FOR A SESSION TERMINATIONSD F RT1533 SEND ERROR: RECEIVED V_OPENREQSD F RT1534 SEND ERROR: RECEIVED V_OPENACKSD F RT1535 SEND ERROR: RECEIVED V_MGCLOSED

SD F RT1536 SEND ERROR: RECEIVED V_DATASD F RT1537 SEND ERROR: RECEIVED V_STARTUPSD F RT1538 SEND ERROR: RECEIVED V_SHUTDOWNSD F RT1539 SEND ERROR: RECEIVED V_LCCLOSEDSD F RT1540 SEND ERROR: RECEIVED V_RDTN

SD F RT1541 SEND ERROR: RECEIVED V_CLGSD F RT1542 SEND ERROR: RECEIVED V_ACKLTSD F RT1543 ESENDR: PROTOCOL ERROR: RECEIVED A CKM MARK ACK WHEN NO CKM SENTSD F RT1601 SEMSR: TIMEOUT ON SEMAPHORESD F RT1602 SEMSR: RECEIVE AN IMMEDIATE ATTENTION

SD F RT1603 SEMSR: RECEIVE A SUSPEND ATTENTIONSD F RT1604 SEMSR: RECEIVE A CANCEL ATTENTIONSD F RT1605 SEMSR: OPCODE VALUE IS xxSD F RT1606 SEMSR: INT_TYPE,INT_VALUE ARE xxxxxxSD F RT1607 SEMSR: ABNORMAL TERMINATION OF SESSION. VALUE xxxx

CO F RT1701 UNABLE TO ACCESS WKS PARAMETERCO F RT1702 UNABLE TO ACCESS MGI PARAMETERCO F RT1703 MGI_F15MGID ERRORCO F RT1704 MGI_L08JNUMB GREATER THEN MAXIMUM VALUE FOR TELECOM.CO F RT1705 ACCEPT WHILE INIT IS NOT RUNNING.

CO F RT1706 EACONN: H_SSMGET FAILED.CO F RT1707 ACCEPT CALLED FOR RDTE AND MAILBOX NOT CREATED IN DICTIONARY.CO F RT1708 EACONN: PROTOCOL ERROR,ADDRESSING RECORD NOT FOUND IN ILCAL CONNECTIONCO F RT1709 EACONN: PROTOCOL ERROR,CONNECTION RECORD NOT FOUND IN ILCAL CONNECTIONCO F RT1710 EACONN: PROTOCOL ERROR,PRESENTATION CONTROL RECORD NOT FOUND IN ILCALCO F RT1711 EACONN: PROTOCOL ERROR,MESSAGE GROUP RECORD NOT FOUND IN ILCAL CONNECTIONCO F RT1712 EACONN: ALLOCATION IF BLOCKING AREA (H_SGCR) FAILED.CO F RT1713 EACONN: H_FN_BUILD FAILED.CO F RT1714 EACONN: ALLOCATING ENTRY FOR MCSEM FAILED.CO F RT1715 UNABLE TO ACCESS TERMINAL IDENTIFICATION (MGI_P04AREA).

CO F RT1716 UNABLE TO ACCESS TO USER INFORMATION FIELD (MGI_P04AREA).CO F RT1717 EACONN: UNKNOWN REASON.SY F RT1801 ESRVR CANNOT DELETE THE TIMER.SY F RT1802 ESRVR CANNOT DELETE THE SEMAPHORE.UF F RT1805 PARAMETERS ERROR IN RECEIVED DAP.


47 A2 14UC Rev05 F-13

PR F RT1901 EAUTMS PROTOCOL ERROR: UNKNOWN RECORD TYPEPR F RT1902 EAUTMS: PROTOCOL ERRORPR F RT1903 EAUTMS: PROTOCOL ERROR, ACK HASN'T TYPE 1 AHEADPR F RT1904 PROTOCOL ERROR DETECTED BY SERVERUF F RT1905 SERVAUTOMAT: MISSING RFA SLFICB SECTIONS

CK F RT2001 CKM_INTERVAL OR ACK INTERVAL NOT GIVEN.CK F RT2002 H_RFA_ECKM: LACK OF MANDATORY PARAMETERCK F RT2003 REMOTE FILE IS NOT YET OPEN.CK F RT2004 CKM MANAGEMENT ERROR.CK F RT2005 H_RFA_ESYNC: SET AND WAIT PARAMETER ARE EXCLUSIVE

CK F RT2006 ACK_RECORD_NUMBER > LAST_RECORD_SENT.CK F RT2007 H_RFA_ESYNC: RECEIVED AN ACK BIGGER AS LAST CKM SENTCK F RT2008 H_RFA_ESYNC: OPTION WAIT ALTHOUGH ACK INTERVAL IS NULLCK F RT2009 CKM PRIMITIVE CALL ERROR.CK F RT2010 CALL FROM SERVER INSTEAD REQUESTOR.

CK F RT2011 H_RFA_ECKM: ERROR DURING SENDCK F RT2012 H_RFA_ESYNC: RECEIVED AN ACK OUT OF SEQUENCE. LOOP = 1UF F RT2101 H_RFA_EDSAC: TOO MUCH WARNING IN AN ACK.SOME INFORMATION MAY BE LOSTUF F RT2102 H_RFA_EDSAC: WRONG ACK RECORD STRUCTURE ---> structureCO F RT2201 UFT SERVER CANNOT BE STARTED: ENABLE TO CREATE A JOB MANAGEMENT TABLE

CO F RT2202 UFT SERVER CANNOT BE STARTEDCO F RT2203 UFT SERVER CANNOT BE STARTED: THERE ARE TOO MANY PROCESSESCO F RT2204 UFT SERVER CANNOT BE STARTED: THE TELECOM CLASS IS NOT STARTEDCO F RT2205 UFT SERVER CANNOT BE STARTED: TOO MANY INTERACTIVE AND SERVICE JOBSCO F RT2206 UFT SERVER CANNOT BE STARTED: USER MEMORY OVERLOADED.

CO F RT2207 UFT SERVER CANNOT BE STARTED: CLASS OVERLOADED.AC F RT2208 EWMGT, ACTIVE UFT WORKSTATION: ALREADY ACTIVEAC F RT2209 EWMGT, ACTIVE UFT WORKSTATION: IS DEACTIVATINGAC F RT2210 EWSMGT, ACTIVE UFT WORKSTATION: ABNORMAL RC FROM H_SMPLCR, H_SSMGET, DICTIONNARY, MUX, SGSIZE OR SGCREATEAC F RT2211 EWSMGT, ACTIVE UFT WORKSTATION: CHECK

AC F RT2212 EWSMGT, ACTIVE UFT WORKSTATION: EXCEPTION DURING ACCESS TO WKS PARAMETERAC F RT2213 EWSMGT, ACTIVE UFT WORKSTATION: ARGERRAC F RT2214 EWSMGT, DEACTIVE UFT WORKSTATION: WORKSTATION NOT CREATEDAC F RT2215 EWSMGT, DEACTIVE UFT WORKSTATION: SESSION STILL ACTIVE FOR THIS MAILBOX OR LINKED TO THE WORKSTATIONAC F RT2216 EWSMGT, DEACTIVE UFT WORKSTATION: CHECK

AC F RT2217 EWSMGT, DEACTIVE UFT WORKSTATION: WRONG WSF15IDENTAC F RT2218 EWSMGT, DEACTIVE UFT WORKSTATION: ARGERRAC F RT2219 H_GSYSTI ON LOCAL SITE FAILEDAC F RT2301 EWSMGT, ACTIVE REQUESTOR MAILBOX: ALREADY ACTIVEAC F RT2302 EWSMGT, ACTIVE REQUESTOR MAILBOX: IS DEACTIVATING

DJP User's Guide

F-14 47 A2 14UC Rev05

AC F RT2303 EWSMGT, ACTIVE REQUESTOR MAILBOX: ABNORMAL RC FROM H_SMPLCR, H_SSMGET, DICTIONARY, MUX, SGSIZE, OR SGCREATEAC F RT2304 EWSMGT, ACTIVE REQUESTOR MAILBOX: CHECKAC F RT2305 EWSMGT, ACTIVE REQUESTOR MAILBOX: EXCEPTION DURING ACCESS TO MBX PARAMETERAC F RT2306 EWSMGT, ACTIVE REQUESTOR MAILBOX: WKS NOT CREATEDAC F RT2307 EWSMGT, ACTIVE REQUESTOR MAILBOX: EXCEPTION DURING ACCESS TO WKSTABLE

AC F RT2308 EWSMGT, ACTIVE REQUESTOR MAILBOX: WKS NOT ACTIVEAC F RT2309 EWSMGT, ACTIVE REQUESTOR MAILBOX: MBX ALREADY ACTIVEAC F RT2310 EWSMGT, ACTIVE REQUESTOR MAILBOX: ARGERRAC F RT2401 EWSMGT, ACTIVE REQUESTOR MPD: CHECKAC F RT2402 EWSMGT, ACTIVE REQUESTOR MPD: WORKSTATION NOT CREATED

AC F RT2403 EWSMGT, ACTIVE REQUESTOR MPD: EXCEPTION DURING ACCESS TO WKSTABLEAC F RT2404 EWSMGT, ACTIVE REQUESTOR MPD: WKS NOT ACTIVEAC F RT2405 EWSMGT, ACTIVE REQUESTOR MPD: ARGERRAC F RT2501 EWSMGT, ACTIVE SERVER MAILBOX: ALREADY ACTIVEAC F RT2502 EWSMGT, ACTIVE SERVER MAILBOX: IS DEACTIVATING

AC F RT2503 EWSMGT, ACTIVE SERVER MAILBOX: ABNORMAL RC FROM H_SMPLCR, H_SSMGET, DICTIONNARY, MUX, SGSIZE OR SGCREATEAC F RT2504 EWSMGT, ACTIVE SERVER MAILBOX: CHECKAC F RT2505 EWSMGT, ACTIVE SERVER MAILBOX: EXCEPTION DURING ACCESS TO MBX PARAMETERAC F RT2506 EWSMGT, ACTIVE SERVER MAILBOX: WKS NOT CREATEDAC F RT2507 EWSMGT, ACTIVE SERVER: EXCEPTION DURING ACCESS TO WKSTABLE

AC F RT2508 EWSMGT, ACTIVE SERVER MAILBOX: WKS NOT ACTIVEAC F RT2509 EWSMGT, ACTIVE SERVER MAILBOX: MBX ALREADY ACTIVEAC F RT2510 EWSMGT, ACTIVE SERVER MAILBOX: ARGERRAC F RT2601 EWSMGT, ACTIVE SERVER MPD: CHECKAC F RT2602 EWSMGT, ACTIVE SERVER MPD: WORKSTATION NOT CREATED

AC F RT2603 EWSMGT, ACTIVE SERVER MPD: EXCEPTION DURING ACCESS TO WKSTABLEAC F RT2604 EWSMGT, ACTIVE SERVER MPD: WKS NOT ACTIVEAC F RT2605 EWSMGT, ACTIVE SERVER MPD: ARGERRAC F RT2701 EWSMGT, DEACTIVE REQUESTOR MAILBOX: NOT ACTIVEAC F RT2702 EWSMGT, DEACTIVE REQUESTOR MAILBOX: SESSION STILL ACTIVE

AC F RT2703 EWSMGT, DEACTIVE REQUESTOR MAILBOX: CHECKAC F RT2704 EWSMGT, DEACTIVE REQUESTOR MAILBOX: WRONG WSF15IDENTAC F RT2705 EWSMGT, DEACTIVE REQUESTOR MAILBOX: MAILBOX NOT CREATEDAC F RT2706 EWSMGT, DEACTIVE REQUESTOR MAILBOX: WRONG MBXF15IDENTAC F RT2707 EWSMGT, DEACTIVE REQUESTOR MAILBOX: MAILBOX DOES NOT BELONG TO CALLER S WORKSTATIONAC F RT2708 EWSMGT, DEATIVE REQUESTOR MAILBOX: ARGERRAC F RT2801 EWSMGT, DEACTIVE SERVER MAILBOX: NOT ACTIVEAC F RT2802 EWSMGT, DEACTIVE SERVER MAILBOX: SESSION STILL ACTIVEAC F RT2803 EWSMGT, DEACTIVE SERVER MAILBOX: CHECKAC F RT2804 EWSMGT, DEACTIVE SERVER MAILBOX: WRONG WSF15IDENT


47 A2 14UC Rev05 F-15

AC F RT2805 EWSMGT, DEACTIVE SERVER MAILBOX: MAILBOX NOT CREATEDAC F RT2806 EWSMGT, DEACTIVE SERVER MAILBOX: WRONG MBXF15IDENTAC F RT2807 EWSMGT, DEACTIVE SERVER MAILBOX: MAILBOX DOES NOT BELONG TO CALLER S WORKSTATIONAC F RT2808 EWSMGT, DEACTIVE SERVER MAILBOX: ARGERRAS F RT2901 ccccccc: THE PARAMETER INDEX FILE DESCRIPTION IS NOT$ SUPPORTED.

AS F RT2902 ccccccc: CONFLICT RECEIVED FROM DYNAMIC FILE ASSIGN. GR4AS F RT2903 ccccccc: "INTERNAL FILE NAME ALREADY ASSIGNED" RECEIVED FROM DYNAMIC FILE ASSIGN. GR4AS F RT2904 ccccccc: ALREADY OPEN RECEIVED FROM DYNAMIC FILE cccccc. GR4AS F RT2905 ccccccc: FILE BUSY RECEIVED FROM DYNAMIC FILE cccccc. GR4AS F RT2906 ccccccc: UNEXPECTED RETURN CODE FROM DYNAMIC FILE cccccc. GR4

AS F RT2907 ccccccc: ACCESS RIGHT VIOLATION RECEIVED FROM DYNAMIC FILE cccccc. GR4AS F RT2908 UNKNOWN OPTIONAS F RT2909 ccccccc: SUBFILE NAME NOT PROVIDEDUF F RT3001 ccccccc: THE PARAMETER CATALOG FILE IN CR RECORD IS NOT SUPPORTEDCR F RT3002 BAD OPTION OF CREATE. VALUE= cccc

CR F RT3003 INVALID PARAMETER OF CREATE. VALUE= cccccAS F RT3004 FILE DESCRIPTION ERRORS IN ccccccAS F RT3005 UNKNOWN OPTION IN cccccc. VALUE= cccccRD F RT3006 USER ERROR: MUST GIVE LIST OF MEDIA OR RESIDENT OPTIONDC F RT3008 ccccccc: ERROR WITH DEALLOC.GR4

CR F RT3009 ccccccc: ERROR, FILE ALREADY EXISTS.GR4CR F RT3010 FILE ALREADY EXISTED.A NEW ONE HAS BEEN CREATED. GR4CR F RT3011 ccccccc: FILE ALREADY EXISTED. GR4CR F RT3012 ccccccc: INSUFFICIENT SPACE ON MEDIA. GR4CR F RT3013 ccccccc: RECORD SIZE NOT SPECIFIED. GR4

CR F RT3014 FILE HAS NOT BEEN CREATED.GR4CR F RT3015 ERROR WITH SEND OF CR RECORDCR F RT3016 ccccccc: ERROR IN ASSIGN DURING THE RESEARCH OF THE MEDIA LIST.CR F RT3017 ccccccc: ERROR IN RFLDEF DURING THE RESEARCH OF THE MEDIA LIST.CR F RT3018 ccccccc: ERROR IN RTVOLID DURING THE RESEARCH OF THE MEDIA LIST.

CR F RT3019 ccccccc: ERROR IN DEASSIGN DURING THE RESEARCH OF THE MEDIA LIST.DC I RT3101 ccccccc: THE FILE HAS BEEN DELETED.DC I RT3102 ccccccc: FILE HAS NOT BEEN DELETED BECAUSE IT DOES NOT EXIST.GR4CR I RT3103 AUTOMATIC CREATION ON TAPE FOR UNCAT FILE.CR I RT3104 FILE HAS BEEN CREATED.CR I RT3105 A NEW FILE WILL BE CREATED BECAUSE IT DID NOT EXIST. GR4DA I RT3106 NUMBER OF TAPE MARKS: nnnDA I RT3107 NUMBER OF TRANSFERRED RECORDS: nnnRS I RT3108 NORMAL RESTART COMPLETEDRS I RT3109 PARTIALLY RESTART CAN BE PERFORMED

DJP User's Guide

F-16 47 A2 14UC Rev05

DA F RT3110 cccccccc: xxxxxxxxxx PRIMITIVE NOT DONE. GR4RN I RT3111 THE FILE HAS BEEN MODIFIEDSD I RT3112 RECEIVE INTERRUPT ON SEND cccccDA F RT3201 VOLUME LIMIT. GR4DA F RT3202 RECORD > MAXIMUM RECORD LENGTH. GR4

DA F RT3203 DUPLICATE KEY ON RECORD. GR4DA F RT3204 FILE TOO SHORT TO CONTAIN ALL THE RECORDS. GR4DA F RT3205 ADDRESS OUT OF FILE. GR4DA F RT3206 ABNORMAL PUT. GR4DA F RT3207 RECORDS SEQUENCE ERROR. GR4

DA F RT3208 ABNORMAL GET. GR4DA F RT3209 NUMBER OF SPLIT OR SYNONYM RECORDS: xxxxDA F RT3210 NUMBER OF SKIPPED RECORDS: xxxxOP F RT3301 H_RFA_ESOPN: INVALID IFN PROVIDEDOP F RT3302 H_RFA_ESOPN: MOUNT OPTION SHOULD BE ALL. GR4

OP F RT3303 H_RFA_ESOPN: BUFFER NOT AVAILABLE. GR4OP F RT3304 H_RFA_ESOPN: ILLEGAL SHARING OPTION. GR4OP F RT3305 H_RFA_ESOPN: UNCOMPATIBLE PMD AGAINST SHARING. GR4OP F RT3306 H_RFA_ESOPN: PMD OUTPUT AND FILE IS ALREADY OPEN BY CONCURRENT PROCESS. GR4OP F RT3307 H_RFA_ESOPN: UNAUTHORIZED CONCURRENT ACCESS. GR4

OP F RT3308 H_RFA_ESOPN: WRONG ORGANISATION. GR4OP F RT3309 H_RFA_ESOPN: FILE AREADY OPEN. GR4OP F RT3310 H_RFA_ESOPN: IFN NOT ASSIGNED. GR4OP F RT3311 H_RFA_ESOPN: FILE STILL VALID: SCRATCH NOT PERMITTED. GR4OP F RT3312 H_RFA_ESOPN: EFN NOT FOUND. GR4

OP F RT3313 H_RFA_ESOPN: SUBFILE NOT EXISTING. GR4OP F RT3314 H_RFA_ESOPN: CONFLICTING PARAMETERS. GR4OP F RT3315 H_RFA_ESOPN: ACCESS RIGTH VIOLATION .GR4OP F RT3316 H_RFA_ESOPN: UNEXPECTED RETURN CODE FROM H_OPEN. GR4SY F RT3401 ABNORMAL RETURN CODE FROM H_CLOSE OF LOCAL FILE. GR4

RS F RT3501 REQUESTOR: RETURN VOLUME ID.RS F RT3502 RESTART, RC=WRONGPMD, PMD=APPEND REJECTED WITH RESTART OPTIONRS F RT3503 RESTART, RC=WRONGPMD, PMD=INPUT AND RESTART= -1 REJECTEDRS F RT3504 RESTART: OPEN OF THE LOCAL FILE INPUT WITH RESTARTRS F RT3505 RESTART: OPEN OF THE LOCAL FILE OUTPUT WITH RESTART

RS F RT3506 RESTART CANNOT BE PERFORMEDRS F RT3507 FILE PROBABLY EMPTY OR IN UNSTABLE STATERS F RT3508 OPEN UPDATE OR APPEND AFTER CLOSERS F RT3509 RFLDEF IN RESTARTRS F RT3511 CONTROL MEMORY WORKING SET EXCEEDED

RS F RT3512 MAXIMUM SIZE EXCEEDEDRS F RT3513 USER MEMORY SATURATEDRS F RT3514 BACKING STORE SATURATEDRS F RT3515 NO MORE VACANT ENTRYRS F RT3516 SPECIFIED SIZE IS NEGATIVE


47 A2 14UC Rev05 F-17

RS F RT3517 SYSTEM BACKING STORE WORKING SET OVERFLOWUF W RT3601 THE PARAMETER CATALOG FILE IN DL RECORD IS NOT SUPPORTEDDL F RT3602 INVALID PARAMETER OF DELETE. VALUE= cccccDL F RT3603 PARAMETER ERRORSDL F RT3607 INSUFFICIENT ACCESS PERMISSION

DL W RT3608 FILE IS BUSYDL F RT3609 FATAL I/O ERRORRN W RT3701 THE PARAMETER CATALOG FILE IN RN RECORD IS NOT SUPPORTED. GR4RN F RT3702 INVALID PARAMETER OF RENAME. GR4RN F RT3703 PARAMETERS ERRORS. GR4

RN F RT3705 FILE CANNOT BE ASSIGNED BEFORE TO RENAME IT. GR4RN W RT3706 FILE HAS NOT BEEN MODIFIED BECAUSE IT DOES NOT EXIST. GR4RN F RT3707 ERROR WITH FILMODIF. GR4RN F RT3708 FILE CANNOT BE DEASSIGNED AFTER TO HAVE BEEN RENAMEDUF I RT3801 ********** UFT OPTIONS: CREATE= aaaaaaa, compact:nocompact, binary:no-binary, append:no-append

FD I RT3802 ********** OUTPUT FILE DEFINITION IS:FD I RT3803 ********** FILEFORM= fileform, FILEORG= fileorg, CISIZE/BLOCKSIZE= aaaaaaaFD I RT3804 ********** RECSIZE= aaaaa, RECFORM= aaa, LIBTYPE= aaFA I RT3805 ********** OUTPUT FILE ALLOCATION IS:FA I RT3806 ********** UNIT= aaaaaaaa, SIZE= aaaaa, INCRSIZE= aaaaa, MAXSIZE= aaaaa

AS I RT3807 ********** ASKED ASSIGNED PARAMETERS:AS I RT3808 ********** RESTART NEGOCIATION AT RECORD: aaaaaaaaaaRS I RT3809 ********** RESTART EXECUTED AT RECORD: record, RECORDS ADDED: number RECORDS IN OUTFILE: numberDL I RT3810 ********** DELETED FILE NAME: EFN file-nameCR F RT3811 cccccccc NOT POSSIBLE: MAXIMUM NUMBER OF EXTENTS REACHED.

AS I RT3812 ********** LOCAL ACCESS= aaaaaaAS I RT3813 ********** OLD FILE NAME: file-nameAS I RT3814 ********** NEW FILE NAME: file-nameAS I RT3815 ********** INFILE: infile-definitionAS I RT3816 ********** OUTFILE: outfile-definition

FD I RT3817 ERROR ON USER LABEL NUMBER: aaFD I RT3818 ********** REMOTE SITE NAME: siteUF I RT3819 ********** ccccccc FUNCTION EXECUTED.FD I RT3820 ********** KEYLOC= cccccccc, KEYSIZE= ccccccccFD I RT3821 ********** EXPIRATION DATE: YEAR= cc MONTH= cc DAY= cc

FD I RT3822 ********** RECSIZE= cccccccccc, RECFORM= ccccccccCR I RT3823 ********** UNIT= cccccccc , SIZE= cc, INCRSIZE= ccccccccccXX X RT3838 message

DJP User's Guide

F-18 47 A2 14UC Rev05

F.1.2.2 Details on RFA Messages

All RT messages are self-explanatory whatever the severity. Where the message is fataland user intervention is required, the reason is clearly given. In all cases, if userintervention is unsuccessful, call the Service Center and hand in the report.

AC Remote file access initialization at start telecom time. These messages appear onthe main console because there is still no transfer started. These fatal messagesappear at the initialization time of RFA. UFT has not been initialized. There areproblems in activating or deactivating the workstation, the mailbox or MPD ofrequestor or server.

AS Assign remote file. These are often user errors in the step assigning the file.

CK Check mark errors. These are system errors such as sending output to a DPS6.- RT2001 and RT2002: missing system parameters. Call the Service Center and

transmit the report.- RT2003: The remote file is not open due to a system error. Call the Service

Center and transmit the report.

CO Connect time errors. These are errors in:- catalog management- network generation- a crash on the Datanet- no communications session on the remote site.

Before starting a file transfer, UFT needs a connection between the two sites.- RT103 and RT104: Inform the user of the relationship between the Requestor

and the Server process and even with the JON or FON of the requestor requestif it was a UFT interactive request.

- RT201 through RT431: The connection is not possible for the present time.- RT221: gives the reason of the difficulty in the connection with the code

0235xxxx:02: asking a connection35: rejectedxxxx: connection reject in session/transport or due to PID (ISO-DSA Datanet) orJANUS (SNA-DSA Datanet) if connecting to an ISO or IBM machine.


47 A2 14UC Rev05 F-19

CR Create function messages.- RT621: File creation cannot be called from a user procedure.- RT627: The remote site does not support the create function; preallocate the

file on the other site, then request a transfer omitting CREATE.- RT3002 through RT3005: UFT protocol errors in the create control record.- RT3006: Specify the list of media since the file is UNCAT or RESIDENT.- RT3008: Deallocate the file and replace it; check the assign parameters and the

state of the file before restarting the file transfer.- RT3009: CREATE=NEW cannot be executed since the file already exists;

restart UFT with another file or omit CREATE=NEW.- RT3011: The file already existed and is not replaced by CREATE=KEEP.- RT3012: The media does not have enough space to create the file; restart the

file transfer on another media or delete files on the same media.- RT3013: The record size is mandatory and comes from the input file image; if

absent such as UNIX, specify it in the request.- RT3014: The file has not been created because of a failure previously reported.- RT3015: The create record cannot be sent; resubmit the file transfer.- RT3016 through RT3019: Error from a system procedure during file creation.- RT3101 and RT3102: The file has been deleted before creating the new one by

CREATE=REPLACE.- RT3103: A file will be created with the input image and any overriding user-

defined parameters.- RT3104: The file has been created. This is an information message.- RT3105: The file will be created with CREATE=REPLACE.

DA Messages about the data transfer on the server site.- RT3201 through RT3210: explain the problem of the data transfer.- RT3202: The maximum record size of the input file is bigger than the output file

maximum record size; if variable length, a record is bigger than the maximumoutfile record size.

- RT3203: For an indexed outfile, the input file may have two records with thesame key and is not accepted by the DPS 7/7000.

- RT3204: The output file is not large enough to receive all the records.- RT3207: The record sequence is not correct.- RT3206 and RT3208: Errors have occurred on the output or the input file.

DI Disconnect messages.- RT126: an information trace message for maintenance.- RT127: a normal disconnection for trace.- RT128: abnormal disconnection probably due to a bad transfer or a previous

disconnection; the first fatal message is the origin of the problem.- RT129: UFT asks for a premature disconnection either following a bad transfer

or because normal disconnexion is not possible.- RT130: displays session interface- RT804: Error in close message group at the end of UFT; this does not concern

the user if there is no error in UFT itself.RT805: UFT has terminated the session due to a protocol error. This isabnormal because the site does not have the turn.

DJP User's Guide

F-20 47 A2 14UC Rev05

DL Delete function messages.- RT622: Delete file cannot be called from a user procedure.- RT738: Delete file is requested but was not negotiated at the beginning of the

protocol dialog; this is a system error on the executing site.- RT3006: This is an assign error because the media is not correctly described; if

the file is uncat, specify the list of media.- RT3008: The file cannot be deallocated; see the return code and correct the

problem before reissuing the command.- RT3101 through RT3110: Confirmation that the file has been deleted.- RT3102: The file to be deleted does not exist.- RT3602 and RT3603: There is an invalid parameter for the delete function sent

to the other site.- RT3607: the user does not have access rights to the file to execute the delete

command.- RT3608: The file is busy; it cannot be deleted.- RT3609: An I/O error has occurred on the file to be deleted; it cannot be

deleted.- RT3810: This is information for retaining the name of the deleted file.

FA File allocation messages.RT3805 and RT3806: Message to display the allocation parameters of the created

file. They may be different from the asked allocationparameters because the allocation unit to allocate cannot bethe same and some rounded values may be necessary fortracks and labels.

FD File definition messages.Errors can occur when the file transfer processes the definition of the file of theserver site. Both requestor and server sites dialog on the processing of thisdefinition, namely:

- on the requestor site if the file on server site is to be created- or on the server site if the file is an input file serving as is the model.

RT602 through RT607: As well the receiving site of the definition file informations candetect some wrong values for these definition. The RT609 ->RT612 messages are in this category.

RT613 through RT619: show errors detected by system primitives when file transferprocesses the file definition. Check the output file definitionvalues if file has been created.

GI Get information messages.The DPS 7/7000 UFT received a request about a get information (GI protocol record)which it does not support.

OP Remote open messages.The opening of the local file on the server site may produce some errors which are listedin messages RT3301 to RT3316.RT3315: The user does not have the right to access the file.RT3312: The file does not exist on this site.


47 A2 14UC Rev05 F-21

PR Protocol errors or protocol trace messages.RT701 through RT718RT1901 through RT1904: System errors have violated DSA62 UFT protocol; they may

be the consequence of a previous reported error. Correct thepreceding error.

RT1527: The demand turn conforms to V2A protocol; check the UFTversion on the other site.

RN Rename messages.These messages are displayed whren an error occurs while rename is processing.RT623: The rename function cannot be called from a user procedure.RT3006: Specify the media list if the file is UNCAT; otherwise, the file

must be cataloged or RESIDENT.RT3701: The catalog name is not supported by GCOS 7 UFT; use the

site catalog and the autoattach catalogs.RT3702: Parameter of rename conforms to DSA UFT protocol; check

the requestor site UFT.RT3703: Check the file description given by user on the requestor site.RT3705: The file to be renamed cannot be assigned; check the

deassign definition given and whether the file can beaccessed on the server site before reissuing the renamecommand.

RT3706: The file to be renamed does not exist.RT3707: The file cannot be renamed; consult the return code to

correct the error.RT3708: The renamed file cannot be deassigned.

RS Restart messages.RT3501: The return volume id system service failed on the local file.

The return code shows the system error and what appropriateaction to take.

RT3502: The append processing mode cannot be used with restart.Restart requires the record relative address of the filewhereas APPEND starts at the previous end of the file. Theinput file cannot be positioned from the same reference. Thestart of input and output files are not the same.

RT3503: The output file has not been positioned. This is a malfunctionof UFT managing the output file.

RT3504: Open on the local input file has failed; see the return-code forthe appropriate action.

RT3505: Open on the local output file has failed; see the return-codefor the appropriate action.

RT3506: The output file cannot be positioned because the system getprimitive has failed; see the return-code for the appropriateaction.

RT3507: Same as for RT3506 but here the failure has occured on thefirst record of the file.

RT3508: Reopening of the file in update mode to begin the file transferafter positioning has failed; see the return-code for theappropriate action.

RT3509: The retrieve file definition of the local file has failed; see thereturn-code for the appropriate action.

RT3511: Creating the type2 segment for scanning the input file hasfailed

RT3517: See the system return-code for the appropriate action.

DJP User's Guide

F-22 47 A2 14UC Rev05

RV Receive messages.RT1202 through RT1309: Communications modules have malfunctioned causing fatal

errors. Once these protocol errors are located and corrected,the request can be resubmitted.

SD Send messages.UFT uses communications session primitives to send and receive records.RT120: Warning. The input file is empty.RT725: A send system protocol error has occurred.RT726: Reports attention sent to the other site on erroneous length

due to a malfunction of UFT. Call the Service Center.RT727: Compaction error on send has occurred and has been

detected at decompaction.RT728: A system error has occurred; UFT cannot call a SM

procedure since it cannot get the procedure address.RT730: Timeout on semaphore for PUT or SEND; UFT restarts

automatically.RT1243 through RT1263: A system error has occurred on the session.RT1310 and RT1311: A system error has occurred due to unexpected events on

the session.RT1312 through RT1314: The receiving file on the other site has stopped receiving the

file transfer since it is too small. This error appears after thissite has sent a SDT NACK.

RT1402, RT1405 through RT1418, and RT1502 through RT1607:Unexpected session events have occurred.

SS Session messages.The session interface reports to UFT all communications events affecting the file transfer.SD, RV, SR, CO and DI messages are in this category.

TR Trace messages.These messages appear in the JOR or on the console when TRACE is specified in theUFT command or when the operator command STTR UFT is issued. These messagesare useful where UFT fails. The trace gives the interface between the session and theUFT dialog concerning the data phase transfer.

UF UFT errors messages.These are errors of UFT management. They are often inconsistencies in structures orprocedures calls.• RT501, RT504, RT1006, RT2009, RT624, RT624, RT722 and RT601: Incorrect UFT

management due to misuse of UFT.• RT719, RT802, RT1003, RT1009 and RT1905: Main UFT structure missing.• RT502 and RT505: A protocol error on the number of protocols has occurred. UFT

cannot execute.• RT503: A protocol error on protocol attrbutes has occurred. UFT cannot execute.• RT1605: The protocol definition is not suitable.• RT507 through RT510: The applications EXECUTE JOB, FILE TRANSFER, INPUT

READER, OUTPUT WRITER are not allowed in the site catalog.• RT718, RT720 and RT721: Incorrect processing has been detected.• RT723: The communications session is not active. Issue the STSVR operator

command.• RT729 and RT730: Timeout due to the other site not answering to the previous

command or no longer sending data.• RT801 and RT803: Incorrect processing has been detected. The communications

request identifier has been lost.• RT807 and RT808: System errors have occurred on termination of UFT when clearing

the system resources used for the transfer. This does not affect the user transfer.


47 A2 14UC Rev05 F-23

• RT904: Reason of error received from the other site does not conform to V2A protocoldefinition; it is therefore not available to the user.

• RT1002, RT1004, RT1005 and RT1008: A system failure has occurred when gettingthe address of a UFT module. Call the Service Center and transmit the JOR andconsole report.

• RT1001 and RT1007: Data transfer cannot be started. Restart the transfer withoutcreate if this option was used before, otherwise call the Service Center.

• RT1227: The file transfer with another site does not comply with V2A protocol.• RT2101: An overflow has occurred in the acknowledgement record.• RT2102: Incorrect structure of the acknowledgement record.• RT2908: Unknown assign option received from other site.• RT3001: The parameter catalog is not supported by DPS 7/7000 UFT.• RT3601: The DPS 7/7000 supports the files in UNCAT and site.catalog or autoattach

catalog files.• RT2004 through RT2007: System management errors have occurred.• RT2006 through RT2008, and RT2010: System management error.• RT2011: A send error has occurred. See the send error previously displayed.• RT2012: Incorrect management of CKM ACK between the two sites.

F.1.3 Messages Coming from Server Site

F.1.3.1 Format and Explanation of Messages

These messages must have a structured format which gives:• the reason for the error• the severity (warning, recoverable or fatal)• the class (file transfer protocol, session control, file/data management, system, higher

level application protocol)• following the severity and the class, the message may be accompanied by a diagnostic

supplement.

The reason code number, severity and class are translated into characters strings for useby the RFA which displays them in messages RT901 and RT905.

DJP User's Guide

F-24 47 A2 14UC Rev05

Common errors reported in messages follow:

Code Sev Class DiagSupp

Explanation of Error

20 1 0 2 Missing parameter or value21 1 0 2 Invalid parameter value22 1 0 2 Parameter value incorrect in context23 0 0 2 Parameter duplicated (Last value retained)

24 0 0 2 Unknown parameter (skipped)25 1 0 2 Parameter out of sequence26 1 0 2 Unsupported parameter value30 2 3 - Insufficient access permission

31 2 3 - File does not exist32 1 3 - File busy33 1 3 - Device not currently available34 2 3 - Invalid file identification syntax

40 2 3 1 Fatal I/O error100 2 6 4 System specific error1000 2 3 - Insufficient characteristics1001 2 3 - Subfile name not provided

1002 1 4 - Sufficient memory not currently available1200 1 0 - Some negociation failed1201 2 3 - File cannot be opened1202 2 3 - Subfile not existing

1400 2 2 1 Decompression error1401 2 2 1 Invalid character in code translation1420 2 6 - Voluntary abort1421 2 0 - Too many non acknowledged checkpoints

1430 1 1 Transmission error1440 2 3 1 File space exhausted1450 2 0 1 Record or CI > max size1451 2 0 1 Illegal file record type

1452 2 0 1 Record number sequence error1453 2 3 1 Key sequence error1454 2 3 1 Illegal duplicate key value1800 0 3 - File cannot be properly closed

1801 0 3 - Rewind failed2600 2 3 - Restart key/address not supported2800 0 3 - File already existed (Warning)2801 2 3 - File already existed (Rejection)

2802 2 3 - Insufficient space on media2803 2 3 - Insufficient characteristics2804 2 3 - Record size not specified3000 0 3 - File does not exist (Warning)

Explanations of headings in the table appear overleaf.


47 A2 14UC Rev05 F-25

Column 1: reason code number of DSA protocol

Column 2: severity 0 Warning 1 Recoverable 2 Fatal

Column 3: class 0 FTP (File transfer) 1 session control 2 presentation control 3 file/data management 4 system 5 higher level application protocol 6 other

Column 4: diagnostic supplement number (1 or 2 or 4)

• Type 1:- Reason Codes: 40, 1400, 1401, 1430, 1440, 1450 through 1454- Purpose: Defines the record in error, except in two cases where it defines the last

successful record (40 with error on a read and 1430 with error on receive, sincethere is too little information on the erroneous record)

• Type 2:- Reason Codes: 20 through 26- Purpose: Defines the parameter in error. For reason code 20, the value field is

either absent (truncated) or unsignifiant. For reason code 23, the value fieldcontains the retained value for the duplicated parameter.

• Type 4:- Reason Codes: 100- Purpose: Conveys a system specific error description. To be used only when the

error cannot be described by a standard reason code.

The DPS 7/7000 uses when possible, standard reason codes of the file transfer protocoleven if it does not exactly describe the error since the file transfer can be sent frommachines other than the DPS 7/7000. For detailed information, the DPS 7/7000 sends afurther type 4 error message with a reason code which does not exactly match the errorbut explains it.

F.1.3.2 Type 4 Messages

Type 4 messages are flagged by:

DPS7 UFT FROM RELEASE V6

followed by a a further error message explaining the reason and giving the return-codeissued by the DPS 7/7000 on the server site.

Type 4 error messages treated in this paragraph are headed by a code which is not partof the message, but is meant to inform the user about what procedure was involved whenthe error occurred. The user at the requestor site is informed of the status of the requestexecution by the server site.

DJP User's Guide

F-26 47 A2 14UC Rev05

CODES

SA Select Application ProtocolCR CreateDL DeleteRN RenameAS AssignOP OpenDT Data Transfer

Messages are arranged in alphabetical order of their texts. Following each message,there is an explanation of the error and the corrective action needed to be taken.

Example:

CR ERROR ON DEALLOCATION OF THE REMOTE FILE ON SERVER SITE+- +----| || +-> The first word in the message is after the code|+----> code: does not appear in the message text Create time during which the message was emitted

CR ALREADY OPEN RECEIVED FROM REMOTE FILE ASSIGNMENT ON SERVER SITE.

A system error has occurred.

CR BAD IFN NUMBER FOR THE SERVER SITE FILEA system error has occurred; call the Service Center and transmit the errorreported by the retrieve file definition primitive.

CR BFAS FILE FORMAT CANNOT BE CREATED FOR OTHER FILE ORGANISATIONS THAN LINKED QUEUED

The V6 UFT release only supports LINKED QUEUED and UFAS file formats;modify the file format or file organisation for the file to be created.

SA BILLING NOT FOUND IN THE CATALOGBilling is unknown on the server site; check user rights on the server site catalog touse this application.

OP BUFNAV. BUFFER NOT AVAILABLE FOR THE LOCAL FILE OF THE SERVER SITE.


SA CATALOG ADDRESS NOT VALIDCorrect the catalog user address for the session.

AS DEASSIGN OF THE REMOTE FILE ON SERVER SITE FAILEDThe remote file will be deassigned on job termination.

AS DEFINE REMOTE FILE FAILED ON SERVER SITE.A system error has occurred.

RN DELETE SEGMENT CANNOT BE EXECUTED PROPERLY ON THE SERVER SITE.This segment will be released after the termination of the file transfer.

AS ERROR ON BUILD AND SEND DRF ON SERVER SITE.A system error has occurred.


47 A2 14UC Rev05 F-27

SA ERROR ON CONTROL OF APPLICATION IN SERVER SITE CATALOGConsult the return-code to correct the error; check user access rights in the catalog.

CR ERROR ON DEALLOCATION OF THE REMOTE FILE ON SERVER SITECheck the return-code to correct the error and restart the file transfer.

DL ERROR ON DEALLOCATION OF THE REMOTE FILE ON SERVER SITE. IMPOSSIBLE TO DELETE THE SUBFILE.

Check the state of the file on the server site before resubmitting the request.

CR ERROR ON PREALLOCATION OF THE REMOTE FILE ON SERVER SITECheck the return-code to correct the error and restart the creation.

RN FILE HAS NOT BEEN MODIFIED.Message complement to error; see the previous error.

CR FILEIDX IS ERRONEOUS ON THE REMOTE FILE ON SERVER SITEA system error has occurred; the index for retrieve volume identification is invalid.

OP IFBNASG. THE LOCAL FILE ON THE SERVER SITE HAS NOT BEEN ASSIGNED BEFORE OPEN.


OP IFNERR. THE LOCAL FILE ON THE SERVER SITE HAS NOT BEEN ASSIGNED BEFORE OPEN.


DT INPUT FILE ACCESS METHOD GOT AN ERROR ON THE SERVER SITE WHILE TRANSFERRING THE USER DATA.

Determine from the return-code what appropriate action is to be taken on the serverfile before resubmitting the file transfer with RESTART.

DL MEDIA DESCRIPTION ERROR.Correct the media description when resubmitting the delete request.

RN MEDIA DESCRIPTION ERROR.Correct the media description when resubmitting the rename request.

OP MOUNTERR. MOUNT OPTION SHOULD BE ALL FOR THE LOCAL FILE ON SERVER SITE.

A system error has occurred with indexed files.

AS NOT DONE RETCODE RECEIVED FROM REMOTE FILE RETRIEVE SOURCE DEFINITION ON SERVER SITE.


CR NOT RESIDENT FILE: THE USER MUST GIVE THE MEDIA LISTSpecify the media and resubmit the file transfer request.

DL NOT RESIDENT FILE: THE USER MUST GIVE THE MEDIA LIST.Specify the media list when resubmitting the request.

OP NOTOBS. THE LOCAL FILE OF THE SERVER SITE IS STILL VALID: SCRATCH IS NOT PERMITTED.

The user does have not the right to write to the output file on the server site.

OP NOWAIT. UNAUTORISED CONCURRENT ACCESS ON THE LOCAL FILE OF THE SERVER SITE.

Reissue the request later.

DJP User's Guide

F-28 47 A2 14UC Rev05

CR OPEN RETURN CODE RECEIVED FROM REMOTE FILE ASSIGNMENT ON SERVER SITE.

A system error has occurred; the file on server site can only be opened once.

AS OPEN RETURN CODE RECEIVED FROM REMOTE FILE ASSIGNMENT ON SERVER SITE.


OP OPEN. THE LOCAL FILE ON THE SERVER SITE IS ALREADY OPENED.A system error has occurred.

DT OUTPUT FILE ACCESS METHOD GOT AN ERROR ON THE SERVER SITE WHILE TRANSFERRING THE USER DATA.

Determine from the return-code what appropriate action is to be taken on the serverfile before resubmitting the file transfer with RESTART.

OP OUTVIOL. THE PROCESSING MODE OF THE LOCAL FILE ON THE SERVER SITE IS OUTPUT AND THE FILE IS ALREADY OPEN BY A CONCURRENT PROCESS.

Restart the file transfer later.

OP PMDVIOL. THE PROCEDURE MODE OF THE LOCAL FILE ON THE SERVER SITE IS UNCOMPATIBLE AGAINST THE SHARING.

Check the share options in server catalog and request, and compare them with theattributes for the file given in INFILE or OUTFILE on the remote site. If correct,contact the Service Center.

SA RELATION APPLICATION/PROJECT NOT FOUNDSA RELATION BILLING/PROJECT NOT FOUNDSA RELATION STATION/PROJECT NOT FOUNDSA RELATION USER/PROJECT NOT FOUND

Check the objects in question in the server site catalog.

AS RETCODE CONFLICT RECEIVED FROM THE LOCAL FILE ASSIGNMENT ON SERVER SITE.

Check the assignment parameters and description of INFILE and/or OUTFILEgiven in the request.

CR RETCODE CONFLICT RECEIVED FROM THE REMOTE FILE ASSIGNMENT ON SERVER SITE.

A system error has occurred; the file on server site can only be assigned once.

OP SHCTVIOL. ILLEGAL SHARING OPTION FOR THE LOCAL FILE OF THE SERVER SITE.

Check the share options in the server catalog and request. If correct, contact theService Center.

SA STATION NOT FOUND IN THE CATALOGStation is unknown on the server site; check user rights on the server site catalog touse this application.

CR SYNTAX ERROR IN REMOTE EXTERNAL FILE NAME TO BE CREATED.Modify the syntax and resubmit the file transfer request.

RN THE CREATE SEGMENT TO RECEIVE THE DATAS ON THE SERVER SITE FAILED.

All segements are being used, so reissue the request later.


47 A2 14UC Rev05 F-29

RN THE FILE ON SERVER SITE CANNOT BE OPENED FOR MODIFICATION OF SUBFILE NAME.

Check the file to determine why the file cannot be opened.

CR THE H_RTVLID PRIMITIVE CANNOT ACCESS THE REMOTE SERVER SITE SYS.KNODET

A system error has occurred; call the Service Center and transmit the report of theserver site.

OP THE PMD OF DRF DOES NOT MATCH WITH ACCESS OF ARF.A system error has occurred.

CR THE REMOTE FILE ON THE SERVER SITE IS NOT OPEN.A system error has occurred; call the Service Center and transmit the report.

CR THE RETRIEVE FILE DEFINITION OF THE REMOTE SERVER SITE FAILED.A system error has occurred.

RN THE SUBFILE CANNOT BE PROPERLY CLOSED ON SERVER SITE.Check in the return-code why it cannot be properly closed.

RN THE SUBFILE DATA CANNOT BE READ ON THE SERVER SITE.Check the remote library to determine why the subfile cannot be read.

RN THE SUBFILE NAME CANNOT BE UPDATED IN THE DATA HEADER 101.The subfile of the remote site is not correct because the name of the subfile inwhich the first record of the subfile is written, cannot be updated.

DL UNCAT AND NOT RESIDENT FILE: THE USER MUST GIVE THE MEDIA LIST.Specify the media list when resubmitting the request.

CR UNCAT NOT RESIDENT FILE: THE USER MUST GIVE THE MEDIA LISTSpecify the media and resubmit the file transfer request.

CR UNEXPECTED RETURN CODE RECEIVED FROM REMOTE FILE ASSIGNMENT ON SERVER SITE.

Check the return-code to correct the assignment error before resubmitting the filetransfer request.

AS UNEXPECTED RETURN CODE RECEIVED FROM REMOTE FILE ASSIGNMENT ON SERVER SITE.

Check the return-code to correct the assign error.

CR UNEXPECTED RETURN CODE RECEIVED FROM REMOTE FILE RETURN VOLUME IDENTIFICATION PRIMITIVE

Check the return-code to correct the error and restart the creation.

CR UNEXPECTED RETURN CODE RECEIVED FROM REMOTE FILE DEASSIGN ON SERVER SITE.

Check the return-code to correct the error.

SA USER NOT FOUND IN THE CATALOGUser is unknown on the server site; check user rights on the server site catalog touse this application.

OP WRONGORG. WRONG ORGANISATION FOR THE LOCAL FILE ON THE SERVER SITE.

Correct the server file organization in the request.

DJP User's Guide

F-30 47 A2 14UC Rev05

F.2 OPERATOR MESSAGES

All messages sent to the user, station and MAIN operators are prefixed by <time>. Thesemessages are issued in response to erroneous commands that cannot be executed.

The following list of messages is arranged in alphabetical order according to the fixed textwithin the message. Metalanguage terms such as <cmd-name>, <function>, <request-id>,<fon>, <jon> and <tf-id> which start the message text, are not considered in thealphabetic sequence and are treated as though they are absent.

Letters in bold indicate the order sequence of the message.

CANNOT PERFORM WAIT CONDITION ON REQUEST request-id

Meaning: For EFTR and MDUR commands with the WAIT clause, therequest concerned cannot be chained to the required requestas submitted.

Action: None

request-id COMPLETED nnnn RECORDS TRANSFERRED

Meaning: Issued by the GTP upon completion of a successful filetransfer, specifying the request-id together with the number ofrecords transferred.

Action: None

request-id END OF JOBSET HANDLING

Meaning: Issued by the GTP upon completing a successful job requesttransfer.

Action: None

function: FUNCTIONALITY NOT AVAILABLE: SEE YOUR SYSTEM ADMINISTRATOR

Meaning: The function may be DJP or UFT7. The message resultsfrom an attempt to use a function not purchased for theDPS 7/7000 site concerned. In the case of UFT 7, themessage occurs as a result of using EFTR.

Action: Ask the Bull Systems representative to install the appropriatesoftware.

<tf-id> <ron:index> HELD GTP TERMINATED RC=xxxxxxxx --> siu-name IC# RC-description ON SYSOUT FILE

Meaning: Issued by a GTP for a report-set request, when a systemerror has been encountered during GTP processing

Action: Call the Service Center and transmit the console listing.


47 A2 14UC Rev05 F-31

ILLEGAL ACCESS TO: request-id

Meaning: An attempt has been made to access a request that does notbelong to the user.

Action: None

cmd-name MEANINGLESS

Meaning: CUR, DUR, FUR, HUR, MDUR, or RUR command does notapply and therefore is not executed.

Action: None

request-id MEANINGLESS: NO TIME CONDITION

Meaning: Results from a MDUR command when an attempt has beenmade to suppress non-existent date and time conditions.

Action: None

request-id MEANINGLESS: NO WAIT CONDITION

Meaning: Results from an MDUR command when an attempt has beenmade to suppress a non-existent WAIT condition.

Action: None

request-id MEANINGLESS: REQUEST BEING PROCESSED

Meaning: Results from a MDUR command when the request to bemodified has already been processed by a GTP; therefore, itis too late to be modified.

Action: The request may be placed in HOLD, thus terminating theGTP which will pass to the next request in the queue. Once inHOLD, the request may be modified and then released.

MEANINGLESS: THIRD PARTY PROCESSING NOT YET SUPPORTED

Meaning: Applies to an MDUR request which attempts to modify thevalue of the HOST parameter. For example, if a request issubmitted on HOST A to be executed on HOST B, with thefile located at B, it is forbidden to modify the HOST to C.

Action: None

cmd-name NOT ALLOWED

Meaning: The user is not authorized to issue:- either the FUR command which may only be entered by

the MAIN operator- or the MDDJP command which may only be entered by

the MAIN operator.

Action: None

DJP User's Guide

F-32 47 A2 14UC Rev05

REQUEST request-id CANCELLED RC=xxxxxxxx --> siu-name IC# RC-description> [ FILE = file-description ]

Meaning: Issued by a GTP trying to transfer a JON or FON requestfrom an erroneously named file.

FILE appears only for jobset requests (JON). The erroneousfile name is in either INFILE or OUTFILE.

Action: Reissue the EFTR or EJR command.

REQUEST: { fon | jon } HELD GTP TERMINATED RC=xxxxxxxx --> SIU-name IC# return-code [FILE = file-description ]

Meaning: Issued by a GTP for a job or file transfer request, when asystem error has been encountered during processing. Therequest is placed in HOLD while the GTP proceeds to selectand process the next request.

Action: Call the Service Center and transmit the console listing.

{ fon | jon } TRANSFER STARTED

Meaning: Issued by the GTP starting a request transfer.

Action: None

fon TRANSFER STARTED OCCURRENCE # nnnn

Meaning: Issued by the GTP starting a file transfer, where <nnnn> isthe occurrence number of a repetitive request, namely theenqueuing REPEAT parameter in the EFTR request.

Action: None

UNKNOWN REQUEST: request-id

Meaning: The request is no longer known, or has never been known, tothe system.

Action: Check that the request is among the list of requests entered.

WAIT CONDITION NOT FULFILLED: REQUEST MODIFIED

Meaning: Applies to an MDUR command submitted with a WAITcondition which cannot be satisfied. The request concerned isalready in HOLD.

Action: Display this request by using:DUR request-idto see what modification is necessary to the requestconcerned.


47 A2 14UC Rev05 F-33

WAIT CONDITION NOT FULFILLED: REQUEST MODIFIED AND HELD

Meaning: Applies to an MDUR command submitted with a WAITcondition which cannot be satisfied. The request concerned ismodified and placed in HOLD.

Action: Display this request by using:DUR request-idto see what modification is necessary to the requestconcerned.

WARNING: SEVERAL REQUESTS CONCERNED, USE REQUEST INDEX (JON OR FON)

Meaning: The user has attempted to access a request by its name,where several requests (listed after the message) have allbeen given the same name. The different requestsconcerned are listed after the message.

Action: Use the request index to distinguish between the variousoccurrences of the same request.

DJP User's Guide

F-34 47 A2 14UC Rev05

F.3 LIST OF STATUS CODES

The status is divided into 4 classes represented by decimal digits. The most significantleftmost digit is SEV 4 for value 2 and SEV 3 for value 1. The least significant pair of digits(rightmost) is SEV 0.

The smaller the SEV, the less important the error.

Example

To interpret status code 12225, proceed as follows :

• divide the code into its components as shown below

• then read off the status of the individual components from the tables given.

+ - 25 SE V 0 : E rro r o r C rea te F ile request to send o r rece ive

1 2 252

+ - 2 SE V 1 : T im eout: O the r s ite does no t respond

+ - 2 SE V 2 : C reate acknowledgem ent not rece ived ;restart transfer w ith CR EATE=R EPLACE

+ - 1 SE V 3 : F ata l e rro r fo r cu rren t file transfe r; p roceed to the next file transfe r


47 A2 14UC Rev05 F-35

-2 0-2 2-2 3-2 4-2 5-2 6-2 7-2 8-2 9-3 0-3 1-3 2-3 3-3 4-3 5-3 6-3 7-3 8-3 9-4 0-4 1-4 2-4 3-4 4-4 6-5 0

E rror a t conne ctio nE rror on D e fin e A pp lica tion P rotoco l to sendE rror on D e fin e A pp lica tion P rotoco l to rece iveE rror on S e le ct A pp lica tio n P rotoco l to se nd o r rece iv eE rror on C reate F i le re q ues t to se nd or rece iv eE rror on S e le ct A pp lica tio n P rotoco l ac know ledg em en tE rror on C reate F i le re q ues t ack no w le dg em entE rror on D e fin e R em ote F ile to sen dE rror on D e fin e R em ote to rece iv eE rror on A ss ig n R em o te F ile to se nd o r rece iv eE rror on A ss ig n R em o te F ile ac know ledg em en tE rror on O p en R e m ote F i le to se nd or rece iceE rror on O p en R e m ote F i le ack no w le dg em entE rror on P os ition R e m ote F ile to se nd or rece iv eE rror on P os ition R e m ote F ile ack no w le dg em e ntE rror on S ta rt D ata Trans fe r to s en d or re ce iv eE rror on S ta rt D ata Trans fe r ackn ow ledg e m en tE rror du ring the D ata p ha seE rror a t E nd o f D ata Tran sfe r to sen d or re ceiv eE rror a t E nd o f D ata Tran sfe r a ckn ow led ge m entE rror on C los e R em o te F ile to e nd or rece iveE rror on C los e R em o te f ile acknow ledg em e ntE rror on R e le ase R em o te F ile to se nd o r rece iv eE rror on R e la se R em ote F ile to sen d or re ce iv eE rror on R e ceiv e E xec ution Job req u estE rror a t D isco nn ect tim e

9 9 999

D a ta m a na g em en t e rro r

T im e ou t: O the r s ite do es no t resp on d

P ro toco l e r ro r

P rog ram m ing er ro r

E rror rece ived ov e r c om m un ic ations se ss io n

S e ss ion p rim itiv e re jec ted

A b norm a l d isc on ne ctio n a fte r d ata acknow ledg e m e nt

+ - v a lues 1 th roug h 5, see p ag e fo llow ing

+ - va lue s 1 a nd 2, se e p ag e fo llow ing

-1

-2

-3

-4

-5

-6

+ -9

DJP User's Guide

F-36 47 A2 14UC Rev05

-20-50 S ee prev iou s p age

9 9 999

F ile tra nsfe r res ta rta b le ; rese nd w ith sam e p aram ete rs

C rea te ac kno w ledg em e nt no t rec eiv ed ; re s ta rt tra ns fer w ith C R E A TE = R E P LA C E

F ile tra nsfe r res ta rta b le ; ou tp ut f ile a lloca tion if req ue s te d,is c om p lete - restar t f ile trans fer w itho ut crea te op tion

F ile tra nsfe r res ta rta b le ; cu rren t trans fe r o f d ata a bor te d-res tart f i le tra ns fer w ithout c rea te op tion bu t w ith R E S TA R T

F ile tra nsfe r n ot resta rtab le ; er ro r to b e c orrec ted b y the u sersuch as D a ta Lim it, F ile o r sub file u nknow n or m is s ing or A P P E N Dw hich p re ve nts res tar ting th e f ile tran sfer

-1

-2

-3

-4

+ -5

-1-9 S ee prev ious p ag e

F ata l e rro r fo r curren t f ile tran sfer; p ro ceed to th e nex t f ile tran s fer

M ajo r e rro r ; use r f ile tran sfer se ss io n is d isc on ne cte d

-1

-2

47 A2 14UC Rev05 i-1

Index

A

Absentee A-32ADDAPPL

MDP parameter to add applications D-2ADDSITE

MDS parameter to add sites D-4ADDSTTN

MDP parameter to add stations D-3application

cataloging -s D-2APPLIST

CRP parameter to declareapplications D-2

C

cancel_output A-3CANCEL_USER_REQ (CUR)

syntax of - A-6catalog

description of site - D-1codes

- for RFA messages F-3- status F-34

CUR (CANCEL_USER_REQ)syntax of - A-6

D

DC A-8DDJP A-11DISPLAY_CONFIGURATION A-8DISPLAY_DJP A-11DISPLAY_JOB (DJ)

syntax of - A-15DISPLAY_JOB)

syntax of - A-15

DISPLAY_SECURITY_OPTIONS (DSO)syntax of - A-26

DISPLAY_USER_REQ (DUR)syntax of - A-29

Distributed Job Processing (DJP)functions with DPS 7/7000 1-2functions with DPS 6 3-1

DJP (Distributed Job Processing)functions with DPS 7/7000 1-2functions with DPS 6 3-1

DSO (DISPLAY_SECURITY_OPTIONS)syntax of - A-26

DUR (DISPLAY_USER_REQ)syntax of - A-29

E

EJ directive A-32EJR directive A-32ENTER_JOB_REQ dir A-32EVERY

arguments of - E-5example of - arguments E-5purpose E-5

Executing absentee jobs A-32Executing jobs A-32

F

file transfer capabilityDPS 7/7000 to DPS 7/7000 B-2DPS 7/7000 to non-DPS 7/7000 B-3

FORCEWHEN option E-4

FORCE_OUTPUT A-41FORCE_USER_REQ (FUR)

syntax of - A-42FUR (FORCE_USER_REQ)

syntax of - A-42

DJP User's Guide

i-2 47 A2 14UC Rev05

H

HOLD_USER_REQ (HUR)syntax of - A-43

hostdefinition of - 1-1

HUR (HOLD_USER_REQ)syntax of - A-43

J

jobsubmission 1-3- submission between DPS 7/7000s 2-1- submission from DPS 6 toDPS 7/7000 3-5- submission from DPS 7/7000 toDPS 6 3-2destination of - output 2-5destination of - output on submissionfrom DPS 6 3-6destination of - output on submissionfrom DPS 7/7000 3-3

Job execution A-32job processing commands A-1JOR messages F-1

fatal - F-2information - F-2warning - F-2

M

MAINTAIN_CATALOG D-1MDC (MODIFY_CONFIGURATION)

syntax of - A-44MDDJP (MODIFY_DJP)

syntax of - A-46MDO, syntax of- A-49MDOP(MODIFY_OUTPUT_PARAMETERS)

syntax of - A-53MDST (MODIFY_STATION)

syntax of - A-56MDUR (MODIFY_USER_REQ)

syntax of - A-59messages

- from server site F-23JOR - F-1operator - F-30Type 4 F-25

MO, syntax of- A-49MODIFY_CONFIGURATION (MDC)

syntax of - A-44MODIFY_DJP (MDDJP)

syntax of - A-46

MODIFY_OUTPUT, syntax of- A-49MODIFY_OUTPUT_PARAMETERS(MDOP)

syntax of - A-53MODIFY_STATION (MDST)

syntax of - A-56MODIFY_USER_REQ (MDUR)

syntax of - A-59

N

NETGENdescription of - utility B-1

network generationexample of - in high-level directive B-10example of - in low-level directive B-8general description of - B-6

O

operator messages F-30OUTPUT_WRITER A-65, A-71

P

profiledeclaring explicit - B-1description of - B-1relation to RFA capability B-4

projectcataloging the - D-2

R

RELEASE_USER_REQ (RUR)syntax of - A-62

requestdefinition of - 1-1

request queuedefinition of - 1-1

requestordefinition of - 1-1

RFA capabilityrelation to system profile B-4

RRESTARTarguments of - E-7example of - arguments E-7purpose E-7

RUR (RELEASE_USER_REQ)syntax of - A-62

Index

47 A2 14UC Rev05 i-3

S

serverdefinition of - 1-1

SIR (START_INPUT_READER)syntax of - A-64

sitecataloging -s D-4definition of - 1-1

site catalogdefinition of - 1-1description of - D-1

SITELISTCRS parameter to declare sites D-4

START_INPUT_READER (SIR)syntax of - A-64

stationcataloging -s D-4defining -s D-3definition of - 1-1

status codes F-34STTNLIST

CRP parameter to declare stations D-3system load A-19system profile

declaring explicit - B-1description of - B-1relation to RFA capability B-4

T

TERMINATE_INPUT_READER (TIR)syntax of - A-70

TIR (TERMINATE_INPUT_READER)syntax of - A-70

Type 4 messages F-25

W

WHENabsolute addressing E-1example of - E-2example of - arguments with EVERY E-6fast options E-3FORCE option of - E-4purpose of - E-1relative addressing E-3

DJP User's Guide

i-4 47 A2 14UC Rev05

Technical publication remarks form

Title : DPS7000/XTA NOVASCALE 7000 DJP User's Guide Communications: Applications

Reference Nº : 47 A2 14UC 05 Date : January 1998

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

47 A2 14UC 05REFERENCE

Date post:	08-Jun-2019
Category:	Documents
Upload:	vankien
View:	216 times
Download:	0 times

DJP User's Guide - Welcome to Support On Line...

Documents