DDP-PPC/DDP-FJT Messages Reference Manual - Public Support ...

!+ OS 2200 

Distributed Data 

Processing 

(DDP-PPC/DDP-FJT) 

Messages 

Reference 

Manual 

Copyright 1997 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

DDP-PPC Level 7R1 September 1997 

DDP-FJT Level 5R4 

Printed in U S America 

Priced Item 3787 3528-200

The names, places, and/or events used in this publication are not intended to correspond to any 

individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, 

places, and/or events with the names of any individual, living or otherwise, or that of any group or 

association is purely coincidental and unintentional. 

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE DOCUMENT. Any product and related 

material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly 

executed Program Product License or Agreement to purchase or lease equipment. The only warranties 

made by Unisys, if any, with respect to the products described in this document are set forth in such 

License or Agreement. Unisys cannot accept any financial or other responsibility that may be the result 

of your use of the information in this document or software material, including direct, indirect, special, 

or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies 

with the laws, rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise 

of such changes and/or additions. 

RESTRICTED - Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 

252.227-7013 and 252.11 15/FAR 52.227-14 & 52.227-19 for commercial computer software. 

Correspondence regarding this publication should be forwarded to Unisys Corporation either by using 

the Business Reply Mail form included with this document, or by addressing remarks to Unisys 

Corporation,Tredyffrin/Malvern Product Information, Malvern Development Center, P.O. Box 203, Paoli, 

PA, 19301, U.S.A.Comments about documentation can also be sent through e-mail to: 

aspgpi@unisys.com 

Unisys is a registered trademark of Unisys Corporation. 

All other terms mentioned in this document that are known to be trademarks or service marks have 

been appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this information. 

Use of a term in this document should not be regarded as affecting the validity of any trademark or 

service mark.

Contents 

About This Manual ::::::::::::::::::::::::::::::::::::::::::::: vii 

Section 1. Introduction 

Section 2. DDP-FJT Terminal Messages 

Section 3. Status Codes Returned to DDP-PPC/DDP-FJT 

Programs 

Section 4. DDP-FJT/OSI-FTAM Print and Tape Utilities 


Section 5. DDP-PPC Log and Trace Facility Messages 

Section 6. PPCMASTER Run Messages 

Section 7. DDPMASTER Run Messages 

Section 8. Configuration Services Messages 

3787 3528-200 iii

Contents 

Appendix A. DDP-FJT Internal Error Codes 

Appendix B. Configuration Services Status Codes 

Bibliography 

iv 3787 3528-200

Tables 

2-1. Initialization Error Codes :::::::::::::::::::::::::::::::::::::: 2-5 

2-2. Status and Substatus Codes for File Errors :::::::::::::::::::::::: 2-10 

7-1. RSI Error Status Code Definitions ::::::::::::::::::::::::::::::: 7-8 

A-1. DDP-FJT Internal Error Codes ::::::::::::::::::::::::::::::::::: A-2 

B-1. Configuration Services Status and Substatus Codes ::::::::::::::::: B-1 

3787 3528-200 v

About This Manual 

Purpose 

Scope 

Audience 

Distributed Data Processing File and Job Transfer (DDP-FJT) and Distributed Data 

Processing Program to Program Communications (DDP-PPC) program products are 

communications system software used to handle and control data throughout a 

communications network. 

DDP-FJT enables you to transfer files and jobs between systems by means of terminal 

commands or by program-callable COBOL application programs. DDP-PPC enables 

COBOL, FORTRAN and C Language application programs that reside in a Distributed 

Communications Architecture (DCA) network, Open Systems Interconnection (OSI) 

network, or Transmission Control Protocol/Internet Protocol (TCP/IP) network to 

communicate with each other and exchange data. 

The purpose of this manual is to provide all users of DDP-FJT and DDP-PPC with a 

complete list of status codes and messages issued by these products. 

This manual lists and describes all DDP-FJT and DDP-PPC status codes and messages. 

Also included is information that may be used to determine the cause of the status code or 

message, and information that may be used to correct or continue a job. 

This manual is intended for all users of DDP-FJT and DDP-PPC, including terminal users, 

programmers, system operators, and the systems administrator. This manual may also be 

useful to users of products that work with DDP-PPC, including OSI-FTAM, OSI-MHS, 

SNAPPC, SNARJE, and TAS. 

Prerequisites 

Anyone using this manual should understand DDP-FJT and DDP-PPC terminology. 

3787 3528-200 vii


How to Use This Manual 

This manual is a reference tool. Use it when you receive a message or status code from 

DDP-FJT and DDP-PPC. 

Messages displayed by software products that work with DDP-PPC, such as OSI-FTAM and 

OSI-MHS, may contain DDP-PPC status codes. Look up these codes in Section 3. 

Organization 

Section 1. Introduction 

This section provides an overview of status codes and messages generated by DDP-FJT 

and DDP-PPC. 

Section 2. DDP-FJT Terminal Messages 

This section numerically lists DDP-FJT messages returned to the terminal or the system 

console. 

Section 3. Status Codes Returned to DDP-PPC/DDP-FJT Programs 

This section numerically lists the decimal value and octal equivalent of DDP-PPC and 

DDP-FJT status codes. 

Section 4. DDP-FJT/OSI-FTAM Print and Tape Utilities Messages 

This section numerically lists messages returned to the operator’s console when using 

PSERVER, PRMAN, TXFR, and TXFCPY. 

Section 5. DDP-PPC Log and Trace Facility Messages 

This section alphabetically lists messages returned to the operator’s console and DDP-PPC 

log file when the log/trace background run processes a user command. 

Section 6. PPCMASTER Run Messages 

This section numerically lists messages returned to the PPCMASTER run. 

Section 7. DDPMASTER Run Messages 

This section alphabetically lists messages returned to the DDPMASTER run. 

Section 8. Configuration Services Messages 

This section numerically lists messages returned to Configuration Services. 

viii 3787 3528-200

Appendix A. DDP-FJT Internal Error Codes 


This appendix contains a list of DDP-FJT internal error codes that may be displayed within 

DDP20000 error messages or DDPMASTER run messages. 

Appendix B. Configuration Services Status Codes 

This appendix lists and describes status and substatus codes that may be returned as part 

of Configuration Services messages. 

Related Product Information 

Note: Throughout this manual, when we refer you to another manual, you should use 

the version that applies to the software level in use at your site. 

OS 1100 Distributed Data Processing File and Job Transfer (DDP-FJT) IPF and 

Batch Interface Operations Guide, (3787 3551) 

Describes how to transfer files and jobs between systems in a DDP network using terminal 

commands. 

OS 1100 Distributed Data Processing File and Job Transfer (DDP-FJT) Menu 

Interface Operations Guide, (3787 3569) 

Describes how to transfer files and jobs between systems in a DDP network by means of 

menu selections. 

OS 2200 Communications Management System (CMS 1100) Programming 

Reference Manual ((7831 5827) 

Describes Transport Service Access Method (TSAM) error codes that may be returned to 

DDP-PPC programs. 

OS 2200 Distributed Data Processing (DDP-PPC) DCA Interface C Language 

Programming Guide (3787 3254) 

Describes how to write C Language programs for use with DDP-PPC and DDP-FJT in the 

Distributed Communications Architecture (DCA) interface. 

OS 2200 Distributed Data Processing (DDP-PPC/DDP-FJT) DCA Interface 

COBOL Programming Guide (3787 3510) 

Describes how to write COBOL programs for use with DDP-PPC and DDP-FJT in the 

Distributed Communications Architecture (DCA) interface. 

OS 2200 Distributed Data Processing (DDP-PPC) OSI Interface C Language 


Describes how to write C Language programs for use with DDP-PPC in the Open Systems 

Interconnection (OSI) interface. 

3787 3528-200 ix


OS 2200 Distributed Data Processing (DDP-PPC) OSI Interface COBOL 


Describes how to write COBOL programs for use with DDP-PPC in the Open Systems 

Interconnection (OSI) interface. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface C Language 


Describes how to write C Language programs for use with DDP-PPC in the Transmission 

Control Protocol/Internet Protocol (TCP/IP) interface. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface COBOL 


Describes how to write COBOL programs for use with DDP-PPC in the Transmission 


OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface FORTRAN 


Describes how to write FORTRAN programs for use with DDP-PPC in the Transmission 


OS 2200 Distributed Data Processing File and Job Transfer (DDP-FJT) 

Implementation and Administration Guide (3787 3544) 

Provides implementation, administration, and operations procedures for Distributed Data 

Processing File and Job Transfer (DDP-FJT) software. 

OS 2200 Distributed Data Processing Program to Program Communications 

(DDP-PPC) Implementation and Administration Guide (3787 3270) 

Describes procedures to configure and operate in a DDP environment on OS 1100 systems. 

It lists the hardware and software requirements. It tells how to: 

$ Initialize and terminate the DDP environment 

$ Manage normal DDP activity 

$ Perform error recovery and diagnostic procedures 

OS 2200 Exec System Software Executive Requests Programming Reference 

Manual (7830 7899) 

Describes the Executive Requests (ERs) and Command Statement Format (CSF) errors. 

OS 2200 Interactive Processing Facility (IPF 1100) Command Language User’s 

Guide (7833 3788) 

Contains messages pertaining to local host file transfer commands. 

x 3787 3528-200

Notation Conventions 

The following conventions are used in messages: 


$ Terms in italics denote variables for which the system inserts a value. For example: 

**DDP5010 The status of your job job-id is completed. 

$ When the system inserts one of several specific values in a message, the terms are 

enclosed in braces ({ }) and separated by slashes (/). For example: 

**DDP4060 The USERID specified on your command for the 

{Source/Destination/Requested} host is configured to automatically execute a program 

at logon time. 

3787 3528-200 xi

Section 1 

Introduction 

DDP-PPC and DDP-FJT program products communicate with the terminal user, system 

operator, and programmer through messages and/or status codes. These messages or 

status codes may be displayed: 

$ On the user’s terminal 

$ On the operator’s console 

$ Within an application program 

$ In the DDP-PPC log file 

These messages indicate: 

$ The status of the system 

$ When a job is started or completed 

$ The errors encountered during execution 

$ A wide variety of diagnostic information that may be used to correct or continue a job 

DDP-PPC is the base product that provides distributed data processing capability on 

OS 2200 hosts. Other software products such as OSI-FTAM and OSI-MHS use DDP-PPC to 

support their applications. These products may pass DDP-PPC status codes or messages to 

users in programs or at the terminal. 

3787 3528-200 1-1

Section 2 

DDP-FJT Terminal Messages 

This section numerically lists DDP-FJT messages dynamically returned to the user’s 

terminal or the system console. These messages relate to operations with a remote host. 

Within the messages, variables in italics indicate site-specific information. 

DDP-FJT error messages on operations confined to the local host are not documented in 

this manual, but are contained in the IPF 1100 Command Language User’s Guide. IPF 

manages DDP-FJT commands that do not specify a remote host. 

You can get on-line help for the DDP-FJT IPF interface with the IPF User Assistance 

product. See the DDP-FJT IPF and Batch Interface Operations Guide for further 

information. 

When you are using the DDP-FJT menu interface, on-line help is included in the command 

facility. See the DDP-FJT Menu Interface Operations Guide for further information. 

You can verify status information about a host in your DDP network by using the STATUS 

NETWORK command to get a list of network host names. 

Some messages include a status code from DDP-PPC. Status codes contained within 

messages are returned in the octal format aaa bbb cccccc, where: 

aaa 

Is the class code. 

bbb 

Is the detail status code. 

cccccc 

Is the specific error code. It provides additional information for some error codes. 

For example, 001 022 000000 means an octal class code of 1 and an octal detail status code 

of 22. There is no specific error code. To interpret this status code, look up the class and 

detail status codes in Section 3. 

Note: If a terminal message indicates that an entry was made to the DDP-PPC log 

file, you can find the entry on the system that encountered the error if that 

system is an OS 2200 system. 

3787 3528-200 2-1


DDP100 

Message: 

**DDP100 Monitor is now active. 

Action: 

None Required 


Message: 

**DDP110 Sign-on error received by monitor. 

Action: 

Look for subsequent messages. DDP-PPC class and detail status codes follow with more 

information about the error. 


Message: 

**DDP120 Monitor has been terminated - no further distributed commands will be 

processed. 

Action: 

Look at preceding messages. The monitor tried to recover from a series of errors and 

finally quit. 


Message: 

**DDP130 Monitor failed TRMRG$ registration - no distributed commands can be 

processed. 

Action: 

Check the Exec System Software Executive Requests Programming Reference Manual for 

information. Verify that you have enough PCT space assigned for your application 

processing. 

2-2 3787 3528-200


Message: 

**DDP160 DDPMASTER cannot be executed from a temporary file. 

Action: 

Execute the DDPMASTER from a permanent file. 


Message: 


**DDP200 Buffer allocation error at address address-id. Buffer size requested is size 

words. 

Action: 

Try again later. This is a temporary condition. 


Message: 

**DDP210 Buffer deallocation error at address address-id. Buffer address is address. 

Action: 

None required. 


Message: 

**DDP220 Linked buffer allocation error at address address-id - status returned from 

Validate Pool Address is status. 

Action: 

Retry the command. Releases prior to 4R1 may get this error from time to time. 


Message: 

**DDP230 Linked buffer deallocation error at address address-id - status returned from 

Validate Pool Address is status. 

Action: 

Retry the command. Releases prior to 4R1 may get this error from time to time. 

3787 3528-200 2-3



Message: 

**DDP300 Remote work order message error at address address-id - message status 

returned is status. 

Action: 

Contact your Unisys representative. 


Message: 

**DDP310 Invalid work order message at address address-id. 

Action: 



Message: 

**DDP320 RSI$ initialization error at address address-id - status returned from 

initialization routine is error-code. 

Explanation: 

STATUS JOB and CANCEL JOB commands may be disabled. See Table 2-1for an 

explanation of the initialization error codes. 

2-4 3787 3528-200

Table 2-1. Initialization Error Codes 

Error Code Explanation 

1 Illegal user-id or password. 


2 When entering the user-id/password, the reply received was not "Destroy 

Userid/Password". 

3 "Enter Userid/Password" was never output at terminal. 

4 Reserved for future use. 

5 Site-id already active with this run. 

6 Site-id already active, or signed on by another run or Exec handler 

7 ER RSI$ not allowed for the user’s account/user-id quota set. 

8 Site-id syntax error. 

9 Device not configured (batch only). 

10 Initialization cannot be done due to Exec storage limits (EXPOOL). 

11 The maximum number of RSI$ terminals is already active. 

12 Demand initialization of batch or non-PSI$ device not allowed. 

13 RSI GET Error. 

Possible Cause: RSI interface to this demand run has terminated; there was no 

second reply after entering the user-id/password. 

14 RSI PUT Error. 

Possible Cause: The system rejected the userid/password input. 

15 Reserved for future use. 

16 XQT CARD Error. 

Possible Cause: The system would not allow the terminal to be put in HOLD state. 

17 "Unisys 2200 Operating System" not output by EXEC during sign on of demand RSI. 

Because this message was not output by the EXEC, RSI sign on failed. Do not 

change the EXEC sign-on message when using DDP. 

19 Password for the user-id supplied on the DEMANDID keyword is invalid. 

3787 3528-200 2-5



Message: 

**DDP330 No worker activity currently available to process command. 

Action: 

Try again later. Releases prior to 4R1 may get this error from time to time. 


Message: 

**DDP350 Invalid work order report at address address-id. 

Action: 

Retry the command. This is a protocol error. If it persists, contact your system 

administrator. 


Message: 

**DDP370 DDP encountered an error in sending an exception message on the conversation 

being used to process your command. 

A DDP-PPC network error was logged in the DDP-PPC Log File. 

Action: 

Contact your system administrator. 


Message: 

**DDP380 DDP encountered an error in receiving a message during the processing of your 

command. 


Action: 


2-6 3787 3528-200


Message: 


**DDP400 DDP was unable to sign on an activity to process your command. 


Action: 



Message: 

**DDP490 DDP encountered an error in sending an abort message on the conversation 

being used to process your command. 


Action: 



Message: 

**DDP500 DDP encountered an error during the passoff of a conversation used to process 

your command. 


Action: 



Message: 

**DDP510 DDP was unable to sign off one of the activities used to process your command. 

Action: 

None required. Although DDP-FJT did not disconnect, the activity did terminate. Activity 

termination forces disconnection. 

3787 3528-200 2-7



Message: 

**DDP520 The path to the remote host is down. This can occur when: 

(1) The DDP transport server on the remote host is down. 

(2) A Front End Processor is down. 

(3) An Undeliverable Message status is received from the network. 

Remote processing to other hosts in the network or to the local host is available. 

Action: 

Check to see if remote CMS or DDP process is down. For more information, see the 

DDP-PPC Implementation and Administration Guide. 


Message: 

**DDP530 The DDP-PPC OSITSU component on the local host is down. DDP-FJT 

processing is not available until the DDP-PPC OSITSU component is brought up. 

Action: 

Issue an UP OSITSU command to the PPCMASTER processor. 


Message: 

**DDP540 DDP encountered an unrecoverable communication network error with the 

remote host. 

Possible causes are: 

$ The TRANSPORT keyword on the REMOTE host image in the DDP Configuration File 

does not match a TRANSPORT name in the CMS Configuration 

$ The NETWORK name on the TRANSPORT image does not match a NETWORK image 

$ The LOCAL-NUMBER on the NETWORK image does not provide a complete path to 

the remote host 

Action: 

Correct the configuration of CMS 1100. 

2-8 3787 3528-200


Message: 


**DDP560 The remote host is available, but there is no DDPMASTER currently running on 

that remote host. 

Action: 

Start the DDPMASTER run on the remote host. 


Message: 

**DDP570 Your COPY command has not completed in the allocated time. The copy may 

still be in progress. 

Explanation: 

The probable cause is that you are attempting to copy a very large file, and the copy was 

still in progress when the DDP-FJT maximum command time expired. The copy will 

continue to execute after control has been returned to you. 

Action: 

None required. The COPY command will continue. 


Message: 

**DDP600 File READ error : I/O status status code substatus substatus code. 

Explanation: 

See Table 2-2 for an explanation of status and substatus codes for file errors. 

3787 3528-200 2-9


Table 2-2. Status and Substatus Codes for File Errors 

Status Code Substatus Code Explanation 

4 25 An SDF file contains a bad control word, or the file is in an 

illegal or unrecognizable format. Try using 

TYPE=UNDEFINED if you are copying from an OS 2200 host 

to an OS 2200 host. 

4 64 An SDF file has no SDF end-of-file marker. Correct the file, or 

use TYPE=UNDEFINED if you are copying from an OS 2200 

host to an OS 2200 host. 

4 (all others) EXEC I/O error. See the Exec System Software Executive 

Requests Programming Reference Manual. 

(all others) (all others) Contact your Unisys representative. 


Message: 

**DDP610 File WRITE error : I/O status status code substatus substatus code. 

Explanation: 



Message: 

**DDP620 File FREE error : I/O status status code substatus substatus code. 

Explanation: 



Message: 

**DDP630 Element initialization error: I/O status status code substatus substatus code. 

Explanation: 


2-10 3787 3528-200


Message: 


**DDP640 READ end of element error : I/O status status code substatus substatus code. 

Explanation: 



Message: 

**DDP650 WRITE end of element error : I/O status status code substatus substatus code. 

Explanation: 



Message: 

**DDP660 A record larger than one track was encountered while copying a file, or a 

segmented PCIOS record was encountered in a heterogeneous COPY. DDP does not 

support records longer than 1 track (7168 bytes) and DDP will not copy segmented PCIOS 

records to non-1100 hosts. The copy has been terminated. 

Explanation: 

This may happen when you are copying to a non-OS 2200 host. 


Message: 

**DDP770 **FATAL ERROR** No DEMANDID’s were found in the network configuration 

file. 

Action: 

Place at least one DEMANDID image in your DDP-PPC configuration services database. 

3787 3528-200 2-11



Message: 

**DDP840 **WARNING** The default for the initial MAXWRKRS value has been set to 

number. 

Action: 

Contact your system administrator. This error condition may cause system optimization 

problems later. 


Message: 

**DDP850 **WARNING** The default for the initial MAXWRKRS value and the absolute 

MAXWRKRS value has been set to number. This is the largest value allowable by DDP File 

and Job Transfer. 

Action: 

Contact your system administrator. This error condition may cause system optimization 

problems later. 


Message: 

**DDP860 **WARNING** DDP File and Job Transfer cannot be initialized with the 

maximum number of workers as zero. 

The default for the MAXWRKRS value has been set to number. 


Message: 

**DDP870 **WARNING** The MAXJWRKR statement was either missing from the 

configuration file or was invalid. The default for MAXJWRKR has been set to number. 


Message: 

**DDP880 **WARNING** The MAXJWRKR value exceeds the value of the MAXWRKR. The 

maximum job worker count has been set to number. 

2-12 3787 3528-200


Message: 

**DDP900 Destination host-id was not recognized by DDP. 


Message: 

**DDP910 An error has occurred while initializing the batch RSIs. 

Action: 


Check that the RSI statements in the DDP-PPC configuration services database are valid 

EXEC RSI statements. Also, make sure that the RSIs are not being used by another product. 


Message: 

**DDP920 The WARM START processing has set the MAX-WORKERS value to value and 

the MAX-JOB-WORKERS value to value. 

Explanation: 

When the DDPMASTER is initiated with a warm start, it may set these parameters to 

different values than the values in the DDP-PPC configuration file. This is based on the 

values that were saved in the FJT$RECOVER file from the previous execution of the 

DDPMASTER. 

Action: 

None required. This is an informational message. The same information can be displayed 

through the WORKERS console command after DDPMASTER initialization. 


Message: 

**DDP1010 Unrecognized WO type request type received on a receive (new) request. 


Message: 

**DDP1020 Error occurred during receive (new) processing in DDP monitor. 

3787 3528-200 2-13



Message: 

**DDP1040 Monitor activity continues execution. 

Action: 



Message: 

**DDP1050 Illegal description segment in WO. Segment number was request type. 

Action: 

Contact your Unisys representative. You should have your DDP-PPC log file ready. 


Message: 

**DDP1060 Invalid field in WO. 

Action: 

Contact your Unisys representative. You should have your DDP-PPC log file ready. 


Message: 

**DDP1070 No worker activity waiting for a reply from the specified conversation. 

Action: 

Look at the messages following this one for more detail. 


Message: 

**DDP1080 A source file description was received with no destination description. 

Action: 


2-14 3787 3528-200


Message: 


**DDP1210 The host host-id is not in the DDP network.Use the STATUS NETWORK 

command to see the list of host names. 

Action: 

Check to make sure you spelled the host name correctly. Use the STATUS NETWORK 

command to obtain a list of the network host names. If the command does not display the 

host-id, then the host either is not configured in the DDP-PPC configuration services 

database or is configured as a host type that is not supported by DDP-FJT. Check with your 

DDP administrator concerning the configuration of the host. 


Message: 

**DDP1220 The host host-id detected an invalid parameter error in one of the DDP 

protocol messages associated with this command. This is a fatal error and your command 

has been terminated. Re-entering this same command will lead to similar results. See 

message DDP1221 for additional information. 

Explanation: 

A probable cause of this error is that the hosts involved with the command do not have 

compatible levels of DDP. 


Message: 

**DDP1221 The invalid message has been logged in the DDP Log File. 


Message: 

**DDP1230 DDP is unable to process your request at this time. Possible causes are: 

(1) Heavy use of DDP File and Job Transfer at this time. 

(2) The DDP transport server has insufficient resources to process your request. 

Action: 

This is a temporary condition. Please try again later. If the problem persists, contact your 

systems administrator. 

3787 3528-200 2-15



Message: 

**DDP1240 The command you requested is not supported by one of the hosts named in 

your command. Some host types and/or previous levels of DDP do not support the full set 

of DDP commands. 

Other commands involving the same hosts will lead to similar results. 

Action: 

Check the release levels of the hosts in your command. See one of the DDP-FJT Operations 

Guides for descriptions of commands. 


Message: 

**DDP1250 The file name file name contains an illegal character, has too many characters, 

or has an element or element cycle specified when elements are not allowed. 

Explanation: 

File name syntax error. 

Action: 

Correct the file name and retry. 


Message: 

**DDP1260 Missing or invalid READ or WRITE keys. 

Explanation: 

If you did not specify keys on your command, this means that the file being referenced 

requires a key for the type of access requested, or the read or write keys you specified are 

incorrect. 

Action: 

Use the correct READ or WRITE key. 

2-16 3787 3528-200


Message: 


**DDP1270 DDP was unable to complete the command requested due to a security conflict 

with the type of access you desire. 

Explanation: 

System security does not allow what you are trying to do. 

Action: 

Contact your systems administrator. 


Message: 

**DDP1280 Read/Write key support is currently unavailable. 

Explanation: 

The remote system is presently unable to process files with read and/or write keys. 

Action: 

Try again when support becomes available, or delete keys. 


Message: 

**DDP1300 ** ERROR ** The DDP-PPC configuration services database contains too many 

remote HOST records. Please reduce the number of HOST records in the network 

configuration file to be compatible with the limit set in the DDP Implementation and 

Administration Guide. 

Action: 

See the DDP-FJT Implementation and Administration Guide for more information. 


Message: 

**DDP1410 The file file name already exists on the host host-id. 

Explanation: 

The file name specified already exists in the master file directory. 

3787 3528-200 2-17



Message: 

**DDP1420 The FILE TYPE specified is not supported on host host-id. 

Action: 

Use the correct file type. Consult the appropriate manuals to determine which file types 

are supported on the host. 


Message: 

**DDP1430 An error was detected in the value for either the MAXIMUM_SIZE, 

INITIAL_SIZE, or GRANULARITY_SIZE. One of these size parameters is either missing, 

inconsistent, or not within the range of allowable values. 

Explanation: 

Initial size is greater than the maximum size, or a size parameter contains an illegal value. 

Action: 

Correct your parameters and retry. 


Message: 

**DDP1440 You specified either a DEVICE TYPE, DEVICE CLASS, or VOLUME which is 

not available. 

Explanation: 

Device class/type not available. 


Message: 

**DDP1450 You specified either a DEVICE TYPE, DEVICE CLASS, or VOLUME which is 

not supported. 

2-18 3787 3528-200


Message: 

**DDP1460 The VOLUME volume-id is not available on the host host-id. 

Explanation: 

The removable pack specified is not currently mounted. 


Message: 


**DDP1470 DDP is unable to create the file specified because the quota number of units 

has been exceeded. 

Explanation: 

Quota error. 

Action: 



Message: 

**DDP1480 The DEVICE_TYPE or VOLUME contains an illegal character. Only 

alphanumeric characters are allowed within the DEVICE_TYPE and VOLUME. 

Explanation: 

Invalid characters in device type or volume. 

Action: 

Correct and retry. 

3787 3528-200 2-19



Message: 

**DDP1490 You have specified a VOLUME but have not specified a DEVICE TYPE. 

Explanation: 

Volume specified without device type. 

Action: 

If you need to specify a volume, you must also specify a device type. Retry your command. 


Message: 

**DDP1500 Your command could not be processed for one of the following reasons: 

(1) There is no space available on the VOLUME you requested. 

(2) You have attempted to CREATE or COPY into a UNIX or MS-DOS directory that does 

not exist, or cannot be accessed by you. 

Explanation: 

Space not available on volume. 

Action: 

If (1), use another volume. If (2), see if the remote directory exists, or check the 

permissions on the remote directory. 


Message: 

**DDP1510 Your request has been denied due to a security violation. 

Explanation: 

System security does not allow what you are trying to do. 

Action: 


2-20 3787 3528-200


Message: 


**DDP1530 The access control record (ACR) name contains an illegal character. Only 

alphanumeric characters are allowed in an ACR name. 

Explanation: 

Invalid ACR name. 

Action: 

Check to see if you spelled the ACR name correctly, or use the correct ACR name. 


Message: 

**DDP1610 DDP cannot purge this private file. 

Explanation: 

Wrong project-id for private file. The DDP-FJT run on the remote system is not permitted 

to access it. 

Action: 

Retry the command with the correct access information. 


Message: 

**DDP1620 The element eltname does not exist on host host-id with the TYPE that you 

specified. 

Action: 

Check that you spelled the file name correctly, or use a different file. 


Message: 

**DDP1630 The file file name is not available on host host-id. 

Explanation: 

The file is in use, rolled out, or on an unmounted removable disk pack. 

3787 3528-200 2-21



Message: 

**DDP1640 The file file name requires a write key for access. 


Message: 

**DDP1650 The file file name requires a read key for access. 


Message: 

**DDP1810 The TO (Destination) file file name does not exist on host host-id. 

Explanation: 

File not found. 

Action: 

Check that you spelled the file name correctly, or use a different file, or create the file on 

the destination host. 


Message: 

**DDP1820 The FROM (Source) file file name does not exist on host host-id. 

Explanation: 

Source file not found. 

Action: 

Check that you spelled the file name correctly or use a different file. 

2-22 3787 3528-200


Message: 


**DDP1830 The TYPE specified is not supported by the FROM (Source) host. 

Explanation: 

Source element type error (heterogeneous only). 

Action: 

Use a different type. 


Message: 

**DDP1840 No elements of the TYPE(s) specified exist in the FROM (Source) file. 

Explanation: 

Nothing was copied. 


Message: 

**DDP1850 The TO (Destination) file file name is not available. Please retry later. 

Explanation: 



Message: 

**DDP1860 The FROM (Source) file file name is not available. Please retry later. 

Explanation: 


3787 3528-200 2-23



Message: 

**DDP1870 An error occurred while accessing the TO (Destination) file file name. 

Explanation: 

Error in processing the destination file. Possible causes are: 

$ The wrong type was specified. 

$ DDP-FJT was unable to write to or add an element to the file. 

$ The destination file is not a program file or an empty file. 

The exact error has been logged in the DDP-PPC log file. 


Message: 

**DDP1880 An error occurred while accessing the FROM (Source) file file name. You 

specified the wrong type, the file is empty, or the file cannot be read by DDP. 

The exact error has been logged in the DDP Log File. 

Explanation: 

Error in processing source file. 


Message: 

**DDP1890 The TRANSLATE type specified is not supported on the TO (Destination) host 

host-id. 

Explanation: 

Destination file encoding error. DDP-FJT allows TRANSLATE only when copying files 

between OS 2200 and non-OS 2200 hosts. TRANSLATE = ASCII is permitted when copying 

to an OS 2200 host from a non-OS 2200 host. 

Action: 

Use a different TRANSLATE type. 

2-24 3787 3528-200


Message: 


**DDP1900 An unrecoverable error occurred when processing your command. Possible 

causes are: 

(1) An @CAT or @SYM error occurs during the SUBMIT or print copy (@SYM) commands. 

(2) An I/O error occurs during the COPY command. 

Explanation: 

Unrecoverable copy error. 


Message: 

**DDP1910 The TO (Destination) file file name is too small and cannot be expanded by 

DDP. 

Your COPY command was not completed. 

Explanation: 

File too small. 

Action: 

Enlarge the file or use a larger destination file. 


Message: 

**DDP1920 The TYPE specified is not supported on host host-id for file file name. 

Action: 

Use a different type to copy the file. 

3787 3528-200 2-25



Message: 

**DDP1930 One of the file names specified contained an illegal character, too many 

characters, or had an element cycle specified. 

Explanation: 

DDP-FJT does not support element cycles. 


Message: 

**DDP1940 The checkpoint identifier checkpoint-id cannot be found in the SOURCE 

checkpoint file on the host host-id. 

This is a fatal error and your command cannot be restarted. 

Explanation: 

Checkpoint was not found on the source host. This can occur when: 

$ You enter an incorrect command-id 

$ The command has already completed 

$ The source host DDPMASTER is brought up cold 


Message: 

**DDP1950 The checkpoint identifier checkpoint-id cannot be found in the DESTINATION 

checkpoint file on the host host-id. 


Explanation: 

Checkpoint was not found on the destination host. This can occur when: 

$ You enter an incorrect command-id 

$ The command has already completed 

$ The source host DDPMASTER is brought up cold 

2-26 3787 3528-200


Message: 


**DDP1960 The checkpoint identifier checkpoint-id was found on both the SOURCE and 

the DESTINATION host systems. However, a common established checkpoint did not exist 

in the files. 


Explanation: 

A common checkpoint did not exist. 


Message: 

**DDP1970 The CHECKPOINT feature of DDP may not be used when a single element is 

copied to the destination file. 

If you are issuing a COPY command, the copy will continue without checkpointing.If you 

are issuing a RESTART request, the command may have completed. 

Please issue a STATUS request to determine the progress of the command. 

Explanation: 

Cannot checkpoint single element copies. 


Message: 

**DDP1980 The DESTINATION host does not support the DDP CHECKPOINT feature. 

If you issued a COPY command, your COPY will continue without checkpointing. 

If you issued a RESTART command, your command cannot be processed. 

3787 3528-200 2-27



Message: 

**DDP1990 An error occurred while processing the DESTINATION CHECKPOINT request 

during file transfer. The file transfer may have continued to completion. Use the DDP 

STATUS command to see the results of the file transfer. You may not RESTART this file 

transfer. 

Explanation: 

Checkpoint logging error. 


Message: 

**DDP1995 Your command cannot be RESTARTed. Only COPY or SPOOL commands may 

be RESTARTed. 


Message: 

**DDP2000 Your command cannot be RESTARTed because it is still executing. You cannot 

RESTART a command that is currently active. 

Explanation: 

Cannot issue a restart; command in progress. 


Message: 

**DDP2005 Your RESTART cannot be restarted due to a security violation. 

Explanation: 

The user-id and password you use on the RESTART request must be the same as those 

used on the original command. 


Message: 

**DDP2010 The EXECUTION host host-id cannot service your SUBMIT request. The host 

may not be a valid host in your DDP network. 

2-28 3787 3528-200

Explanation: 

Execution host not available (SUBMIT). 

Action: 


Check that you specified the name correctly, or add the host to the DDP-PPC configuration 

services database. 


Message: 

**DDP2020 An unrecoverable error occurred while executing the job file transfer for your 

SUBMIT command. 

The copy of the job file to the destination host ended because a network connection has 

aborted. 

Explanation: 

Unrecoverable file transfer error on your SUBMIT command. This error and file name have 

been logged in the DDP-PPC log file. 


Message: 

**DDP2030 There is no job stream in the file file name or the file is not of the correct TYPE. 

An OS 1100 host expects an @RUN image as the first image in the file, and 

TYPE=DDPFILE is used for data files and TYPE=SYMBOLIC is used for elements. 

Explanation: 

No run-id or illegal file type. 

Action: 

Check to ensure you specified the file name correctly and that you used the correct TYPE 

specification. An OS 2200 host expects an @RUN image in the file. 

Use TYPE=DDPFILE for data files, and TYPE=SYMBOLIC for files within a directory. 

3787 3528-200 2-29



Message: 

**DDP2050 An error occurred while trying to send the submitted job-id back to your host. 

The possible causes are: 

(1) The remote host failed to respond with the submitted job names. 

(2) The remote host is unable to return one or more of your job names because an error 

occurred while copying your job stream to another host. 


Message: 

**DDP2060 An error occurred while copying the submitted job stream to the executing 

host. The error has been logged in the DDP Log File. 

Explanation: 

Write file error. 


Message: 

**DDP2210 The JOB job-id is not known to DDP. 

Explanation: 

The job was not submitted through DDP-FJT, or the system completed the execution and 

output printing of your job. 


Message: 

**DDP2220 An error occurred while trying to delete the job output delivery information. 

The job has been CANCELled but the output will be printed. 

2-30 3787 3528-200


Message: 


**DDP2225 The CANCEL cannot be processed due to a security violation. 

Explanation: 

The userid and password you use on the CANCEL request must be the same as those used 

on the original command. 


Message: 

**DDP2230 The status of job name is job status. 


Message: 

**DDP2240 If your command was a COPY or a SPOOL, then the FROM (SOURCE) file 

specified contains one or more records whose length exceeds 1792 words (7168 bytes). The 

maximum record or block size that can be transferred by DDP is 1792 words (one track). 

If your command was a SUBMIT, then the submitted runstream file specified contains one 

or more records whose length exceeds 224 words (896) bytes. The maximum record size 

that can be submitted by DDP is 224 words. 

Explanation: 

Record in files exceeds the maximum length supported by DDP-FJT. 

Action: 

Shorten the offending record, if possible. Otherwise, the file cannot be used by DDP-FJT. 


Message: 

**DDP2250 The TO (Destination) file is too small to receive the FROM (Source) file. 

Explanation: 

Destination file too small to create an element table. 

If the destination file is a program file, its element table space may be full. It may help to 

pack (@PACK) the destination file if it is a program file. 

3787 3528-200 2-31



Message: 

**DDP2260 The TO (Destination) file is catalogued as a read-only file, or has a write key, 

which was not supplied. 


Message: 

**DDP2270 The TO (Destination) file is a word-addressable file. DDP does not support 

word-addressable files. 

Explanation: 

The destination file is a word-addressable file. 

Action: 

Do not try to copy to word-addressable files. 


Message: 

**DDP2280 The destination file is a private file and the access information provided does 

not allow access to the file. 


Message: 

**DDP2290 Nothing was copied because the FROM (Source) file is empty. 

Action: 

Make sure you are using the correct source file. 


Message: 

**DDP2300 The FROM (Source) file is catalogued as a write-only file, or has a write key, 

which was not supplied. 

2-32 3787 3528-200


Message: 

**DDP2310 The FROM (Source) file is a word-addressable file. 

DDP does not support word-addressable files. 


Message: 


**DDP2320 The COPY could not be completed because the FROM (Source) file has no 

EOF marker. 

Explanation: 

If the FROM file is an SDF file, it is missing an SDF end-of-file control word. 


Message: 

**DDP2330 The FROM file is a private file and the access information provided does not 

allow access to the file. 

If the FROM host is running an older version of DDP, the DDPMASTER run is unable to 

access the file. 

Explanation: 

Source file is private; access denied. 


Message: 

**DDP2340 The FROM (Source) file has an invalid or missing READ key. 

Explanation: 

Your source file has a read key other than the one you specified, or the source file has a 

read key and you did not supply one. 

3787 3528-200 2-33



Message: 

**DDP2350 One of the files you specified has an invalid or missing READ key. 

Explanation: 

One of the files has a read key other than the one you specified, or the file has a read key 

and you did not supply one. 


Message: 

**DDP2360 One of the files you specified has an invalid or missing WRITE key. 

Explanation: 

One of the files has a write key other than the one you specified, or the file has a write key 

and you did not supply one. 


Message: 

**DDP2370 DDP support for read or write keys is not currently available on one of the 

hosts named in your command. 


Message: 

**DDP2380 The FROM (Source) file is in use by another run. 

Explanation: 

Another run has your FROM file assigned to it. The file must be freed by the run that has it 

assigned before DDP-FJT can access the file. 

2-34 3787 3528-200


Message: 

**DDP2390 The FROM (Source) file is in use by another DDP user. 

Explanation: 


Another DDP-FJT user on your local system or on a remote system has issued a DDP 

command that updates your FROM file. DDP-FJT users cannot concurrently write to and 

read from the same file. 

Action: 

Retry your command later. 


Message: 

**DDP2400 The FROM (Source) file is rolled out. 

You must wait for the file to be rolled in by the EXEC, or have your systems personnel 

restore the file. 


Message: 

**DDP2410 The TO (Destination) file is in use by another run. 

Explanation: 

Another run has your TO file assigned to it. The file must be freed by the run that has it 

assigned before DDP-FJT can write to the file. 


Message: 

**DDP2420 The TO (Destination) file is in use by another DDP user. 

Explanation: 

Another DDP-FJT user on your local system or on a remote system has issued a DDP-FJT 

command that uses your destination file. Only one DDP-FJT user may write to a file at a 

time. 

Action: 

Retry your command later. 

3787 3528-200 2-35



Message: 

**DDP2430 The TO (Destination) file is rolled out. 

You must wait for the file to be rolled in by the EXEC or restored by systems personnel. 


Message: 

**DDP2440 Your FROM (Source) file cannot be assigned by DDP. Possible reasons are: 

(1) You supplied read or write keys on a file that does not have them. 

(2) The file is private or catalogued at a higher security level than is allowed by the login 

parameters supplied on your command. 

(3) You specified the wrong TYPE. 


Message: 

**DDP2450 Your TO (Destination) file cannot be assigned by DDP. Possible reasons are: 

(1) You supplied read or write keys on a file that does not have them. 

(2) The file is private or catalogued at a higher security level than is allowed by the login 

parameters supplied on your command. 

(3) You specified the wrong TYPE. 

(4) You requested an element or multiple elements to be copied into a write-only file. 


Message: 

**DDP2460 A file cycle conflict exists for the file you specified. Possible reasons are: 

(1) Using the file would force the system to delete a cycle that is currently assigned. 

(2) The requested cycle is not within the currently allowable range. 

(3) F-cycle generation is not possible at this time because a cycle of (+1) is assigned. 

2-36 3787 3528-200


Message: 


**DDP2470 DDP is unable to access your FROM (Source) file because the drop flag has 

been set. 

Explanation: 

Your source file has been marked for deletion by the Exec, but it is still assigned by an 

active run. When the run terminates or frees the file, it will be deleted. 


Message: 

**DDP2480 DDP is unable to access your TO (Destination) file because the drop flag has 

been set. 

Explanation: 

Your file is marked for deletion by the Exec, but it is still assigned by an active run. When 

the run terminates or frees the file, it will be deleted. 


Message: 

**DDP2490 DDP is unable to access your FROM (Source) file due to a file cycle conflict. 

Explanation: 

Your source file may be at its maximum f-cycle, or another run may have created this file 

via @ASG,CP and has not freed the file. 


Message: 

**DDP2500 DDP is unable to access your TO (Destination) file due to a file cycle conflict. 

Explanation: 

The file may be at its maximum f-cycle, or another run may have created this file via 

@ASG,CP and has not freed the file. 

3787 3528-200 2-37



Message: 

**DDP2510 Your command has been terminated because DDP encountered a bad SDF 

Control Word when reading your SOURCE file. The file contains an illegal control word, 

causing DDP to be unable to read it. Other attempts to copy this file will lead to similar 

results. 


Message: 

**DDP2520 No response was received from the destination host in the allotted time. 

Explanation: 


$ DDP File and Job Transfer is not available on the remote host. 

$ The master run or worker RSI on the remote host is at too low of a priority. 

$ The master run on the remote host is overloaded with work. 

$ A network error prevents receipt of response from the destination host. 


Message: 

**DDP2530 You have specified an invalid start time on your command. 

Action: 

Specify start time correctly. 


Message: 

**DDP2540 Only single elements may be copied within the same file. You may have 

specified the wrong element type or you may have failed to specify an element name. 

2-38 3787 3528-200


Message: 


**DDP2550 Your command was terminated. You cannot copy a symbolic element that has 

element cycles to a non-program file or spool it to an OS 1100 system. 

Action: 

Read the file with a system editor, such as IPF 1100, that does not use element cycles when 

it updates an element. Then rewrite the element and copy or spool it using DDP-FJT. 


Message: 

**DDP2560 The host containing the source file is not configured to communicate with the 

system you are on (origin system). The source system must be configured to communicate 

with your system to return status after the file or job service is complete. 

Action: 

Update the configuration file on the source host to allow communications with your 

system. 


Message: 

**DDP3000 You have specified an element type to be purged, but you have not indicated 

the element name. 

Explanation: 

When purging an element from a file you must specify both the element type and the 

element name. 


Message: 

**DDP3010 You have specified an element name to be purged, but you have not indicated 

the element type. 

Explanation: 

When purging an element from a file, you must specify both the element type and the 

element name. 

3787 3528-200 2-39



Message: 

**DDP3020 You have specified parameters which are invalid with the MODE keyword. 

Explanation: 

You may only use the FILE and MAXIMUM_SIZE parameters with the MODE keyword. 


Message: 

**DDP3030 You have specified parameters which are invalid when creating a mass storage 

file. 

Explanation: 

Tape parameters are not valid on a disk CREATE command. 

Action: 

Do not use Parity, Density, Label_Format, Format, or Units parameters on a DDP CREATE 

through IPF. 


Message: 

**DDP3040 You have specified parameters which are invalid when setting the MODE 

keyword to DELETE. When trying to remove security information for specific hosts from 

the system you may only specify the HOST keyword with the MODE=DELETE option. 


Message: 

**DDP3050 You are trying to change or delete security information of which DDP has no 

record. In order to use the MODE keyword, you must have previously ADMITted security 

information into the system. 

2-40 3787 3528-200


Message: 


**DDP3060 You have specified security parameters which are invalid when setting the 

MODE keyword to CLEAR. When trying to remove all of the security information from the 

system, you may only specify the MODE=CLEAR option. 


Message: 

**DDP3070 You have specified the HOST parameter, which is invalid when setting the 

MODE= CLEAR option. When trying to remove all of the security information from the 

system, you may only specify the MODE=CLEAR option. 


Message: 

**DDP3080 DDP is unable to ADMIT your default security information into the system 

because there are not enough system resources available at this time. Please try your 

request again later. 


Message: 

**DDP3090 Your ADMIT request could not be processed completely. There was no space 

available for host(s) host-ids in your security profile. You may delete previously entered 

security information in order to ADMIT the access information for more hosts into the 

system. 


Message: 

**DDP3100 Your ADMIT request could not be completed for the host(s) host-ids because 

no access information for these hosts was previously ADMITted. If other hosts were 

specified on the command then their access information was deleted. 

Explanation: 

Access information for the specified host cannot be deleted because either: 

$ Access information for that host was never entered on an ADMIT command 

$ Access information for that host was deleted on a previous ADMIT command. 

3787 3528-200 2-41



Message: 

**DDP3110 Your security information could not be stored by DDP because DDP was 

unable to register for an IPF reload trap. The area where the security information would be 

stored could not be secured. 


Message: 

*DDP3120 All ADMIT information has been lost. Use the ADMIT command to reestablish 

security profiles for future DDP processing. 


Message: 

**DDP3130 **WARNING** All ADMIT information has been lost. This command and all 

further DDP commands will be processed with the default security information about the 

specified hosts. New ADMIT information may be specified for future DDP processing. 


Message: 

**DDP3140 DDP cannot process your ADMIT request without the HOST parameter. The 

HOST parameter is required to use the ADMIT command when the MODE parameter has 

been set to DELETE. 


Message: 

**DDP3150 DDP cannot process your ADMIT request without the HOST parameter. The 

HOST keyword is required when using the ADMIT command with the default UPDATE 

mode. 


Message: 

**DDP3160 DDP cannot process your ADMIT request when the HOST parameter has 

duplicate identifiers within the list you specified. 

2-42 3787 3528-200


Message: 


**DDP3170 Your ADMIT request could not be completed because the syntax for the 

host(s) host-ids is invalid. Only alphanumeric characters are allowed in a host name. 


Message: 

**DDP4000 The remote host has returned text with its command completion status. This 

text cannot be displayed, but will be logged in the DDP Log File. 


Message: 

**DDP4010 Your command could not be processed because DDP was unable to logon a 

run on the {Source/Destination/Requested} host with the access information that you 

specified. Please try your request again with the correct access information. 


Message: 

**DDP4020 Your command could not be processed because DDP was unable to logon to 

the {Source/Destination/Requested} host because the access information being used on 

that host has expired. Notify your system administrator to correct the problem. 


Message: 

**DDP4040 Your command could not be processed because DDP was unable to logon a 

run to process your command on the {Source/Destination/Requested} host. This may be 

because the operator on that host has placed a hold on demand runs or terminals. Please 

try again later. 

Action: 

Check with the system operator. 

3787 3528-200 2-43



Message: 

**DDP4050 DDP was unable to logon a run to process your command on the 

{Source/Destination/Requested} host because that host does not use standard OS 1100 

messages in the logon sequence. 


Message: 

**DDP4060 The USERID specified on your command for the 

{Source/Destination/Requested} host is configured to automatically execute a program at 

logon time. 

A userid configured in this manner cannot be used by DDP. 


Message: 

**DDP4070 The program RCAS$WORKER$ was not found in the DDP-FJT absolute file on 

the {Source/Destination/Requested} host or the USERID under which your command is 

running on that host could not access the DDP-FJT absolute for security reasons. 

This may be a result of an installation error, or someone may have accidentally deleted the 

program absolute. Notify your system administrator to correct the problem. 


Message: 

**DDP4080 The DDP-supplied program RCAS$WORKER$ on the 

{Source/Destination/Requested} host abnormally terminated during initialization. 

This error has been logged in the DDP Log File on that host. 

2-44 3787 3528-200


Message: 


**DDP4090 DDP was unable to process your command on the 

{Source/Destination/Requested} host because the maximum number of RSIs allowed on 

that host has been reached. 

Action: 

Wait and retry. If you are the systems administrator, increase Exec configuration 

parameter RSICNT. 


Message: 

**DDP4100 DDP was unable to process your command because the EXEC on the 

{Source/Destination/Requested} host will not allow DDP to logon a run due to an EXEC 

EXPOOL problem. 

Action: 



Message: 

**DDP4110 DDP was unable to process your command due to an error in the EXEC RSI 

component on the {Source/Destination/Requested} host. 

Action: 

Check the DDP-PPC log file and report the error. 


Message: 

**DDP4120 Your command cannot be processed because the maximum allowable number 

of DDP workers or DDP Job workers has been exceeded on one of the hosts in your 

command. Ask your systems administrator to increase the number of workers, or try your 

command again later. 

3787 3528-200 2-45



Message: 

**DDP4125 Your command cannot be processed because the maximum allowable number 

of DDP delayed workers has been exceeded on the source host in your command. Please 

try your command again later. 


Message: 

**DDP4130 Your command cannot be processed because DDP has been canceled. 

Action: 

Try again later. 


Message: 

**DDP4135 Your command cannot be processed because a DDP shut down is in progress. 

Action: 

Try again later. 


Message: 

**DDP4150 The volume requested is unavailable. It is being retrieved. Please try your 

command again later. 


Message: 

**DDP4160 Your command cannot be processed because index key fields are invalid or 

missing. 


Message: 

**DDP4170 The size of the file named in your command cannot be changed. 

2-46 3787 3528-200


Message: 


**DDP4180 Your SUBMIT command could not be processed because the file you specified 

does not contain a valid job stream. 

Explanation: 

Illegal runstream for execution host. 


Message: 

**DDP4190 Your SUBMIT command cannot be processed due to a specification error. 

Explanation: 

Illegal runstream for execution host. 


Message: 

**DDP4200 Your SUBMIT command cannot be processed because the EXECUTION HOST 

named in your command is not accepting jobs from the network. 


Message: 

**DDP4210 You may not SPOOL more than 99 or less than zero copies of a file in a SPOOL 

request. Please try your command again and specify from 1 to 99. 


Message: 

**DDP4220 Your command cannot be processed because the output device specified in 

your command is invalid. 

3787 3528-200 2-47



Message: 

**DDP4230 DDP was unable to return the output of your job because it has already been 

printed/punched, or was deleted by an operator command. 


Message: 

**DDP4240 DDP was unable to deliver the output from your job because it had already 

been discarded on the remote system. 


Message: 

**DDP4250 DDP was unable to deliver the output from your job because it has already 

been printed or punched locally. 


Message: 

**DDP4260 Your command has been canceled by the console operator or by another user. 


Message: 

**DDP4270 Your command could not be CANCELed because it has already completed or 

aborted. 


Message: 

**DDP4280 Your command could not be CANCELed because it has already been 

CANCELed by the console operator or another user. 

2-48 3787 3528-200


Message: 


**DDP4290 Your CANCEL request has been performed, but output could not be deleted on 

the executing host. 


Message: 

**DDP4300 DDP encountered an RSI error when attempting to CANCEL your job. The RSI 

terminal used by the DEMANDID may have been terminated. If this problem persists, 

contact your systems personnel. 


Message: 

**DDP4310 DDP encountered an RSI error when attempting to STATUS your job. The RSI 

terminal used by the DEMANDID may have been terminated. If this problem persists, 

contact your systems personnel. 


Message: 

**DDP4320 DDP was unable to CANCEL the requested job because it has already been 

terminated. 


Message: 

**DDP5000 The status of your job job-id is not known. 


Message: 

**DDP5010 The status of your job job-id is completed. 


Message: 

**DDP5020 The status of your job job-id is not started. Its job state is job status. 

3787 3528-200 2-49



Message: 

**DDP5030 The status of your job job-id is in progress. Its job state is job status. The 

program program-name is currently executing. 


Message: 

**DDP5040 The status of your job job-id is not available. 


Message: 

**DDP5050 The status of your command command-id is completed successfully. 


Message: 

**DDP5055 The status of your command command-id is aborted with the following 

results: 


Message: 

**DDP5060 The status of your command command-id is in progress. Tracks have been 

transferred. It is percentage complete. 


Message: 

**DDP5065 The status of your command command-id is scheduled for execution at time 

local time on the SOURCE (From) host. 


Message: 

**DDP5070 The status of your command command-id is canceled. 


Message: 

**DDP5080 The status of your command command-id is queued. 

2-50 3787 3528-200


Message: 

**DDP5090 The status of your command command-id is not found. 


Message: 

**DDP5095 The status of your command command-id is unavailable. 

Explanation: 


You may have mis-typed the command-id, or it may be too old for DDP-FJT to remember. 


Message: 

**DDP5100 The status of your command command-id is in progress. Number elements 

have been transferred. Number percent completed. 


Message: 

**DDP5110 Your command has completed successfully. 


Message: 

**DDP5120 You may issue a STATUS request to check on the progress of your command. 


Message: 

**DDP5130 Your command has been scheduled by the source host. Please wait. 


Message: 

**DDP5300 The job ids submitted are: job-id-list 

Explanation: 

This message is returned after a SUBMIT command. The job-ids may be used to cancel or 

obtain the status of a job. 

3787 3528-200 2-51



Message: 

**DDP6200 Your command-id is: command-id 

Explanation: 

This message is returned after a COPY, SPOOL, or RESTART command. The command-id 

may be used to restart, cancel or obtain the status of a command. 


Message: 

**DDP8010 You failed to specify whether you wish to CANCEL a Job, Command, or 

Checkpoint. 


Message: 

**DDP8020 You may specify only one of the Job, Command, or Checkpoint options. 


Message: 

**DDP9010 You failed to specify whether you wish to STATUS a Job, a Command, or a list 

of DDP hosts. 


Message: 

**DDP9020 You may specify only one of the Job, Command, or Network options. 


Message: 

**DDP9025 No command-ids were found which match your user-id. 


Message: 

**DDP9030 DDP cannot RESTART this SPOOL command because the temporary file 

created by DDP to hold the spooled output has been deleted on host host-id. 

2-52 3787 3528-200


Message: 


**DDP9040 Your command has been rejected because you failed to supply logon 

information (USERID, PASSWORD, etc.) for the {Source/Destination/Requested} host and 

that host requires logon information. 


Message: 

**DDP9050 Your command could not be processed because one of the hosts specified in 

your command has exhausted its buffer space. 

Explanation: 

Memory unavailable. 


Message: 

**DDP9060 Your command could not be processed because the SOURCE host named in 

your command has no configured paths to the DESTINATION host, or the DESTINATION 

host does not support DDP File and Job Transfer. 

Action: 

Make sure you spelled the host name correctly. If it is correct, check with the DDP 

administrator for the source file host to see if the destination host is not configured in the 

DDP-PPC configuration services database or is configured as a host type that is not 

supported by DDP-FJT. 


Message: 

**DDP9070 Your CANCEL CHECKPOINT request could not be processed because the 

command specified by the CHECKPOINT parameter is currently executing. 

Explanation: 

You cannot cancel the checkpoint feature of a command while the command is active. 

Action: 

Wait until the command completes, or cancel the command first. 

3787 3528-200 2-53



Message: 

**DDP9080 Your SPOOL request could not be processed because the file named in your 

request is a temporary file or a program file. Temporary files and program files cannot be 

SPOOLed. 


Message: 

**DDP9090 Your SPOOL request could not be processed because you have requested that a 

print file be SPOOLed to a punch device, or you have requested that a punch file be 

SPOOLed to a print device. 

Action: 

Check your command request or configuration file. 


Message: 

**DDP10000 The file you requested may not be SPOOLed. Possible reasons are: 

(1) The file is a system file or a non-spoolable file. 

(2) The file is in a +1 state, or has its drop flag set. 

(3) The file is a print file with no main item. 


Message: 

**DDP10010 Your command could not be processed because a file specified in your 

command has been DISABLED by the EXEC. The file must be ENABLED before DDP File 

and Job Transfer can access it. 

Action: 

If the file is in your local host, try @ENABLE. 

2-54 3787 3528-200


Message: 


**DDP10020 DDP-FJT on the queue or execution host detected an error while attempting 

to use the print/punch device in your command. 

Explanation: 

If your command was a: 

$ SPOOL, the specified print/punch device was not configured 

$ SUBMIT, the print/punch device was the same as the routing-queue specification on 

the ROUTING-Q record for the execution host in the execution host’s configuration. 


Message: 

**DDP10030 Your command could not be processed because there is a bad SDF control 

word in your FROM file. 


Message: 

**DDP10040 Your RESTART request could not be processed because the SOURCE file used 

in the original command has been modified since the termination of the original command. 


Message: 

**DDP10050 Your RESTART request could not be processed because the DESTINATION 

file used in the original command has been modified since the termination of the original 

command. 


Message: 

**DDP10060 The source file is too large to be copied into the destination element. The size 

of your source file is greater than the maximum size allowed for elements on the 

destination host. 

3787 3528-200 2-55



Message: 

**DDP15010 Use this field to type the command code of the DDP-FJT command you wish 

to use. The command codes precede the command name on the MAIN MENU, and must be 

typed exactly as they appear. You do not have to fill in this field. 


Message: 

**DDP20000 DDP has received an unexpected error from the remote host. The exact 

internal status code is error-code. 

The processing of this command has been terminated. Re-entering this same command 

may lead to similar results. 

Explanation: 

See Appendix A for DDP-FJT internal error codes. 


Message: 

**DDP20010 DDP created an invalid protocol message. The work order error returned by 

the remote host was error-code. 

The processing of this command has been terminated. Re-entering this same command 

may lead to similar results. 

Explanation: 


2-56 3787 3528-200


Message: 


**DDP20020 *IPF ERROR* Service module error error-code. The associated data is data. 

Explanation: 


The processing of this request is incomplete. Further requests of this type may lead to 

similar results. 

Action: 

Report the associated technical information to your systems personnel. 


Message: 

**DDP20030 *IPF ERROR* Service module error error-code. The associated data is data. 

Explanation: 


The processing of this request is incomplete. Further requests of this type may lead to 

similar results. 

Action: 

Report the associated technical information to your systems personnel. 


Message: 

**DDP20040 Your IPF session is no longer connected to DDP. Log off from IPF, then 

re-enter IPF and retry your command. 

Explanation: 

The probable cause of this error is that the DDPMASTER run was terminated and restarted 

while your IPF session remained active. 

3787 3528-200 2-57



Message: 

**DDP20050 *IPF ERROR* The address of a file name specified by the service module is in 

error. 

Explanation: 

The processing of this request has been terminated. Further requests of this type may lead 

to similar results. 

Action: 

Report error to your systems personnel. 


Message: 

**DDP20060 Your command has abnormally terminated because the DDP conversation 

between your local host and the remote host has been aborted. 

Explanation: 

If this was a COPY command, the TO file may be too small to hold the amount of data 

requested. 

Action: 

Check the file and retry. 

2-58 3787 3528-200


Message: 


**DDP20070 A network failure occurred causing DDP to be unable to continue sending 

messages. The possible causes are: 

(1) The DDP transport server is down or CMS process may be down. 

(2) There is excessively heavy use of the DDP network. 

(3) The master run has terminated. 

(4) The conversation that DDP-FJT was using to execute your command was aborted. In 

this case, if you retry the command, it may be successful. 

DDP-PPC network error status code was logged in the DDP Log File. 

Action: 

Check the DDP-PPC log file for the error status code and see Section 3for an explanation. 


Message: 

**DDP20080 The DDP conversation has abnormally terminated. A possible cause is that 

the DDP run on the host you wish to go to has abnormally terminated. You must restart the 

DDPMASTER run on that host and re-enter your command. 

Another cause could be that a network error aborted the conversation. In this case, if you 

retry the command, it may be successful. 


Message: 

**DDP20090 DDP File and Job Transfer is not available on the remote system. The 

DDPMASTER run has not been started or has abnormally terminated. 


Message: 

**DDP20100 Network Interface Error - MCP status status-code returned on 

request-number. 

Explanation: 

See Section 3 for an explanation of the status code. 

3787 3528-200 2-59



Message: 

**DDP20110 The ROUTING-Q record batch-id associated with the execution host in the 

DDP-PPC configuration services database is not a valid station-id for that host. This is NOT 

a recoverable error. You have a problem in one or more of the following areas: 

(1) The ROUTING-Q station-ids in your DDP-PPC configuration services database are 

invalid on the host. 

(2) RSI sign-on is illegal for your account/user-id. 

(3) The site-id is syntactically incorrect (illegal character or blank). 

(4) The RSI device is not configured. 

(5) The device specified is not an RSI device. 

(6) The RSI exists, but there was an error when signing on the device. The device itself may 

be bad. 

(7) You have NO ROUTING-Q records in your CS database. Without these, DDP will do NO 

SYM or SUBMIT processing. 


Message: 

**DDP20120 DDP is unable to process your command because the batch RSI on the 

executing host is temporarily unavailable. Some possible causes are: 

(1) The site-id is already active or already signed on with another run. 

(2) Another SUBMIT command is using the site-id you require. 

(3) Initialization of the RSI cannot be done due to EXEC storage limits. 

(4) The maximum number of RSI$ terminals are already active. Please re-enter your 

command later. 

2-60 3787 3528-200


Message: 


**DDP20130 DDP was unable to open a conversation to perform the requested function. 

Some possible causes for this are: 

(1) The local or remote DDP process is down. 

(2) A DDP, CMS, or Telcon configuration error exists. 

(3) The CMS or Telcon transport network is down. 

(4) An improperly configured network exists. 

DDP-PPC network error status-code was logged in the DDP Log File. 

Explanation: 

See Section 3 for an explanation of the DDP-PPC status code. 


Message: 

**DDP20140 A network failure has occurred causing DDP to be unable to close the 

conversation that was opened for this function. 


Explanation: 



Message: 

**DDP20150 DDP encountered an error while trying to create the protocol messages 

needed to process your command. The processing of this command is terminated. 

Re-entering this same command may produce similar results. 

3787 3528-200 2-61



Message: 

**DDP20160 DDP was unable to get a close confirm for the conversation that was opened 

for this command. 


Explanation: 



Message: 

**DDP20170 DDP received a bad status from MCP while waiting for a reply on the 

conversation that was opened for this command. 

Possible causes for this are: 

(1) The remote DDPMASTER or worker RSI run has terminated. 

(2) A time-out occurred while waiting for the remote DDP run to reply. 

(3) The conversation DDP-FJT used for your command was aborted by the network. 


Explanation: 



Message: 

**DDP20180 This command has not completed in the allocated time. 

(1) The DDPMASTER run has terminated. 

(2) The DDPMASTER run was executing at too low of a priority. Because of this, it 

was not getting enough processing time to complete the command. 


Message: 

**DDP20190 An entry for your function is not contained in a DDP internal table. 

2-62 3787 3528-200


Message: 


**DDP20200 A remote host encountered an error attempting to allocate the buffer space 

required to process your command. This is a fatal error and your command has been 

terminated. Re-entering this same command may lead to similar results. 


Message: 

**DDP20210 A remote host encountered an error attempting to free the buffer space 

acquired during the processing of your command. This is a fatal error and your command 

has been terminated. Re-entering this same command may lead to similar results. 


Message: 

**DDP20220 The source or destination host encountered an error in the DDP File and Job 

Transfer protocol messages used for record control information during the processsing of 

your command. This is a fatal error and your command has been terminated. Re-entering 

this same command may lead to similar results. See message DDP20221 for additional 

information. 


Message: 

**DDP20221 This error has been entered in the DDP Log File on the host where the error 

occurred. 


Message: 

**DDP20230 The source or destination host detected a sequence error in the DDP File and 

Job Transfer protocol messages used for record control information during the processing 

of your command. 

This is a fatal error and your command has been terminated. Re-entering this same 

command may lead to similar results. See message DDP20231 for additional information. 


Message: 

**DDP20231 This error has been entered in the DDP Log File on the host where the error 

occurred. 

3787 3528-200 2-63



Message: 

**DDP20240 The DDP conversation used to process your command was aborted by one of 

the remote hosts. Possible causes are: 

(1) The DDPMASTER processor on the remote host has aborted. 

(2) A run started by DDP to process your command has aborted. 

(3) Your RSI worker run on the remote host was canceled by the operator. 


Message: 

**DDP20250 Your DDP File and Job Transfer command cannot be processed at this time 

because the DDPMASTER processor is not executing on your system. 


Message: 

**DDP20260 The DDP conversation that was copying your submitted job stream to another 

host has erred. The SUBMITTED job is incomplete. DDP will attempt to remove it. It will 

not be run. 


Message: 

**DDP20270 You entered a JOBNAME that was longer than the allowable number of 

characters. Please re-enter your command with a valid jobname. 


Message: 

**DDP20280 The print-host and the punch-host cannot be different hosts. Please reenter 

your command with identical print-host and punch-host values. 


Message: 

**DDP20290 The print-host or the punch-host specified in a SUBMIT request has not been 

configured at the EXECUTION host. 

2-64 3787 3528-200


Message: 


**DDP20300 Your command could not be processed because the memory required to 

register a DDP user is temporarily unavailable. Please try again later. 


Message: 

**DDP20400 DDP could not register your session for an IPF termination trap. 


Message: 

**DDP20500 Your command could not be processed because DDP was unable to register 

for TRMRG processing. 


Message: 

**DDP20600 Your CREATE command was processed successfully, however, DDP 

encountered a security warning during the processing of your request. 


Message: 

**DDP21000 DDP was unable to access your SOURCE file because of a security violation. 


(1) The security information you supplied does not allow access to the file. 

(2) You did not supply any security information and the default supplied by DDP 

does not allow access to the file. 


Message: 

**DDP21010 DDP was unable to access your DESTINATION file because of a security 

violation. Possible causes are: 

(1) The security information you supplied does not allow access to the file. 

(2) You did not supply any security information and the default supplied by DDP does not 


3787 3528-200 2-65



Message: 

**DDP21020 You have entered an illegal character in the SPOOL BANNER-ID. The 

allowable characters are: numbers, letters, $, *, or - . 


Message: 

**DDP21030 *WARNING* Your request for immediate control of your console and/or your 

request for a delayed start on a command has been ignored because the File and Job 

Transfer facility on the source host does not support these functions. Control will be 

defaulted to complete and your command will be started immediately. 


Message: 

**DDP23000 *Warning* The job name(s) listed above may not have executed because FJT 

encountered the following error during the SUBMIT. 


Message: 

**DDP23010 DDP-FJT cannot process your SUBMIT command because there are no 

entries available in the DDP-FJT JOB NAME table. Either you have SUBMITs running that 

have not yet FINNED, or the print out from FINNED jobs has not been printed. You might 

try printing some of your SUBMITted output and then re-SUBMIT your command. 


Message: 

**DDP262000 This completes the message series. Type a ? to repeat the series. 


Message: 

**DDP262010 There are no optional parameters for this command. 

2-66 3787 3528-200

Section 3 

Status Codes Returned to 

DDP-PPC/DDP-FJT Programs 

DDP-PPC and program-callable DDP-FJT always return a class code and usually a detailed 

status code after each function call issued by your application program. The DDP-PPC OSI 

and DCA interfaces also return a specific error code. 

DDP-PPC and DDP-FJT place these codes into the information packets of your COBOL, C 

language, or FORTRAN application program. Your application program should then test 

the contents of these fields and perform routines to handle the conditions indicated by 

them.This section lists the decimal and octal values of all the status codes that can be 

reported to your program. Status codes are returned in the octal format aaabbb or aaa bbb 

cccccc, where: 

aaa 

Is the class code 

bbb 

Is the detailed status code 

cccccc 

Is the specific error code. It provides additional information for some error codes. 

When the specific error is 0, no additional information is available. 

Specific errors are also recorded in the DDP-PPC log file in the format: 

 

You may receive DDP-PPC status codes from other software products that work with 

DDP-PPC. For example, errors with class codes 6, 7, and 8 may be returned by OSI-FTAM 

or OSI-MHS. 

The detailed status code received in your DDP-FJT COBOL program is also used as an 

index to Table A-1. This provides a cross-reference to messages in Section 2. 

3787 3528-200 3-1

Status Codes Returned to DDP-PPC/DDP-FJT Programs 

CLASS-CODE DETAIL-STATUS Explanation 

Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

0 0 0 0 Normal completion for file and job transfer 

functions. 

0 0 X X When using Single Message Transfer via the MCB, 

an error occurred calling MCB; X represents the 

MCB error. 

1 1 0 0 Program-to-program application, normal 

completion. 

1 1 5 5 The types you specified in the COPY FILE TYPE 

field conflict. You must specify the DDPFILE and 

UNDEFINED types by themselves. 

1 1 16 20 The types you specified in the PURGE ELEMENT 

TYPE field conflict. You must specify type ALL by 

itself. 

1 1 17 21 The value that was filled in for the 

CREATE-ACCESS-TYPE is invalid. You may only 

specify a 1 for PUBLIC or a 0 for PRIVATE. All 

other values are invalid. 

1 1 18 22 You specified an invalid value for the COPY 

POSITION TYPE. You may only specify a 1 for ADD, 

or a 2 for REPLACE. All other values are invalid. 

1 1 19 23 You specified an invalid value for the COPY 

TRANSLATE TYPE. You may only specify a 1 for 

ASCII,a2forEBCDIC,ora9forTRANSPARENT. 

1 1 20 24 You specified an invalid value for the CONTROL 

RETURN. You may only specify 0 for COMPLETE or 

a 1 for IMMEDIATE. 

1 1 21 25 You specified an invalid value for the SPOOL 

DEVICE TYPE. You may only specify a 0 for PRINT, 

or a 1 for PUNCH. 

1 1 22 26 You specified an invalid value for the SUBMIT 

TYPE. You may only specify a 0 for SYMBOLIC, or 

a 1 for DDPFILE. 

3-2 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

1 1 23 27 You specified an invalid value for the STATUS 

ACTION. You may only specify a 0 for STATUS JOB 

or a 1 for STATUS COMMAND. 

1 1 24 30 You specified an invalid value for the CANCEL 

OUTPUT DISPOSITION. You may only specify a 1 

for DISCARD or a 2 for DELIVER. 

1 1 25 31 You specified an invalid value for the CANCEL 

ACTION. You may only specify a 0 for CANCEL 

JOB, a 1 for CANCEL COMMAND, or a 2 for 

CANCEL CHECKPOINT. 

1 1 26 32 You specified an invalid value for one of the 

CREATE size fields. The INITIAL SIZE, MAXIMUM 

SIZE, and GRANULARITY SIZE must all be positive 

numbers that are less than 262144. 

1 1 64 100 You did not fill in the CANCEL JOB NAME field. You 

must fill in this field when you specify a cancel job 

action on a cancel function request. 

1 1 65 101 You did not fill in the CANCEL COMMAND ID field. 

You must fill in this field when you specify a cancel 

command action on a cancel function request. 

1 1 66 102 You did not fill in the CANCEL CHECKPOINT ID field. 

You must fill in this field when you specify a cancel 

checkpoint action on a cancel function request. 

1 1 67 103 You did not fill in the CREATE FILE NAME field. You 

must fill in this field when you issue a create 

function request. 

1 1 68 104 You did not fill in the PURGE FILE NAME field. You 

must fill in this field when you issue a purge 


1 1 69 105 You did not fill in the COPY FROM FILE NAME field. 

You must fill in this field when you issue a copy 


3787 3528-200 3-3



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

1 1 70 106 You did not fill in the COPY TO FILE NAME field. 

You must fill in this field when you issue a copy 


1 1 71 107 You did not fill in the STATUS JOB NAME field. You 

must fill in this field when you specify a status job 

action on a status function request. 

1 1 72 110 You did not fill in the STATUS COMMAND ID field. 

You must fill in this field when you specify a status 

command action on a status function request. 

1 1 73 111 You did not fill in the SUBMIT FILE NAME field. You 

must fill in this field when you issue a submit 


1 1 74 112 You did not fill in the RESTART CHECKPOINT ID 

field. You must fill in this field when you issue a 

restart function request. 

1 1 75 113 You did not fill in the SPOOL FILE NAME field. You 

must fill in this field when you issue a spool 


2 2 0 0 The DDP-PPC network tables have not been 

initialized. The PPCMASTER run is not executing. 

2 2 1 1 The calling program did not issue a BIND request 

to the DDP network. A program must issue a BIND 

request to the network before attempting any 

other command. 

2 2 2 2 The calling program is already bound to the 

DDP-PPC network. DDP-PPC ignores a BIND 

request if the program is already bound. 

2 2 3 3 The maximum number of calling programs has 

been reached. No more resources are available 

until an active program unbinds. 

3-4 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

2 2 4 4 The IPC-INT-AP-NAME field in the 

IPC-REGISTER-PKT is invalid - must be 12-character 

ASCII string, left- justified, blank-filled, A to Z, 0 to 

9, $ (dollar sign), and - (hyphen).+ 

2 2 5 5 The PPCMASTER run has been terminated. 

2 2 6 6 The message buffer address and/or packet 

addresses are not above 0100000. 

2 2 7 7 The message buffer does not reside entirely in one 

of the based banks. 

2 2 8 10 The IPC-BUFFER-OFFSET field in the IPC-DATA-PKT 

is not a multiple of 4. 

2 2 9 11 The IPC-TEXT-START field in the IPC-DATA-PKT is 

not a multiple of 4 or is beyond the end of the 

message. 

2 2 10 12 Reserved for internal use. 

2 2 11 13 A user program with your user-id has already 

issued a BIND request to the network. 

2* 2 12 14 The PPCMASTER OSITSU/TASTSU component is 

not up. 

2* 2 13 15 The DCA open request that DDP-PPC issued for 

your command/function was rejected or the DCA 

Transport connection that DDP-PPC used for your 

command or function was disconnected. Possible 

causes are: 

$ TheremoteDCAterminationsystem(HOSTor 

DCP) is or went down. 

$ The local CMS or the remote DCA termination 

system (HOST or DCP) rejected the open 

request. 

$ A transport disconnect was sent by the 

remote termination system without the 

necessary session/IPC layer protocol. 

2 2 14 16 Access to the IPC-AP-ALIAS or IPC-QUEUE-NAME is 

restricted. The value in one or both of these fields 

must be changed before reissuing the command. 

*Fatal error - conversation is aborted. 

3787 3528-200 3-5



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

2* 2 15 17 The value in the IPC-USER-ID field does not match 

the value returned by the BIND command. The 

user program must terminate and restart. 


2* 2 17 21 DDP, CMS, and Telcon are configured improperly. 

Check that the transport names, network names, 

and network numbers are used consistently in all 

three configurations. 

2 2 18 22 The banks based when DDP-PPC is called. May not 

have overlapping addresses. 

2 2 19 23 The transport connection has been closed, but one 

or more messages exist on the input queue. The 

user program should receive the input messages 

until an abort is received or issue an abort. 

2 2 24 30 A basic mode user was unable to access the 

DDP-PPC subsystem due to an error returned from 

URTS. The specific error field of the status packet 

contains the URTS error value. 

2 2 25 31 A Called Transport parameter was supplied on the 

OPEN function, but the level of CMS 1100 on the 

system does not support this feature. Use of the 

Called Transport feature requires a CMS 1100 with 

TSAM interface level 4. 

3 3 - - Request not accepted (IPC). 

3 3 2 2 For DCA applications, the IPC-IP-STATION-ALIAS 

field is not defined in the DDP-PPC configuration, 

or the CALLED-HOST-NAME is not valid. 

For OSI applications, either the 

OSI-CALLED-S-SELECTOR or the 

OSI-CALLED-T-SELECTOR parameter is invalid, or 

both parameters are missing valid values. 

Valid names may include alphanumeric characters, 

the hyphen, and the dollar sign. 

*Fatal error - conversation is aborted. A peer program is given a CLASS-CODE 204 (octal) 

and a DETAIL-STATUS 2 (octal). 

3-6 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

3* 3 4 4 A parameter in one of the user’s packets is set to 

an unknown value. Check packets for proper 

values. 

3* 3 5 5 A parameter in one of the user’s packets is a legal 

value, but not permitted for the current state of the 

conversation. 

3 3 6 6 The IPC-CONNECTION field in the IPC-DATA-PKT is 

not known to DDP-PPC. 

3 3 7 7 Insufficient resources exist to perform the 

command. The request should be retried. If this 

error occurs frequently, consider increasing the 

size of the DDP-PPC common banks. See the 

DDP-PPC Implementation and Administration Guide 

for instructions. 

3 3 8 10 The peer program has sent an EXCEPTION 

message. This message must be received before 

the user program may resume sending data. 

3 3 9 11 The peer program has sent an ABORT message. 

This message must be received before the 

connection is terminated. 

3* 3 10 12 A command was issued that is inconsistent with 

the state of the connection. 

3 3 11 13 An unknown command was issued. 

3 3 13 15 No input message is available at this time. The 

receive command should be retried, perhaps with 

a longer wait time specified. 

3 3 14 16 The IPC-QUEUE-NAME field must match the 

IPC-INT-AP- NAME field used in the 

IPC-REGISTER-PKT on the BIND. 


3 3 16 20 A DDP$DUMP file could not be allocated. 



3787 3528-200 3-7



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

3 3 17 21 The OSI-VERSION specified in the OSI-STATUS-PKT 

is not 1536 or 1537. 


3 3 19 23 A required user packet is missing. 

3 3 20 24 The peer program has sent a SYNC-ACK message. 

This message must be received before continuing 

to output. 

3 3 21 25 The peer program has sent a EXCEPTION-DATA 


continuing to output. 

3 3 22 26 A TAKE-CONVERSATION function was issued, but 

no conversations are being held as a result of a 

previous GIVE-CONVERSATION function. 

3 3 23 27 ThepeerprogramhassentaRESYNCACK 


continuing output. 

3 3 24 30 A command has been issued that DDP-PPC cannot 

process currently because the sending or receiving 

of a segmentation message is in progress. 

3 3 25 31 Output flow control timeout. DDP-PPC is unable to 

initiate current output request because the output 

enqueue count cannot exceed the message 

threshold value for the period of time specified in 

the user data packet. 

3 3 26 32 Duplicate setup request. 

When the SETUP option is: 

2 The calling activity previously 

issued a successful SETUP 

command with option=2 

1 or 3 There is already a 

user_hold_ap_copy record with 

the same specified in the 

user_hold_ap_name parameter. 

3-8 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

3 3 27 33 No input pending queue. 

There is no input pending queue allocated for the 

specified input_pending_id and 

input_pending_id_type parameters. Either the 

SETUP function was never issued to allocate the 

input pending queue or the activity that set up the 

input pending queue had already terminated. 

3 3 28 34 No input pending. 

There is no input available for the specified input 

pending id. 

3 3 29 35 Input pending queue term. 

The DDP-PPC user activity that set up the input 

pending queue is in the process of terminating. 

3 3 30 36 The queue name provided for a GIVE/TAKE 

function does not exist. Issue a setup function for 

this queue before using a GIVE/TAKE function. 

4 4 - - Conversation aborted locally (IPC). 

4* 4 2 2 DDP-PPC detected an error in the lower levels of 

the network. 

A procedural error occurred in the network that 

caused DDP-PPC to receive an unexpected 

message. 

If you are using the OSITS program product, 

process the DDP-PPC log file; turn on DDP-PPC, 

CMS, and OSITS traces and recreate the problem. 

If you are not using OSITS, turn on CMS and 

DDP-PPC traces and recreate the problem. Then 

take a CMS and DDP-PPC dump. 

If the problem persists, reinitialize the network. 

See the DDP-PPC Implementation and 




3787 3528-200 3-9



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

4* 4 4 4 DDP-PPC internal error. Check the DDP-PPC log file 

for additional information if the problem persists. 

Take a DDP-PPC dump and reinitialize DDP-PPC. 

See the DDP-PPC Implementation and 


5 5 1 1 Parameter error. 

A fatal parameter error was detected. 

5 5 2 2 Temporarily unable to service your request. Please 

retry. 

DDP cannot service your request at this time 

because, either a host you wish to use is not 

available, or DDP does not have enough storage 

available to complete your command. 

5 5 3 3 Function code not supported. 

The remote host does not support the function. 

5 5 4 4 Work order header in error. 

DDP created an invalid work order. Set the DDP 

traces to FJT,3 on all hosts involved with this 

function and retry the function. The trace files and 

the corresponding log files should provide 

sufficient documentation to be analyzed by your 

Unisys representative. 

5 5 5 5 Work order class not supported. 


traces to FJT,3 on all hosts involved with this 

function and retry the function. The trace and 

corresponding log files should provide sufficient 

documentation to be analyzed by your Unisys 

representative. 



3-10 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 6 6 Checkpoint protocol error. 

DDP-FJT encountered an invalid protocol message. 

Set the DDP traces to FJT,3 on all hosts involved 

with this function and retry the function. The trace 

file and corresponding log file should provide 

sufficient documentation to be analyzed by your 

Unisys representative. 

5 5 11 13 Open error. 

DDP was unable to open a conversation to perform 

this function. Possible causes for this are: 

5 5 12 14 Close error. 

5 5 13 15 Send error. 

$ The local or remote PPCMASTER OSITSU 

component or DDP process is down. 

$ A DDP, CMS, or Telcon configuration error. 

$ The CMS or Telcon transport network is down. 

A network failure has occurred, causing DDP to be 

unable to close the conversation that was opened 

for this function. 

A network error has occurred, causing DDP to be 

unable to continue sending messages. This may 

be caused by: 

$ The local or remote DDPMASTER or RSI 

worker run terminating 

$ The remote host going down 

$ An improperly configured network 

5 5 14 16 Close-confirm error. 

$ The conversation that DDP-FJT used to 

execute your command was aborted 

DDP was unable to get a close confirm for the 

conversation that was opened for this command. 

3787 3528-200 3-11



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 15 17 Message build error. 

An error occurred while building a message to be 

sent to the destination host. DDP cannot finish 

processing this command. 

5 5 16 20 Reply-wait error. 

DDP received a bad status from MCP while waiting 

for a reply on the conversation that was opened 

for this command. Possible causes for this are: 

$ The remote DDPMASTER or worker RSI run 

has terminated. 

$ A timeout occurred while waiting for the 

remote run to terminate. 

5 5 17 21 Abort. 

The local or remote master run has abnormally 

terminated during processing of this function. You 

mustrestarttheDDPMASTERrunonthathostand 

re-execute the function or the conversation that 

DDP-FJT was using for your command was 

aborted. This may be a temporary condition. Retry 

the command. 

5 5 18 22 Timeout. 

This function did not complete in the allocated 

time. It could have been caused by: 

$ DDPMASTER or worker RSI run terminating 

$ DDPMASTER run executing at too low a 

priority, thus not getting enough processing 

time 

5 5 19 23 Work order report error. 


traces on all hosts involved with this function and 

retry the the function. The trace and corresponding 

log files should provide sufficient documentation to 

be analyzed by your Unisys representative. 

3-12 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 20 24 Reply wait new error. 

An entry for your function is not contained in a DDP 

internal table. 

5 5 21 25 Allocate buffer error. 

A DDP routine that allocates buffer space has 

encountered an error. 

5 5 22 26 Deallocate buffer error. 

A DDP routine that deallocates buffer space has 

encountered an error. 

5 5 23 27 RCI message error. 

DDP created an invalid record control information 

message. Set the FJT traces to FJT,3 on all hosts 

involved with this function and retry the function. 

The trace files and corresponding log files should 

provide sufficient documentation to be analyzed by 

your Unisys representative. 

5 5 24 30 RCI message missing. 

DDP sent a message out of sequence. 


message. Set the Set the FJT traces to FJT,3 on 

all hosts involved with this function and retry the 

function. 




3787 3528-200 3-13



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 25 31 Text message missing. 

DDP sent a message out of sequence. 


message. Set the Set the FJT traces to FJT,3 on 

all hosts involved with this function and retry the 

function. 




5 5 26 32 Write file error while copying submitted job stream 

to the executing host. Error has been logged in the 

DDP-PPC log file. 

5 5 27 33 Site-id not available. 

The first ROUTING-Q associated with the 

SUBMIT-EXECUTION-HOST in the Configuration 

Services file is not valid for that host. This is not a 

recoverable error. Possible causes are: 

$ ThenameoftheROUTING-Qisthe 

Configuration Services database on the 

execution host corresponding to the print 

host-id is invalid. (Not in EXEC config.) 

$ The RSI sign-on is invalid for your 

account/user-id 

$ The site-id is syntactically incorrect; that is, 

contains an illegal character or a blank) 

$ The RSI device is not configured 

$ The RSI device exists, but there was an error 

when signing on. 

3-14 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 28 34 Site-id in use. 

Your command has timed out waiting for your 

batch RSI on the SUBMIT-EXECUTION-HOST to 

become available. The problem is one of the 

following: 

$ Initialization of the RSI cannot be done 

because of EXEC storage limits 

$ The maximum number of RSI$ terminals are 

already active. 

$ A previous submit command is using the 

site-id you require. 

Please try your request again later. 

5 5 29 35 Job name return error. 

An error occurred while the SUBMIT-FILE-HOST 

was attempting to send the submitted job names 

back to your program. 

5 5 30 36 The DDPMASTER or worker RSI run on the remote 

host has aborted. 

A probable cause is that the remote DDPMASTER 

run abnormally terminated, or the RSI started by 

DDP to process your command has aborted, or 

the RSI started by DDP to process youir command 

has been cancelled by the operator. 

5 5 31 37 Your DDP$COPY function has not completed in the 

allocated time. The copy may still be in progress. 

3787 3528-200 3-15



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 32 40 No response was received from the destination 

host in the allotted time. 


$ DDP-FJT is not available on the remote host. 

$ The master run or worker RSI on the remote 

host is at too low apriority or is overloaded 

with work. 

$ A network error prevents receipt of a 

response from the destination host. 

5 5 34 42 DDP encountered an error during the passoff of a 

conversation used to process your command. 

5 5 35 43 DDP received a bad status from MCP while waiting 

for a reply on the conversation that was opened 

for this command. 


$ The remote DDP master run or worker RSI 

was terminated. 

$ A timeout occurred while waiting for the 

remote DDP run to reply. 

5 5 36 44 Exception error. 

DDP encountered an error in sending an exception 

message on the conversation used to process 

your command. 

Check the DDP Log File for the error. 

5 5 37 45 Receive error. 

DDP encountered an error in receiving a message 

during the processing of your command. 

Check the DDP Log File for the error. 

3-16 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 38 46 Signon error. 

DDP was unable to sign on an activity to process 

your command. 

Check the DDP-PPC log file for the error. 

5 5 39 47 Your DDP-FJT command cannot be processed at 

this time because the DDPMASTER processor is 

not executing on your system. 

5 5 40 48 DDP-FJT is not available on the remote system. 

The DDPMASTER run has not been started or has 

abnormally terminated. 

5 5 41 51 Your command could not be processed because 

one of the hosts specified in your command has 

exhausted its buffer space. 

Memory is unavailable. 

5 5 45 55 The checkpoint identifier checkpoint-id cannot be 

found in the source checkpoint file on the named 

host-id. You entered an incorrct command-id, the 

command has already completed, or the 

DDPMASTER was brought up cold. 

5 5 46 56 The checkpoint identifier checkpoint-id cannot be 

found in the destination checkpoint file on the 

named host-id host-id. You entered an incorrect 

command-id, the command has already completed 

on the destination host, or the DDPMASTER was 

brought up cold. 

5 5 47 57 The checkpoint identifier checkpoint-id was found 

on both the source and destination host systems. 

However, a common established checkpoint did 

not exist in the files. 

5 5 49 61 No security information was supplied to a host that 

requires one. 

5 5 50 62 The command could not be processed because 

DDP-FJT was unable to log on a run with the 

access information you specified. Please try again 

with the correct access information. 

3787 3528-200 3-17



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 


DDP-FJT was unable to log on to the system you 

have specified because the access information 

being used in the system has expired. 

5 5 53 65 The command could not be processed because 

DDP-FJT was unable to log on a run to process 

your command on the remote host system. This 

maybebecausetheremoteoperatorplaceda 

hold on demand runs or terminals. Please try again 

at a later time. 

5 5 54 66 DDP-FJT was unable to log on a run to process 

your command because the system you are 

attempting to access does not use standard 

OS 2200 messages in the logon sequence. 

5 5 55 67 The user-id specified on your command is 

configured to automatically execute a program at 

logon time. A user-id configured in this manner 

cannot be used by DDP-FJT. 

5 5 56 70 The program RCA$WORKER$ was not found in the 

DDP-FJT absolute file, or the user-id under which 

your command is running could not access the 

DDP-FJT absolute file for security reasons. This 

may be the result of an installation error or 

someone may have accidentally deleted the 

program absolute. 

Please notify your system administrator to correct 

the problem. 

5 5 57 71 The DDP-supplied program RCA$WORKER$ 

abnormally terminated during initialization. 

This error has been logged in the DDP-PPC log file. 

5 5 58 72 DDP-FJT was unable to process your command 

because the maximum number of RSI’s has been 

reached. If you are the system administrator, 

increase the EXEC configuration parameter 

RSICNT. 

3-18 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 


because the remote system will not allow DDP-FJT 

to log on a run due to an EXEC EXPOOL problem. 


due to an error in the EXEC RSI component on the 

remote host. 

Check the DDP-PPC log file and report the error. 


the maximum allowable number of DDP-FJT job 

workers has been exceeded on one of the hosts in 

your command. 

Please ask your system administrator to increase 

the number of workers, or try your command again 

at a later time. 


the maximum allowable number of DDP-FJT 

delayed workers has been exceeded on the source 

host in your command. Try the command later. 

5 5 70 106 The PPCMASTER OSITSU component or DDP 

process on the remote host is down. 

Remote processing to other hosts in the network 

or to the local host is unavailable. 

5 5 71 107 The PPCMASTER OSITSU component or DDP 

process on the local host is down. Only local DDP 

processing is available until the DDP transport is 

brought up. 

3787 3528-200 3-19



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 72 110 DDP encountered an unrecoverable communication 

network error with the remote host. 


$ The TRANSPORT keyword value on the 

REMOTE image for the remote host in the 

Configuration Services file does not match a 

transport-name parameter on a TRANSPORT 

image in the CMS Configurator file. 

$ The network-name parameter on the 

TRANSPORT image does not match a 

NETWORK image in the CMS Configurator File. 

$ The LOCAL-NUMBER parameter on the 

NETWORK image in the CMS Configurator File 

does not provide a complete path to the 

remote host CMS. 

$ CMS has terminated on the remote host. 

5 5 73 111 Theremotehostisup,butthereisno 

DDPMASTER currently running on the remote host. 

The DDPMASTER batch run must be started on the 

remote host. 

5 5 77 115 The print host and punch host cannot be different 

hosts. Please reenter your command with identical 

print host and punch host values. 

3-20 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 81 121 The host containing the source file cannot return 

status after the file or job service is complete 

because it is not configured to communicate with 

your system (the originating system). 

Update the configuration file on the source host to 

communicate with your system. 

5 5 90 132 The source file is too large to be copied into the 

destination element. The size of your source file is 

greater than the maximum allowable for elements 

on the destination host. 

5 5 91 133 The DDP conversation that was copying your 

submitted job stream to another host has errored. 

The submitted ob is incomplete. DDP will attempt 

to remove it. It will not be run. 

5 5 92 134 You have entered an illegal character in the spool 

banner-id. The allowable characters are: numbers, 

letters,/,or-. 

5 5 93 135 The job name(s) listed above may not have been 

executed because DDP-FJT encountered the 

following error during the SUBMIT. 

5 5 94 136 DDP-FJT cannot process your SUBMIT function 

because there are no entries available in the 

DDP-FJT job name table. Either you have SUBMIT 

functions running that have not yet completed, or 

the listing from completed jobs has not been 

printed. You might try printing some of your 

submitted output and then resubmit your 

command. 


DDP was unable to register for TRMRG processing. 

5 5 100 144 Conversation aborted by remote host. 

3787 3528-200 3-21



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 101 145 Your command cannot be processed because DDP 

has been cancelled. Please try again at a later 

time. 

5 5 102 146 Your command cannot be processed because a 

DDP shutdown is in progress. Please try again at a 

later time. 

5 5 110 156 Your command cannot be restarted because it is 

still executing. You cannot restart a command that 

is currently active. 

5 5 111 157 Your cancel checkpoint request could not be 

processed because the command specified by the 

checkpoint parameter is currently executing. Wait 

until the command completes, or cancel the 

command first. See message DDP 9071 in 

Section 2 for additional information. 

5 5 112 160 The CANCEL function cannot be processed due to 

a security violation. See message DDP2226 in 

Section 2 for additional information. 

5 5 113 161 DDP-FJT cannot restart this SPOOL function 

because the temporary file created by DDP to hold 

the spooled output has been deleted on the host-id 

specified. 

5 5 120 170 Your spool request could not be processed 

because the file named in your request is a 

temporary file or a program file. Temporary files 

and program files cannot be spooled. 

5 5 121 171 Your spool request could not be processed 

because you requested a print file to be spooled to 

a punch device, or a punch file spooled to a print 

device. 

Check your command request configuration file. 

3-22 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 122 172 The file you requested may not be spooled. 

Possible reasons are: 

$ The file is a system file or nonspoolable file. 

$ The file is in a +1 state or has its drop flag 

set. 

$ The file is a print file with no main item. 

5 5 128 200 Volume is specified with no device type on 

DDP$CREATE function. 

5 5 129 201 Invalid characters used in the volume or device 

type. 

5 5 130 202 The file named by CREATE-FILE-NAME already 

exists on the host named by CREATE-HOST-ID. 

5 5 131 203 No space left on the volume named by 

CREATE-VOLUME-ID. 

5 5 132 204 The volume named by CREATE-VOLUME-ID is not 

available. 

The removable pack specified is not currently 

mounted. Please try later. 

5 5 133 205 Volume temporarily unavailable. Please retry later. 

5 5 134 206 File type is not supported. 

The file type specified is not supported. 

5 5 135 207 Your command cannot be processed because 

index keys are invalid or missing. 

5 5 136 210 File size is inconsistent or conflicts with initial or 

maximum size. 

The remote host detected a conflict in the values 

for CREATE-MAXIMUM-SIZE, CREATE-INITIAL-SIZE, 

or CREATE-GRANULARITY-SIZE. 

3787 3528-200 3-23



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 137 211 Wrong project-id for private file. 

The file named by PURGE-FILE-NAME is a private 

file and cannot be accessed by the DDPMASTER 

run. DDP-JT can purge public files or private files 

created via DDP-FJT. 

5 5 138 212 You have specified an element type to be purged, 

but you have not indicated the element name. See 

message DDP3001 in Section 2 for additional 

information. 

5 5 139 213 You have specified an element name to be purged, 

but you have not indicated the element type. See 

message DDP3011 in Section 2 for additional 

information. 

5 5 140 214 The device type specified by CREATE-DEVICE-TYPE 

is not available. 

5 5 141 215 The device type specified by CREATE-DEVICE-TYPE 

is not supported. 

5 5 142 216 File name syntax error. 

The file name contains an illegal character, has too 

many characters, or has an element cycle 

specified. 

5 5 143 217 A file cycle conflict exists for the file specified by 

CREATE-FILE-NAME or PURGE-FILE-NAME. 

5 5 144 220 The size of the file named in your command cannot 

be changed. 

5 5 145 221 The file name contains an illegal character, has too 

many characters, or has an element or element 

cycle specified when elements are not allowed. 

Correct the file name and retry. 

5 5 146 222 The access control record (ACR) contains an illegal 

character. Only alphanumeric characters are 

allowedinanACRname.Checktoseeifyou 

spelled the ACR name correctly or use the correct 

name. 

3-24 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 147 223 Your request has been denied due to a security 

violation. Please contact your system 

administrator. 

5 5 148 224 Your command could not be processed, because 

a file specified in your command has been disabled 

by the Exec. The file must be enabled before 

DDP-FJT can access it. If the file is in your local 

host, try an @ENABLE of the file and retry the 

command. 

5 5 149 225 DDP-FJT on the queue or execution host detected 

an error attempting to use the print/punch device 

in your command. 

If your command was a SPOOL, the print/punch 

device was not configured. 

If your command was a SUBMIT, the print/punch 

device specified was the same as the 

routing-queue specification on the ROUTING-Q 

record for the execution host in the execution 

host’s configuration. 

5 5 150 226 Your command was terminated. You cannot copy a 

symbolic element that has element cycles to a 

non-program file or spool it to an OS 2200 system. 

5 5 157 235 Only single elements may be copied within the 

same file. You may have specified the wrong 

element type or you may have failed to specify an 

element name. 

5 5 158 236 DDP-FJT was unable to access your source file 

because of a security violation. Possible causes 

are: 

$ The security information you supplied does 


$ You did not supply any security information 

and the default supplied by DDP does not 


3787 3528-200 3-25



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 159 237 DDP-FJT was unable to access your destination file 

because of a security violation. Possible causes 

are: 

5 5 160 240 Source file not found. 

$ The security information you supplied does 


$ You did not supply any security information 

and the default supplied by DDP-FJT does not 


The file named by COPY-SOURCE-FILE-NAME does 

not exist on the host named by 

COPY-SOURCE-HOST-ID. 

5 5 161 241 Source element type error. 

The value specified for COPY-FILE-TYPE is not 

supported by the host named by 

COPY-SOURCE-HOST-ID. 

5 5 162 242 Source element not found. 

The element named in COPY-SOURCE-FILE-NAME 

does not exist on the host named by 

COPY-SOURCE-HOST-ID. Make sure the correct 

COPY-FILE-TYPE was specified. 

5 5 163 243 Source file not available. 

The file named by COPY-SOURCE-FILE-NAME is not 

available. Please retry later. The file is in use, rolled 

out, or on an unmounted removable disk pack. 

5 5 164 204 The source file drop flag is set. The file named by 

the COPY-SOURCE-FILE-NAME cannot be assigned 

because its drop flag is set. 

5 5 165 245 Source read key error. 

The file named by COPY-SOURCE-FILE-NAME has 

an invalid or missing read key. Either it has a read 

key other than the one you specified, or it has a 

read key and you did not supply one. 

3-26 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 166 246 Source file in use by another run. 

The file named by COPY-SOURCE-FILE-NAME is in 

use by another run. Another run has the file 

assigned to it. The file must be freed by that run 

before DDP-FJT can access the file. 

5 5 167 247 Source file already being used by DDP-FJT. 

The file named by COPY-SOURCE-FILE-NAME is in 

use by another DDP-FJT user. Another DDP-FJT 

user on your local system or on a remote system 

has issued a DDP-FJT command that uses the file. 

5 5 168 250 Source file is rolled out. 

The file named by COPY-SOURCE-FILE-NAME is 

rolled out. You must wait for the file to be rolled in 

by the Exec, or have your systems personnel 


5 5 169 251 Your SPOOL request could not be processed 

because the file named in your request is a 

temporary file or a program file. Temporary files 

and program files cannot be spooled. 

5 5 170 252 Error in processing the source file. 

An error occurred processing the file named by 

COPY-SOURCE-FILE-NAME. Either you copied the 

wrong COPY-FILE-TYPE, the file is empty, or the file 

cannot be read by DDP-FJT. 

3787 3528-200 3-27



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 171 253 Record in file exceeds maximum size supported by 

DDP-FJT. 

The file named by COPY-SOURCE-FILE-NAME for a 

COPY function or the SPOOL-FILE-NAME for a 

SPOOL command contains one or more records 

whose length exceeds 1792 words. The maximum 

record size that can be transferred by DDP-FJT is 

1792 words (one track). 

The file named by SUBMIT-FILE-NAME for a SUBMIT 

function contains one or more records whose 

length exceeds 224 words. The maximum record 

size that can be submitted by DDP-FJT is 224 

words. 

5 5 172 254 Destination file too small. 

If the file named by COPY-DESTINATION-FILE-NAME 

is a program, its element table may be full. It may 

help to @PACK the file. Otherwise, create a file of 

sufficient size and retry the function. 

5 5 173 255 Destination file is read-only. 

The file named by COPY-DESTINATION-FILE-NAME 

is catalogued as a read-only file, or has a read key 

that was not supplied. 

5 5 174 256 DDP-FJT is unable to access the file named by 

COPY-DESTINATION-FILE-NAME because the drop 

flag has been set. The file has been marked for 

deletion by the Exec, but it is still assigned to an 

active run. When the file is free, it will be deleted. 

5 5 175 257 Destination file is a word-addressable file. 

DDP-FJT does not support word-addressable files. 

3-28 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 176 260 Destination file is a private file. 


is catalogued as a private file and cannot be 

accessed using the access information provided. 

5 5 177 261 Destination file in use by another run. 


is in use by another run. Another run has your file 

assigned to it. The file must be freed by the run 

that has it assigned before DDP-FJT can access 

the file. 

5 5 178 262 Destination file already being used by DDP-FJT. 


is in use by another DDP-FJT user. 

Another DDP-FJT user on your local system or on a 

remote system has issued a DDP-FJT command 

that uses the file. 

5 5 179 263 Destination file is rolled out. 


is rolled out. You must wait for the file to be rolled 

in by the Exec, or have your systems personnel 


5 5 180 264 Destination file not found. 


does not exist on the specified host. Check the file 

name or create the file on the destination host. 

5 5 181 265 Destination element type not supported. 

The COPY-FILE-TYPE specified is not supported on 

the host named by COPY-DESTINATION-HOST. 


Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 182 266 Bad system data file (SDF) control word in the 

source file. 

A bad SDF control word was encountered in the file 

named by COPY-SOURCE-FILE-NAME. DDP-FJT 

cannot continue the copy processing. 

3787 3528-200 3-29 

continued


continued 


Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 183 267 Destination file not available. 

The file named by COPY-DESTINATION-HOST is not 

available. Please retry later. The file is in use, 

rolled out, or on an unmounted removable disk. 

5 5 184 270 Write key missing or invalid. 

One of the files has a write key other than the one 

you specified, or the file has a write key and you 

did not supply one. 

5 5 185 271 Read key missing or invalid. 

One of the files has a read key other than the one 

you specified, or the file has a read key and you 

did not supply one. 

5 5 186 272 Destination file translate error. This value in the 

COPY-TRANSLATE-TYPE field is not supported by 


5 5 187 273 File is read-only (write-protected). 


was cataloged as read-only and the DDPMASTER 

run cannot write to it. 

5 5 188 274 File is write-only (read-protected.) 

The file named by COPY-SOURCE-FILE-NAME was 

cataloged as write-only and the DDPMASTER run 

cannot read it. 


Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 189 275 An unrecoverable error occurred when processing 

the command. Possible causes are: 

$ An @CAT error occurred during the submit 

processing. 

$ An I/O error occurred during the copy 

processing. 

continued 

3-30 3787 3528-200

continued 



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 190 276 Error in processing destination file. 

An error occurred processing the file named by 

COPY-DESTINATION-FILE-NAME. You specified the 

wrong COPY-FILE-TYPE, or DDP-FJT was unable to 

write to or add an element to the file. 

5 5 191 277 Invalid read or write keys given. 

If you did not specify keys on your command, this 

means that the file being referenced requires a key 

for the type of accesses requested, or the read or 

write keys you specified are incorrect. 

5 5 192 300 Source file empty, nothing copied. 


empty. No copy was performed. 

5 5 193 301 Source file is write-only. 


cataloged as a write-only file, or has a write key 

that was not supplied. 

5 5 194 302 Source file is word-addressable. 

DDP-FJT does not support word-addressable files. 

5 5 195 303 DDP-FJT support for read or write keys is not 

currently available. 


Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 196 304 Source file is a system data file (SDF) file with no 

SDF end-of-file (EOF) marker. 

The file named by COPY-SOURCE-FILE-NAME is an 

SDF file but it does not contain an SDF end-of-file 

marker. 

3787 3528-200 3-31 

continued


continued 


Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 197 305 Source file is private; access denied. 

The file named by COPY-FILE-FILE-NAME is a 

private file and cannot be accessed by the 

DDPMASTER run. DDP-FJT can access public files 

and private files created via DDP-FJT. 


COPY-SOURCE-FILE-NAME due to a file cycle 

conflict. 


COPY-DESTINATION-FILE-NAME due to a file cycle 

conflict. 


the SOURCE host named in your command has no 

configured paths to the DESTINATION host, or the 

DESTINATION host is configured as a HOST-TYPE 

that is not supported by DDP-FJT. 

5 5 201 311 The host named by SUBMIT-EXECUTION-HOST 

cannot service your DDP$SUBMIT request. 

5 5 202 312 You have specified parameters that are invalid with 

theMODEkeyword.YoumayonlyusetheFILEand 

MAXIMUM_SIZE parameters with the MODE 

keyword. 

5 5 203 313 You have specified parameters that are invalid 

when creating a mass storage file. 

5 5 204 314 The checkpoint feature of DDP-FJT may not be 

used when a single element is copied to the 

destination file. If you are issuing a COPY 

command, the copy will continue without 

checkpointing. If you are issuing a RESTART 

request, the command may have completed. 

Please issue a STATUS request to determine the 

progress of the command. 

3-32 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 205 315 The destination host does not support the 

checkpoint feature. If you issued a COPY 

command, your copy will continue without 

checkpointing. If you issued a RESTART command, 

your command cannot be processed. 

5 5 206 316 An error occurred while processing the destination 

checkpoint request during file transfer. The file 

transfer may have continued to completion. Use 

the DDP-FJT STATUS command to see the results 

of the file transfer. You may not restart this file 

transfer. 

5 5 207 317 Your RESTART request could not be processed 

because the source file used in the original 

command has been modified since the termination 

of the original command. 

5 5 208 320 Your RESTART request could not be processed 

because the destination file used in the original 

command has been modified since the termination 

of the original command. 

5 5 209 321 You specified an invalid start time on your 

command. 

5 5 210 322 The file named by COPY-SOURCE-FILE-NAME 

cannot be assigned by DDP-FJT. The possible 

reasons are: 

$ You supplied read or write keys on a file that 

does not have them. 

$ The file is private or cataloged at a higher 

security level than the worker RSI can access. 

$ You specified the wrong COPY-FILE-TYPE. 

$ The file is disabled. 

3787 3528-200 3-33



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 212 324 The COPY-DESTINATION-FILE-NAME cannot be 

assigned by DDP-FJT. The possible causes are: 

$ You supplied read or write keys on a file that 

does not have them. 

$ The file is private or cataloged at a higher 

security level than the worker RSI can access. 

$ You specified the wrong COPY-FILE-TYPE. 

$ The file is disabled. 

5 5 213 325 DDP-FJT cannot restart this SPOOL command 

because the temporary file created by DDP-FJT to 

hold the spooled output has been deleted on the 

host. 

5 5 214 326 Your RESTART request cannot be made due to a 

security violation. 

5 5 218 326 You may not spool more than 99 or less than zero 

copies of a file in a SPOOL request. Please try 

again. 

5 5 219 333 The job name is too long. 

5 5 220 334 Your SUBMIT command cannot be processed due 

to an invalid runstream. Check the execution host 

runstream. 

5 5 221 335 Your SUBMIT command cannot be processed due 

to a specification error. 

5 5 222 336 An unrecoverable error occurred while copying the 

file named by SUBMIT-FILE-NAME to the host 

named by SUBMIT-EXECUTION-HOST. 

5 5 223 337 Jobs not being accepted from the network. The 

SUBMIT-EXECUTION-HOST is not accepting jobs at 

this time. 

5 5 224 338 The print host or punch host specified in a SUBMIT 

request has not been configured at the execution 

host. 

3-34 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 225 341 DDP-FJT on the queue or execution host detected 

an error attempting to use the print/punch device 

in your command. 

If your command was a SPOOL, the print/punch 

device that was specified was not configured. 

If your command was a SUBMIT, the print/punch 

device specified was the same as the 

routing-queue specification on the ROUTING-Q 

record for the execution host in the execution 

host’s configuration. 

5 5 226 342 The job named by STATUS-JOB-NAME is not known 

by DDP-FJT. 

The job was not submitted through DDP-FJT, or the 

system completed the execution and output 

printing of your job. 

5 5 227 343 DDP-FJT is unable to return the output of your job 

because it has already been printed/punched or 

was deleted by an operator command. 


because it had already been discarded on the 

remote system. 


because it has already been printed/punched on 

the local system. 

5 5 230 346 There is no job stream in the file named by 

SUBMIT-JOB-NAME, or the file is not of the type 

specified by SUBMIT-TYPE. 

5 5 231 347 The status of your job-id is unknown. 

5 5 232 348 The status of your job-id is completed. 

5 5 233 349 The status of your job-id is not started. 

5 5 234 350 The status of your job-id is in progress. The 

program is currently running. 

3787 3528-200 3-35



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 235 351 The status of your job-id is not available. This may 

be a temporary condition. Retry the status 

command. 

5 5 236 354 An error occurred while trying to delete the job 

output delivery. 

The job has been cancelled, but the output will be 

delivered. 

5 5 237 355 The status of your command-id is completed 

successfully. 

5 5 238 356 The status of your command-id is in progress. 

Tracks have been transferred. It is partially 

complete. 

5 5 239 357 The status of your command-id is canceled. 

5 5 240 360 The file named by COPY-DESTINATION-FILE-NAME 

is too small to perform the requested function. 

The file must have a larger maximum size and/or 

granularity. 

5 5 241 361 There is no element of the name and type specified 

by COPY-SOURCE-FILE-NAME and COPY-FILE-TYPE. 

5 5 242 362 The status of your command-id is queued. 

5 5 243 363 Your command has been canceled by the console 

operator or by another user. 

5 5 244 364 The status of your command is aborted. 

5 5 245 365 Your command could not be canceled because it 

has already completed or aborted. 

5 5 246 366 Your command could not be canceled because it 

has already been canceled by the console 

operator or by another user. 

5 5 247 367 The status of your command is not found. 

5 5 248 370 Your CANCEL request has been performed, but 

output could not be deleted on the executing host. 

3-36 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 249 371 The status of your command is unavailable. 

5 5 250 372 File is not available. 

The file is in use, rolled out, or on an unmounted 

removable disk pack. 

5 5 251 373 DDP-FJT encountered an RSI error when 

attempting to cancel your job. 

The RSI terminal used by the demand id may have 

been terminated. If this problem persists, see your 

system admiistrator. 

5 5 252 374 DDP-FJT encountered an RSI error when 

attempting to status your job. 

The RSI terminal used by the demand id may have 

been terminated. If this problem persists, see your 

system administrator. 

5 5 253 375 DDP-FJT was unable to cancel the requested job 

because it has already been terminated. 

5 5 254 376 The status of your command is scheduled for 

execution at a certain local time on the source 

host. 

5 5 255 377 Quota error. 

Unable to create the file specified because the 

quota number of units has been exceeded. 

5 5 256 400 The SUBMIT-PRINT-HOST and 

SUBMIT-PUNCH-HOST have the same value. Output 

can only go to one host. 

5 5 257 401 The host is not in the DDP-FJT network or the host 

is configured as a HOST-TYPE that is not 

supported by DDP-FJT. 

5 5 258 402 DDP-FJT cannot process your ADMIT command 

when the HOST parameter has duplicate identifiers 

within the list you specified. 

3787 3528-200 3-37



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

5 5 260 404 Security error. 

DDP-FJT was unable to complete the function due 

to a security conflict with the type of access you 

desire. 

6 6 1 1 The OSI-BUFFER-OFFSET field in the OSI-DATA-PKT 

is not a multiple of 4. 

6 6 2 2 The OSI-TEXT-LENGTH field in the OSI-DATA-PKT is 

invalid. It is greater than the maximum length for 

the function or it is 0 and function requires data to 

be sent. 

6 6 3 3 The OSI-UNIT-INDICATOR field in the OSI-DATA-PKT 

is not set to 1 (OSI-MSG-COMPL). 

6 6 4 4 The OSI-SYNC-POINT-SERIAL-NUM is less than 0 or 

greater than 999999. 

6 6 5 5 The CALLED-S-SELECTOR-LEN or 

CALLING-S-SELECTOR-LEN field is invalid. It must 

range from 0 to 16. 

6 6 6 6 Reserved. 

6 6 7 7 The user selected one of the following invalid 

combinations: 



$ Both full and half-duplex functional units 

$ Neither full or half-duplex functional units 

$ Capability functional units and not activity 

management functional units 

$ Exception data functional units and not 

half-duplex functional units 

3-38 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 10 12 The OSI-SERVICE-ENTRY field value in the 

OSI-CONNECT-PKT is not 5 or 7. 

6 6 11 13 The OSI-TEXT-LENGTH field in the OSI-DATA-PKT 

has a non-zero value for a command where data is 

not allowed. 

6 6 12 14 The function required the token to be set. This can 

be caused by: 


$ One or more of the token fields in the 

OSI-DATA-PKT was set to 2 (CHOICE) but no 

choice was made on the Response. 

$ A GVTOKEN function was issued and none of 

the token fields was set to 1 (PASS). 

$ A PLSTOKEN function was issued and none of 

the token fields was set to 3 (REQUEST). 

6 6 15 17 Oneormoreofthetokenfieldsinthe 

OSI-DATA-PKT was set to 2 (CHOICE) on a function 

other than OPEN or RESYNCHRONIZE. 

6 6 16 20 Token requesting is not permitted on the following: 

Activity Management Start 

Activity Management Resume 

Activity Management Interrupt 

Activity Management Discard 

Activity Management End 

3787 3528-200 3-39



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 17 21 Token passing and token requesting are not 

permitted on the following: 

Abort 

Activity Management Start 

Activity Management Resume 

Activity Management Interrupt 

Activity Management Interrupt Ack 

Activity Management Discard 

Activity Management Discard Ack 

Activity Management End 

Activity Management End Ack 

Capability Data 

Capability Data Response 

Sync with Confirmation Expected 

Sync with Confirmation Optional 

Sync Confirmation 

Exception Report (XRPT) 

Close 

Close Confirm 

Send 

Typed-Data 

6 6 18 22 The value entered in the 

SCI-CALLING-REFERENCE-LEN or the 

OSI-OLD-SCI-CALLING-REF-LEN parameter is 

invalid. It must be between 0 and 64. 


OSI-OLD-SCI-CALLED-REF-LEN parameter is invalid. 

It must be between 0 and 64. 


SCI-COMMON-REFERENCE-LEN or the 

OSI-OLD-SCI-COMMON-REF-LEN parameter is 



SCI-ADDITIONAL-REFERENCE-LEN or the 

OSI-OLD-SCI-ADD-REF-LEN parameter is invalid. It 

must be between 0 and 4. 

6 6 22 26 The value entered in the OSI-ACT-ID-LEN parameter 

is invalid. It must be between 1 and 6. 

6 6 23 27 The value entered in the OSI-OLD-ACT-ID-LEN 

parameter is invalid. It must be between 1 and 6. 

3-40 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 24 30 The value entered in the OSI-EXCEPTION-RSN 

parameter is invalid. 

6 6 25 31 The value entered in the OSI-SESSION-RESULT 

parameter is invalid. It must be between 0 and 8. 


OSI-PRES-CONTEXT-TABLE-ENTRIES parameter is 

too large. The maximum value is 15. 

6 6 27 33 The OSI-PRES-CONTEXT-TABLE must contain an 

entry in which OSI-ABSTRACT-SYNTAX-ALIAS s 

"ACSE-AS" and OSI-TRANSFER-ALIAS is "ASN1-TS". 

6 6 28 34 The value entered in the OSI-PRES-CONTEXT-IDENT 

parameter is invalid. It must be in the range 

-32767 to 32767. 


parameter is invalid. It must be an odd integer. 


parameter has already been associated with an 

abstract syntax. If the same value for 

OSI-PRES-CONTEXT-IDENT is used in more than 

one entry of the OSI-PRES-CONTEXT-TABLE, the 

same value for OSI-ABSTRACT-SYNTAX-ALIAS must 

be used in each of those entries also. 

6 6 31 37 There are two identical entries in the 

OSI-PRES-CONTEXT-TABLE. 

6 6 32 40 The value entered in OSI-PRES-TABLE-ENTRIES for 

the Open response does not match the value 

returned in that field when the Open request was 

received. 

6 6 33 41 The value entered in the OSI-CONTEXT-INDICATOR 

field is invalid. It must be between 0 and 4. 

3787 3528-200 3-41



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 34 42 Theremustbeanentryinthe 

OSI-PRES-CONTEXT-TABLE in which 

OSI-ABSTRACT-SYNTAX-ALIAS is "ACSE-AS", and 

OSI-TRANSFER-SYNTAX-ALIAS is "ASN1-TS", and 

OSI-CONTEXT-INDICATOR is 0 for acceptance. 

6 6 35 43 Only one transfer syntax may be accepted for any 

given abstract syntax. If more than one entry in the 

OSI-PRES-CONTEXT-TABLE has the same 

OSI-PRES-CONTEXT-IDENT and 

OSI-ABSTRACT-SYNTAX-ALIAS, one may have 

OSI-CONTEXT-INDICATOR set to 0 for acceptance. 

6 6 36 44 An entry was found in the 

OSI-PRES-CONTEXT-TABLE for the Open response 

which was not contained in the table when the 

Open request was received. 

6 6 37 45 The OSI-CONTEXT-INDICATOR field was set 

incorrectly. If the OSI-CONTEXT-INDICATOR field 

contained a value indicating a provider rejection 

when the Open request was received, it cannot be 

changed by the user program when the Open 

response is issued. 



6 6 40 50 DDP-PPC Configuration Services has reported a 

no-find. For outgoing messages, the identifier 

corresponding to a given alias was not found. For 

incoming messages, the alias corresponding to a 

received identifier was not found. 

See the DDP-PPC log file for details. 

6 6 41 51 DDP-PPC Configuration Services has reported a 

user error. This indicates an internal error in 

DDP-PPC OSI Services. 


3-42 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 42 52 DDP-PPC Configuration Services has reported an 

internal error. 


6 6 43 53 DDP-PPC OSI Services could not connect with 

DDP-PPC Configuration Services. 


6 6 44 54 The value entered for OSI-DATA-TYPE is invalid. 

Possible causes for this error are: 

$ The value entered for the OSI-DATA-TYPE is 

invalid. It may be 134, 135, 138, 140, or 

141. 

$ The OSI-DATA-TYPE value was changed 

between segments in a segmented message. 

6 6 45 55 The presentation context required for the given 

OSI-DATA-TYPE either was not proposed or was 

not successfully negotiated. That data type may 

not be used on this conversation. 

6 6 46 56 A unique OSI-PRES-CONTEXT-IDENT must be given 

for each context representing the transfer 

syntaxes required for the compressed/padded 

data types. 

6 6 47 57 The value entered for OSI-ACT-MSG-FUNC is 


6 6 48 60 The value entered for OSI-ACT-REASON is invalid. 

6 6 49 61 The value entered for OSI-SYNC-FUNC is invalid. It 


6 6 50 62 The value entered for OSI-MODE in the 

OSI-RCV-PKT is invalid. It must be 0 or 1. 

6 6 51 63 The value entered for OSI-DATA-RELEASE is invalid. 

It must be 1. 


3787 3528-200 3-43



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 53 65 The values entered for transport class are invalid. 

See the DDP-PPC OSI Interface programming 

manuals for the correct values. 

6 6 54 66 Token requesting and token passing may not be 

specified on the same Send function. 

6 6 55 67 The value entered for OSI-APPL-PRES-RESULT is 

invalid. It may be 0 to 10, 13, or 19. 

6 6 56 70 The value entered for 

OSI-APPL-PRES-RESULT-TYPE is invalid. It must be 

between 0 and 2. If the value in 

OSI-APPL-PRES-RESULT is 1 or 2, this field must 

not be 0. 


OSI-TRANSPORT-SELECTOR-LEN is invalid. It must 

be between 0 and 32. 

6 6 58 72 A value was not supplied for 

OSI-APPL-CONTEXT-NAME-ALIAS or the 

OSI-APPL-CONTEXT-NAME-LEN was set to 0. 


6 6 60 74 A value was not entered for 

OSI-ABSTRACT-SYNTAX-ALIAS in the 

OSI-PRESENTATION-CONTEXT-TABLE. 

6 6 61 75 A value was not entered for 

OSI-TRANSFER-SYNTAX-ALIAS in the 

OSI-PRESENTATION-CONTEXT-TABLE. 

6 6 62 76 Neither session version was specified when 

accepting an Open request. 

6 6 63 77 No session version which was proposed on the 

Open request was specified on the Accept. 


3-44 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 65 101 The value entered for OSI-RESYNC-FUNC is invalid. 

It must be between 0 and 3. 

6 6 66 102 The value entered for OSI-CALLING-AP-TITLE-LEN, 

OSI-CALLED-AP-TITLE-LEN, or 

OSI-RESPONDING-AP-TITLE-LEN is invalid. It must 


6 6 67 103 The value entered for OSI-CALLING-AE-QUAL-LEN, 

OSI-CALLED-AE-QUAL-LEN, or 

OSI-RESPONDING-AE-QUAL-LEN is invalid. It must 



OSI-CALLING-P-SELECTOR-LEN, 

OSI-CALLED-P-SELECTOR-LEN, or 

OSI-RESPONDING-P-SELECTOR-LEN is invalid. It 


6 6 69 105 The value entered for OSI-CALLING-NSAP-LEN, 

OSI-CALLED-NSAP-LEN, or 

OSI-RESPONDING-NSAP-LEN is invalid. It must be 

between 0 and 32. 


OSI-APPL-CONTEXT-NAME-LEN is invalid. It must be 

between 0 and 44. 

6 6 71 107 The value entered for OSI-CALLED-AE-TITLE-ALIAS 

was not found in the configuration services 

database. 

6 6 72 110 The value entered for OSI-CALLING-AE-TITLE-ALIAS 

was not found in the configuration services 

database. 

6 6 73 111 The value entered for OSI-RESPONDING-AE-TITLE 

was ALIAS not found in the configuration services 

database. 

6 6 74 112 The value entered for OSI-TITLE-FORM is invalid or 

not supported. For this release, the value must be 

the letter ’O’ or ’D’. 

3787 3528-200 3-45



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

6 6 75 113 DDP-PPC received an invalid context set that 

cannot be supported due to the limitations in the 

local implementation. If it is returned on an Open 

function, then either: 

$ The compressed octet data type (141) was 

proposed without the octet data type (140). 

$ The compressed and padded data type (139) 

was proposed without the padded data type 

(138). 

If it is returned on the Open Response function, 

then either: 

$ The compressed octet data type (141) was 

accepted and the octet data type (140) was 

not accepted. 

$ The compressed and padded data type (123) 

was accepted and the padded data type (138) 

was not accepted. 

$ An octet data type (140 or 141) was 

accepted along with context(s) other than the 

ACSE context and other DP data types. 

7* 7 1 1 The user issued a command in the wrong state or 

with the wrong tokens, functional units, or sync 

point variables set. 

7* 7 2 2 Invalid protocol was received, or valid protocol 

was received in the wrong state or with the wrong 

tokens, functional units, or sync point variables set. 

7* 7 3 3 DDP-PPC acting as ACSE, Presentation, or Session 

service provider detected an error on an input 

from a remote host. DDP-PPC terminated the 

conversation by issuing an Abort or Refuse PDU. 

This is a fatal error, and the conversation is 

terminated. 

7* 7 4 4 DDP-PPC received a PDU containing an encoding 

that cannot be supported due to hardware and/or 

software limitations in the local implementation. 

*Fatal protocol error. 

3-46 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 - - For errors in this class code, the specific error 

field contains the error code returned to DDP-PPC 

by the CMS 1100 TSAM interface. The specific 

error is logged in the DDP-PPC log file. For an 

explanation of the specific error, see the CMS 

1100 Programming Reference Manual. 

The specific error field contains the code portion 

of the CMS 1100 error. These errors are listed in 

the OSI and DCA TSAM status code table in the 

CMS 1100 manual. 

8* 10 1 1 The transport layer service provider detected an 

error in the bridge protocol that is exchanged at 

the transport layer. Possible causes for this error 

are: 

*All CLASS-CODE 8 errors are fatal. 

$ Invalid immediate data length. The amount of 

data to be included with a connect request 

exceeds the maximum length allowed (32 

octets). 

$ Invalid network type. The network type 

selected is not supported by the transport 

service provider. Take DDP-PPC and CMS 

traces. 

$ Missing required HIC 

$ Invalid length for HIC 

$ Duplicate HIC found 

$ Byte count expired without END-HIC 

$ Invalid version 

See the DDP-PPC log file for the specific error.** 

**The specific error field contains an error code returned by the CMS 1100 TSAM interface. 

See the OSI/DCA TSAM status code table in the CMS 1100 Programming Reference 

Manual. 

3787 3528-200 3-47



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 2 2 The transport service provider detected an invalid 

length for the OSI-CALLING-T-SELECTOR-LEN, 

OSI-CALLED-T-SELECTOR-LEN, or 

OSI-RESPONDING-T-SELECTOR-LEN fields. The 

valid values are 0 to 32. Possible causes for this 

error are: 

$ Invalid local transport selector length. The 

Transport selector received by the transport 

service provider as the local (calling) TSEL 

exceeds the maximum length for a transport 

selector (32 octets). 

$ Invalid remote transport selector length. The 

Transport selector received by the transport 

service provider as the remote (called) TSEL 

exceeds the maximum length for a transport 

selector (32 octets). 



length for the OSI-CALLING-NSAP-LEN, 

OSI-CALLED-NSAP-LEN, or 

OSI-RESPONDING-NSAP-LEN fields. The valid 

values are 1 to 20. Possible causes for this error 

are: 


$ The NSAP or X.21 address supplied to the 

OSI transport service provider as the remote 

NSAP exceeds the maximum length (max 10 

bytes for TP4/IP and 8 bytes for other 

transport classes) 

$ TheNSAPorX.21addressisnotthe 

minimum length required for a non-TP4/IP 

network connection (3 bytes). 





3-48 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 


value for the OSI-TRANSPORT-CLASS or 

OSI-TRANSPORT-CLASS-ALT fields. The valid 

values are 0, 2, 4, or 20. Possible causes for this 

error are: 

$ Invalid transport class. An invalid transport 

class was requested. Check the Transport 

Class parameter supplied by the user 

program. Turn on DDP-PPC traces, if 

necessary. 

$ Undefined Transport class. A request for a 

transport class other than 0, 2, or 4 was 

received by the transport service provider. 

Check the value supplied by the user 

application. Take DDP-PPC and CMS traces if 

necessary. 

$ Invalid alternate class. A request for an invalid 

alternate transport class was received by the 

transport service provider. Check the value 

supplied by the user application. Take 

DDP-PPC and CMS traces if necessary. 

$ Invalid alternate class. A request for an invalid 

alternate transport class was received by the 

transport service provider. Check the value 

supplied by the user application. Take 

DDP-PPC and CMS traces if necessary. 


8* 10 5 5 Expedited data was not negotiated, or the 

maximum length for expedited data was exceeded. 



$ Expedited data was not negotiated 

$ Expedited data length was exceeded 





3787 3528-200 3-49



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 6 6 The OSI-CALLED-NSAP parameter was reported 

missing. 

The destination NSAP is missing. Check DDP-PPC 

configuration services or the information supplied 

by the user program for the called NSAP in the 

user application. 


8* 10 7 7 The value provided for the facility byte was invalid. 


8* 10 8 10 The OSI-CALLED-T-SELECTOR parameter is 

unknown. 

The called TSAP address (the combination of TSEL 

and NSAP address) is not known to the remote 

transport service provider. Check the remote OSI 

configuration. 


8* 10 9 11 The OSI-CALLED-T-SELECTOR parameter is 

unavailable. 

The called remote user is unavailable. Check the 

remote system status. 






3-50 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 10 12 A network error caused a failure with the transport 

connection. Possible causes for this error are: 


$ Network not working. This error code 

indicates that the CONS network configured 

to carry the desired connection is not active. 

This could indicate a DCP configuration error, 

the X.25 line is not connected or up, or the 

PSCS program product is not installed or is 

installed incorrectly. 

$ Network connection disconnected. This error 

code indicates that a CONS network 

connection was cleared. In the case of a class 

0 transport connection, this situation is 

indistinguishable from a normal transport 

close and may not indicate an error. In all 

other classes, however, this indicates a 

malfunction of the network connection. 

This can occur if the network provider is 

having problems, the PSCS line is 

disconnected, or any network multiplexers 

have gone down. 

This error may be a transient problem and the 

user may succeed with a retry. 

$ Net connection refused. The destination 

system refused the network connection 

during a CONS connection request. 





3787 3528-200 3-51



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 11 13 An error was detected by the transport service 

provider. Possible causes for this error are: 


$ Transport retry timer has expired. This error 

indicates that a connection waiting for internal 

resources had waited too long and was 

disconnected by the transport service. This 

may indicate the retry/retransmission timer is 

set too low for exising network conditions. 

$ Retransmit count exceeded. The 

retransmission count was exceeded and the 

transport connection was cleared by the 

transport service provider. This normally 

occurs when the transport service is not able 

to contact its peer on the CLNS(OSI/IP) 

network. This can happen when: 

v The peer OSI system is down or not 

configured properly 

v The OSIROUTE statement in the DCP 

configuration is incorrect 

v The remote host does not have a valid 

route back to the local DCP 

This error may also occur if a network goes 

down while a transport connection is being 

activated or is active. 

$ Net connection has gone away. The transport 

service provider has detected the absence of 

a network connection on a CONS transport 

connection. Reasons for this are unknown by 

the transport service. This error may be 

transitory and the user should try again. 

3-52 3787 3528-200



Decimal 

Value 

8* 

(cont.) 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

10 11 13 $ Time to wait for net connect has expired. This 

error occurs if a network connection cannot 

be established within the TS1 time. This may 

occur in a CONS network if the TS1 time is 

configured too short for existing conditions or 

the DTE address of the remote host is wrong 

andnoreplycomesbackbeforetheTS1time 

expires. 

$ The inactivity timer expired. This error occurs 

for the OSI transport connection if nothing is 

received from the peer within the inactivity 

time. This may occur if the the remote host 

crashed or the network went down. It may 

also occur if the remote host’s window timer 

is set to a value greater than the local host’s 

inactivity timer. 


8* 10 12 14 An error was detected by the OSI transport bridge 

component of the transport service provider. 


$ Unknown reason 

$ Insufficient resources 

$ Bridge state error 

$ Bridge program error 


8* 10 13 15 Not used by DDP-PPC in this release. 





3787 3528-200 3-53



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 16 20 A transport congestion error was returned from 

the peer transport service provider. Possible 

causes for this error are: 

$ Local congestion at the time of the connect 

request 

$ Remote transport entity congestion at 

connect request time. The remote transport 

service did not have enough resources to 

accept the transport connection. 

For all the errors in this group, try again. If the 

problem persists, take OSI traces on the remote 

(peer) system. 


8* 10 17 21 The remote session entity is not attached to the 

called transport services access point. 

The called TSEL does not match any TSEL for 

which the remote transport service is listening. 


If the remote system is an OS 2200 system 

running DDP-PPC level 6R1 or higher, the OSITSU 

component may not be up. 





3-54 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 18 22 A transport layer error occurred. Many of these 

errors are transient errors and may not recur if the 

connection is retried. Possible causes for this 

error are: 

$ Connection negotiation failed. The requested 

negotiable parameters were not acceptable to 

theremotesystem. 

$ Duplicate source references detected for the 

same pair of NSAPS. This is a protocol 

violation. It may indicate that two similar 

systems are configured with the same NSAP 

on the same network. 

$ Mismatched references. The source and 

destination references were mismatched. This 

is a transport protocol error. 

$ Protocol error. An undefined transport 

protocol error was detected by the remote 

OSI system. 

$ Reference overflow. 

$ Connection request refused on this network. 

$ Header or parameter length invalid. This is a 

transport protocol error. 

For all the errors in this group, try again. If the 

problem persists, take OSI traces on the remote 

(peer) system. All of these errors are generated by 

the peer system. 


8* 10 19 23 A "session layer issued transport disconnect" error 

was returned to the local transport services 

provider from the peer transport service provider. 






3787 3528-200 3-55



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 25 31 An error occurred in the local network services 

provider. 


8* 10 36 44 The remote network number is busy. 


8* 10 37 45 The remote network is congested. 


8* 10 38 46 The remote network is out of order. 


8* 10 39 47 A network layer error occurred. Possible causes 

for this error are: 


$ Invalid facility request 

$ Access barred 

$ Not obtainable 

$ Remote procedure error 

$ Local procedure error 

$ RPDA out of order 

$ Reverse charging acceptance not subscribed 

$ Incompatible destination 

$ Fast select acceptance not subscribed 

$ Ship absent 





3-56 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 40 50 The local network services provider received an 

error from the remote network services provider 

with no specific reason provided. 


8* 10 50 62 An error was detected by the local network 

services provider. 



invalid protocol error from the remote network 

services provider or the network. 



invalid packet type error from the remote network 

services provider or the network. 






3787 3528-200 3-57



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

8* 10 62 76 The local network services provider received a 

packet not allowed error from the remote network 

services provider or the network. Possible causes 



$ Packet not allowed 

$ Unidentifiable object 

$ Call on one-way logical channel 

$ Invalid packet type on permanent virtual circuit 

$ Packet on unassigned logical channel 

$ Reject not subscribed to 

$ Packet too short 

$ Packet too long 

$ Invalid general format identifier 

$ Restart or registration packet with a non-zero 

value in bits 1 to 4 of octet 1, or bits 1 to 8 of 

octet 2. 

$ Packet type not compatible with facility 

$ Unauthorized interrupt confirmation 

$ Unauthorized interrupt 

$ Unauthorized reject 





3-58 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 


network timer expired error from the remote 

network services provider or the network. Possible 


$ Timer expired 

$ Timer expired for incoming call 

$ Timer expired for clear indication 

$ Timer expired for reset indication 

$ Timer expired for restart indication 


8* 10 64 100 The local network services provider received a call 

setup, call clearing, or registration error from the 

remote network services provider or the network. 



$ Call setup, call clearing, registration problem 

$ Facility/registration code not allowed 

$ Facility/parameter not allowed 

$ Invalid called address 

$ Invalid calling address 

$ Invalid facility/registration length 

$ Incoming call barred 

$ No logical channel available 

$ Call collision 




3787 3528-200 3-59



Decimal 

Value 

8* 

(cont.) 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

10 64 100 $ Duplicate facility requested 

$ Non-zero address length 

$ Non-zero facility length 

$ Facility not provided when expected 

$ Invalid CCITT specified DTE facility 



miscellaneous type error from the remote network 

services provider or the network. Possible causes 



$ Miscellaneous 

$ Improper cause code from DTE 

$ Octet not aligned 

$ Inconsistent Q bit setting 





3-60 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 


international problem type error from the remote 

network services provider or the network. Possible 


$ Remote network problem 

$ International protocol problem 

$ International link out of order 

$ International link busy 

$ Transit network facility problem 

$ Remote network facility problem 

$ International routing problem 

$ Temporary routing problem 

$ Unknown called DNIC 

$ Maintenance action 


8* 10 67 103 A network specific error occurred. To determine 

the exact cause, you may need to contact a 

representative of the network supplier. 


8* 10 68 104 The transport services provider received a 

transport disconnect with a value of "no reason." 






3787 3528-200 3-61



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

10 12 - - Request not accepted. 

Any errors in this class code mean DDP-PPC has 

committed a protocol error. Take a DDP-PPC 

dump, process the log file, and recreate the error 

with DDP-PPC traces. (See the DDP-PPC 

Implementation and Administration Guide.) 

10* 12 2 2 DDP-PPC internal error. 

10* 12 4 4 DDP-PPC internal error. 

128* 200 - - Any errors in this class code mean DDP-PPC has 

committed a protocol error. Take a DDP-PPC 

dump, process the log file, and recreate the error 

with DDP-PPC traces set to level 3. (See the 

DDP-PPC Implementation and Administration 

Guide.) 

128* 200 0 0 No SUP-END (octal 204) is present in the IPC 

header. 

128* 200 1 1 IPC header does not start with a valid IPC function 

or is missing required fields. 

128* 200 2 2 IPC header contains fields that do not belong in the 

header. 

128* 200 3 3 IPC header contains an invalid function. 


128* 200 5 5 User-id field in IPC header is not valid. 

128* 200 6 6 Service name field in IPC header is not valid. 

128* 200 7 7 IPC header sequence number in IPC header is out 

of sequence. This is caused by a lower level 

network error that causes loss of message. 

128* 200 10 12 Conversation is not in the proper state to receive 

this message. 



3-62 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

128* 200 11 13 IPC header sequence number is too long, or an 

invalid or unrecognizable field was found in the IPC 

header. 

128* 200 12 14 An unsupported or invalid version of DDP-PPC is 

attempting to open a conversation. 

128* 200 13 15 An invalid class of procedure was detected. 

128* 200 14 16 A reply request has been detected that does not 

appear at the end of a blocked message. 

129* 201 9 11 A read key exists on the file 

DDP*RUN-STREAMS.** 

129* 201 10 12 The file DDP*RUN-STREAMS does not exist on the 

destination host.** 

129* 201 11 13 The file DDP*RUN-STREAMS is rolled out on the 


129* 201 12 14 The file DDP*RUN-STREAMS is assigned 

exclusively to another run on the destination 

host.** 

129* 201 13 15 The file DDP*RUN-STREAMS is marked for deletion 

on the destination host.** 

129 201 14 16 The file DDP*RUN-STREAMS is catalogued as a 

private file on the destination host.** 

129 201 15 17 The file DDP*RUN-STREAMS is disabled on the 


129 201 17 21 An error occurred searching the 

DDP*RUN-STREAMS table of contents for your 

element.** 

129 201 18 22 An improper runstream exists in 

DDP*RUN-STREAMS.** 

Your job cannot be started by DDP-PPC. Fix the 

runstream and try again. 



**Referenced by the configuration services program record for the program that DDP-PPC 

is to start. This may be the DDP*RUN-STREAMS file or a user-defined file. 

3787 3528-200 3-63



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

129 201 19 23 An error occurred when the remote host read your 

element from DDP*RUN-STREAMS.* Please 

contact your Unisys representative. 

129 201 20 24 Your element in DDP*RUN-STREAMS on the 

destination host is not in ASCII.* The element must 

be in ASCII. 

129 201 21 25 When the destination host tried to start your job, 

the file DDP*RUN-STREAMS was unobtainable.* 


the element in the file DDP*RUN-STREAMS was 

unobtainable.* 


an I/O error occurred. 

129 201 24 30 There are unavailable resources on the destination 

host to start your job. Please try again. 

129 201 25 31 The PROGRAM record in the configuration services 

database for the program to be started by 

DDP-PPC has the COPIES keyword set to ERROR. 

This is normal for RCASCONTROL or FTAM$$$$ 

which are the DDP-FJT and OSI-FTAM monitors. 

129 201 26 32 Your TIP transaction cannot be started because 

the Message Control Bank (MCB) is not running on 



the maximum number of activities are initialized 

with MCB. 


your transaction code is invalid. 

129 201 29 35 An MCB error occurred while trying to start your 

TIP transaction. The MCB error is also printed in 

the DDP-PPC Log file on the destination host. 

*Referenced by the configuration services program record for the program that DDP-PPC 

is to start. This may be the DDP*RUN-STREAMS file or a user-defined file. 

3-64 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

129 201 30 36 No MCB images are found in the configurated 

services database file. Your TIP transaction cannot 

be started. 


your application group number is not in the range 

of 1 through 9. 

129 201 32 40 An MCB image is not found in the configuration 

services database file for the application group 

number you specified. 

129 201 33 41 A security violation error is returned on the 

@START. 

129 201 34 42 An unexpected error is returned on the @START. 

See the DDP-PPC log file for the @START result. 

129 201 35 43 An unexpected error was encountered when 

DDP-PPC attempted to access the configuration 


This error is usually returned by the host receiving 

the OPEN request (destination host) when DDP-PPC 

encounters an error while attempting to find a 

PROGRAM record in the configuration services 

database. 

129 201 36 44 DDP-PPC cannot initiate TIP transactions because 

no PID-NUM parameter was found in the LOCAL 

host record in the DDP-PPC configuration services 

database. This error is usually returned by the host 

receiving the OPEN request (destination host) when 

DDP-PPC attempts to initiate a TIP transaction. 

Make sure the PID-NUM parameter is configured. 

You may be able to find additional information in 

the DDP-PPC log file on the destination host. 

129 201 64 100 Your data is greater than 8K bytes. Data must be 

less than or equal to 8K bytes. 

129 201 65 101 A host name was not specified in your user 

interface area. 

129 201 66 102 A remote program name was not specified in your 

user interface area. 

3787 3528-200 3-65



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

129 201 67 103 Transaction code PASS was not specified in your 

user interface area. 

129 201 68 104 The correct data type was not specified in your 

user interface area. Only ASCII, EBCDIC, 

TRANSPARENT, or PAD TRANSPARENT are 

permitted. 

129 201 69 105 The correct conversation type was not specified in 

your user interface area. Only IPC or SNA is 

permitted. 

129 201 70 106 The reply field was not specified in your user 

interface area. 

129 201 71 107 The PASS transaction is invalid. 

129 201 72 110 Single Message Transfer via MCB is down. 

129 201 73 111 Your application group number is not in the range 

of 1 through 9 in the VALTAB entry for the PASS 

transaction. 

129 201 74 112 Your conversation is no longer active. The DDP 

process went down before you sent your 

response. 


129 201 76 114 The IBM CICS program sent more than one data 

complete. This violates the documented protocol 

for Single Message Transfer via MCB. 

129 201 77 115 The IBM CICS program sent a send indication. This 

violates the documented protocol for Single 

Message Transfer via MCB. 

129 201 78 116 The AUDIT NUM returned via a VINDEX READ is not 

in the range of 1 through 9 for the TIP transaction 

specified in the remote program name field. 

129 201 79 117 The TIP transaction specified in the remote 

program name field cannot send a response 

because its user interface area is in error. 

129 201 80 120 An error occurred in MCB while executing a 

VINDEX READ to obtain the AUDIT NUM of the 

PASS transaction code. 

3-66 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

129 201 81 121 The MCB record for your remote transaction was 

not found in the configuration services database. 

129 201 82 122 The MCB record for your PASS transaction was 

not found in the configuration services database. 

130 202 - - An error ocurred in MCB on the remote host. The 

detail status is the MCB error code. 

132 204 - - User request error. 

132* 204 1 1 Successor program on PASSOFF function call has 

not issued an BIND request. 

132* 204 2 2 A peer program committed procedure error - 

conversation aborted. 

132* 204 3 3 The peer user program has aborted the 

connection. 

132* 204 4 4 The OSI service provider (DDP-PPC) issued a 

provider abort. 

132* 204 5 5 The peer session protocol machine has sent an 

exception report, indicating that a protocol error 

has been detected. 

140* 214 1 1 This error may be caused by one of the following: 

$ The peer application sent an illegal data type. 

$ DDP-PPC encountered an internal protocol 

error. 

$ The user activity could not allocate a program 

d-bank during a BIND function. The program 

tried to receive a compressed message. 

The most common reason why a user activity 

cannot allocate a program d-bank is that the 

activity is running in real time and the PCT cannot 

be expanded. To solve this problem, increase the 

PCT blocks allocation on the @RUN statement. 



3787 3528-200 3-67



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

192 300 1 1 Parameter or parameters missing for function call. 

192 300 2 2 Required entry in parameter-name is missing. 

192 300 3 3 Entry in parameter-name is invalid. 

195 303 1 1 The specified connection does not exist. 

195 303 2 2 The TCP connection used up the entire Upper 

Layer Protocol (ULP) specified timeout period. 

195 303 3 3 An unknown error. 

195 303 4 4 Unsupported event. 

196 304 - - TCP/IP interface errors 

196 304 1 1 The packet is formatted incorrectly or has bad 

field values. 

196 304 2 2 The specified connection already exists. 

196 304 3 3 Insufficient resources are currently available to 

complete the requested function. 

196 304 4 4 No peer socket was specified on an "active" 

connect function. 

196 304 5 5 A security/precedence violation occurred in a ULP 

request. 

196 304 6 6 The local network cannot deliver a message to the 

DDP-PPC network. 

196 304 7 7 TCP service failure due to a synchronization 

problem between the two TCPs. 

196 304 8 10 TCP service failure due to a synchronization 

problem between the two TCPs. 

196 304 9 11 The ULP requested that the connection be 

terminated prior to complete establishment. 

196 304 10 12 The connection requested earlier is denied for 

unspecified reasons. 

3-68 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

196 304 11 13 IP detected an error in options (such as stream-id 

and security. 

196 304 12 14 Active open was rejected for unspecified reasons. 

196 304 13 15 Connection failure in lower-level protocols. 

196 304 14 16 The function specified is illegal for the type of 

connection, or the "state" of the connection may 

not allow specific functions. 

196 304 15 17 Route list is absent; a routing list size is indicated 

but the list address is null. 

196 304 16 20 Timestamp list is absent; a list of timestamp 

routes is indicated but the list address is null. 

196 304 17 21 The buffer provided is too small to receive the 

current list. Increase the buffer size and reissue 

the command. 

196 304 18 22 The message buffer is too small. 

196 304 19 23 Invalid route list; the route list is either included 

when not needed or not included when needed. 

196 304 20 24 Invalid timestamp list; the timestamp list is either 

included when not needed or not included when 

needed. 

196 304 21 25 Internal error. This error is not recoverable. 

196 304 22 26 Illegal route option. This error is caused by 

specifying more than one of the mutually exclusive 

options. 

196 304 23 27 Invalid IP options. Either an illegal option was 

specified, or too many options were specified 

causing an overflow of the reserved IP option area. 

3787 3528-200 3-69



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

196 304 24 30 An error was found in the receive buffer. In order 

to recover, the Receive buffer must be received 

again. 

196 304 25 31 Data is trying to be sent over a passive connection. 

196 304 26 32 Both route list and timestamp list absent 

conditions have occurred. See detail status codes 

15 and 16 (decimal). 

196 304 27 33 DDP-PPC received an input message from Telcon 

in an incorrect format. 

196 304 65 101 Invalid Open Accept. An Open Accept was received 

while the connection was in a state where an Open 

Accept was not expected. 

196 304 66 102 Invalid local internet address. The internet address 

is not configured for this TSU. 

196 304 67 103 Invalid local port number. The specified local port 

number is either 0 or greater than 65,535. 

196 304 68 104 Invalid remote internet address. The remote 

internet address is either 0, broadcast, or 

otherwise invalid. 

196 304 69 105 Invalid remote port number. The specified remote 

port number is either 0 or greater than 65,535. 

196 304 70 106 Duplicate Active Open request. Another TSU has 

already established a passive open or a transport 

connection with the same port number and internet 

address parameters. 

196 304 71 107 Invalid CMS connection-id. This CMS connection-id 

is unknown or closed, or the CMS connection-id is 

invalid for this TSU. 

196 304 72 110 Invalid retransmissions value. The retransmissions 

parameter exceeds its maximum allowable value. 

3-70 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

196 304 73 111 Invalid precedence parameter. The precedence or 

high precedence parameter is not in the range of 0 

to 7, or the precedence range is invalid. 

196 304 74 112 Invalid Open type. The Open type is not 0 (passive) 

or 1 (active). 

196 304 75 113 Invalid time to live parameter. The parameter is not 

in the range of 0 to 255. 

196 304 76 114 Invalid type of service parameter. The type of 

service parameter passed to CMS 1100 is 

undefined. 

196 304 77 115 Too much user data. The number of bytes of user 

output data passed on this request exceeds the 

limit for this request. 

196 304 78 116 Invalid IP options. The IP options sent by the TSU 

are invalid or are too long for this version of IP. 

196 304 79 117 Invalid TCP options. The TCP options sent by the 

TSU are invalid or are too long for this version of 

TCP. 

196 304 80 120 In time wait state. The transport connection cannot 

be established until the previous transport 

connections time out. The TSU can try again later 

or use a different port number or internet address 

to establish a transport connection. 

196 304 81 121 Invalid byte offset. The specified byte offset was 

greater than 3. 

196 304 82 122 Connection not opened. 

196 304 83 123 Duplicate Active Open Different TSU. Another TSU 

has already established a passive open, or a 

transport connection with the same port number 

and internet address parameters already exists. 

3787 3528-200 3-71



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

196 304 84 124 Four minute initial wait. The transport connection 

cannot be established until CMS 1100 waits for all 

previous network traffic to time out. The TSU must 

wait and try again later. 

196 304 85 125 The local port number is in use by another TSU. 

Repeat the request using a different local port 

number. 

196 304 86 126 No address available. 

196 304 87 127 The port number and internet address combination 

is invalid. 

196 304 88 130 The local port number is in use. Specify a different 

local port number or internet address. 

196 304 89 131 No local ports are available. 

196 304 90 132 Configuration services error; there was an error 

while attempting to access the configuration 


196 304 92 134 Network unreachable; DDP-PPC cannot connect to 

the network. 

196 304 93 135 Host unreachable; DDP-PPC cannot connect to the 

network. 

196 304 94 136 Protocol unreachable. 

196 304 95 137 Port unreachable. 

196 304 96 140 Fragmentation needed and the Don’t Fragment flag 

is set. 

196 304 97 141 Source route failed. 

196 304 98 142 Destination network unknown. 

196 304 99 143 Destination host unknown. 

196 304 100 144 Source host isolated. 

3-72 3787 3528-200



Decimal 

Value 

Octal 

Value 

Decimal 

Value 

Octal 

Value 

196 304 101 145 Communication with destination network is 

administratively prohibited. 

196 304 102 146 Communication with destination host is 

administratively prohibited. 

196 304 103 147 Network unreachable for the type of service 

specified. 

196 304 104 150 Host unreachable for the type of service specified. 

196 304 105 151 Time to live count exceeded. 

196 304 106 152 Fragment reassembly exceeded. 

196 304 107 153 Source quench. 

196 304 108 154 Parameter problem. 

196 304 109 155 No path to destination. There is a down or failed 

component in the network. Either the local LAN is 

down, or one or more IP addresses are bad. 

196 304 110 156 Invalid internet address specified. 

196 304 111 157 Invalid domain name specified. 

196 304 112 160 No domain name or internet address supplied. 

196 304 113 161 Local internet address not available. 

196 304 114 162 Local internet address not known. 

196 304 115 163 Remote internet address not available. 

196 304 116 164 Remote internet address not known. 

196 304 117 165 Domain name not available. 

196 304 118 166 Domain name not known. 

196 304 119 167 CMS 1100 resources not available. 

196 304 120 170 The TAS TSU is in a shutdown state. No new 

connections can be established. 

3787 3528-200 3-73

Section 4 

DDP-FJT/OSI-FTAM Print and Tape 

Utilities Messages 

This section numerically lists error messages returned from the following print and tape 

utilities: 

$ PSERVER (Print Server Utility) 

$ PRMAN (Print Manager Utility) 

$ TXFR (Tape Transfer Utility) 

$ TXFCPY (Tape Copy Processor) 

3787 3528-200 4-1

DDP-FJT/OSI-FTAM Print and Tape Utilities Messages 

PSR1790 

TXFR has aborted with an error condition. See the DDP-PPC log file for more information. 

PSR2010 

Statement number statement-number cannot be read by PRMAN. It will be ignored. 

PSR2020 

No LOCAL host card was found in the PRMAN runstream. This a required parameter. 

SYNTAX: LOCAL host-name (where host-name matches the LOCAL HOST record in the 

Configuration Services Database). 

PSR2030 

An invalid MODE was specified in the PRMAN runstream. Valid modes are: DRIVER, 

MANAGER, MULTI-SYS, and SINGLE-SYS. 

PSR2040 

Statement number statement-number has a field missing. It will be ignored. See the 

DDP-PPC log file for more information about the field. 

PSR2050 

The queue-id on the QUEUE parameter statement does not exist. This queue-id must 

appear on a STATION card in the EXEC configuration for this system. See the system 

adminstrator of your site for assistance. 

PSR2060 

A value used on a PRMAN parameter statement is out of range. See the DDP-PPC log file 

for more information about the field. 

PSR2070 

The USERID under which you are trying to run requires SMOQUE$ privilege. PRMAN will 

not run under this USERID. 

PSR2080 

PRMAN received this ER SMOQUE$ error status: octal-code. See the DDP-PPC log file and 

the Executive Requests (ER) Programmer’s Reference Manual for more information. 

Explanation: 

See the Exec System Software Executive Requests (ER) Programming Reference Manual 

for an explanation of the octal status code. 

4-2 3787 3528-200

PSR2090 


PRMAN found either the laser name printer-name or the system host-name to be invalid. 

PRMAN could not mark this laser as AVAILABLE. Check the accuracy of the LASER cards 

in the PRMAN runstream. 

PSR2100 

PRMAN received an unknown command from either the DRIVER or the MANAGER. See 

the DDP-PPC log file for more information. 

PSR2120 

No USERID or PASSWORD was given for signing on the RSI activity. A SIGNON card must 

be added to the PRMAN runstream. 

PSR2130 

PRMAN is missing a parameter card for one of these reasons: 

(1) PRMAN is running in MODE DRIVER, but the manager system name or the manager 

receive application name is missing. Add a MANAGER-PATH statement to the PRMAN 

runstream. 

(2) PRMAN is running in MODE MANAGER or MULTI-SYS, but the manager receive 

application name or the manager send application name is missing. Add a MANAGER 

statement to the PRMAN runstream. 

PSR2140 

No PRINT queues were supplied to PRMAN. These are queues that PRMAN will control. 

Add at least one QUEUE statement to the PRMAN runstream. 

PSR2150 

PRMAN recovery failed. The PRMAN-PSAVE file does not match the current PRMAN 

running. PRMAN will come up, but previous laser requests are lost. 

3787 3528-200 4-3


PSR2160 

The @ASG of the PRMAN save file PRMAN-PSAVE returned an error status of octal-code. 

This is a fatal error. 

Explanation: 



PSR2180 

Statement number statement-no is missing a field required by the MODE parameter. 

PSR2190 

Too many PRINTER/LASER statements - excess statements will be ignored. 

PSR3000 

ER ATREAD$ Error: error-status (octal) = octal-code 

Explanation: 



PSR3010 

File I/O error octal-code (octal) on file-name file. This is a fatal error. The file may be 

corrupted. Notify your system administrator to correct the problem. 

Explanation: 



PSR3020 

$$STAT was not found in TXFR status file. The TXFR status file is corrupted and can no 

longer be used. Erase and re-catalogue the file. 

PSR3030 

The catalogue or the assign of the TXFR$START file got the following error: octal-code 

(octal). 

Explanation: 



4-4 3787 3528-200

PSR3050 


A REQUIRED PARAMETER is missing from the TXFR$CONFIG file. The missing 

parameter has been logged in the DDP-PPC log file. After adding the paramter to the 

TXFR$CONFIG file, re-try TXFR. 

PSR3060 

The TXFR$CONFIG file contains too many TAPE-DEVICE cards. The total number of 

equipment type mnemonics permitted is 50. This is not a fatal error. TXFR will ignore all 

mnemonics after the first 50. 

PSR3070 

A REQUIRED FIELD is missing from the TXFR$CONFIG file. The missing field has been 

logged in the DDP-PPC log file. After adding the field to the TXFR$CONFIG file, re-try 

TXFR . 

PSR3080 

The TXFR$CONFIG file contains too many OUT-Q cards. The total number of out-queues 

permitted is 50. This is a fatal error. After correcting the TXFR$CONFIG file, re-try TXFR. 

PSR3090 

The TXFR processor was returned the following error from INFOR$: octal-code (octal). 

This is a fatal error. Notify your system administrator to correct the problem. 

Explanation: 



PSR3100 

Facilities error octal-code on file-name. This is a fatal error. Make sure the file exists on 

your system. Notify your system administrator to correct the problem. 

Explanation: 



3787 3528-200 4-5


PSR3150 

One of the following statements is missing from the SYS$LIB$TXFR-CONFIG: IN-Q, 

OUT-Q, or HOLD-Q. This is a fatal error. 

PSR5000 

The laser printer-name is in an unknown state. It has been marked STOPPED. 

PSR5040 

No initial response from manager system host-name. DDP receive error 3-015 returned 

from PPC. 

Explanation: 

The DDP-PPC status code consists of an octal class code and detail-status code. See 

Section 3 of this manual for an explanation of these codes. 

PSR5050 

Bad response to initialize. No accept-driver received. 

PSR5070 

No response from manager system host-name. DDP receive error 3-015 returned from PPC. 

Explanation: 



PSR5080 

Bad response to done-with-laser. No laser-marked-available received. 

PSR5090 

Bad response to request-laser. No request-queued received. 

PSR6000 

PRMAN LOCAL parameter missing from runstream. This is a required statement. 

FORMAT: LOCAL host-name (where host-name is the LOCAL host name in your 

Configuration Services database). 

4-6 3787 3528-200

PSR6010 


The PRMAN-PSAVE save file is unavailable. The @ASG error status returned was: 

octal-code. A new save file will be catalogued. 

Explanation: 



PSR10000 

PSERVER LOCAL parameter is missing. This is a required paramter. 

PSR10001 

Input SEND statements in excess of number are ignored. 

PSR10010 

No response from path path-name. 

PSR10020 

Confirmation not received on open-new-act. Alternate path will be attempted. See 

DDP-PPC log file for more information. 

PSR10030 

Checkpoint file not on queue queue-name. FILE:qual*file-name (cycle). No file will be 

transferred. 

PSR10040 

Checkpoint file found on queue queue-name. FILE:qual*file-name (cycle). 

PSR10055 

Unable to catalogue file on queue queue-name. FILE:qual*file-name (cycle). Probable 

f-cycle conflict. 

Explanation: 

PSERVER catalogs a file on the receiving system to receive the transferred print file. If this 

file already exists, PSERVER attempts to catalog a +1 cycle of the file. If that is 

unsuccessful, PSERVER logs the PSR10055 message in the PRINT$ file of the receiving 

system and returns an error to the sending system. The sending system queues the file to 

the PSERVER error queue if one is configured. 

3787 3528-200 4-7


PSR10090 

Main activity restarting. Receive-new status: PPC-status-code 

Explanation: 



PSR10100 

PSERVER levels unmatched on host host-name. 

PSR10105 

PSERVER levels unmatched on send to host-name/application-name 

PSR10110 

Invalid peer host host-name from queue queue-name to queue-name 

PSR10131 

MOVE statement statement-number is incomplete. Statement is ignored. 

PSR10132 

MOVE statement statement-number does not contain the keyword MOVE. Statement is 

ignored. 

PSR10133 

MOVE statement statement-number is missing from-queue field. Statement is ignored. 

PSR10134 

MOVE statement statement-number has a from-queue which is too long. Statement is 

ignored. 

PSR10135 

MOVE statement statement-number duplicates previous from-queue. Statement is ignored. 

PSR10136 

On MOVE statement statement-number, queue queue-name does exist. Statement is 

ignored. 

PSR10137 

MOVE statement statement-number is missing the TO keyword. Statement is ignored. 

4-8 3787 3528-200

PSR10138 


MOVE statement statement-number is missing the to-queue field. Statement is ignored. 

PSR10139 

MOVE statement statement-number has a to-queue which is too long. Statement is ignored. 

PSR10140 

RUNID run-id is entering termination process. 

PSR10141 

MOVE statement statement-number has the same to- and from- queues. Statement is 

ignored. 

PSR10142 

MOVE statement statement-number has a to-queue which does not exist. Statement is 

ignored. 

PSR10143 

MOVE statement statement-number has missing qualifier mask or identifier field. 

Statement is ignored. 

PSR10144 

MOVE statement statement-number has unknown identifier: identifier. Statement is 

ignored. 

PSR10145 

MOVE statement statement-number has improper qual*file mask. Statement is ignored. 

PSR10146 

MOVE statement statement-number has missing file name mask field. Statement is 

ignored. 

PSR10147 

MOVE statement statement-number has missing banner-id mask field. Statement is 

ignored. 

PSR10148 

MOVE statement statement-number has missing project-id mask field. Statement is 

ignored. 

3787 3528-200 4-9


PSR10149 

MOVE statement statement-number has missing account-id mask field. Statement is 

ignored. 

PSR10150 

Terminating PSERVER activity. See DDP-PPC log file for more information. 

PSR10151 

MOVE statement statement-number has missing user-id mask field. Statement is ignored. 

PSR10152 

MOVE statement statement-number has missing run-id mask field. Statement is ignored. 

PSR10153 

MOVE statement statement-number has missing the ELSE keyword. Statement is ignored. 

PSR10154 

MOVE statement statement-number has missing else-queue field. Statement is ignored. 

PSR10155 

MOVE statement statement-number has else-queue which is too long. Statement is 

ignored. 

PSR10156 

MOVE statement statement-number in error. Else-queue cannot match from-queue. 

Statement is ignored. 

PSR10160 

ER KEYIN$ error: octal-code (octal) 

Explanation: 



PSR10165 

Unknown subfield for IOTRACE or DDPTRACE ... keyin ignored. 

4-10 3787 3528-200

PSR10166 

No input receiving configured. 

PSR10167 

** No input received yet ** 

PSR10168 

No output queues are configured. 

PSR10169 

** No files transfered yet ** 

PSR10170 


PS REDIR keyin ignored. PSERVER must be executed with the O-option. 

PSR10171 

Parameter missing on MSG-ON or MSG-OFF keyin. 

PSR10172 

Index provided is out of range. It cannot be less than 1 or larger than the total number of 

send statements. 

PSR10173 

Index provided is not in use. The send queue you referred to is marked as SPARE. 

PSR10174 

Delete of active queue is ignored. There is a transfer in-progress. 

PSR10175 

The QUEUE queue-name does not exist. 

PSR10176 

No spare queues are available for this ADD request. 

PSR10177 

Unknown keyin command entered for keyin type keyin-type. 

PSR10178 

Number entries changed. 

3787 3528-200 4-11


PSR10180 

PS ADD keyin ignored. PSERVER must be executed with the O-option. 

PSR10181/PSR10182 

Do NOT SX run-id or files will be lost. 

Explanation: 

This is a warning not to do an ’SX runid’. This warning will appear each time a PSERVER 

TERM or PSERVER ABORT command is performed. When followed by an A, this message 

requires an operator response. 

PSR10183 

RUNID run-id is in unattended mode. 

PSR10184 

Invalid MAX-Q-ACT value. Must be a number between 1 and 15. 

PSR10190 

PSERVER run-id run-id requires SMOQUE$ privileges. 

PSR10200 

Facilities error octal-code (octal) on queue-id for file qual*file-name (cycle). This is a fatal 

error. Make sure the file exists on your system. Notify your system administrator to correct 

the problem. 

Explanation: 



PSR10210/PSR10211 

Unexpected SMOQUE$ error: octal-code 

Explanation: 


for an explanation of the octal status code. When followed by an A, this message requires 

an operator response. 

PSR10215 

Sending AP has sent an abort message. 

4-12 3787 3528-200

PSR10216 


Receiving AP application-name has sent an abort message. 

PSR10217 

No response from application-name on attempt to open a session. 

PSR10218 

Nothing received from a sender application-name on attempt to receive a session. 

(DDP-PPC error: 003-015) 

Explanation: 



PSR10220 

DDP-PPC sign-on error: PPC-status-code. This is a fatal error. Notify your system 

administrator to correct the problem. 

Explanation: 



PSR10225 

SEND activity PPC sign-on error: PPC-status-code. The sign-on is attempted ten times. 

Then PSERVER is terminated. Notify your system administrator to correct the problem. 

Explanation: 



PSR10230 

DDP-PPC sign-off error: PPC-status-code. Notify your system administrator to correct the 

problem. 

Explanation: 



3787 3528-200 4-13


PSR10235 

DDP-PPC send error of 003-015 (no response) to file transfer from system host-name. 

Notify your system administrator to correct the problem. 

Explanation: 



PSR10240 

Checksum failure from host-name. A mismatch exists between data received at the 

destination system and the data sent. Your destination file may be corrupted. Re-send the 

file. 

PSR10250 

DDP-PPC open error: PPC-status-code. This is a fatal error. Check that the receiving 

system is up. Notify your system administrator to correct the problem. 

Explanation: 



PSR10255 

SEND activity PPC open error: PPC-status-code. Alternate path will be attempted. 

Explanation: 



PSR10260 

DDP-PPC receive error: PPC-status-code. This is a fatal error. Your transfer is no longer 

active. Notify your system administrator to correct the problem. 

Explanation: 



PSR10270 

Bad data in PSERVER status file. The file being read by PSERVER was assumed to be a 

TXFR status file with information about a tape transfer. But the file could not be read. If 

this problem persists, notify your system administrator to correct the problem. 

4-14 3787 3528-200

PSR10280 


Exceeded time limit. No file will be transferred. 

PSR10290 

ER-ACSF$ error: octal-code on file file-name. Notify your system administrator to correct 

the problem. 

Explanation: 



PSR10300 

File I/O error octal-code (octal) on FILE: qual*file-name (cycle). This is a fatal error. The 

file may be corrupted. Notify your system administrator to correct the problem. 

Explanation: 



PSR10310 

File on queue queue-name is not in SDF format. FILE: qual*file-name (cycle). The file 

cannot be transferred by PSERVER. Notify your system administrator to correct the 

problem. 

PSR10315 

File on queue queue-name has record > 290 chars. FILE: qual*file-name (cycle). The file 

cannot be transferred by PSERVER. Notify your system administrator to correct the 

problem. 

PSR10320 

ER-ACSF$ SYM error: octal-code. This is a fatal error. File from system host-name cannot 

be SYMed to queue queue-name. Notify your system administrator to correct the problem. 

Explanation: 



PSR10321 

To-queue not configured. File file-name cannot be SYMed. 

3787 3528-200 4-15


PSR10322 

You are trying to punch to a print queue. File file-name cannot be SYMed. 

PSR10323 

ER-ACSF$ SYM error: octal-code. This is a fatal error. File cannot be SYMed to queue 

queue-name. Notify your system administrator to correct the problem. 

Explanation: 



PSR10325 

Transfer exceeding number tracks in progress on queue queue-name. Notify your system 


PSR10330 

A PSERVER peer-status of DATA-ACK was not returned by the destination PSERVER. The 

transfer has been aborted. Re-try the transfer, or notify your system administrator to 

correct the problem. 

PSR10340/PSR10345 

Alternate path queue-name/host-name failed. Error messages on this path have been 

inhibited. 

Explanation: 

When the first part of this message is followed by an A, an operator response is required. 

PSR10350/PSR10355 

Primary path queue-name/host-name failed. Error messages on this path have been 

inhibited. 

Explanation: 

When the first part of this message is followed by an A, an operator response is required. 

PSR10360 

Alternate path not configured. 

PSR10370 

Alternate path queue-name/host-name to be attempted. 

4-16 3787 3528-200

PSR10390 


Unknown status passed. The RCV activity was expecting either close-request, 

file-to-be-xfered, or ckpt-file-to-be-xfered. None of these statuses was received, so the 

activity aborted. Notify your system administrator to correct the problem. 

PSR10391 

The PSERVER RCV activity got a status error in the UNIX-WRITE element. See the 

DDP-PPC log file for more information. The destination file may be corrupted. 

PSR10392 

The PSERVER RCV activity got an unknown error in the UNIX-WRITE element. See the 

DDP-PPC log file for more information. The destination file may be corrupted. 

PSR10400 

Facility or I/O error octal-code (octal) on host-name. This is a fatal error. Make sure the file 

exists on your system. Notify your system administrator to correct the problem. 

Explanation: 



PSR10410 

PSERVER received this ER LOG$ error status octal-code while trying to write to the system 

log file. See the DDP-PPC log file and the Executive Requests (ER) Programmer’s 

Reference Manual for more information. 

Explanation: 



PSR10420 

PSERVER recovered the following checkpoint file transfer: qual*file-name 

PSR10430 

Facilities error octal-code on file-name. This is a fatal error. Make sure the file exists on 

your system. Notify your system administrator to correct the problem. 

Explanation: 



3787 3528-200 4-17


PSR10450 

PSERVER SYM completed successfully for file: file-name 

PSR10451 

PSERVER SYM ERROR for file on queue queue-name 

PSR10452 

Queue queue-name does not exist on system host-name. Transferonqueue-name has 

terminated - A 

Explanation: 

This message requires an operator response. 

PSR10453 

A print/punch file was sent to punch/print queue queue-nameon system host-name. 

Transfer on host-name has terminated - A 

Explanation: 


PSR10454 

An @SYM error occurred while symming to queue queue-name on system host-name. 

Transfer on host-name has terminated - A 

Explanation: 


PSR10460 

PSERVER closing session early. A previous PSERVER RCV activity error occurred, causing 

the transfer to close the conversation early. 

PSR10470 

Pserver received a program hold file error of octal-code. This is a fatal error. Notify your 

system administrator to correct the problem. 

Explanation: 

This is an Exec ER PFWL$ status error. See the Exec System Software Executive Requests 

(ER) Programming Reference Manual for an explanation of the octal status code. 

4-18 3787 3528-200

PSR10480 


MOVE I/O read/write error octal-code (octal). This is a fatal error. Notify your system 


Explanation: 



PSR10495 

PSERVER attempted to move a TXFR file to invalid queue: queue-name. File will be moved 

to PR instead. 

PSR10500 

PSERVER got an ER-SMOQUE$ NO-FIND error when trying to delete a file from the 

HOLD-QUEUE. Notify your system administrator to correct the problem. 

PSR10510 

PSERVER found no data in a file that was left on the HOLD-QUEUE. This is a fatal error. 


PSR10515 

PSERVER found the userid user-id to be invalid on host host-name. The file will be moved 

to the HOLD queue. Notify your system administrator to correct the problem. 

PSR10520 

PSERVER could not find any OUTPUT-STATUS-QUEUE associated with the system 

host-name. All status information about any tape transfers done on this system cannot be 

sent back to the originating system. The status files will remain on the HOLD-QUEUE. 

To correct this problem, add an OUTPUT-STATUS-QUEUE to the SYS$LIB$TXFR-CONFIG 

on this system for the system on which the transfer was initiated. Then, re-queue the status 

files to this OUTPUT-STATUS-QUEUE. 

PSR10530 

PSERVER got ER-SUMOD$ error type: error-type code: octal-code. This is a fatal error. 


Explanation: 



3787 3528-200 4-19


PSR10535 

PSERVER got FAC error octal-code on @START of runstream. This is a fatal error. Notify 

your system administrator to correct the problem. 

Explanation: 



PSR10540 

PSERVER got ER-MSCON$ error octal-code. This is a fatal error. Notify your system 


Explanation: 



PSR10542 

PSERVER got FAC error octal-code trying to assign the tape pool file. Notify your system 


Explanation: 



PSR10550 

PSERVER found no path from the local host to system host-name. 

PSR10560 

PSERVER processor call error. This is the correct way to call the PSERVER processor: 

"@sys$lib$*ddp-fjt.pserver,[opts] [chkpt-file.]" or "@sys$lib$*ddp-fjt.pserver,[opts] 

[chkpt-file.]" 

PSR10565 

Error assigning CHECKPOINT file: octal-code. Checkpoint feature unavailable. 

Explanation: 



4-20 3787 3528-200

PSR10566 


I/O error octal-code (octal) or verify error reading checkpoint file. File will be initialized. 

Explanation: 



PSR10570 

PSERVER has aborted due to some previous fatal error. Close and process the DDP-PPC 

log file to get previous errors. Notify your system administrator to correct the problem. 

PSR10590 

PSERVER initialization has aborted due to some previous fatal error. Close and process 

the DDP-PPC log file to get previous errors. Notify your system administrator to correct 

the problem. 

PSR10610 

PSERVER has aborted due to some previous fatal error. Close and process the DDP-PPC 

log file to get previous errors. Notify your system administrator to correct the problem. 

PSR11000 

Unknown statement statement-number will be ignored. 

PSR11005 

Statement statement-number has unknown subfield field-name. Statement will be ignored. 

PSR11010 

Statement statement-number is missing the HOST field. Statement will be ignored. 

PSR11015 

Statement statement-number is missing the DEVICE-NAME field. Statement will be 

ignored. 

PSR11020 

Unable to assign sinch input. See DDP-PPC log file for more information. 

PSR11025 

Statement statement-number is ignored. Too many SINCH-PEER Statements. 

PSR11030 

Statement statement-number has invalid MAX-BLK-SIZE. Statement will be ignored. 

3787 3528-200 4-21


PSR11035 

Statement statement-number is missing the DEVICE-OUT field. Statement will be ignored. 

PSR11040 

Statement statement-number is ignored. Too many SINCH-OUTP Statements. Statement 

will be ignored. 

PSR11045 

Statement statement-number is missing the DEVICE-OUT field. Statement will be ignored. 

PSR11050 

Statement statement-number has field missing. Statement will be ignored. 

PSR11055 

Statement statement-number has invalid field. QUAL-FILE will be defaulted. 

PSR11060 

Statement statement-number has field missing. Statement will be ignored. 

PSR11065 

Statement statement-number has invalid field. QUAL-FILE will be defaulted. 

PSR11070 

ASSIGN-SIZE cannot exceed 262143. Statement will be ignored. 

PSR11075 

Invalid BANKPOOLMIN: value must be between 0 and number. 

PSR11080 

Invalid BANKPOOLMAX: value must be between 0 and number. 

PSR11081 

Invalid BANKPOOL values: MIN must be less than or equal to MAX. Parameters ignored. 

PSR11085 

Invalid RT-LEVEL: value must be between 0 or 2 thru 35. 

PSR11090 

Invalid LOOP-TIME: value must be greater than 0. 

PSR11095 

Statement statement-number is missing the send QUEUE-NAME. 

4-22 3787 3528-200

PSR11100 


Statement statement-number is missing the send TO-SYSTEM. 

PSR11105 

Statement statement-number is missing the send TO-QUEUE. 

PSR11110 

Unknown keywords where ALT or ALTERNATE should appear. Statement ignored. 

PSR11115 

Statement statement-number error: ALTERNATE not allowed on transfer to local host. 

Statement ignored. 

PSR11120 

Statement statement-number is missing the TO-AP-NAME. Statement ignored. 

PSR11125 

Statement statement-number is missing the TIME information. Statement ignored. 

PSR11130 

Statement statement-number has an invalid start time. Statement ignored. 

PSR11135 

Statement statement-number has an invalid end time. Statement ignored. 

PSR11140 

Statement statement-number error: start time is greater than end time. Statement ignored. 

PSR11145 

Statement statement-number has no valid alternate day values. Statement ignored. 

PSR11150 

Acquiring area for number SEND entries. 

PSR11155 

No valid SEND, MOVE or RECEIVE directives. 

PSR11160 

Invalid SPARE-SENDS value - must be greater than 0. Default of 5 will be used. 

PSR11165 

Recover run-id from the checkpoint file? 

3787 3528-200 4-23


PSR11235 

Block size exceeds maximum size. COPY aborted. 

PSR11240 

ER TLBL$ error: octal-code. This is a fatal error. TXFCPY will be aborted. Notify your 


Explanation: 



PSR11245 

Block sequence error. This is a fatal error. TXFCPY will be aborted. Notify your system 


PSR11250 

Incompatible TXFCPY levels installed. This is a fatal error. TXFCPY will be aborted. Notify 


PSR11255 

TXFCPY contingency error. See DDP-PPC log file for more information. Notify your 


PSR11260 

Probable tape pool file/reel# error. This is a fatal error. TXFCPY will be aborted. Notify 


PSR11265 

Probable tape labeling/options error. This is a fatal error. TXFCPY will be aborted. Notify 


PSR11270 

TXFCPY processor call error. This is a fatal error. The correct way to call TXFCPY is as 

follows: 

 

PSR11275 

The TXFR tape pool file cannot be a temporary file. Notify your system administrator to 

correct the problem. 

PSR11280 

ER-CSF$ error octal-code on file-name. Notify your system administrator to correct the 

problem. 

4-24 3787 3528-200

Explanation: 




PSR11285 

ER-PFS error octal-code. The input element may not be in the file. Notify your system 


Explanation: 



PSR11290 

This file was not created by a compatible level of TXFCPY. Notify your system 


PSR11295 

Unknown equipment code on file. 

PSR11300 

TXFCPY error: The input and output files are either both tape or both disk. This is a fatal 

error. 

PSR11305 

TXFCPY error: The TLBL$ status indicates that the input file is badly positioned. This is a 

fatal error. 

PSR11310 

The {input/output} tape is {labeled/unlabeled}. 

PSR11315 

ER PFWL error: octal-code. The output element may not be in the file. 

Explanation: 



PSR11320 

No files copied. Transfer has been aborted. 

PSR11325 

TXFCPY cannot find the input file on the hold queue in order to delete it. No deletion will 

be done. 

3787 3528-200 4-25


PSR11330 

TXFCPY got error octal-code when trying to sym the TXFR STATUS file to queue 

queue-name. 

Explanation: 



PSR11335 

TXFCPY got error octal-code when trying to free the TXFR STATUS file. 

Explanation: 



PSR11340 

ER PFI error: octal-code. The input element may not be in the file. 

Explanation: 



4-26 3787 3528-200

Section 5 

DDP-PPC Log and Trace Facility 


This section alphabetically lists error messages returned to the operator’s console when 

the log/trace background run processes a user command. 

Command Service Format (CSF) and Initiate I/O and Wait (IOW) status codes returned 

with messages are contained in the Exec System Software Executive Requests 

Programming Reference Manual. 

3787 3528-200 5-1

DDP-PPC Log and Trace Facility Messages 

BATCH START JOB QUEUED 

Explanation: 

Notifies you that a job stream has been queued for processing a trace file as a result of a 

log or trace CLOSE,PROCESS request. 

CLOSED DDP-PPC LOG FILE SYS$LIB$*DDP$LOG(...) 

Explanation: 

Indicates that the log file was successfully closed. A file is closed when either the CLOSE 

or TERM command is entered, or when the file becomes full. 

CLOSED DDP-PPC TRACE FILE SYS$LIB$*DDP$TRC(...) 

Explanation: 

Indicates that the trace file was successfully closed. A file is closed when either the CLOSE 

or TERM command is entered, or when the file becomes full. 

CLOSED/TRMRG DDP-PPC LOG FILE SYS$LIB$*DDP$LOG(...) 

Explanation: 

Indicates that the log file was closed during TRMRG processing. 

CLOSED/TRMRG DDP-PPC TRACE FILE SYS$LIB$*DDP$LOG(...) 

Explanation: 

Indicates that the trace file was closed during TRMRG processing. 

CONFIGURATION SERVICES ERROR STATUS = x / SUBSTATUS = y 

Explanation: 

DDPLTR experienced an error attempting to access the configuration services database. 

The status and substatus codes are octal values. Refer to Table B-1 at the end of Section 8. 

Action: 

The corrective action is determined by the specific error reported. 

5-2 3787 3528-200


CURRENT DDP-PPC LOG FILE IS SYS$LIB$*DDP$LOG(...) 

Explanation: 

Indicates the current cycle of the log file. It is displayed when DDP-PPC initialization 

invokes Distributed Data Processing Log and Trace (DDPLTR), or when the log file is 

closed and the next F-cycle is assigned. 

CURRENT DDP-PPC TRACE FILE IS SYS$LIB$*DDP$TRC(...) 

Explanation: 

Indicates the current cycle of the trace file. It is displayed when DDP-PPC initialization 

invokes DDPLTR, or when the trace file is closed and the next F-cycle is assigned. 

CURRENTLY PROCESSING A PREVIOUS REQUEST TO OPEN FILE 

Explanation: 

A request to open a log/trace file was made while DDPLTR was in the process of opening a 

log/trace file. 

DDPLTR PROGRAM IS ALREADY ACTIVE 

Explanation: 

A version of DDPLTR was currently running when you tried to start it. 

DDPLTR TERMINATION PROCESS COMPLETE 

Explanation: 

This is the final statement from DDPLTR as the result of termination processing. It is 

informational only. 

DDPLTR COMMAND MODE COMPLETE 

Explanation: 

This message is displayed in response to the END command. 

3787 3528-200 5-3


DDPLTR TERMINATING--UNABLE TO OBTAIN LOG AND TRACE FILES 

Explanation: 

DDPLTR was unable to assign both the log and trace files. This message should be 

preceded by one or two messages stating the specific error conditions. This is an 

unrecoverable error. 

Action: 

The corrective action is determined by the specific errors reported. The DDPLTR run will 

have to be restarted manually with the following command: 

 

DDP-PPC LOG/TRACE FILE IS UNAVAILABLE --REQ IGNORED 

Explanation: 

A request was made to close a log or trace file when no log or trace file was available. 

DDP-PPC SUBSYSTEM BEING DEACTIVATED, DDPLTR PROGRAM NOT 

AVAILABLE 

Explanation: 

A log or trace function was requested while the DDP-PPC subsystem was being 

deactivated. 

FILE IS ALREADY OPENED 

Explanation: 

A request to open a log/trace file was made when a log/trace file was currently active. This 

message is only informational. 

INCORRECT PARAMETER SUPPLIED WITH CLOSE REQUEST 

Explanation: 

The only option accepted on a file close command is the PROCESS option. 

Action: 

Correct the command and reenter. 

5-4 3787 3528-200

INVALID DDPTYPE SELECTED 

Explanation: 


The DDPTYPE entered on the trace command was not recognized by DDPLTR. This is a 

recoverable error. 

Action: 

Verify the DDPTYPEs registered with DDPLTR. Reenter the command with a valid 

DDPTYPE. 

INVALID FUNCTION REQUESTED 

Explanation: 

If using the format 1 operator interface (II DDPLTR), valid commands in response to the 

ENTER COMMAND prompt are: 

$ LOG 

$ TRACE 

$ LIST 

$ STATUS 

$ TERM 

If using the format 2 operator interface (II DDPLTR COMMAND), valid commands in 

response to the ENTER COMMAND prompt are: 

$ TRACE 

$ LIST 

$ STATUS 

$ TERM 

Action: 

Correct and reenter the command. 

3787 3528-200 5-5


INVALID LEVEL SUPPLIED 

Explanation: 

The level entered on the TRACE ON command, or the level associated with the specified 

DDPTYPE was not a numeric value. 

Action: 

Verify the levels registered with DDPLTR for the DDPTYPE in question. Reenter the 

command with a valid level. 

INVALID SUBFUNCTION SUPPLIED 

Explanation: 

The only subfunction accepted on a LOG command is the CLOSE subfunction. 

Action: 

Correct the command and reenter. 

LOG FILE UNAVAILABLE--CSF ERR=__________________ 

Explanation: 

DDPLTR experienced an error either in assigning the log file or in establishing the 

USE-name for the file. The severity of this error is determined by the specific error 

reported. 

Action: 

Issue LOG OPEN command once the reported error condition has been corrected. 

LOG FILE UNAVAILABLE--IOW ERR=____________________ 

Explanation: 

DDPLTR experienced an error writing the log header to the log file file. The severity of this 

error is determined by the specific error reported. 

Action: 

Issue LOG OPEN command once the reported error condition has been corrected. 

5-6 3787 3528-200


TRACE FILE UNAVAILABLE--CSF ERR=__________________ 

Explanation: 

DDPLTR experienced an error either in assigning the trace file or in establishing the 

USE-name for the file. 

Action: 

Issue TRACE OPEN command once the reported error condition has been corrected. 

TRACE FILE UNAVAILABLE--IOW ERR=________________ 

Explanation: 

DDPLTR experienced an error writing the trace header to the trace file. 

Action: 

Issue TRACE OPEN command once reported error condition has been corrected. 

UNABLE TO FREE LOG FILE--CSF ERR=__________________ 

Explanation: 

DDPLTR experienced an error attempting to free the log file. 

Action: 


UNABLE TO FREE TRACE FILE--CSF ERR=__________________ 

Explanation: 

DDPLTR experienced an error attempting to free the trace file. 

Action: 


3787 3528-200 5-7


UNABLE TO READ HDR--IOW ERR=________________ 

Explanation: 

DDPLTR experienced an error attempting to read the log/trace header record (during the 

process of closing the file in question). 

Action: 


UNABLE TO START REQUEST--CSF ERROR=________________ 

Explanation: 

Unable to initiate the start stream to process the log/trace file on a log or trace 

CLOSE,PROCESS request due to the specified CSF error. 

Action: 

The file is already closed. You will need to process the file using the DDP utility with the P 

option and respond to the prompts. 

UNABLE TO START REQUEST--IOW ERROR=________________ 

Explanation: 

Unable to initiate the start stream to process the log/trace file on a log or trace 

CLOSE,PROCESS request due to the specified IOW error. 

Action: 

The file is already closed. You will need to process the file using the DDP utility with the P 

option and respond to the prompts. 

UNABLE TO WRITE DATA--IOW ERR=_______________ 

Explanation: 

DDPLTR experienced an error attempting to write the log/trace data to the file. The 

severity of this error is determined by the specific error reported. 

Action: 


5-8 3787 3528-200


UNABLE TO WRITE EOF--IOW ERR=___________________ 

Explanation: 

DDPLTR experienced an error attempting to write the end-of-file record to the log/trace 

file. The severity of this error is determined by the specific error reported. DDPLTR 

continues with the close procedure. 

Action: 


UNABLE TO WRITE HDR--IOW ERROR=________________ 

Explanation: 

DDPLTR experienced an error attempting to write the log/trace header record (during the 

process of closing the file in question). The severity of the error is determined by the 

specific error reported. No closing date or time will be in the edited output file. 

Action: 


3787 3528-200 5-9

Section 6 

PPCMASTER Run Messages 

This section numerically lists error and status messages generated by the PPCMASTER 

run. These messages are issued during either initialization or operation. 

Additional information about some of these messages can be found in the DDP-PPC log file. 

3787 3528-200 6-1


DDP-PPC1 

PPCMASTER RUN ALREADY ACTIVE 

Explanation: 

An attempt was made to start a PPCMASTER run when one was already active. 

Action: 

Terminate the active run if a new PPCMASTER run is needed. 


PPCMASTER INITIALIZATION IS IN PROGRESS 

Explanation: 

Status message only. PPCMASTER run initialization has begun. 


DDP-PPC IP$NETD STATIC TABLES INITIALIZING 

Explanation: 

Status message only for PPCMASTER run initialization. 


DDP-PPC IP$NETD BUFFER POOL INITIALIZING 

Explanation: 



DDP-PPC CDB BANK CONTROL TABLE INITIALIZING 

Explanation: 



PPCMASTER RUN INITIALIZATION COMPLETE 

Explanation: 

Status message only for PPCMASTER run initialization completion. 

6-2 3787 3528-200


COMMAND IGNORED 

Explanation: 

Current command will not be procesed due to previous error. 



ERROR WHEN REGISTERING WITH PPC CONFIGURATION SERVICES 

Explanation: 

Unable to access the DDP-PPC configuration file. 

Action: 

Check the status of the DDP-PPC configuration file. 


TYPE xxxxxx DUMP FOR xxxxxx/xxxxxx IN DDP$DUMP*xxxxxx 

Explanation: 

Informational message specifying the type of dump taken, the run-id and switch-list-id of 

the run taking the dump, and the file containing the dump. 


UNABLE TO ASSIGN DUMP FILE FOR xxxxxx/xxxxxx, STATUS = xxxxxx 

FAC STATUS = xxxxxx 

Explanation: 

Error occurred attempting to assign a dump file. Check FAC status for further explanation. 

Action: 


for a description of the error status and facility status codes. 

3787 3528-200 6-3



DDP-DUMP TERMINATED WITH CNTG ERROR, STATUS = xxxxxx 

CNTG ERROR = xxxxxx 

Explanation: 

Error occurred while taking dump. 

Action: 


for a description of the error status and contingency status. 


INTERNAL ERROR WHILE PROCESSING DUMP FOR xxxxxx/xxxxxx 

STATUS = xxxxxx, SUBSTATUS = xxxxxx 

Explanation: 

Error occurred processing dump. 

Action: 


for a description of the status and substatus fields codes. 


xxxxxx UP ATTEMPTED IN AN INVALID STATE 

CURRENT STATE IS: xxxxxx 

Explanation: 

An UP command was attempted for a component in an invalid state. The UP command is 

ignored. 

6-4 3787 3528-200


xxxxxx COMPONENT-STATE IS UNKNOWN 

UP NOT ALLOWED 

Explanation: 


An UP command was attempted for a component which is in the UNKNOWN state. 

Action: 

Restart the PPCMASTER run to bring this component back up. 


xxxxxx UP-IN-PROGRESS 

Explanation: 

Status message only, component is in the process of coming up. 


INVALID EVENT FOUND ON EVENT QUEUE 

Explanation: 

Error specifying an invalid event was found on the event queue. The error is logged and 

processing continues. 


ERROR READING PPCMASTER RECORD IN PPC CONFIGURATION FILE 

CHECK PPCMASTER RECORD IN PPC CONFIGURATION FILE 

Explanation: 

The PPCMASTER record could not be read from the DDP-PPC configuration file. 

Action: 

Check the DDP-PPC configuration file status. 

3787 3528-200 6-5



DOWN OF xxxxxx DISCARDED 

Explanation: 

A DOWN command was issued for a component which is in the process of shutting down. 

The DOWN command is ignored. 


DOWN OF xxxxxx FAILED 

Explanation: 

An attempt was made to down a component which was not up or in the process of coming 

up. 


SHTDWN OF xxxxxx DISCARDED u SUBSEQUENT DOWN ISSUED 

Explanation: 

A DOWN command was issued for a component before a previous SHTDWN command 

was processed. The DOWN command is processed and the SHTDWN command is ignored. 


SHTDWN OF xxxxxx FAILED 

CURRENT STATE IS: xxxxxx 

Explanation: 

An attempt was made to shut down a component which was not up or in the process of 

coming up. 

6-6 3787 3528-200


UP SNAPPC FAILED 

NODE RECORD MISSING FROM PPC CONFIGURATION FILE 

Explanation: 


SNAPPC requires a NODE record be present in the DDP-PPC configuration file, and none 

was found. 

Action: 

Add a NODE record to the DDP-PPC configuration file and retry. 


ERROR READING NODE RECORD FROM PPC CONFIGURATION FILE 

SNAPPC WILL NOT BE STARTED 

Explanation: 

An error occurred reading the NODE record from the DDP-PPC configuration file. 

SNAPPC will not be brought up. 


UP SNARJE FAILED 

NODET1 RECORD MISSING FROM PPC CONFIGURATION FILE 

Explanation: 

SNARJE requires a NODET1 record be present in the DDP-PPC configuration file and none 

was found. 

Action: 

Add a NODET1 record to the DDP-PPC configuration file and retry. 

3787 3528-200 6-7



ERROR READING NODET1 RECORD FROM PPC CONFIGURATION FILE 

SNARJE WILL NOT BE STARTED 

Explanation: 

An error occurred reading the NODET1 record from the DDP-PPC configuration file. 

SNARJE will not be brought up. 


UP SMT FAILED 

COMPONENT SMT REQUIRES CMS-NUMBER 

Explanation: 

SMT requires a CMS-number in the PPCMASTER record and none was found. SMT will not 

be brought up. 

Action: 

Add the correct CMS-number to the PPCMASTER record and retry. 


UP xxxxxx FAILED 

xxxxxx REQUIRES OSITSU 

DOWN/SHTDWN QUEUED FOR OSITSU 

Explanation: 

An attempt was made to up a component which requires the OSITSU component, and the 

OSITSU component is in the process of coming down. 

Action: 

Restart the OSITSU component after the down/shtdwn completes and retry. 

6-8 3787 3528-200


UP xxxxxx FAILED 

xxxxxx REQUIRES OSITSU 

COMPONENT OSITSU STATE IS: xxxxxx 

Explanation: 


An attempt was made to up a component which requires the OSITSU component, and the 

OSITSU component is not up or in the process of coming up. 

Action: 

Up the OSITSU and retry. 


PPCMASTER RUN SHTDWN IN PROGRESS 

Explanation: 

Status message indicating a shutdown of the PPCMASTER run has begun. 


PPCMASTER RUN TERM IN PROGRESS 

Explanation: 

Status message indicating a TERM of the PPCMASTER run has begun. No further 

commands are accepted. 


PPCMASTER RUN ABORT IN PROGRESS 

Explanation: 

Status message indicating an ABORT of the PPCMASTER run has begun. No further 

commands are accepted. 


PPCMASTER RUN TERMINATED 

Explanation: 

Status message indicating PPCMASTER run has terminated normally. 

3787 3528-200 6-9



PPCMASTER ACTIVITIES HAVE NOT EXITED IN ALLOTTED TIME 

ABORTING PPCMASTER RUN 

An error occurred terminating one of the PPCMASTER run activities. The run is aborted. 


PPCMASTER ACTIVITIES HAVE NOT STARTED IN ALLOTTED TIME 

ABORTING PPCMASTER RUN 

Explanation: 

An error occurred starting one of the PPCMASTER run activities. The run is aborted. 


DDPLTR STARTED 

Explanation: 

Status message indicating the DDPLTR run has been started. 


@START DDPLTR FAILED DUE TO IMPROPER RUNSTREAM 

Explanation: 

The runstream used to start the DDPLTR run is in error. 

Action: 

Correct the runstream and retry. 


@START DDPLTR FAILED DUE TO FILE UNOBTAINABLE 

Explanation: 

File required for DDPLTR run could not be obtained. 

Action: 

Check status of file. 

6-10 3787 3528-200


@START DDPLTR FAILED DUE TO ELEMENT UNOBTAINABLE 

Explanation: 

Element required for DDPLTR run could not be found. 

Action: 

Check status of the element. 


@START DDPLTR FAILED DUE TO I/O ERROR 

Explanation: 

DDPLTR run could not be started due to I/O error. 


@START DDPLTR FAILED DUE TO FILE NOT CATALOGUED 

Explanation: 

File required for DDPLTR run is not cataloged. 


@START DDPLTR FAILED DUE TO SECURITY VIOLATION 

Explanation: 

DDPLTR run could not be started because of a security violation. 

Action: 

Verify run privileges required for DDPLTR. 



@START DDPLTR RETURNED UNEXPECTED ERROR u STATUS IS : xxxxxx 

Explanation: 

DDPLTR run could not be started due to unexpected error. 

Action: 

Check status for further explanation. 

3787 3528-200 6-11



xxxxxx FOR yyyyyy TIMEOUT 

Explanation: 

A state transition (xxxxxx) for a component (yyyyyy) did not occur within the alloted 

time. The component is aborted. 


COMPONENT xxxxxx DID NOT SUCCESSFULLY COMPLETE STATE-TRANSITION 

PPCMASTER MUST BE TERMED AND RESTARTED TO USE THIS COMPONENT AGAIN 

Explanation: 

A timeout occurred while attempting to change the state of a component. The component 

is put in the UNKNOWN state and cannot be brought back up until the PPCMASTER run is 

restarted. 


xxxxxx ABORT IN PROGRESS 

Explanation: 

Status message indicating the component is in the process of being aborted. 


CONSOLE ACTIVITY STARTED 

Explanation: 

Status message indicating the PPCMASTER run console activity has been started. 


MONITOR ACTIVITY STARTED 

Explanation: 

Status message indicating the PPCMASTER run monitor activity has been started. 

6-12 3787 3528-200


START-RUN ACTIVITY STARTED 

Explanation: 


Status message indicating the PPCMASTER run start-run activity has been started. 


UNEXPECTED ERROR INITIALIZING PPCMASTER 

Explanation: 

An unexpected error occurred during PPCMASTER run initialization and the run is 

terminated. 


COMPONENT xxxxxx DOWN COMPLETE 

Explanation: 

Status message indicating the component has come down. 


COMPONENT xxxxxx SHTDWN COMPLETE 

Explanation: 

Status message indicating the component has shut down. 


COMPONENT xxxxxx ABTERM COMPLETE 

Explanation: 

Status message indicating the component has abnormally terminated. 


COMPONENT xxxxxx ABORT COMPLETE 

Explanation: 

Status message indicating the component has aborted. 

3787 3528-200 6-13



INVALID OPTION SPECIFIED - PROGRAM TERMINATED 

Explanation: 

An invalid option was specified on the PPCMASTER run processor call. The valid option 

are: 

$ i - Reload NETD bank as part of initialization 

$ No options 


ERROR READING PPCMASTER RECORD FROM PPC CONFIGURATION FILE 

PPCMASTER WILL NOT INITIATE TIP TRANSACTIONS 

Explanation: 

An error occurred reading the PPCMASTER record from the DDP-PPC configuration file 

attempting to get the PID and CMS numbers for the start-run activity. 

The numbers are set to 0 and processing continues. 


UP SMT FAILED 

UNABLE TO READ PPCMASTER RECORD FROM PPC CONFIGURATION FILE 

Explanation: 

An error occurred reading the PPCMASTER record from the DDP-PPC configuration file 

while attempting to verify that the CMS-number exists in the record. SMT is not brought up. 

Action: 

Verify that the CMS-number is in the PPCMASTER record. 


UNABLE TO INITIALIZE PPC SUBSYSTEM 

Explanation: 

An error occurred attempting to initialize the PPC subsystem. Processing continues. 

6-14 3787 3528-200


PPCMASTER RUN SHTDWN IN PROGRESS 

WAITING FOR CONVERSATIONS TO COMPLETE 

Explanation: 


Status message indicating that there are still local conversations running and shutdown of 

the PPCMASTER run cannot yet be completed. 


PROCESSOR CALL ERROR 

Explanation: 

An error occurred on the processor call for PPCMASTER. The run is terminated. 


ABNORMAL RETURN FROM READ$ ON PROCESSOR CALL 

Explanation: 

An error occurred attempting to read data images on the PPCMASTER processor call. The 

run is terminated. 


TOO MANY SPECIFICATIONS ON PROCESSOR CALL 

Explanation: 

Too many parameters were specified on the PPCMASTER processor call. The run is 

terminated. 


UNEXPECTED ERROR ON PROCESSOR CALL 

Explanation: 

An unexpected error occurred on the PPCMASTER processor call. The run is terminated. 

3787 3528-200 6-15



UNABLE TO ACQUIRE IP$NETD BANK u PROGRAM TERMINATED 

Explanation: 

An error occurred while attempting to acquire the IP$NETD bank. The run is terminated. 


UNABLE TO ACQUIRE SWITCH-LIST TABLE BANK u PROGRAM TERMINATED 

Explanation: 

An error occurred while attempting to acquire the switch-list table bank pool. The run is 

terminated. 


PPCMASTER DEACTIVATING SUBSYSTEM BEFORE INITIALIZATION 

Explanation: 

The DDP-PPC subsystem will be deactivated before initialization as requested by the I 

option on the processor call. 


PPCMASTER ISSUING AN SFREE_ALL TO RELEASE SHARED MEMORY 

Explanation: 

All acquired shared memory from previous activities is released. 


ENTER COMMAND 

Explanation: 

Response message from console interface requesting input. 


xxxxxx IS AN INVALID PPCMASTER COMMANDu IGNORED 

Explanation: 

A non-supported command was entered. The command is ignored. 

6-16 3787 3528-200


xxxxxx IS AN INVALID COMPONENT 

Explanation: 

A request was made to an unknown component. The request is ignored. 


xxxxxx COMMAND IS INVALID FOR PPCMASTER RUN 

Explanation: 


A system supported command which is valid only for a component was entered for the 

PPCMASTER run. The command is ignored. 


xxxxxx COMMAND IS VALID ONLY FOR PPCMASTER RUN 

Explanation: 

A system supported command which is valid only for the PPCMASTER run was entered for 

a component. The command is ignored. 


INPUT MODE PROCESSING COMPLETE 

Explanation: 

Indicates the console interface received the END command and is waiting for an 

unsolicited input. 

Action: 

Key in II at the console or @@X C from a demand terminal to enter any additional 

commands. 


PPCMASTER TERM IN PROGRESS u CURRENT REQUEST IGNORED 

Explanation: 

The requested function is invalid after a term of the PPCMASTER run was initiated. The 

command is ignored. 

3787 3528-200 6-17



PPCMASTER xxxxxx QUEUED u CURRENT REQUEST IGNORED 

Explanation: 

The requested function is not valid at this time because there is another command queued 

for the run. 


PPCMASTER SHTDWN QUEUED... 

DO YOU REALLY WANT TO TERM? (Y/n) 

Explanation: 

A validation message indicating that the PPCMASTER run has a shutdown request queued 

when a TERM command was entered. The default response is Y, in which the termination 

request is accepted and will override the previous shutdown request. 


xxxxxx REQUEST DISCARDED 

Explanation: 

A message to indicate the request was discarded because ’no’ was entered to one of the 

validation messages. 


PPCMASTER SHTDWN IN PROGRESS... 

DO YOU REALLY WANT TO TERM? (Y/n) 

Explanation: 

A validation message indicating that the PPCMASTER run is in shutdown mode when a 

TERM command was entered. The default is yes, in which the termination request is 

accepted and will overide the previous shutdown request. 


xxxxxx REQUEST QUEUED 

Explanation: 

Indicates the request was accepted and is on queue to be processed.This message is output 

only to the PPCMASTER run PRINT$ file. 

6-18 3787 3528-200


DO YOU REALLY WANT TO ABORT PPCMASTER? (Y/n) 

Explanation: 


A validation message to make sure that the intent is to abort the PPCMASTER run. The 

default response is Y, which results in the PPCMASTER run error termination. 


PPCMASTER ABORTING 

Explanation: 

A message which indicates the response to message 113 was Y. 


PPCMASTER CONSOLE INTERFACE DEACTIVATING 

Explanation: 

This message indicates the console interface is terminating. It is output just prior to 

notifying the coordinator activity to abort the run. 

This message is output only to the PPCMASTER run print$ file. 


PPCMASTER SHTDWN ALREADY IN PROGRESS u CURRENT REQUEST IGNORED 

Explanation: 

A shutdown of the run or a component, or an up was requested of a component after the 

PPCMASTER run was in shutdown mode. 

The request is ignored. 

3787 3528-200 6-19



PREVIOUS xxxxxx COMMAND IS PENDING u CURRENT REQUEST IGNORED 

Explanation: 

Either: 

$ An up or shutdown for a component was requested when the identified previous 

command has not been processed. 

$ A down was requested of a component while an up or down for that component was 

still pending. 



PREVIOUS xxxxxx COMMAND STILL QUEUED--CURRENT REQUEST IGNORED 

Explanation: 

Either: 

$ An up or shutdown for a component was requested when the identified previous 

command is queued for processing. 

$ A down was requested of a component while an up or down for that component was 

still queued for processing. 



COMPONENT xxxxxx STATE IS xxxxxx u CURRENT REQUEST IGNORED 

Explanation: 

Various commands cannot be issued when the component is in certain states: 

$ A shutdown can only be requested when the current component state is UP, 

UP-IN-PROGRESS, or RESET-IN-PROGRESS. 

$ A component up cannot be requested when the current component state is UP, 

UP-IN-PROGRESS, RESET-IN-PROGRESS, or UNKNOWN. 

$ A component down cannot be requested unless the state of the component is UP, 

UP-IN-PROGRESS, RESET-IN-PROGRESS, SHTDWN-NOTICE, or 

SHTDWN-IN-PROGRESS. 

6-20 3787 3528-200


DOWN IS NOT VALID IF PPCMASTER IS IN STATE xxxxxx 

CURRENT REQUEST IGNORED 

Explanation: 


The PPCMASTER run state must be UP or SHTDWN-IN-PROGRESS when a down of the 

run is requested. 



PREVIOUS xxxxxx COMMAND STILL PENDING u 

DO YOU REALLY WANT TO DOWN? (Y/n) 

Explanation: 

A validation message indicating that the component has a shutdown request pending when 

this DOWN command was requested. The default response is Y, resulting in the acceptance 

of the down request. 


PREVIOUS xxxxxx COMMAND STILL QUEUED-- 


Explanation: 

A validation message indicating that the component has a shutdown request queued when 

this DOWN command was requested. The default response is Y, resulting in the acceptance 

of the down request. 


COMPONENT STATE IS xxxxxx ... 


Explanation: 

A validation message indicating that the down of the component was issued when its state 

was SHTDWN-NOTICE or SHTDWN-IN-PROGRESS. The default response is Y, which 

results in the acceptance of the down request. 

3787 3528-200 6-21



THE CURRENT PPCMASTER ENVIRONMENT IS: 

RUN STATE : xxxxxx SIGNED-ON USERS : xxxxxx 

THE CURRENT STATES OF THE COMPONENTS ARE: 

OSITSU : xxxxxx TASTSU : xxxxxx 

SMT : xxxxxx 

SNAPPC : xxxxxx SNARJE : xxxxxx 

Explanation: 

Response to the request for status of the PPCMASTER run. 


xxxxxx COMPONENT STATE IS : xxxxxx 

Explanation: 

Response to the request for status of the specified component. 


PPCMASTER xxxxxx ACTIVITY TERMINATED 

Explanation: 

Specified PPCMASTER run activity has terminated normally. 

This message is output only to the PPCMASTER run PRINT$ file. 


PPCMASTER xxxxxx ACTIVITY CONTINGENCY PROCESS COMPLETE 

Explanation: 

Specified PPCMASTER run activity has terminated due to an abnormal condition. 


6-22 3787 3528-200


PPCMASTER CDB REINITIALIZED WHILE xxxxxx ACTIVE 

Explanation: 


The common data bank which contains the PPCMASTER run’s control information has 

been reinitialized while the specified activity was active. 



PPCMASTER xxxxxx ABORT IN PROGRESS 

Explanation: 

This message is output prior to actual error termination of the PPCMASTER run due to an 

abort request. 


PPCMASTER xxxxxx ACTIVITY TRMRG PROCESS COMPLETE 

Explanation: 

The specified activity of the PPCMASTER run has terminated either due to an abnormal 

termination or as the result of an executive ’e’ keyin for the run. 



PPCMASTER xxxxxx ERROR TERMINATION 

Explanation: 

Identified activity of the PPCMASTER run error terminated because it did not complete the 

change of state processing within the specified time limit. 



ENTERING PPCMASTER xxxxxx TRMRG PROCESS 

Explanation: 

The identified activity of the PPCMASTER run is terminating abnormally. 


3787 3528-200 6-23



PPCMASTER xxxxxx CONTINGENCY DURING TRMRG PROCESS 

Explanation: 

The identified activity of the PPCMASTER run received an error while terminating 

abnormally. 




Explanation: 





** xxxxxx UNABLE TO INITIALIZE ** 

Explanation: 

Indicates that the specified activity was unable to initialize. 


** xxxxxx UNABLE TO OBTAIN MEMORY FOR PSEUDO QUEUE ** 

Explanation: 

The specified TSU was unable to obtain memory for its output queue. 



** xxxxxx INITIALIZATION COMPLETE ** 

Explanation: 

The specified component has completed its initialization process and is now up. 

6-24 3787 3528-200


** xxxxxx cannot START OUTPUT ACTIVITY ** 

Explanation: 


The output activity of the identified TSU would not activate. This will result in the TSU 

being unable to complete its initialization. 



** xxxxxx cannot START TIMER ACTIVITY ** 

Explanation: 

The timer activity of the OSITSU would not activate. This will result in the OSITSU being 

unable to complete its initialization. 



** xxxxxx ATTACH FAILED u CMS INSUFFICIENT RESOURCES u 

WILL RETRY IN 30 SEC ** 

Explanation: 

The attach request to CMS 1100 via TSAM for the identified TSU failed due to CMS 

insufficient resources. A reattach will be attempted for a specified increment every 30 

seconds in case CMS resources become available. 


** MAX ATTACH RETRIES REACHED FOR xxxxxx ** 

Explanation: 

The identified TSU was unable to attach to CMS1100 after predefined amount of attempts. 

3787 3528-200 6-25



** xxxxxx ACTIVITY TERMINATED ** 

Explanation: 

Indicates the identified activity of a component has terminated normally. This message is 

output only to the PPCMASTER run PRINT$ file. 


** xxxxxx COMPONENT INITIALIZATION IN PROG ** 

Explanation: 

The identified component has begun its initialization process. 


** CMS1100 DETACHED WHILE xxxxxx ACTIVE 

COMPONENT RE-INITIALIZATION IN PROGRESS ** 

Explanation: 

CMS 1100 detached the specified TSU while the TSU was active. The TSU will attempt to 

reattach to CMS a predefined amount of times. All active connections have been 

terminated by CMS and will result in error terminations of current sessions. 


** xxxxxx COMPONENT INITIALIZATION REQUESTED 

IN THE WRONG STATE ** 

Explanation: 

A request was made to initialize the identified TSU while its current state was not 

UP-IN-PROGRESS or RESET-IN-PROGRESS. 


6-26 3787 3528-200


** CS FAILURE WITH GET xxxxxx REQUEST ** 

Explanation: 


An error was returned while attempting to read the identified record from the DDP-PPC 

configuration file. 

If the record was not in the configuration file, this message will be followed by message 

DDP-PPC214. 


Action: 

If DDP-PPC214 does not follow, refer to the DDP-PPC log file for the specific reject reason. 


** xxxxxx RECORD MISSING FROM CONFIGURATION FILE ** 

Explanation: 

The identified TSU record is missing from the DDP-PPC configuration file. 



** CS BEGIN FAILED FOR COMPONENT xxxxxx ** 

Explanation: 

The identified component’s initialization to the DDP-PPC configuration data base was 

rejected. 


Action: 

Refer to the DDP-PPC log file for the specific reject reason. 

3787 3528-200 6-27



** xxxxxx ACTIVITY CNTG TERMINATED ** 

Explanation: 

The identified activity terminated abnormally due to internal errors. 


Action: 

Refer to the DDP-PPC log file or the PPCMASTER run PRINT$ file for the reason for the 

contingency. 


** xxxxxx ACTIVITY ERROR TERMINATED BY PPCMASTER ** 

Explanation: 

The identified activity was abnormally terminated by the PPCMASTER run because it did 

not complete process of a change of state within a specified interval. 



** xxxxxx ACTIVITY TRMRG COMPLETE ** 

Explanation: 

The identified activity completed termination processing. 



** ENTER xxxxxx TRMRG PROCESS ** 

Explanation: 

The identified activity has begun termination processing as the result of an exec ’e’ keyin 

or abnormal termination due to internal errors. 


6-28 3787 3528-200


** TASTSU UNABLE TO ATTACH TO TSAM ** 

Explanation: 

The TASTSU component was unable to attach to CMS 1100 via TSAM. 


** xxxxxx ATTACH FAILED u 

CMS1100 NOT AVAILABLE u WILL RETRY IN 30 SEC ** 

Explanation: 


CMS 1100 is not available, probably because CMS 1100 could not initialize with TSAM. The 

identified TSU will try to reattach every 30 seconds for a predefined number of times. 

Action: 

Verify that CMS 1100 was SOLAR installed and that the CMS 1100 absolute is being 

executed from a file that contains the symbolic element TSAMSYMBDI. 



TSU ALREADY ATTACHED BY THIS RUN 

Explanation: 

The identified TSU could not attach to CMS 1100 for this request because it was already 

attached. This will cause the TSU to terminate abnormally. 




TSU ATTACHED VIA ANOTHER RUN ** 

Explanation: 

The identified TSU could not attach to CMS 1100 for this request because it was already 

attached under another run. This will cause the TSU to terminate abnormally. 

3787 3528-200 6-29




CMS TABLE SPACE TOO LOW TO SUPPORT TSU ** 

Explanation: 

The identified TSU could not attach to CMS 1100 because CMS did not have enough table 

space to support the TSU. 




TSU NOT CONFIGURED IN CMS1100 ** 

Explanation: 

The identified TSU could not attach to CMS 1100 because it is not in the CMS configuration. 


Action: 

Check the CMS 1100 configuration PROCESS statement and the identified TSU record in 

the DDP-PPC configuration file. 



INVALID PASSWORD ** 

Explanation: 

The identified TSU could not attach to CMS 1100 because the password supplied was 

invalid. 


Action: 

Check the CMS 1100 configuration PROCESS statement for this TSU and the identified 

TSU record in the DDP-PPC configuration file. 

6-30 3787 3528-200



Explanation: 






** TASTSU CANNOT RESERVE FTP, SMTP PORTS ** 

Explanation: 

The TASTSU component was unable to reserve necessary FTP and SMT ports. 


** xxxxxx CANNOT ALLOCATE PROGRAM BANK FOR DATA AREA TO SEND OR 

RECEIVE DATA TO CMS1100** 

Explanation: 

The TSU could not acquire subsystem resources and will be terminated. 


** xxxxxx UNABLE TO ALLOCATE START-RUN QUEUE ** 

Explanation: 

The start-run activity is unable to obtain memory for its queue. This results in normal 

termination of the start-run activity. 



** xxxxxx UNABLE TO INITIALIZE WITH CS ** 

Explanation: 

The start-run activity was unable to register with the DDP-PPC configuration services 

logic. This results in normal termination of the start-run activity. 


3787 3528-200 6-31


Action: 

Refer to the DDP-PPC log file for the specific reason. 


** xxxxxx DETECTED MCB ERROR ** 

Explanation: 

An MCB error was received while processing a conversation. This results in abnormal 

termination of the related conversation. 


Action: 

Refer to the DDP-PPC log file for the specific error. 


** xxxxxx INSUFFICIENT DDP RESOURCES TO INTERFACE WITH MCB ** 

Explanation: 

The start-run activity is unable to obtain memory for the MCB packet. This results in 

normal termination of the start-run activity. 

Action: 



** xxxxxx UNABLE TO CONNECT TO TIP** 

Explanation: 

The start-run activity is unable to connect to TIP. This results in normal termination of the 

start-run activity. 

Action: 


6-32 3787 3528-200


** xxxxxx IS UNABLE TO SIGNON TO DDP ** 

Explanation: 


The Single Message Transfer component is unable to sign on to DDP-PPC. This results in 

normal termination of the Single Message Transfer component. 


Action: 




Explanation: 

The Single Message Transfer component is unable to obtain memory to be used for its 

output routing queue. This results in normal termination of the Single Message Transfer 

component. 


Action: 



** xxxxxx UNABLE TO ESTABLISH ROQ FOR INTERFACE WITH MCB ** 

Explanation: 

The Single Message Transfer component is unable to establish the output routing queue 

interface with the MCB. This results in normal termination of the Single Message Transfer 

component. 


Action: 


3787 3528-200 6-33



** xxxxxx UNABLE TO INITIALIZE WITH CS ** 

Explanation: 

The Single Message Transfer component is unable to obtain memory for its queue. This 

results in normal termination of the Single Message Transfer component. 



** xxxxxx UNABLE TO REGISTER PID TO INTERFACE WITH MCB ** 

Explanation: 

The Single Message Transfer component was unable to register the pid to interface with 

the MCB. This results in normal termination of the Single Message Transfer component. 


Action: 



** THE FOLLOWING MCB APPLICATION IS DOWN: xxxxxx ** 

Explanation: 

The identified MCB application is down. 


** xxxxxx DETECTED NO MCBs ARE RUNNING u 

PLEASE START MCB(s) ** 

Explanation: 

No MCBs are up for use by Single Message Transfer. 

6-34 3787 3528-200


** xxxxxx TRANSACTION CODE FAIL NOT SPECIFIED IN USER 

INTERFACE AREA ** 

Explanation: 

The transaction code fail is not in the user interface area. 



** THE FOLLOWING TRANSACTION IS INVALID: xxxxxx ** 

Explanation: 

The indicated transaction is invalid. 



** AUDIT FIELD IS INVALID FOR TRANSACTION: xxxxxx ** 

Explanation: 

The audit field is invalid for the transaction. 



** xxxxxx VIA MCB IS TERMINATED ** 

Explanation: 

Indicates termination of the Single Message Transfer component. 


3787 3528-200 6-35



** NO MCB RECORDS WITH PID-NUM PARAMETER ARE FOUND IN THE CS 

DATABASE. ** 

Explanation: 

The Single Message Transfer component is unable to find any MCB records with a 

PID-NUM parameter in the configuration services database. The component must register 

a pid to interface with MCB. This results in normal termination of the Single Message 

Transfer component. 



** MCB IS NOT CONFIGURED FOR TRANSACTION CODE xxxxxx ** 

Explanation: 

The MCB record associated with the FAIL transaction is not found in the configuration 




Explanation: 

The Single Message Transfer component is unable to obtain memory for the MCB message 

area. This results in normal termination of the Single Message Transfer component. 

Action: 




Explanation: 

The Single Message Transfer component is unable to obtain memory for the MCB packet. 

This results in normal termination of the Single Message Transfer component. 

Action: 


6-36 3787 3528-200


** xxxxxxUNABLE TO CONNECT TO TIP ** 

Explanation: 


The Single Message Transfer component is unable to connect to TIP. This results in normal 

termination of the Single Message Transfer component. 

Action: 



** xxxxxxUNEXPECTED RESULT FROM ER TIP$SM ** 

Explanation: 

The Single Message Transfer component received an unexpected error from ER TIP$SM. 

This results in normal termination of the Single Message Transfer component. 

Action: 



** xxxxxxUNABLE TO RELEASE PID ** 

Explanation: 

The Single Message Transfer component was unable to release the pid associated with the 

MCB that just came up. 


Action: 


3787 3528-200 6-37



** xxxxxxUNEXPECTED RESULT FROM ER TIP$SM ** 

Explanation: 

The Single Message Transfer component received an unexpected error from ER TIP$SM. 

Action: 



** SMT CANNOT STORE DATA TO TRANSACTIONxxxxxx DUE TO MCB ERROR 

xxxxxx** 

Explanation: 

The Single Message Transfer component received an error from MCB while trying to store 

data to the specified transaction. 



NO IP$NETD BUFFER AVAILABLE 

Explanation: 

An error occurred while attempting to acquire the IP$NETD bank pool space. The SNA 

component activity is unable to complete initialization. 


ERROR ON CHAIN SEARCH 

Explanation: 

Improper or incomplete configuration. The SNA component activity is unable to complete 

initialization. 


ERROR: EMPTY CHAIN, NO LINK ENTRY IN WORK BUFFER 

Explanation: 



6-38 3787 3528-200


ERROR: EMPTY CHAIN ON KEY SEARCH 

Explanation: 





ERROR: NO FIND ON KEY SEARCH 

Explanation: 




ERROR: RECORD FOUND, BUT MARKED DELETED. 

Explanation: 




ERROR: ATTEMPTED READ-FIRST WITHOUT FIRST READING OWNER 

Explanation: 




ERROR: ATTEMPT TO READ PAST END OF SEARCH TABLE 

Explanation: 



3787 3528-200 6-39



ERROR: UNSUPPORTED FUNCTION 

Explanation: 




ERROR: WORK BUFFER DESTROYED OR NOT INITIALIZED 

Explanation: 




ERROR: INVALID RECORD SIZE 

Explanation: 




ERROR: RECORD-TYPE MISMATCH 

Explanation: 




ERROR: DUPLICATE NAMES NOT PERMITTED 

Explanation: 



6-40 3787 3528-200


ERROR: ATTEMPTED LINK OF RECORD ALREADY IN CHAIN 

Explanation: 





ERROR: INVALID KEY SIZE 

Explanation: 




ERROR: SEARCH BUFFER TOO SMALL 

Explanation: 




ERROR: UNABLE TO WRITE TO SEARCH BUFFER 

Explanation: 




ERROR: CS-GET REQUESTED BEFORE CS-BEGIN 

Explanation: 



3787 3528-200 6-41



ERROR: INCORRECT VERSION OF CS COMMON BANK IS LOADED 

Explanation: 




ADDRESS ERROR: DATA STRUCTURE MUST BE > 040000 

Explanation: 




NONSPECIFIC I/O ERROR 

Explanation: 




ERROR: RECORD LINK POINTS BEYOND FILE LIMITS 

Explanation: 




ERROR: INVALID RECORD TYPE 

Explanation: 



6-42 3787 3528-200


ERROR: REFERENCE TO UNASSIGNED AREA OF MASS STORAGE 

Explanation: 





ERROR: WORK-BUFFER LINK-ENTRY OVERFLOW 

Explanation: 




ERROR: WORK-BUFFER SEARCH-DESCRIPTOR OVERFLOW 

Explanation: 




ERROR: RECORD LINK-ENTRY OVERFLOW 

Explanation: 




ERROR: MISSING LINK IN CHAIN 

Explanation: 



3787 3528-200 6-43



ERROR: INVALID SEARCH-TABLE ID 

Explanation: 




CONTINGENCY ERROR 

Explanation: 




FACILITY ERROR 

Explanation: 




ERROR: CS DATABASE FILE DOES NOT EXIST 

Explanation: 




CS DATABASE FILE WRITE KEY ERROR 

Explanation: 



6-44 3787 3528-200


CS DATABASE FILE READ KEY ERROR 

Explanation: 





ERROR: CS DATABASE FILE READ INHIBITED 

Explanation: 




ERROR: CS DATABASE FILE IS PRIVATE 

Explanation: 




ERROR: CS DATABASE FILE IS ROLLED OUT 

Explanation: 




ERROR: CS DATABASE FILE CANNOT BE ROLLED IN 

Explanation: 



3787 3528-200 6-45



ERROR: CS DATABASE FILE IS ASSIGNED TO ANOTHER RUN 

Explanation: 




ERROR: CS DATABASE FILE IS NOT WORD-ADDRESSABLE 

Explanation: 




INSTALLATION VERIFY FAILED ON RUN START (SNAPPC$) 

Explanation: 

The SNAPPC installation verification process failed because either: 

$ SNAPPC is not installed 

$ The run stream (DDP*RUN-STREAMS.SNAPPC$) cannot be started 

The SNAPPC component activity is unable to complete initialization. 


INSTALLATION VERIFY FAILED v SNAPPC NOT INSTALLED 

Explanation: 

The SNAPPC installation verification process failed. SNAPPC is not installed 

The SNAPPC component activity is unable to complete initialization. 

6-46 3787 3528-200


CONFIGURATION SERVICES ERROR CODE : xxxxxx 

Explanation: 

A Configuration Services problem has occurred. 

The SNA component activity is unable to complete initialization. 


3787 3528-200 6-47

Section 7 

DDPMASTER Run Messages 

This section alphabetically lists error messages generated by the DDPMASTER run. These 

messages are issued during either initialization or operation. Status or error codes 

appearing within a DDPMASTER run message are returned in the format nnn, where: 

nnn 

Is a decimal internal error code corresponding to a DDP-FJT message. Table A-1 in 

Appendix A lists the related message number. The related message can then be found 

in Section 2, or by using Message Help in the DDP-FJT menu interface. 

Additional information about these errors is contained in the Exec System Software 

Executive Requests Programming Reference Manual. 

3787 3528-200 7-1


Checking configuration file... 

Explanation: 

The DDPMASTER run is checking to see if it is able to access and use the DDP-PPC 

configuration services database. Any problems will be noted in subsequent messages. 

Checking recovery file... 

Explanation: 

The DDPMASTER run is checking to see if it is able to access and use the recovery file 

(SYS$LIB$*FJT$RECOVER). Any problems will be noted in subsequent messages. 

DDPMASTER - COLD START 

Explanation: 

The DDPMASTER run is attempting a cold start. 

DDPMASTER - DDP-PPC PROCESS DOWN 

Explanation: 

The local DDP-PPC process has been terminated. DDP-FJT will promptly terminate. 

DDP-FJT may be brought back up when the local DDP-PPC process is back up. 

DDPMASTER - FATAL RECEIVE ERROR STATUS 

Explanation: 

An unexpected error was received by the DDPMASTER run from the local DDP-PPC 

process in the receive message processing. The exact error is logged in the log file. 

DDPMASTER - NO BATCH QUEUES ERROR 

Explanation: 

No batch queues were found in the local configuration file. DDP-FJT requires at least one 

batch queue in order to do SUBMIT processing. Please correct the problem using the 

DDP-PPC configuration services CSUPDT processor. 

DDPMASTER - RCASMON FATAL BIND ERROR 

Explanation: 

The DDPMASTER run failed to bind (sign on) with the local DDP-PPC process. The exact 

error is logged in the DDP-PPC log file. 

7-2 3787 3528-200

*DDPMASTER stopped due to system hold 

Explanation: 

The operator has placed a hold on runs or terminals. 

Action: 

Remove the hold(s). 

DDPMASTER - USERID DOES NOT ALLOW SMOQUE 

Explanation: 


The user-id under which the DDPMASTER run was executed and started from does not 

have SMOQUE privileges. 

Action: 

Attempt to restart the DDPMASTER run with an appropriate user-id. 

DDPMASTER - WARM START 

Explanation: 

The DDPMASTER run is attempting a warm start. 

Action: 


*ERROR* Another run has file assigned 

Explanation: 

You cannot use a file assigned to another run. 

Action: 

None. The other run must free the file before you can use it. 

*ERROR* Another run has file exclusively 

Explanation: 

Another run has exclusive use of a shareable file. 

Action: 

None. The other run must free the file before you can use it. 

3787 3528-200 7-3


*ERROR* Equipment holding file is down 

Explanation: 

You cannot access the file because the device on which the file resides is down. 

Action: 

Try again afer the device is restored. 

*ERROR* Equipment is tape 

Explanation: 

You cannot use a tape file for what you are doing. 

*ERROR* Facility request not accepted 

Explanation: 

This message usually precedes one or more additional messages from this section. 

Action: 

The console messages following this one explain more about the error. 

*ERROR* File cycle conflict 

Explanation: 

You tried to access a file that is marked for deletion. 

Action: 

Restore the file from backup. 

*ERROR* File has drop flag set 

Explanation: 

You tried to access a file that is marked for deletion. 

Action: 

Restore the file from backup. 

7-4 3787 3528-200

*ERROR* File has not been catalogued 

Explanation: 

You must catalog files before using them. 

Action: 

Issue the @CAT command and specify the file name. 

*ERROR* File is a read-only file 

Explanation: 

You cannot write to a read-only file. 

*ERROR* File is a write-only file 

Explanation: 

You cannot read a write-only file. 

*ERROR* File is permanently disabled 

Explanation: 

The file is no longer available. 

Action: 

Restore the file from a backup. 

*ERROR* File is rolled out 

Explanation: 

File is unavailable. 

Action: 

Restore the file from a backup. 

*ERROR* File MFD disabled - Try @ENABLE 


3787 3528-200 7-5


*ERROR* Hardware not part of system 

Explanation: 

You tried to use a device that is not part of the system. 

Action: 

Check the device names. 

*ERROR* Illegal equipment type 

Explanation: 

You tried to move a file to or from a tape, or you tried to access a file that was moved using 

tape. 

ERROR* PCT overflow has occurred 

Explanation: 

The system reached the maximum number of files it can assign. 

*ERROR* Private file cannot be assigned 

Explanation: 

You tried to assign a secured (private) file. 

Action: 

You must either change the ownership or security of the file or sign on as the owner. 

*ERROR* Quota limits have been exceeded 

*ERROR* Run held for facilities 

*ERROR* Security violation has occurred 

ERROR - Warm start- Empty recovery file cannot start WARM, will start COLD 

Explanation: 

A warm start is not possible because the SYS$LIB$*FJT$RECOVER file is empty. 

7-6 3787 3528-200

*FATAL ERROR* DEMANDID security info bad 

Explanation: 


The user-id, password, etc. specified for the demand user-id in the Configuration Services 

database is incorrect. 

Action: 

Correct and retry. 

FJT-DEMAND-ID DOES NOT ALLOW SMOQUE 

SYMS and SUBMIT OUTPUT WILL NOT WORK!! 

Explanation: 

The user-id in the demand user-id configuration does not have SMOQUE privileges. 

Action: 

Either: 

$ Reconfigure DDP-FJT, specifying another demand user-id that has SMOQUE privileges 

$ Rerun SIMAN to give this demand user-id SMOQUE privileges 

RCASINIT - CMDPRO failed to sign on 

Explanation: 

An error was encountered on an attempt to bind to DDP-PPC. 

Action: 

Take a DDP dump. 

RCASINIT - DEMAND RSI ERR status code 

Explanation: 

See Table 7-1 for an explanation of the status code. 

3787 3528-200 7-7


Status Code 

(Decimal) 

Table 7-1. RSI Error Status Code Definitions 

Explanation 

50 DDP-FJT was unable to log on the demand RSI with the access information you 

provided for the demand user-id. Correct the demand-id configuration parameters 

and restart the DDPMASTER run. 


provided for the demand user-id because the access information has expired. 

Update the user-id and/or the demand-id configuration parameters and restart the 

DDPMASTER run. 

53 DDP-FJT was unable to log on the demand RSI because there is a system hold on 

demand runs or terminals. Remove the hold condition and restart the DDPMASTER 

run. 

54 DDP-FJT was unable to log on the demand RSI because your system does not use 

standard OS 2200 messages in the logon sequence. 


provided for the demand user-id because that user-id is configured to automatically 

execute a program at log-on time. A user-id configured in this manner cannot be 

used. Change the user-id configuration or use a different user-id for the demand-id. 


provided for the demand user-id. DDP-FJT could not process the logon sequence 

successfully. If you cannot determine the cause of this problem, set the DDP 

traces to FJT,3 and restart the DDPMASTER run. Process the DDP-PPC trace file 

and contact your Unisys representative. 

58 DDP-FJT was unable to log on the demand RSI because the maximum number of 

RSIs allowed on the system was reached. Correct the problem and restart the 

DDPMASTER run. 

59 DDP-FJT was unable to log on the demand RSI. The Exec does not allow DDP-FJT 

to log on a run due to an Exec EXPOOL problem. Correct the problem and restart 

the DDPMASTER run. 

60 DDP-FJT was unable to log on the demand RSI because of an error in the Exec RSI 

component on the host. If you cannot determine the cause of this problem, set the 

DDP traces to FJT,3 and restart the DDPMASTER run. Process the DDP-PPC trace 

file and contact your Unisys representative. 

RCASINIT - Failed recovering CST’s 

Explanation: 

Due to a problem in reading the SYS$LIB$*FJT$RECOVER file, the tables that contain 

command statuses have been lost. There is no recovery of command statuses from the 

previous DDP-FJT session. 

7-8 3787 3528-200

RCASINIT - Read of CSDB failed 

Explanation: 


DDP-FJT encountered an error reading the Configuration Services database. See the 

DDP-PPC log file for the specific error. 

RCASINIT - Recovery of CSTs failed 

Explanation: 

An error was encountered in reading the SYS$LIB$*FJT$RECOVER file during a warm 

start. 

Action: 

Try to use a backup version of the file, if you have saved one. Otherwise, start the 

DDPMASTER run cold. 

RCASINIT - Reinitializing CST links1 

Explanation: 

Due to a problem in reading the SYS$LIB$*FJT$RECOVER file, the tables that contain 

command statuses have been lost. There is no recovery of command statuses from the 

previous DDP-FJT session. 

RCASINIT - RSI inits not signed on 

Explanation: 

An error was encountered on an attempt to bind to DDP-PPC. 

Action: 

Take a DDP dump. 

RCASINIT - TRMRG reg. failed status code 

Explanation: 

The DDPMASTER run was unable to register for ER TRMRG$ functions and cannot 

execute. 

Action: 

Check the error given in the message and correct, if possible. Otherwise, notify systems 

support. 

3787 3528-200 7-9


RCASINIT - Verify NETWORK failed 

Explanation: 

DDP-FJT could not be brought up because one of the following was not configured: 

$ The local host 

$ At least one remote host 

$ A symbiont output queue (BATCHID or ROUTING-Q) 

$ A privileged user-id (DEMANDID or DEMAND-USER-ID) 

RCASINIT - Warm start read1 err status code 

Explanation: 


start. Refer to Appendix B of the Exec System Software Executive Requests Programming 

Reference Manual for an explanation of the I/O status codes. 

Action: 

None. The DDPMASTER will automatically do a cold start. 


Explanation: 




Action: 


7-10 3787 3528-200


Explanation: 





Action: 



Explanation: 




Action: 


RCASINIT - Warm start read 5 err status code 

Explanation: 




Action: 


*WARNING* File has been disabled 

3787 3528-200 7-11

Section 8 

Configuration Services Messages 

This section numerically lists messages returned from the following Configuration 

Services processors: 

$ CSCOPY 

$ CSDUMP 

$ CSPACK 

$ CSUPDT 

Additional information about some of these errors can be found in the DDP-PPC log file. 

Exec facility status codes provided in the log file for some errors are listed in the Exec 

System Software Executive Requests (ER) Programming Reference Manual. 

3787 3528-200 8-1


*ERROR* CS100 

AT LINE line# Illegal character follows xxxxxx-- character ignored. 

Explanation: 

The CSUPDT processor detects the indicated illegal character at the indicated line and 

ignores the command. 

Action: 

Check the indicated line. See the specific product implementation or configuration guide 

for the correct command format and description. 

If you are entering CSUPDT commands individually, you may enter a new command. 

If the CSUPDT processor is processing a command element, processing continues with the 

next command. Correct the element before processing it again. 

*ERROR* CS101 

AT LINE line# Illegal character -- ignored. 

Explanation: 

The CSUPDT processor detects an illegal character at the indicated line and ignores the 

command. 

Action: 






8-2 3787 3528-200

*ERROR* CS102 

AT LINE line# Illegal space character -- ignored. 

Explanation: 


The CSUPDT processor detects an illegal space character at the indicated line and ignores 

the command. 

Action: 






*ERROR* CS103 

AT LINE line# Illegal character follows xxxxxx. Components of an object identifier must 

be decimal integers. 

Explanation: 

The CSUPDT processor detects an illegal character for the object identifier. An object 

identifier must be decimal integers. The command is ignored. 

Action: 






3787 3528-200 8-3


*ERROR* CS104 

AT LINE line# Illegal character follows xxxxxx. Hexadecimal values must consist of only 

the characters 0-9 or A-F. 

Explanation: 

The CSUPDT processor detects an illegal hexadecimal character at the indicated line and 

ignores the command. 

Action: 






*ERROR* CS105 

AT LINE line# Illegal character follows xxxxxx. Octal values must consist of only the 

characters 0-7. 

Explanation: 

The CSUPDT processor detects an illegal octal value at the indicated line and ignores the 

command. 

Action: 






8-4 3787 3528-200

*ERROR* CS106 

AT LINE line# Missing closing quote at end of xxxxxx. 

Explanation: 


The CSUPDT processor detects an end quote missing at the indicated line and ignores the 

command. 

Action: 

Check the indicated line. 




*ERROR* CS107 

AT LINE line# Illegal character follows xxxxxx. 

Explanation: 

Components of an Internet address must be decimal integers. 

Action: 



If you are entering commands individually, CSUPDT ignores this command. You may 

continue entering commands. 

If the CSUPDT processor is processing a command element, CSUPDT ignores all 

characters from the indicated line to the next verb. Processing continues at that next verb. 

Correct the element before processing it again. 

3787 3528-200 8-5


*ERROR* CS150 

AT LINE line# xxxxxx is an invalid or misspelled verb or keyword. The word is ignored. 

Explanation: 

The CSUPDT processor expects a new verb to start at the indicated line. Perhaps a verb 

(ADD, MODIFY, DELETE, READ, or READALL) does not occur after a semicolon (;) 

character, which indicates the end of a record. 

Action: 






characters from the indicated line to the next verb. Processing continues at that next verb 

or keyword. Correct the element before processing it again. 

*ERROR* CS151 

AT LINE line# The record type xxxxxx following the verb is undefined. The entire 

command is ignored. 

Explanation: 

The CSUPDT processor expects a record type immediately after the verb (ADD, DELETE, 

MODIFY, READ, or READALL) in CSUPDT commands. 

Action: 

Check the indicated line position. See the specific product implementation or 

configuration guide for the correct command format and description. 




characters from the indicated line to the next verb. 

Processing continues at that next verb. Correct the element before processing it again. 

8-6 3787 3528-200

*ERROR* CS152 


AT LINE line# The keyword parameter xxxxxx is undefined for this record. The keyword 

is ignored. 

Explanation: 

The CSUPDT processor expects a parameter at the indicated line and column position. 

Action: 








*ERROR* CS153 

AT LINE line# There is no equal sign after the keyword. The parameter is ignored. 

Explanation: 

The CSUPDT processor expects an equal sign after the keyword at the indicated line. 

Action: 






characters from the indicated line and column position to the next verb. Processing 

continues at that next verb. Correct the element before processing it again. 

3787 3528-200 8-7


*ERROR* CS154 

AT LINE line# A name consisting of A to Z, a to z, or 0 to 9 is expected. The parameter 

xxxxxx is ignored. 

Explanation: 

The CSUPDT processor expects a value containing only the characters A to Z, a to z, or 0 to 

9 at the indicated line. 

Action: 








*ERROR* CS155 

AT LINE line# xxxxxx is an invalid or misspelled keyword. The parameter is ignored. 

Explanation: 

The CSUPDT processor detected invalid characters at the indicated line. 

Action: 








8-8 3787 3528-200

*ERROR* CS156 


AT LINE line# The keyword value xxxxxx is invalid. Valid values are ALL or ENTERED. 

Explanation: 

The CSUPDT processor expects a value of ALL or ENTERED. A default of ENTERED is 

used. 

Action: 

None, if ENTERED is acceptable. Otherwise, enter a MODIFY command to change the 

value. 

*ERROR* CS157 

AT LINE line# A decimal integer is expected. The parameter xxxxxx is ignored. 

Explanation: 

The CSUPDT processor expects a value containing only the characters 0 to 9 at the 

indicated line. 

Action: 








3787 3528-200 8-9


*ERROR* CS158 

AT LINE line# An octal value in the form O’nn’ is expected. The parameter xxxxxx is 

ignored. 

Explanation: 

The CSUPDT processor expects a value containing only the characters 0 to 7 at the 

indicated line. 

Action: 








*ERROR* CS159 

AT LINE line# An object identifier is expected. 

It consists of a series of at least 3 integer components separated by colons. The first 

component is 0, 1, or 2. The second component is 0 thru 39. There may be up to eight 

remaining components consisting of 1 to 10 digits. 

The parameter xxxxxx is ignored. 

Explanation: 

The CSUPDT processor expects an object identifier value at the indicated line. It should 

consist of at least 3 integers with a colon (:) character as a separator between integers. The 

first integer must be 0, 1, or 2. The second integer must be 0 through 39. There may be up 

to eight more integers each consisting of 1 to 10 digits. 

Action: 








8-10 3787 3528-200

*ERROR* CS161 


AT LINE line# The keyword value contains invalid character(s). The parameter xxxxxx is 

ignored. 

Explanation: 


Action: 








*ERROR* CS162 

AT LINE line# The RDN attribute list is not enclosed in parentheses. The parameter 

xxxxxx is ignored. 

Explanation: 

The CSUPDT processor expects a value enclosed in parentheses at the indicated line. 

Action: 








3787 3528-200 8-11


*ERROR* CS163 

AT LINE line# A hexadecimal value in the form X’nn’ is expected. The parameter xxxxxx 

is ignored. 

Explanation: 

The CSUPDT processor expects a hexadecimal value containing only the characters 0 to 9 

and A to F at the indicated line. 

Action: 








*ERROR* CS164 

AT LINE line# A quoted string is expected. The parameter xxxxxx is ignored. 

Note that lowercase characters within quoted strings are NOT converted to uppercase. 

Explanation: 

The CSUPDT processor expects a quoted string at the indicated line. 

Action: 








8-12 3787 3528-200

*ERROR* CS165 


AT LINE line# The DESTINATION-Q parameter must be enclosed in single quotes. 

Lowercase characters within quoted strings are NOT converted to uppercase. 

Explanation: 

The CSUPDT processor expects a value enclosed in single quotes at the indicated line. 

Action: 








*ERROR* CS166 

AT LINE line# The keyword value xxxxxx is invalid. Valid values are LOCAL or 

RECIPIENT. 

Explanation: 

The CSUPDT processor expects a value of LOCAL or RECIPIENT. 

Action: 






3787 3528-200 8-13


*ERROR* CS167 

AT LINE line# The keyword value xxxxxx contains invalid characters. Acceptable formats 

are HEXADECIMAL or QUOTED-STRING or limited ASCII string, for example A to Z, 0 to 

9, !"@#$%^&*()_+:""?[\]‘{3}’. 

Explanation: 


Action: 








*ERROR* CS168 

AT LINE line# The keyword value xxxxxx contains invalid characters. Acceptable formats 

are QUOTED-STRING or limited ASCII string, for example A to Z, 0 to 9, and 

!"@#$%^&*()_+:""?[\]‘{3}’. 

Explanation: 


Action: 








8-14 3787 3528-200

*ERROR* CS170 


AT LINE line# The keyword value xxxxxx is invalid. Valid values are YES or NO. 

Explanation: 

The CSUPDT processor expects a value of YES or NO. 

Action: 






*ERROR* CS171 

AT LINE line# The keyword value xxxxxx is invalid. Valid values are UP or DOWN. 

Explanation: 

The CSUPDT processor expects a value of LOCAL or RECIPIENT. 

Action: 






3787 3528-200 8-15


*ERROR* CS172 

AT LINE line# The keyword value must contain a dotted decimal representation of the 

internet address. 

Explanation: 


Action: 








*ERROR* CS200 

Cannot assign DDP*CSCONFIG. 

Explanation: 

The CSDUMP processor was unable to assign the DDP*CSCONFIG file. 

Action: 

See the DDP-PPC log file for exact error information. See the DDP-PPC Implementation 

and Administration Guide for instructions on accessing information in the log file. 

*ERROR* CS202 

CS Database file is not word-addressable. 

Explanation: 

The CSDUMP processor could not access the configuration services database file. A dump 

was not taken. 

Action: 

Check the file name, and make sure that the file is word-addressable before re-executing 

CSDUMP. 

8-16 3787 3528-200

*ERROR* CS204 

CS Database file is empty. 

Explanation: 




Action: 

Correct the problem and re-execute CSDUMP. 

*ERROR* CS206 

CSDB is empty. 

Explanation: 



Action: 

Correct the problem and re-execute CSDUMP. 

*ERROR* CS208 

Unable to read CS Database file. 

Explanation: 

The CSDUMP processor could not read the configuration services database file. A dump 


Action: 

Correct the problem and re-execute CSDUMP. See the DDP-PPC log file for exact error 

information. 

*ERROR* CS210 

Element name is invalid - nothing dumped. 

Explanation: 

File name given to the CSDUMP processor included an element name. 

Action: 

Correct the file name. 

3787 3528-200 8-17


*ERROR* CS300 

The @USE of DDP*CS$CONFIG file resulted in an error. A pack of the Configuration 

Services Database was not done. 

Explanation: 

The CSPACK processor could not access the configuration services database file 

DDP*CS$CONFIG. 

Action: 

See the CSPACK entry in the DDP-PPC log file for the detailed Exec facility status code. 

See the DDP-PPC Implementation and Administration Guide 

*ERROR* CS301 

The @USE of PACK*CS$CONFIG(+1) file resulted in an error. A pack of the Configuration 

Services Database was not done. 

Explanation: 

The CSPACK processor could not create a new cycle of the PACK*CS$CONFIG file. 

Action: 


See the DDP-PPC Implementation and Administration Guide for instructions on 

accessing information in the log file. 

*ERROR* CS302 

The @ASG of {DDP*CS$CONFIG/PACK*CS$CONFIG} file resulted in the following error: 

illegal project-id for private file. A pack of the Configuration Services Database was not 

done. 

Explanation: 

The CSPACK processor could not assign the indicated file. 

Action: 




8-18 3787 3528-200

*ERROR* CS303 


The @ASG of the {DDP*CS$CONFIG/PACK*CS$CONFIG} file resulted in the following 

error: file is write-only (read-inhibited). A pack of the Configuration Services Database was 

not done. 

Explanation: 


Action: 




*ERROR* CS304 


error: file is disabled, backup unrecoverable. A pack of the Configuration Services 

Database was not done. 

Explanation: 


Action: 




*ERROR* CS305 


error: file is rolled out, rollback started. A pack of the Configuration Services Database was 

not done. 

Explanation: 


Action: 




3787 3528-200 8-19


*ERROR* CS306 


error: file is assigned to another run. A pack of the Configuration Services Database was 

not done. 

Explanation: 


Action: 




*ERROR* CS307 


error: write key is missing or invalid. A pack of the Configuration Services Database was 

not done. 

Explanation: 


Action: 




*ERROR* CS308 


error: read key is missing or invalid. A pack of the Configuration Services Database was 

not done. 

Explanation: 


Action: 




8-20 3787 3528-200

*ERROR* CS309 



error: file is on an illegal equipment type. A pack of the Configuration Services Database 

was not done. 

Explanation: 


Action: 




*ERROR* CS310 


error: a quota or security violation has occurred. A pack of the Configuration Services 


Explanation: 


Action: 




*ERROR* CS311 


error: file does not exist. A pack of the Configuration Services Database was not done. 

Explanation: 


Action: 




3787 3528-200 8-21


*ERROR* CS312 


error: an f-cycle conflict exists. A pack of the Configuration Services Database was not 

done. 

Explanation: 


Action: 




*ERROR* CS313 


error: the equipment holding the file is down. A pack of the Configuration Services 


Explanation: 


Action: 




*ERROR* CS314 


error: file is disabled, try @ENABLE. A pack of the Configuration Services Database was 

not done. 

Explanation: 


Action: 

1. Enter an @ENABLE executive control language statement for the DDP*CS$CONFIG 

file. 

2. Execute the CSPACK processor again. 

3. If the same error occurs again, see the CSPACK entry in the DDP-PPC log file for the 

detailed Exec facility status code. See the DDP-PPC Implementation and 

Administration Guide for instructions on accessing information in the log file. 

8-22 3787 3528-200

*ERROR* CS315 


The initialization of the new Configuration Services Database file failed. See log file snaps 

for detailed error. A pack of the Configuration Services Database was not done. 

Explanation: 

The CSPACK processor could not write to the newly assigned configuration services 

database file DDP*CS$CONFIG. 

Action: 

See the CSPACK entry in the DDP-PPC log file for error information. See the DDP-PPC 

Implementation and Administration Guide for instructions on accessing information in 

the log file. 

*ERROR* CS316 

A read/lock of the DDP*CS$CONFIG file failed. See log file snaps for detailed error. A pack 

of the Configuration Services Database was not done. 

Explanation: 

The CSPACK processor could not read the configuration services database file 


Action: 




*ERROR* CS317 

CSPACK, CSUPDT or CSCOPY is currently running. Therefore the CS Data Base file 

cannot be updated. A pack of the Configuration Services Data Base was not done. 

Explanation: 

The CSPACK processor is unable to lock the configuration services database file 

DDP*CS$CONFIG to prevent access by other CSPACK, CSUPDT, or CSCOPY processors 

that may be executing in other runs. 

Action: 




3787 3528-200 8-23


*ERROR* CS318 

CSPACK could not write back the DDP*CS$CONFIG file. CSPACK could not lock out the 

file. See log file snaps for detailed error. A pack of the Configuration Services Database 

was not done. 

Explanation: 

The CSPACK processor was unable to lock the configuration services database file 

DDP*CS$CONFIG to prevent access by other CSPACK, CSUPDT, or CSCOPY processors 


Action: 



the log file. 

*ERROR* CS319 

CSPACK could not unlock the DDP*CS$CONFIG file. See log file snaps for detailed error. 

A pack of the Configuration Services Data Base was not done. You will not be able to use 

CSPACK with the current CS Data Base File until the lock is unlocked. Execute the 

CSUPDT processor with the U option to unlock the lock. 

Explanation: 

The CSPACK processor was unable to unlock the configuration services database file 

DDP*CS$CONFIG. Any subsequent call to the CSPACK, CSUPDT, or CSCOPY processor 

will fail. 

Action: 



the log file. 

Execute the CSUPDT processor with the U option to unlock the lock. 

8-24 3787 3528-200

*ERROR* CS320 


CSPACK could not internally assign the DDP*CS$CONFIG file. See log file snaps for 

detailed error. A pack of the Configuration Services Database was not done. 

Explanation: 

The CSPACK processor was unable to assign the configuration services database file 


Action: 



the log file. 

*ERROR* CS321 

CSPACK could not internally assign the new PACK*CS$CONFIG(+1) file. See log file snaps 


Explanation: 

The CSPACK processor was unable to assign the PACK*CS$CONFIG file. 

Action: 



the log file. 

*ERROR* CS322 

CSPACK could not find the root record of the file DDP*CS$CONFIG. See the log file snaps 


Explanation: 

The configuration services database file DDP*CS$CONFIG has either been corrupted or 

not been initialized as a configuration services database file. 

Action: 



the log file. 

3787 3528-200 8-25


*ERROR* CS323 

CSPACK could not read the root record of the file DDP*CS$CONFIG. See the log file snaps 


Explanation: 

The CSPACK processor encountered an internal input/ouput error trying to read the 

configuration services database file DDP*CS$CONFIG. 

Action: 

See the CSPACK entry in the DDP-PPC log file for the detailed error information. See the 

DDP-PPC Implementation and Administration Guide for instructions on accessing 

information in the log file. 

*ERROR* CS324 

CSPACK could not find the root record of the new file PACK*CS$CONFIG(+1). See the log 

file snaps for detailed error. A pack of the Configuration Services Database was not done. 

Explanation: 

The CSPACK processor encountered an internal error in the DDP-PPC configuration 

services software. 

Action: 

See the CSPACK entry in the DDP-PPC log file for the detailed configuration services 

status information. See the DDP-PPC Implementation and Administration Guide for 

instructions on accessing information in the log file. 

*ERROR* CS325 

CSPACK could not read the root record of the new file PACK*CS$CONFIG(+1). See the log 

file snaps for detailed error. A pack of the Configuration Services Database was not done. 

Explanation: 



Action: 




8-26 3787 3528-200

*ERROR* CS326 


CSPACK encountered an unrecoverable internal error while attempting to build all the 

chains of a root record. See the log file snaps for detailed error. A pack of the 

Configuration Services Database was not done. 

Explanation: 



Action: 




*ERROR* CS327 

There is an unexpected error internal code in CSPACK. The status is nn. The substatus is 

nn. 

Explanation: 

The CSPACK processor detected an error. This may indicate a problem with the DDP-PPC 

configuration services software. 

The internal code is for use by Unisys support personnel only. 

Action: 

1. See Table B-1 in Appendix B for an explanation of the status and substatus code. 

2. Check the DDP-PPC log file. See the DDP-PPC Implementation and Administration 

Guide for instructions on accessing information in the log file. 

3. Re-execute CSPACK with CFG-SVC level 3 traces set on. 

3787 3528-200 8-27


*ERROR* CS328 

Unable to assign the DDP*CS$CONFIG file. A pack of the Configuration Services database 

was not performed. The status is nn. The substatus is nn. 

Explanation: 

The CSPACK processor could not assign the file. 

Action: 





*ERROR* CS330 

The @USE of the DDP*CS$CONFIG file resulted in an error. A pack of the Configuration 

Services database was not performed. The status is nn. The substatus is nn. 

Explanation: 


Action: 





8-28 3787 3528-200

*ERROR* CS335 


The @USE of the PACK*CSTEMP file resulted in an error. A pack of the Configuration 


Explanation: 


Action: 





*ERROR* CS340 

CSPACK could not internally assign the filename file. A pack of the Configuration Services 

database was not performed. The status is nn. The substatus is nn. 

Explanation: 


Action: 





3787 3528-200 8-29


*ERROR* CS345 

CSPACK could not internally assign the new filename file. A pack of the Configuration 


Explanation: 


Action: 





*ERROR* CS350 

CSPACK could not internally assign the new filename file. The file was already assigned or 

cataloged. A pack of the Configuration Services database was not performed. The status is 

nn. The substatus is nn. 

Explanation: 


Action: 





8-30 3787 3528-200

*ERROR* CS355 


CSPACK is being executed from a temporary file. CSPACK must be executed from a 

permanent file which also contains the CSUPDT processor. A pack of the Configuration 

Services database was not performed. 

Explanation: 

The CSPACK and CSUPDT processors must be in the same permanent file. 

Action: 

Execute CSPACK from a permanent file which also contains the CSUPDT processor. 

*WARNING* CS405 

You specified the N and Z options on the call to CSUPDT. The N option is used. 

Explanation: 

N and Z is not a valid combination of options for the CSUPDT processor call. Only the N 

option takes effect when both N and Z are specified. The N option performs a syntax check 

only. The Z option allows CSUPDT command processing to continue after any syntax error. 

Action: 

No corrective action is necessary if only the N option is sufficient. 

To use the Z option, do the following: 

1. Enter an @EOF executive control language statement to end the current execution of 

the CSUPDT processor 

2. Enter a new CSUPDT processor call with a Z option without an N option. 

3787 3528-200 8-31


*ERROR* CS410 

CSUPDT received an error on an @USE CSDB$IN,DDP*CS$CONFIG statement. CSUPDT 

will perform syntax analysis only. 

Explanation: 

Internal error during execution of the CSUPDT processor. 

Action: 



*ERROR* CS415 

CSUPDT is unable to initialize the CS Database file. CSUPDT will perform syntax analysis 

only. 

Explanation: 


Action: 



8-32 3787 3528-200

*ERROR* CS420 

CSUPDT is unable to read the CS Database file. 

CSUPDT will perform syntax analysis only. 

Explanation: 


Action: 




*ERROR* CS425 

CSPACK, CSUPDT, or CSCOPY is currently running. Therefore the CS Database file cannot 

be updated. 


Explanation: 

There are three processors capable of writing to the CS Database (file DDP*CS$CONFIG) - 

CSUPDT, CSPACK, and CSCOPY. To ensure that these three processors are not 

simultaneously modifying the database file, each processor ’locks’ the file upon entrance 

and ’unlocks’ it upon normal or abnormal exit. 

The most probable cause of this error is that CSUPDT, CSPACK, or CSCOPY is currently 

executing under another user-id. If this is not the case, some internal error must have 

caused the last execution of CSUPDT, CSPACK, or CSCOPY to terminate without 

unlocking the file. CSCOPY only unlocks the file if it is DDP*CS$CONFIG. 

Action: 

To unlock the lock, run CSUPDT with the u option when none of the three processors is 

running. 

CFG-SVC level 3 traces from the DDP-PPC trace file may be helpful for future analysis of 

the cause of the internal error. 

3787 3528-200 8-33


*ERROR* CS427 

The CS database cannot be accessed because xxxxxx is currently executing xxxxxx, 

which locked the database on xxxxxx. 


Explanation: 

There are three processors capable of writing to the CS Database (file DDP*CS$CONFIG) - 

CSUPDT, CSPACK, and CSCOPY. To ensure that these three processors are not 

simultaneously modifying the database file, each processor locks the file upon entrance 

and unlocks it upon normal or abnormal exit. 

The most probable cause of this error is that CSUPDT, CSPACK, or CSCOPY is currently 

executing under another user-id. If this is not the case, some internal error must have 

caused the last execution of CSUPDT, CSPACK, or CSCOPY to terminate without 

unlocking the file. 

Action: 


running. 

CFG-SVC level 3 traces from the DDP-PPC trace file may be helpful for future analysis of 

the cause of the internal error. 

*ERROR* CS430 

CSUPDT is unable to write to the CS Database file. 


Explanation: 


Action: 



If you submit commands to the CSUPDT processor, CSUPDT only checks the syntax of 

those commands. It does not process them. 

8-34 3787 3528-200

*ERROR* CS435 

Unable to open CS Database. 


Explanation: 


Action: 




*ERROR* CS440 

Unable to unlock the CS Data Base File due to an internal error. A copy of the 

Configuration Services Data Base was not done. 

You will not be able to use CSUPDT, CSPACK, or CSCOPY with the current CS Data Base 

File until the lock is unlocked. Execute the CSUPDT processor with the U option to unlock 

the lock. 

Explanation: 


Action: 


running. 

3787 3528-200 8-35


*ERROR* CS500 

A valid xxxxxx parameter is missing for the verb AT LINE line#. 

This parameter is required for the xxxxxx command. 

Explanation: 

The CSUPDT processor expects the indicated parameter in the indicated command line 

because it is required for the indicated command. 

Action: 

Check the indicated command line. See the specific product implementation or 

configuration guide for the correct command format, parameters, and description. 



If the CSUPDT processor is processing a command element, CSUPDT ignores the indicated 

line. Processing continues at that next verb. Correct the element before processing it again. 


AT LINE line# The keyword xxxxxx is no longer required. 

The parameter is ignored. 

Explanation: 

The CSUPDT processor no longer requires this parameter. It is ignored. 

Action: 



8-36 3787 3528-200

*ERROR* CS503 

AT LINE line# Invalid choice for the TYPE parameter. 


Valid choices are LOCAL, OS1100, UNIX, MSDOS, BTOS, OSI, DDP4000, TELCON, or 

SNAHOST. 


Explanation: 

The CSUPDT processor expects a TYPE parameter value to be LOCAL, OS1100, UNIX, 

MSDOS, BTOS, OSI, DDP4000, TELCON, or SNAHOST. 

Action: 

Check the HOST record in the indicated line. See the specific product implementation 

guide for the correct command format and description. 



If the CSUPDT processor is processing a command element, CSUPDT ignores the 

indicated line and continues processing. Correct the element before processing it again. 

*ERROR* CS504 

AT LINE line# Invalid choice for the xxxxxx parameter. 

Valid choices are xxxxxx. 


Explanation: 

The CSUPDT processor expects only the values indicated for this parameter. 

Action: 

Check the HOST record in the indicated line. See the specific product implementation 

guide for the correct command format and description. 

3787 3528-200 8-37


*ERROR* CS510 

AT LINE line# xxxxxx parameter exceeds limit of nn characters. 

Explanation: 

The CSUPDT processor expects only the indicated number of characters for the indicated 

parameter in the line indicated. 

Action: 


for the correct command format, parameters, and description. 





*ERROR* CS511 

AT LINE line# Parameter must be at least xxxxxxand not more than xxxxxx characters in 

length. 

Explanation: 

The CSUPDT processor expects only the indicated number of characters for the indicated 

parameter in the line indicated. 

Action: 








8-38 3787 3528-200

*ERROR* CS515 


AT LINE line# Duplicate xxxxxx record name. The record is not added or modified. 

Explanation: 

The CSUPDT processor determined that the record you attempted to add already exists in 

the configuration services database. Therefore, it does not add the duplicate record. 

Action: 

Check the indicated command line. Use a READ or READALL command to display the 

existing records in the configuration services database. If you want to modify the record, 

decide if you want to use a MODIFY command or a DELETE command followed by an 

ADD command. 





*ERROR* CS520 

AT LINE line# The specified xxxxxx record does not exist. 

Explanation: 

The CSUPDT processor determined that the record specified does not exist. Therefore, it 

cannot read or modify the record. 

Action: 

Check the indicated command line. Use a READ or READALL command to display the 

existing records in the configuration services database and make sure the record you are 

concerned with exists. 





3787 3528-200 8-39



AT LINE line# The xxxxxx record you tried to delete does not exist. 

Explanation: 

The CSUPDT processor determined that you tried to delete a record that does not exist. 

This can occur normally during OSI-FTAM installation. 

Action: 



AT LINE line# The xxxxxx record you tried to delete is already deleted. 

Explanation: 

The CSUPDT processor determined that you tried to delete a record that has previously 

been deleted. 

This can occur normally during installation of products such as OSI-FTAM that use DDP 

configuration services. 

It also occurs if you take the precaution of executing a DELETE command prior to an ADD 

command to ensure that the CSUPDT processor deletes any obsolete or temporary version 

of the record that may exist before adding the record. 

Action: 


8-40 3787 3528-200

*ERROR* CS530 


AT LINE line# You cannot modify the xxxxxx record because the xxxxxx specified 

already exists. 

Explanation: 

The CSUPDT processor did not modify the record as specified in the indicated command 

line because this would have created a duplicate record. 

Action: 



Use a READ or READALL command to display the existing records in the configuration 

services database and verify the host name. You may have to delete an existing record or 

specify different parameter values to create a unique record. 





3787 3528-200 8-41


*ERROR* CS535 

AT LINE line# You cannot modify a local host to another host-type or modify a non-local 

host-type to a local host-type. 

Explanation: 


line. 

The host type for the local host is LOCAL, regardless of its hardware system type or 

architecture. There can be one and only one LOCAL host record. You may modify other 

parameters in the LOCAL host record, but not the TYPE=LOCAL parameter. 

Action: 







To change the TYPE parameter value to or from LOCAL in a HOST record, do the following: 

1. Delete any subordinate records associated with the original HOST record 

2. Delete the original HOST record 

3. Add a complete new HOST record with the new TYPE parameter value 

4. Add any subordinate records required for the new HOST record. 

8-42 3787 3528-200

*ERROR* CS540 


AT LINE line# You cannot add this host record as a local host because a local host record 

already exists. 

Explanation: 

The CSUPDT processor did not add the local host record as specified by the indicated 

command line. There can be one and only one LOCAL host record. 

Action: 


configuration guide for valid formats for HOST TYPE=LOCAL commands. 





*ERROR* CS545 

AT LINE line# You cannot delete the xxxxxx record because it is the owner of xxxxxx 

records. 

Explanation: 

The CSUPDT processor cannot delete the indicated record until you delete all the 

indicated records it owns. 

Action: 


configuration guide for the instructions on locating and deleting subordinate records for a 

given host and then deleting the HOST record for that host. 





3787 3528-200 8-43


*ERROR* CS550 

AT LINE line# You cannot modify the xxxxxx record. The xxxxxx already exists. 

Explanation: 


line because this would have created a duplicate record. 

Action: 



Use a READ or READALL command to display the existing records in the configuration 

services database and verify the host name. You may have to delete an existing record or 

specify different parameter values to create a unique record. 






AT LINE line# The xxxxxx keyword is no longer pertinent for a xxxxxx record. The 

parameter will be ignored. 

Explanation: 

The CSUPDT processor no longer supports this parameter for the indicated record. The 

parameter is ignored. 

Action: 



8-44 3787 3528-200



AT LINE line# The xxxxxx parameter is now specified in the xxxxxx record. This xxxxxx 

parameter is ignored. 

Explanation: 

The CSUPDT processor no longer supports this parameter for the record on which it was 

entered. The parameter is ignored. 

Action: 



*ERROR* CS560 

AT LINE line# The xxxxxx parameter is not in the range of 0 to 255. 

Explanation: 

The CSUPDT processor expects an integer value from 0 to 255, inclusive. 

Action: 

If you are entering commands individually, CSUPDT ignores this command. Enter a new 

HOST TYPE=LOCAL command with a valid value for the parameter. 


line. Processing continued at that next verb. Correct the element before processing it again. 

3787 3528-200 8-45


*ERROR* CS561 

AT LINE line# The xxxxxx parameter exceeds the value xxxxxx. 

Explanation: 


Action: 









AT LINE line# You already specified the xxxxxxparameter. The previous specification is 

disregarded. 

Explanation: 

The CSUPDT processor detected a duplicate parameter. It uses the latest value specified. 

Action: 

Check the indicated command line. If the latest value specified for the indicated parameter 

is acceptable to you, no corrective action is necessary. 

If the latest value specified is not acceptable to you, enter a MODIFY command to change 

the value. 

8-46 3787 3528-200

*ERROR* CS575 


AT LINE line# There is an unexpected error internal-code in CSUPDT. The status is nn. 

The substatus is nn. 

Explanation: 

The CSUPDT processor detected an error at the line indicated. This may indicate a 

problem with the DDP-PPC configuration services software. 


Action: 

If you are entering commands individually, enter an @EOF executive control language 

statement to end the use of the CSUPDT processor. 



To further diagnose the error, do the following: 


2. Note the CSUPDT command that produced the problem and any related commands. 

3. Check the snap dumps in the DDP-PPC log file. See the DDP-PPC Implementation 


4. Recreate the command sequence with CFG-SVC level 3 traces set on. 

3787 3528-200 8-47


*ERROR* CS580 

AT LINE line# There is an unexpected error in CS Database File. internal-code The 

substatus is nn. 

Explanation: 

The CSUPDT processor detected an error at the line indicated in the configuration services 

database file (DDP*CSCONFIG). This may indicate a problem with the DDP-PPC 

configuration services software. 


Action: 

If you are entering commands individually, enter an @EOF executive control language 

statement to end the use of the CSUPDT processor. 



To further diagnose the error, do the following: 


2. Note the CSUPDT command that produced the problem and any related commands. 

3. Check the snap dumps in the DDP-PPC log file. See the DDP-PPC Implementation 


4. Recreate the command sequence with CFG-SVC level 3 traces set on. 

8-48 3787 3528-200

*ERROR* CS585 


AT LINE line# The first component of an object identifier must be 0, 1, or 2. 

Explanation: 

The CSUPDT processor expects an object identifier value at the indicated line and column 

position. It should consist of at least 3 integers with a colon (:) character as a separator 

between integers. The first integer must be 0, 1, or 2. The second integer must be an integer 

0 through 39. There may be up to eight more integers, each consisting of 1 to 10 digits. 

Action: 








*ERROR* CS590 

AT LINE line# The second component of an object identifier must be 0 thru 39. 

Explanation: 





Action: 








3787 3528-200 8-49


*ERROR* CS595 

AT LINE line# The components 3 thru 10 of an object identifier must be 1 to 10 digits each. 

Explanation: 





Action: 








*ERROR* CS600 

AT LINE line# You specified more than 10 components in the object identifier. 

Explanation: 





Action: 








8-50 3787 3528-200

*ERROR* CS605 


AT LINE line# At least 3 components of an object identifier must be specified. 

Explanation: 





Action: 








*ERROR* CS610 

AT LINE line# The xxxxxx already exists in the CSDB file. 

Explanation: 

The CSUPDT processor determined that the record specified already exist.The CSUPDT 

processor did not add the record as specified. 

Action: 






3787 3528-200 8-51



AT LINE line# There are no xxxxxx records in the CSDB file. 

Explanation: 

The CSUPDT processor determined that the records specified do not exist. Therefore, it 

cannot perform a READALL command. 

Action: 



AT LINE line# There are no xxxxxx records that meet the criteria. 

Explanation: 

The CSUPDT processor determined that the record specified does not meet the criteria. 

Therefore, it cannot read or modify the record. 

Action: 



AT LINE line# There are no xxxxxx records subordinate to xxxxxx. 

Explanation: 

The CSUPDT processor determined that their are no subordinate records for the 

READALL command. 

Action: 


8-52 3787 3528-200

*ERROR* CS620 


AT LINE line# Exactly 2 hexadecimal digits in the form X’nn’ are required for the xxxxxx 

parameter. 

Explanation: 

The CSUPDT processor expects exactly two hexadecimal digits for the indicated 

parameter. Hexadecimal digits are 0-9 and A to F. 

Action: 







*ERROR* CS625 

AT LINE line# An even number of hexadecimal digits is required for the xxxxxx parameter. 

Explanation: 

The CSUPDT processor expects an even number of hexadecimal digits for the X’xxxxxx’ 

value for the specified parameter. 

Action: 







3787 3528-200 8-53


*ERROR* CS627 

AT LINE line# The X121 parameter must be 1 to 14 decimal digits. 

Explanation: 

The CSUPDT processor expects 1 to 14 decimal digits for the value in the X121 parameter. 

Action: 







*ERROR* CS635 

AT LINE line# The NSAP parameter must be 1 to 64 hexadecimal digits in the form 

X’nn...nn’. 

Explanation: 

The CSUPDT processor expects an NSAP parameter value to be 1 to 64 hexadecimal digits. 

A hexadecimal digit is 0 to 9 and A to F. 

Action: 

Check the indicated line. See specific product implementation or configuration guide for 

the correct command format and description. 





8-54 3787 3528-200

*ERROR* CS637 


AT LINE line# Hexadecimal format (X’nn...nn’) is assumed for the xxxxxx parameter. 

Explanation: 

The CSUPDT processor expects a hexadecimal digit for the specified parameter. A 

hexadecimal digit is 0 to 9 and A to F. 

Action: 

Check the indicated line. See specific product implementation or configuration guide for 

the correct command format and description. 





*ERROR* CS642 

AT LINE line# The UTC parameter must be in the form + or - HHMM where HH is 00 to 12 

and MM is 00 to 59. 

Explanation: 

The CSUPDT processor accepts only 5 characters for the UTC parameter value. This value 

must be in the format +hhmm or -hhmm,wherehh is a number of hours (00 through 12) 

and mm is a number of minutes (00 through 59). The valid range for the UTC parameter 

value is -1200 to +1200. The value +1259 is not valid. 

Action: 

Check the command for the HOST record in the line indicated. See the DDP-PPC 

Implementation and Administration Guide for the correct command format and 

description. 





3787 3528-200 8-55


*ERROR*CS645 

AT LINE line# You cannot xxxxxx the xxxxxx record because the xxxxxx specified does 

not exist. 

Explanation: 

One or more of the parameters you specified identifies a record that does not exist in the 

configuration services database. 

Action: 

Resubmit the command with the correct record name specified. 

*WARNING*CS655 

You did not specify any parameters on the xxxxxx command that cause the record to be 

modified. 

Explanation: 

The parameters you specified on this MODIFY command served only to uniquely identify 

the record to be modified. No action was taken because no modifiable parameters were 

specified. 

Action: 

Check whether you forgot to specify one or more parameters to be modified. If so, 

resubmit the command with the correct parameters. Otherwise, you are probably trying to 

change the owner of a particular record. Since records of this type are not uniquely named 

within the configuration services database, the parameter that identifies the owner record 

is used as a qualifier to uniquely identify a particular record. If you want to change that 

owner, therefore, you must perform a DELETE command followed by an ADD command. 

*ERROR*CS660 

AT LINE line# When TYPE=INTRA, the only valid host name is the local host xxxxxx 

(which is also the default). 

Explanation: 

A node record of type INTRA is assumed to be associated with the local host. 

Action: 

Either change the node type to IBM or DIS, or do not specify the HOST parameter when 

TYPE=INTRA. 

8-56 3787 3528-200

*ERROR*CS665 


AT LINE line# xxxxxx cannot be done because subordinate records xxxxxx exist. 

Explanation: 

You tried to do either of the following: 

$ Delete a record that has subordinate records linked to it 

$ Modify one particular parameter of a record that has subordinate records linked to it. 

The one particular parameter is the parameter that identifies the ’owner’ record. Such 

a modification requires an internal relinking, which is allowed only for records that do 

not have any subordinate records. 

Action: 

If you want to delete or modify the specified record, then all subordinate records must be 

deleted. 

CS666 

xxxxxx cannot be done unless all subordinate xxxxxx records are deleted. 

Do you want CSUPDT to delete them all for you now? (Y or N) 

Explanation: 

You tried to do either of the following: 

$ Delete a record that has subordinate records linked to it. 

$ Modify one particular parameter of a record that has subordinate records linked to it. 

The one particular parameter is the parameter that identifies the ’owner’ record. Such 

a modification requires an internal relinking which is allowed only for records that do 

not have any subordinate records. 

Action: 

This message appears in demand mode only. Respond Y if you want all subordinate 

records to be automatically deleted now. Otherwise, respond N and CSUPDT will generate 

the CS665 error. 

3787 3528-200 8-57


CS667 

AT LINE line# xxxxxx record deleted. 

Explanation: 

Informational message displayed by successful DELETE commands. 

Action: 


CS668 

xxxxxx record deleted. 

Explanation: 

Informational message displayed by successful DELETE commands. 

Action: 


CS670*ERROR* 

AT LINE line# A valid xxxxxx parameter is missing. 

This parameter is required when xxxxxx. 

Explanation: 

A valid FILE or ACCOUNT-NUMBER parameter is missing that is required when 

TYPE=BATCH or a valid CODE parameter is missing that is required when TYPE=SMT or 

TPX. 

Action: 








8-58 3787 3528-200

*ERROR* CS671 


A valid xxxxxx parameter is missing. The parameter is required for xxxxxx. 

Explanation: 

A valid UTC parameter is required for OSI-FTAM. The value must contain exactly 5 

characters in the format +hhmm or -hhhmm, where hh is the number of hours (0 through 

12) and mm is the number of minutes (0 through 59). The valid range for UTC is -1200 to 

+1200. For example, the value +1259 is not valid. Change the value, as necessary, for any 

time corrections (such as Daylight Savings Time). 

Action: 








*ERROR* CS675 

AT LINE line# You cannot specify the xxxxxx parameter unless xxxxxx. 

Explanation: 

There is a conflict between two of the parameters you specified. 

Action: 

Correct the problem and resubmit the command with the proper parameters specified. 

*ERROR* CS677 

AT LINE line# You must specify the T-SEL parameter as SNAAPPL when host type = 

SNAHOST. 

Explanation: 

There is a conflict between two of the parameters you specified. 

Action: 

Correct the problem and resubmit the command with the proper parameters specified. 

3787 3528-200 8-59


*ERROR* CS680 

AT LINE line# The xxxxxx parameter is not in the range nn - nn 

Explanation: 

You specified a value outside of the range allowed for this parameter. 

Action: 

Resubmit the command using a value within the allowed range. 

*ERROR* CS685 

AT LINE line# The xxxxxx parameter is not an integer that can be expressed as a*2**b, 

where 7

*ERROR* CS695 

AT LINE line# Incorrect file name syntax on the xxxxxx parameter. 

Explanation: 

The syntax for the file name for the specified parameter is incorrect. 

Action: 


Check the command for the record in the line indicated. See the specific product 

implementation or configuration guide for the correct command format and description. 






The xxxxxx parameter is meaningless when the host is the local host. The value specified 

for the xxxxxx parameter is stored in the APPLICATION-ENTITY record, but will not be 

used. 

Explanation: 

A parameter was given that has no meaning because the local host is specified on the 

APPLICATION-ENTITY record (TRANSPORT-CLASS, ALT-TRANSPORT-CLASS, and 

CHECKSUM). 

Action: 

No action is necessary. This is a warning message only. 


The START-CMS-NUM parameter defined in the PPCMASTER record cannot have the 

same value as the SMT-CMS-NUM parameter. 

Explanation: 

The value specified does not conform to the requirements for this parameter. 

Action: 

Correct the problem and resubmit the command. 

3787 3528-200 8-61


*ERROR* CS800 

The @ASG of DDP*CS$CONFIG file resulted in the following error: illegal project-id for 

private file. 

Explanation: 

The CSUPDT processor tried to assign the configuration services database file 

DDP*CS$CONFIG, resulting in this error. 

The configuration services database should be cataloged as a public file. Normally, the 

CSUPDT processor does this automatically. Therefore, this error should only occur if you 

deliberately cataloged the DDP*CS$CONFIG file differently. 

Action: 

If you proceed to submit commands to the CSUPDT processor, CSUPDT performs a syntax 

check on the commands only. It does not process them. 

Instead, do the following: 

1. Enter an @EOF executive control language statement to end the use of the CSUPDT 

processor 

2. Catalog the DDP*CS$CONFIG file as a public file 

3. Execute the CSUPDT processor again. 

8-62 3787 3528-200

*ERROR* CS805 


The @ASG of DDP*CS$CONFIG file resulted in the following error: file is write-only 

(read-inhibited). 

Explanation: 

The CSUPDT processor tried to read the configuration serivces database file 

DDP*CS$CONFIG, but the file was cataloged as a write-only file. 

The configuration services database should be cataloged as a public file and not as a 

write-only file. Normally, the CSUPDT processor does this automatically. Therefore, this 

error should occur only if you deliberately cataloged the DDP*CS$CONFIG file differently. 

Action: 





processor 

2. Catalog the DDP*CS$CONFIG file as a public file and not as a write-only file 


*ERROR* CS810 

The @ASG of DDP*CS$CONFIG file resulted in the following error: file is disabled, backup 

unrecoverable. 

Explanation: 

The CSUPDT processor tried to read the configuration serivces database file 

DDP*CS$CONFIG, but the file was disabled. 

Action: 





processor 

2. @ENABLE DDP*CS$CONFIG. fil 


3787 3528-200 8-63


*ERROR* CS815 

The @ASG of DDP*CS$CONFIG file resulted in the following error: file is rolled out, 

rollback started. 

Explanation: 

The CSUPDT processor tried to assign the configuration serivces database file 

DDP*CS$CONFIG, but the file was rolled out. Rollback started. 

Action: 





processor 

2. Wait for a message indicating that the DDP*CS$CONFIG file has been rolled in 


*ERROR* CS820 

The @ASG of DDP*CS$CONFIG file resulted in the following error: file is assigned to 

another run. 

Explanation: 


DDP*CS$CONFIG, but the file was already assigned to another run. 

Action: 





processor 

2. Do an @ENABLE of the DDP*CS$CONFIG file 


8-64 3787 3528-200

*ERROR* CS825 


The @ASG of DDP*CS$CONFIG file resulted in the following error: write key is missing or 

invalid. 

Explanation: 


DDP*CS$CONFIG, but the write key was missing or not valid. 

Action: 





processor 

2. Remove the DDP*CS$CONFIG file write key 


*ERROR* CS830 

The @ASG of DDP*CS$CONFIG file resulted in the following error: read key is missing or 

invalid. 

Explanation: 


DDP*CS$CONFIG, but the read key was missing or not valid. 

Action: 





processor 

2. Remove the DDP*CS$CONFIG file read key 


3787 3528-200 8-65


*ERROR* CS835 

The @ASG of DDP*CS$CONFIG file resulted in the following error: file is on an illegal 

equipment type. 

Explanation: 


DDP*CS$CONFIG, but the file was on an equipment type that OS 2200 cannot access. 

Action: 

Change the configuration services database file DDP*CS$CONFIG file from the illegal 

equipment type to disk. 

*ERROR* CS837 

The @ASG of the DDP*CS$CONFIG file resulted in the following error: file is not 

word-addressable. 

Explanation: 


DDP*CS$CONFIG, but the file was not cataloged as word-addressable. 

Action: 

The DDP*CS$CONFIG file must be cataloged as word-addressable. 

*ERROR* CS840 

The @ASG of DDP*CS$CONFIG file resulted in the following error: a quota or security 

violation has occurred. 

Explanation: 


DDP*CS$CONFIG, but a quota or security violation has occurred. 

Action: 

Execute CSUPDT with a user-id that has access to the configuration services database file 


8-66 3787 3528-200

*ERROR* CS845 


The @ASG of DDP*CS$CONFIG file resulted in the following error: file does not exist. 

Explanation: 


DDP*CS$CONFIG, but the file does not exist. 

Action: 

Check the file name. Correct the name if in error and rerun MCPCONFIG. 

*ERROR* CS850 

The @ASG of DDP*CS$CONFIG file resulted in the following error: an f-cycle conflict 

exists. 

Explanation: 


DDP*CS$CONFIG, but an f-cycle conflict exists. 

Action: 

Execute CSUPDT without the +1 cycle specified on the configuration serivces database 

file DDP*CS$CONFIG. 

*ERROR* CS855 

The @ASG of DDP*CS$CONFIG file resulted in the following error: the equipment holding 

the file is down. 

Explanation: 


DDP*CS$CONFIG, but the equipment containing the file is down. 

Action: 

Turn on the equipment containing the file, make sure all necessary processes are up, and 

rerun CSUPDT. 

3787 3528-200 8-67


*ERROR* CS860 

The @ASG of DDP*CS$CONFIG file resulted in the following error: file is disabled, try 

@ENABLE. 

Explanation: 


DDP*CS$CONFIG, but the file was disabled. 

Action: 





processor 

2. Enter an @ENABLE executive control language statement for the DDP*CS$CONFIG 

file 


*ERROR* CS865 

The @ASG of DDP*CS$CONFIG file from CSUPDT failed. Check the DDP log file for the 

facility status bits of the @ASG. 

Explanation: 


DDP*CS$CONFIG, but the assignment attempt failed. 

Action: 



Instead, enter an @EOF executive control language statement to end the use of the 

CSUPDT processor. 

See the DDP-PPC log file for the status bits of the @ASG executive control language 

statement. See the DDP-PPC Implementation and Administration Guide for instructions 

on accessing information in the log file. 

8-68 3787 3528-200

*ERROR* CS900 

Input-file file is empty. 

Explanation: 


The input file specified in the CSCOPY processor call has never been written to. It is 

empty. The CSCOPY processor terminates. 

Action: 

See the DDP-PPC Implementation and Administration Guide for information about the 

CSCOPY processor. Execute the CSCOPY processor again, specifying one of the following 

as an input file: 

$ The configuration services database file (DDP*CS$CONFIG) created by the CSUPDT 

processor 

$ A copy of the file DDP*CS$CONFIG created by a previous execution of the CSCOPY 

processor. This is the file name specified as the output file for a previous execution of 

the CSCOPY processor. 

*ERROR* CS905 

Input-file file is not a configuration services database. 

Explanation: 

The input file specified in the CSCOPY processor call contains data that is not formatted 

like a configuration services database. The CSCOPY processor terminates. 

Action: 


CSCOPY processor. Execute the CSCOPY processor again, specifying one of the following 

as an input file: 

$ The configuration services database file (DDP*CS$CONFIG) created by the CSUPDT 

processor 

$ A copy of the file DDP*CS$CONFIG created by a previous execution of the CSCOPY 

processor. This is the file name specified as the output file for a previous execution of 

the CSCOPY processor. 

3787 3528-200 8-69


*ERROR* CS910 

Filename file is not catalogued. 

Explanation: 

The file specified in the CSCOPY processor call cannot be assigned. The CSCOPY 

processor terminates. 

Action: 


CSCOPY processor. Take one of the following actions based on your local site practices: 

$ Enter an @ASG,T filename. executive control language statement to assign the file as 

a temporary file to be deleted when the run terminates 

$ Enter an @CAT filename. executive control language statement for the file to 

permanently catalog the file in the system file directory. 

Then, enter the CSCOPY processor call again. 

The Executive Control Language (ECL) and FURPUR Reference Manual describes the 

@ASG and @CAT executive control language statements. 

*ERROR* CS915 

Filename file specification has missing or invalid write key. 

Explanation: 

A missing or invalid write key caused an file assignment error during execution of the 

CSCOPY processor. 

Action: 

Correct the write key specification and execute the CSCOPY processor again. 

*ERROR* CS920 

Filename file specification has missing or invalid read key. 

Explanation: 

A missing or invalid read key caused an file assignment error during execution of the 

CSCOPY processor. 

Action: 

Correct the read key specification and execute the CSCOPY processor again. 

8-70 3787 3528-200

*ERROR* CS925 

Filename file is read inhibited. 

Explanation: 


A read-inhibited attribute caused an file assignment error during execution of the CSCOPY 

processor. 

Action: 

Remove the read-inhibited attribute from the file and execute the CSCOPY processor again. 

*ERROR* CS930 

Filename file is a private file. 

Explanation: 

A file assignment error during execution of the CSCOPY processor because the file was 

cataloged as a private file. 

Action: 

Recatalog the file as a private file and execute the CSCOPY processor again. 

*ERROR* CS935 

Filename file is rolled out. 

Explanation: 


rolled out. 

Action: 

Ask the local host’s system administrator to roll in the file. After the file is rolled in, 

execute the CSCOPY processor again. 

3787 3528-200 8-71


*ERROR* CS940 

Filename file cannot be rolled in. 

Explanation: 


could not be rolled in. 

Action: 

Consult the local host’s system administrator. If the file can be rolled in, execute the 

CSCOPY processor again. 

*ERROR* CS945 

Filename file is assigned to another run. 

Explanation: 


already assigned to another run. 

Action: 

Wait for the other run to free the file then execute the CSCOPY processor again. 

*ERROR* CS950 

Filename file is an unsupported type. 

Explanation: 

The file specified in the CSCOPY processor call is not a sector-addressable file, 

word-addressable file, or tape file. The CSCOPY processor terminated. 

Action: 


CSCOPY processor. Execute the CSCOPY processor again specifying a sector-addressable 

file, word-addressable file, or tape file for filename. 

8-72 3787 3528-200

*ERROR* CS953 

The file DDP*CS$CONFIG is not catalogued as word-addressable. 

Explanation: 


The output file must be word addressable when its name is DDP*CS$CONFIG. 

Action: 

Catalog DDP*CS$CONFIG as word-addressable. 

*ERROR* CS955 

Filename file I/O error. 

Explanation: 

An input/output error other than CS960 (beyond file limits) or CS965 (unassigned mass 

storage) occurred during execution of the CSCOPY processor. The CSCOPY processor 

terminated. 

Action: 

See the DDP-PPC log file for configuration services detailed error information. See the 

DDP-PPC Implementation and Administration Guide for information about the CSCOPY 

processor and for instructions on accessing configuration services entries in the DDP-PPC 

log file. 

*ERROR* CS960 

Filename file I/O error - Attempt to access beyond file limits. 

Explanation: 

An internal DDP-PPC configuration services error occurred while reading from or writing 

to the specified file. This may be due to bad or destroyed information in the input file 

specified in the CSCOPY processor call. The CSCOPY processor terminated. 

Action: 




log file. 

3787 3528-200 8-73


*ERROR* CS965 

Filename file I/O error - Unassigned mass storage. 

Explanation: 

An internal DDP-PPC configuration services error occurred while reading from or writing 

to the specified file. This may be due to bad or destroyed information in the input file 

specified in the CSCOPY processor call. The CSCOPY processor terminated. 

Action: 




log file. 

*ERROR* CS970 

A read/lock of the DDP*CS$CONFIG file failed. See log file snaps for detailed error. 

A copy of the Configuration Services Database was not done. 

Explanation: 

The CSCOPY processor could not read the configuration services database file 


Action: 




log file. 

8-74 3787 3528-200

*ERROR* CS972 


CSPACK, CSUPDT or CSCOPY is currently running. Therefore the CS Data Base file is 

being changed. 

A copy of the Configuration Services Data Base was not done. 

Explanation: 

The CSCOPY processor is unable to lock the configuration services database file 

DDP*CS$CONFIG to prevent access by other CSCOPY, CSUPDT, or CSPACK processors 


Action: 




log file. 

*ERROR* CS974 

CSCOPY could not write to the DDP*CS$CONFIG file. 

CSCOPY could not lock out the file. See log file snaps for detailed error. A copy of the 

Configuration Services Data Base was not done. 

Explanation: 

The CSCOPY processor was unable to lock the configuration services database file 

DDP*CS$CONFIG to prevent access by other CSCOPY, CSUPDT, or CSPACK processors 


Action: 




log file. 

3787 3528-200 8-75


*ERROR* CS975 

Filename file error. 

Explanation: 

An internal DDP-PPC configuration services error occurred while CSCOPY tried to access 

the specified file. The CSCOPY processor terminated. 

Action: 




log file. 

*ERROR* CS976 

CSCOPY could not unlock the DDP*CS$CONFIG file. See log file snaps for detailed error. 

A copy of the Configuration Services Data Base was not done. 

You will not be able to use CSUPDT, CSPACK, or CSCOPY with the current CS Data Base 

File until the lock is unlocked. Execute the CSUPDT processor with the U option to unlock 

the lock. 

Explanation: 

The CSCOPY processor was unable to unlock the configuration services database file 

DDP*CS$CONFIG. Any subsequent call to the CSCOPY, CSUPDT, or CSPACK processor 

will fail. 

Action: 



the log file. 

To unlock the file, execute CSUPDT with the u option when none of the three processors is 

running. 

8-76 3787 3528-200

*ERROR* CS980 

Both input and output files must be specified. 

Explanation: 


The CSCOPY processor call did not include both an input file name and an output file 

name. The processor call is ignored. 

Action: 

Enter another CSCOPY processor call that includes both an input file name and an output 

file name. See the DDP-PPC Implementation and Administration Guide for correct 

format specifications. 

*ERROR* CS985 

Input-file/output-file field cannot be an element name. 

Explanation: 

The CSCOPY processor call included an element name. The processor call is ignored. 

Action: 

Enter another CSCOPY processor call that specifies file names for both the input file and 

the output file. See the DDP-PPC Implementation and Administration Guide for correct 

format specifications. 

The Executive Control Language (ECL) and FURPUR Reference Manual describes 

file-naming conventions. 

3787 3528-200 8-77


*ERROR* CS990 

Output-file file is too small. Re-assign the file with a larger maximum. 

Explanation: 

The CSCOPY processor call specified an output file that was not large enough to 

accommodate the configuration services database input file specified. 

Action: 

Enter an @PRT,F executive control language statement to determine the size of the input 

file. 

Use an @ASG or @CAT executive control language statement to assign or catalog the 

output file again with a larger maximum size. 

The Executive Control Language (ECL) and FURPUR Reference Manual describes how 

to specify a file size in an @ASG or @CAT executive control language statement. 

*ERROR* CS995 

An error was encountered registering for termination registration (TRMRG). See the log 

file snaps for detailed error. 

Explanation: 

The CSCOPY, CSPACK, or CSUPDT processor encountered an error during termination 

registration. This is a fatal error. 

Action: 




log file. 

8-78 3787 3528-200

*ERROR* CS2000 

AT LINE line# The xxxxxx parameter contains invalid characters. 

The valid characters are A to Z, a to z, 0 to 9, ’.’ , ’-’. 

Explanation: 


The CSUPDT processor expects a letter, digit, period, or hyphen characters only for the 

indicated parameter at the indicated command line. 

Action: 




line. Processing continues at the next verb. Correct the element before processing it again. 



The valid characters are A to Z, a to z, 0 to 9, ‘.’ , ‘-’. 

The first character can be *. 

Explanation: 

The CSUPDT processor expects letters, digits, periods, or hyphen characters for the 

indicated parameter at the indicated line. The asterisk (*) may also be used as the first 

character. 

Action: 

If you are entering commands individually, CSUPDT ignores this command. You can 




3787 3528-200 8-79




The valid characters are A to Z, a to z, 0 to 9, ’$’ , ’-’. 

Explanation: 

The CSUPDT processor expects a letter, digit, dollar sign, or hyphen characters only for 

the indicated parameter at the indicated command line. 

Action: 







The valid characters are A to Z, a to z, 0 to 9, ’$’. 

Explanation: 

The CSUPDT processor expects letter, digit, or dollar sign characters only for the indicated 

parameter at the indicated command line. 

Action: 





8-80 3787 3528-200



The invalid characters are ’/’ or ’,’. 

Explanation: 


The CSUPDT processor detects an invalid slash or comma character for the indicated 

parameter at the indicated command line. 

Action: 







The invalid characters are ’@’, ’ ’, ’,’, ’.’, and ’;’. 

Explanation: 

The CSUPDT processor detects an invalid @ character, blank character, comma, period, or 

semicolon for the indicated parameter at the indicated command line. 

Action: 





3787 3528-200 8-81



AT LINE line# The xxxxxx parameter contains the reserved name xxxxxx. 

Explanation: 

The CSUPDT processor detects an invalid parameter at the indicated command line. 

Action: 







The invalid characters are ’ ’, ’,’, ’.’, and ’;’. 

Explanation: 

The CSUPDT processor detects an invalid blank character, comma, period, or semicolon 

for the indicated parameter at the indicated command line. 

Action: 





8-82 3787 3528-200



AT LINE line# The last xxxxxx characters of xxxxxx name must be spaces. 

Explanation: 

The CSUPDT processor detects an invalid parameter value at the indicated command line. 

Action: 






AT LINE line# The SYM-WAIT-TIME parameter must be in the range of 1 to 511. 

Explanation: 

The CSUPDT processor detects an invalid wait time value at the indicated command line. 

This value must be between 1 and 511. 

Action: 





3787 3528-200 8-83



AT LINE line# The HIGH-PRECEDENCE parameter must be equal to or greater than the 

PRECEDENCE parameter. 

Explanation: 


Action: 






AT LINE line# The xxxxxx parameter must be less than or equal to 63. 

Explanation: 

The CSUPDT processor detects an invalid parameter value at the indicated command line. 

Action: 





8-84 3787 3528-200



AT LINE line# The xxxxxx parameter must be of the form ’$LTnn’, where nn is exactly two 

numeric characters. 

Explanation: 

The CSUPDT processor detects an invalid parameter at the indicated command line. The 

parameter must be of the form ’LTnn’. 

Action: 






AT LINE line# The xxxxxx parameter contains invalid characters ’,’ or ’:’. 

Explanation: 

The CSUPDT processor detects an invalid colon (:) or comma (,) character for the 

indicated parameter at the indicated command line. 

Action: 





3787 3528-200 8-85



AT LINE line# The xxxxxx parameter contains characters that are valid for SNA but not 

for PPC. The valid PPC characters are A to Z, a to z, 0 to 9, ’$’ , ’-’. 

Explanation: 

The CSUPDT processor detects characters the are valid for SNAPPC, but invalid for 

DDP-PPC. 

Action: 

None necessary. 


AT LINE line# The xxxxxx parameter is assumed to be xxxxxx. The name you specified is 

ignored. 

Explanation: 

The CSUPDT processor detects an invalid parameter at the indicated command line. The 

parameter is assumed to be xxxxxx. 

Action: 

None necessary. 


AT LINE line# the AE-QUALIFIER parameter must be an integer between -2**63 and 

+(2**63)-1, inclusive. (** here means exponentiation, but is not valid syntax.) 

Explanation: 

The CSUPDT processor detects an invalid value for the indicated parameter at the 

indicated command line. The value must be between -2**63 and +(2**63)-1. 

Action: 





8-86 3787 3528-200



AT LINE line# ALT-TRANSPORT-CLASS = xxxxxx is invalid when TRANSPORT-CLASS = 

xxxxxx. 

Explanation: 

The CSUPDT processor detects an invalid ALT-TRANSPORT-CLASS parameter when this 

TRANSPORT-CLASS is specified. 

Action: 






AT LINE line# If xxxxxx, thenxxxxxxmust be defined unless xxxxxx. 

Explanation: 

If the communication system is defined as COMM-SYSTEM = CSU, the transport must be 

defined unless TYPE = OSI is specified. 

Action: 





3787 3528-200 8-87



AT LINE line# xxxxxx must be defined with TYPE= xxxxxx. 

Explanation: 


Action: 






Remaining parameters cannot be read because this xxxxxx record was created by an 

earlier release of CSUPDT. 

Explanation: 

When reading the specified records, it was found that the record was created by DDP-PPC 

4R1 and the record format has changed for release level 5R1 and later. 

Action: 

No action is required, but you may want to delete the specified record and add it under 

DDP-PPC 5R1 or later. 

8-88 3787 3528-200



If an INTERNET-ADR is specified the TRANSPORT-CLASS must be TP0/TCPIP. 

Conversely, TP0/TCPIP may only be specified when an INTERNET-ADR is specified. 

Explanation: 

Either the INTERNET-ADR keyword was specified without a value of TP0/TCPIP on the 

TRANSPORT-CLASS keyword, or a value of TP0/TCPIP was specified on the 

TRANSPORT-CLASS keyword and the INTERNET-ADR keyword was not specified. 

Action: 

See the specific product implementation guide for the correct command format, 

parameters, and description. 

Enter a MODIFY command with the corrected parameters. 


TPSU TITLE T61 contains invalid T61 character set. 

Explanation: 

An invalid character set was entered. The record being added is ignored. 

Action: 

Reenter the command using the correct character set. 

3787 3528-200 8-89

Appendix A 

DDP-FJT Internal Error Codes 

A DDP-FJT internal error code may be displayed: 

$ As part of the **DDP20000 error message 

$ In the DDPMASTER run when an error occurs during the processing of a file given to 

DDP-FJT by the @SYM command. 

To find out what the code means: 

$ Locate the internal error in Table A-1 and find its corresponding error message 

identifier number. 

$ Then, using the error message identifier, locate the message listed in Section 2. 

You can also use IPF User Assistance to display the complete text of a message that relates 

to an internal error code. 

For example, if you receive the following error message: 

 

 

1. Look up error code 134 (decimal) in Table A-1. Error code 134 relates to DDP-FJT 

message **DDP1420. 

2. Then look up DDP1420 in Section 2, or enter the following command: 

 

Note: While each error mesage number is prefixed with two asterisks (**), you do 

not enter the asterisks. 

IPF 1100 User Assistance responds with the text of message **DDP1420: 

 

Table A-1 provides: 

$ The decimal value of all the internal errors that can be reported 

$ The error code’s octal equivalent 

$ The related DDP-FJT error message number 

3787 3528-200 A-1


Table A-1. DDP-FJT Internal Error Codes 

Value Reported Related Message Number 

Decimal Octal 

1 1 DDP1220 






7 7 Not used 

8 10 Not used 

9 11 Not used 

10 12 Not used 


















continued 

A-2 3787 3528-200

Table A-1. DDP-FJT Internal Error Codes (cont.) 


Decimal Octal 





























continued 

3787 3528-200 A-3




Decimal Octal 




























continued 

A-4 3787 3528-200



Decimal Octal 





























continued 

3787 3528-200 A-5




Decimal Octal 




























continued 

A-6 3787 3528-200



Decimal Octal 





























continued 

3787 3528-200 A-7




Decimal Octal 




























continued 

A-8 3787 3528-200



Decimal Octal 





























continued 

3787 3528-200 A-9




Decimal Octal 




























continued 

A-10 3787 3528-200



Decimal Octal 














3787 3528-200 A-11

Appendix B 

Configuration Services Status Codes 

Some Configuration Services messages include the following text: 

 

 

The status and substatus codes are listed in Table B-1. 

Code* 

Table B-1. Configuration Services Status and Substatus Codes 

Status Codes Substatus Codes 

Description 

Code* 

0 OK 1 Not last record in chain 

2 Last record in chain 

1 End-of-Chain 0 Null 

Description 

2 No-find 21 No-find on Search-thru-Chain 

22 Empty chain on Search-thru-Chain 

23 Empty chain on Search-by-Key 

24 No-find on Search-by-Key 

25 Record found but marked deleted 

26 Caller attempted to read-first-record without first reading 

owner record 

27 Attempt to read past end of a search table 

0 Null (none of the above) 

3787 3528-200 B-1 

continued

Configuration Services Status Codes 

Code* 

Table B-1. Configuration Services Status and Substatus Codes (cont.) 

Status Codes Substatus Codes 

Description 

Code* 

Description 

3 User-error 31 Unsupported function 

32 Work buffer destroyed or not initialized 

33 Modified record is bigger than original 

34 Incorrect record type - differs from "current" type 

35 Duplicate names not allowed 

36 Record already linked in chain 

37 Invalid key size (The key is either larger than the maximum 

key size supported by configuration services or the key size 

differs from the previous records of the same record type.) 

38 Specified search buffer is too small 

39 Unable to write to search buffer 

40 CS-GET-XXXX done without first calling CS-BEGIN 

41 CS common bank currently loaded not the proper version 

42 Data structures must be above 40000 to avoid conflict with 

CS I-banks 

5 Internal-error 3 Record just read is marked deleted 

50 Input/output error (other than "beyond file limits" or 

"unassigned area of mass storage") 

51 Record beyond file limits 

52 Invalid record type 

53 Unassigned area of mass storage referenced 

54 Work buffer overflow (link entries) 

55 Work buffer overflow (search descriptors) 

56 Insufficient link entry slots in record header 

57 Missing link in requested chain 

58 Invalid search table-id 

59 Contingency 

7 Connect-error 70 Assign error of configuration services database file other 

than those defined below. 

71 Configuration services database file does not exist 

72 Configuration services database file has a write key 

73 Configuration services database file has a read key 

74 Configuration services database file is read inhibited 

75 Configuration services database file is a private file 

76 Configuration services database file is rolled out 

77 Configuration services database file cannot be rolled in 

78 Configuration services database file is assigned to another 

run 

79 Configuration services database file is not word addressable 

*Codes are in decimal 

B-2 3787 3528-200

Bibliography 

DCP Series OSI Transport Services (OSITS) Installation, Configuration, and 

Operations Guide (7831 5587). Unisys Corporation. 

OS 1100 Distributed Data Processing File and Job Transfer (DDP-FJT) IPF and Batch 

Interface Operations Guide (3787 3551). Unisys Corporation. 

OS 1100 Distributed Data Processing File and Job Transfer (DDP-FJT) Menu Interface 


OS 1100 OSI-FTAM/DDP-FJT Print and Tape Transfer Facilities Implementation and 


OS 1100/DCP Series Open Systems Communications Software Conceptual Overview 

(7831 5835). Unisys Corporation. 

OS 2200 Communications Management System (CMS 1100) Operations Reference 

Manual (7831 5694). Unisys Corporation. 

OS 2200 Communications Management System (CMS 1100) Programming Reference 

Manual (7831 5827). Unisys Corporation. 

OS 2200 Distributed Data Processing (DDP-PPC) DCA Interface C Language 

Programming Guide (3787 3254). Unisys Corporation. 

OS 2200 Distributed Data Processing (DDP-PPC/DDP-FJT) DCA Interface COBOL 


OS 2200 Distributed Data Processing (DDP-PPC) OSI Interface C Language 


OS 2200 Distributed Data Processing (DDP-PPC) OSI Interface COBOL Programming 

Guide (3787 3296). Unisys Corporation. 

OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface C Language 


OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface COBOL 


OS 2200 Distributed Data Processing (DDP-PPC) TCP/IP Interface FORTRAN 


3787 3528-200 Bibliography-1

Bibliography 

OS 2200 Distributed Data Processing Program-to-Program Communications 

(DDP-PPC) Implementation and Administration Guide (3787 3270). Unisys 

Corporation. 

OS 2200 Distributed Data Processing File and Job Transfer (DDP-FJT) Implementation 

and Administration Guide (3787 3544). Unisys Corporation. 

OS 2200 Exec System Software Executive Requests Programming Reference Manual 


OS 2200 Executive Control Language (ECL) and FURPUR Reference Manual (7830 

7949). Unisys Corporation. 

OS 2200 Interactive Processing Facility (IPF 1100) Command Language User’s Guide 


1100/90 and 2200 Systems Support Guide (7831 2329). Unisys Corporation. 

Bibliography-2 3787 3528-200

DDP-PPC/DDP-FJT Messages Reference Manual - Public Support ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?