airline control system version 2: messages and codes

Airline Control SystemVersion 2.4.1

Messages and Codes

IBM

SH19-6742-24

Note

Before using this information and the product it supports, be sure to read the general information under“Notices” on page v.

This edition applies to Release 4, Modification Level 1, of Airline Control System Version 2, Program Number 5695-068,and to all subsequent releases and modifications until otherwise indicated in new editions. Order publications throughyour IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address givenbelow. A form for readers’ comments appears at the back of this publication. If the form has been removed, address yourcomments to:

ALCS Development2455 South RoadP923Poughkeepsie NY 12601-5400USA

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way itbelieves appropriate without incurring any obligation to you.© Copyright International Business Machines Corporation 2003, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

Notices..................................................................................................................v

Programming interface information.......................................................................vi

Trademarks......................................................................................................... vii

About this book...................................................................................................viiiHow to look up a message.........................................................................................................................viiiAutomated operations...............................................................................................................................viii

Chapter 1. Numbering and format of ALCS messages and codes..............................1Explanation of message formats................................................................................................................. 2Allocation of message numbers.................................................................................................................. 2Severity codes.............................................................................................................................................. 4Subcomponent codes.................................................................................................................................. 5

Chapter 2. Online monitor messages (MVS console): DXC000-DXC479.....................8

Chapter 3. Offline program messages: DXC480-DXC799....................................... 52

Chapter 4. ALCS generation macro MNOTEs: DXC800-DXC999.............................. 80

Chapter 5. ALCS application macro MNOTEs: DXC1000-DXC1999........................102

Chapter 6. Online monitor messages (ALCS printer): DXC2000-DXC2999............. 122

Chapter 7. User-written application program messages: DXC3000-DXC3999.......182

Chapter 8. Responses to ALCS commands: DXC5000-DXC5999........................... 183

Chapter 9. ALCS Web Server and Hierarchical File System (HFS) messages:DXC6000-DXC6999........................................................................................ 209

Chapter 10. Responses to ALCS commands: DXC8000-DXC8999......................... 210

Chapter 11. NetView interface program messages: DXC9000-DXC9099...............291

Chapter 12. Error Messages for COMTC ADD/REPLACE: DXC9100-DXC9199........ 294

Chapter 13. System error codes: 000000-000FFF............................................... 302

Chapter 14. Abnormal termination completion codes..........................................445

Chapter 15. Sense codes....................................................................................450

Appendix A. Messages intended for automated operations................................. 451

iii

Acronyms and abbreviations.............................................................................. 462Glossary............................................................................................................ 474Bibliography...................................................................................................... 504

iv

Notices

References in this publication to IBM® products, programs or services do not imply that IBM intends tomake these available in all countries in which IBM operates. Any reference to an IBM product, program,or service is not intended to state or imply that only IBM's product, program, or service may be used.Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectualproperty rights may be used instead of the IBM product, program, or service. Evaluation and verificationof operation in conjunction with other products, except those expressly designated by IBM, is the user'sresponsibility.

IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries,in writing, to:

The Director of LicensingIBM Corporation500 Columbus AvenueThornwood, NY 10594USA

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM CorporationDepartment 830A522 South RoadMail Drop P131Poughkeepsie, NY 12601-5400USA

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

© Copyright IBM Corp. 2003, 2019 v

Programming interface information

This book is intended to help operators, application programmers, and system programmers tounderstand and respond to the messages they may meet when running or developing applications forAirline Control System Version 2, Program Number 5695-068.

This book also documents General-Use Programming Interface and Associated Guidance Informationprovided by Airline Control System Version 2:

• The section “Automated operations” on page viii describes the General-Use Programming Interfacethat allows customers to write programs that interact with Airline Control System Version 2.

• Appendix A, “Messages intended for automated operations,” on page 451 lists those Airline ControlSystem Version 2 messages that are intended to form part of the General-Use Programming Interface.

vi Airline Control System Version 2: Messages and Codes

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web atCopyright and trademark information at www.ibm.com/legal/copytrade.shtml.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

© Copyright IBM Corp. 2003, 2019 vii

About this book

This book describes the messages and codes issued by Release 4.1 of Airline Control System (ALCS)Version 2, an IBM licensed program.

ALCS is one of a family of IBM programs designed to satisfy the needs of airlines and other industries withsimilar requirements for high-volume and high-availability transaction processing.

The product, which is also known as TPF/MVS, provides the Transaction Processing Facility (TPF)application programming interface (API) for z/OS® environments. It supersedes ALCS/Multiple VirtualStorage/Extended Architecture (ALCS/MVS/XA), known as ALCS Version 1.

Throughout this book:

• Airline Control System Version 2 is abbreviated to ALCS unless the context makes it necessary todistinguish between ALCS Version 2 Release 4.1, and the predecessor products ALCS Version 2 Release3, ALCS Version 2 Release 2, ALCS Version 2 Release, ALCS/MVS/XA and ALCS/VSE.

• Airlines Line Control Interconnection (ALCI) includes the function of network extension facility (NEF). • Advanced Communications Function for the Virtual Telecommunication Method is abbreviated to

VTAM®.• TPF refers to all versions of Transaction Processing Facility and its predecessor, Airlines Control

Program (ACP).• MVS™ refers to z/OS. MVS, s/390, and "OS/390®" also refer to operating systems.

For further details of ALCS, see the relevant manuals listed in “Bibliography” on page 504.

How to look up a messageIn order to find the description of a particular message, make a note of the message number.

• In the printed manual, message numbers are printed on the top outside corner of the page.• When you use the BookManager® softcopy book, you need to include the severity code or an asterisk

when you use the BookManager or IBM Library Reader Search facility. For example:

DXC110RDXC110*

This lists every topic referring to message DXC110R. For most messages, a search produces a singletopic - and since each message is a topic, you have the full description of the message, without anyunnecessary information.

• The softcopy version of this book has been enabled for Online Message Facility. The various softcopycollection kits that this book occurs on contain a full description of how to install the Online MessageFacility at your location.

Automated operationsThe messages listed in Appendix A, “Messages intended for automated operations,” on page 451 areintended as a part of the General-Use Programming Interface.

The wording of messages is not a part of the General-Use Programming Interface.

However, if you wish to use ALCS messages as input to an automated operator, you can do so by makinguse of:

• The message number, and• The tokenized variables (if any)

viii About this book

The basic meaning of the message is intended to remain unchanged, and any tokenized variables areintended to continue to form part of the message. The wording, however, and the sequence of tokenizedvariables could be changed, and additional tokenized variables could be introduced.

Note, also, that not all the message_variables shown in this manual are tokenized.

The tokenized variables take the form:

TOKEN-'variable'TOKEN-X'hex_variable'

If the same token is used more than once in one message, then the token will be suffixed with a numeral,for example:

FOUND NR1-'3' OCCURRENCES -- NR2-'2' CHANGED

The following tokens are used in ALCS messages. If further tokens are introduced in PTFs, they will beannounced in the PTF documentation.

ACabend_code

ACRNassociated_CRN

ACTaction

ADaddress

ANarea_number

ASaddress_space_name

CCcondition_code

CFTconfiguration_table

CRIcommunication_resource_identifier

CRNcommunication_resource_name

CSWchannel_status_word

CTCRAS_type

DDNddname

DNdirectory_number

DSNdata_set_name

DSPdisplacement

ECerror_code

About this book ix

EIBerror_index_byte

FB2feedback_2

FDBK2feedback_2

FNfunction

FTfiletype

HEXHLN_exit_address

HHhours

IAinterchange_address

KCNSLC_link_channel_number

LBLlabel

LEIDlogical_end_point_identifier

LSlog_stream_name

LSETLoad_set

LSIlink_status_identifier

LUNlu_name

MBImessage_block_indicator

MMminutes

MODNmodule_name

MTmessage_type

NRnumber

OFSoffset

OPI/O_operation_code

ORDordinal_number

PLNplan

PNprogram_name

x About this book

POport_number

PROGprogram_name

PTpool_type

PWEpassword_expiry_time

QMqueue_manager_name

QNqueue_name

RCreturn_code

RQTrequest_type

RSCreason_code

RTrecord_type

RTNCDreturn_code

SBSsubsystem_identifer

SCsense_code

SENSEsense_data

SEQNsequential_file_name

SNslot_number

SSsystem_state

TAterminal_address

TCIDterminal_circuit_identity

TCRNsubordinate_terminal_CRN

TNtable_name

TSKtask_ID

UCBTUCB_type

VSvolume_serial

XCRNX.25_CRN

About this book xi

xii Airline Control System Version 2: Messages and Codes

Chapter 1. Numbering and format of ALCS messagesand codes

The messages that ALCS sends to the MVS operator console and MVS job output are in a form thatis compatible with other MVS program products. The format of these messages, together with ALCSmessages sent to other destinations, is shown in Table 1 on page 1.

The message format and numbering range vary with the type of message or code. This book is dividedinto sections, each containing details of different types of message. Table 1 on page 1 lists the types ofmessages and codes and the corresponding numbering ranges and an outline of the formats.

Table 1. ALCS message and code types, format, and number range

Message or code type Destination Numberingrange

Format

Messages generated bythe online monitor

MVS console 000 - 479 DXCnnns ccc i text

Messages generated bythe offline programs

Job output 480 - 799 DXCnnns ccc [i] text

ALCS generation macroMNOTEs

Assembler listing 800 - 999 DXCnnns ccc i text

ALCS application macroMNOTEs

Assembler listing 1000 - 1999 DXCnnnns text

Messages generated bythe online monitor

ALCS printer 2000 - 2999 DXCnnnns ccc i [hh.mm.ss] text

Available for user-writtenapplication programs

3000 - 3999

Responses to ALCScommands

MVS console, RO CRAS,originating terminal

5000 - 5999 DXCnnnns CME i hh.mm.ss aaaa text

ALCS Web Server and HFSmessages


6000 - 6999 DXCnnnns HFS i [hh.mm.ss] text

Responses to ALCScommands


8000 - 8999 DXCnnnns CMD i hh.mm.ss aaaa text

Messages generated bythe NetView® interfaceprogram DXCPPI

NetView log 9000 - 9099 DXCnnnns ccc i [hh.mm.ss] text

Error Messages generatedby OCTM

Returned to applicationwhich issued COMTCmonitor-request macro

9100 - 9199 DXCnnnns text

System errors MVS console, RO CRAS,originating terminal

000000 -000FFF

xxxxxx text

Abnormal terminationcompletion codes

MVS console, ALCS joboutput

nnnn

Sense codes Sent by ALCS as errorindicators on an LU 6.1link

ssssnnnn

© Copyright IBM Corp. 2003, 2019 1

Explanation of message formats

Messages with DXC prefixThe format of ALCS messages prefixed "DXC" is:

DXCIBM product code for ALCS (ALCS/VSE, ALCS/MVS/XA, and ALCS Version 2)

nnn or nnnnA unique decimal number identifying the message

sSeverity code (see below)

cccALCS subcomponent code (see below)

iThe ALCS system identifier. This is one alphanumeric character specified by the ALCS generation.

hh.mm.ssTime stamp

textText of the message.

aaaaThe four alphabetic characters that identify the ALCS command. For example DCOM for the commandZDCOM.

System errorsThe format of ALCS system error messages is:

xxxxxxA 6-digit hexadecimal number identifying the system error

textText of the system error message.

Abnormal termination codesThe format of ALCS abnormal termination completion codes is:

nnnnA 4-digit decimal number identifying the abnormal termination.

Sense codesThe format of ALCS sense codes is:

ssssSNA sense code; a 4-digit hexadecimal number

nnnnALCS unique code; a 4-digit hexadecimal number identifying the error condition.

Allocation of message numbersMessage numbers beginning with "DXC" are allocated in blocks as follows:

000-479ALCS online monitor (DXCMON)

2 Airline Control System Version 2: Messages and Codes

480-489ALCS cross reference facility (DXCXREF)

490-499ALCS statistical report generator (DXCSRG)

500-549DRIL file create (DXCSTCDR)

550-599ALCS system test compiler (DXCSTC)

600-609Database compress/expand utility

610-699STC edit (DXCSTCED)

700-749ALCS communication report generator (DXCCOMOL)

750-779Offline C utilities

780-799ALCS diagnostic file processor (DXCDTP)

800-839ALCS generation - communication subcomponent (YCM)

840-899ALCS generation - DASD subcomponent (YDB)

900-949ALCS generation - general messages

950-959ALCS generation - ALCS, ALCSGEN, and JOBCARD macros

960-979ALCS generation - sequential file subcomponent (YSF)

980-989ALCS generation - system parameters subcomponent (YST)

990-999ALCS generation

1000-1099General macro parameter MNOTEs

1100-1199Common macro parameter MNOTEs

1500-1590Macro-unique MNOTEs

1900-1999Logic errors in ALCS application macros.

2000-2299System

2300-2349TCP/IP

2350-2399MQSeries® bridge

2400-2599Communication

2600-2649Timer

Chapter 1. Numbering and format of ALCS messages and codes 3

2650-2699Sequential file

2700-2749Initializer

2750-2799DASD

2800-2824Program

2825-2849Loader

2850-2874Dump

2875-2899Keypoint

2900-2919DB2®

2920-2939MQSeries

2940-2959APPC/MVS

2960-2998TCP/IP

3000-3999Available for user-written application programs

5000-5999Responses to ALCS commands

6000-6999ALCS Web Server and Hierarchical File System (HFS)

8000-8999Responses to ALCS commands

9000-9099NetView interface program (DXCPPI)

9100-9199Online communication table maintenance

Severity codesALCS uses the following severity codes:

AAction. The MVS operator must take some action.

RReply. The MVS operator must reply.

DReply. The MVS operator may reply.

IInformation. Processing continues normally.

WAttention. Processing continues but results may differ from those required.

EError. Processing continues but results will differ from those required.


SSevere error. Processing cannot continue.

TTermination. Processing is terminated.

Subcomponent codesALCS uses the following subcomponent codes:

APPReserved for customer use

CMDOnline monitor - operator commands

CMEOnline monitor - operator commands

COMOnline monitor - communication initialization

CMPDatabase compress/expand utility

DASOnline monitor - DASD initialization and termination

DB2Online monitor - DB2 routines

DFSOnline monitor - TPFDF support

DMPOnline monitor - system error routines

DTPALCS diagnostic file processor program (DXCDTP)

HFSOnline monitor - ALCS Web Server and Hierarchical File System (HFS)

HTPOnline monitor - HTTP Client

ICFOnline monitor - ICSF

INTOnline monitor - initialization

JSNOnline monitor - JSON Parser

KPTOnline monitor - keypoint routines

LDEOnline monitor - module load routines

LU6Online monitor - Advanced Program-to-Program Communications/MVS (APPC/MVS) routines

MQBOnline monitor - MQSeries bridge

MQMOnline monitor - MQSeries

OCMCommunication report generator program (DXCCOMOL)


PGMOnline monitor - program management

SAFOnline monitor - security

SEQOnline monitor - sequential file initialization

SRGStatistical report generator program (DXCSRG)

STCSystem test compiler programs (DXCSTC, DXCSTCED, DXCSTCDR)

SYSOnline monitor - system routines

TCPOnline monitor - TCP/IP routines

TIMOnline monitor - timer routines

XRFALCS cross reference facility (DXCXREF)

YCMALCS generation - communication subcomponent macros

YDBALCS generation - DASD subcomponent macros

YGNALCS generation - ALCS, ALCSGEN, and JOBCARD macros

YSFALCS generation - sequential file subcomponent macros

YSTALCS generation - system parameters subcomponent macros

Arranged according to the component of ALCS that uses them:

• ALCS generationYGN

ALCS, ALCSGEN, and JOBCARD macrosYCM

Communication subcomponent macrosYDB

DASD subcomponent macrosYSF

Sequential file subcomponent macrosYST

System parameters subcomponent macros• Online monitorCMD

Responses to ALCS commandsCME

Responses to ALCS commandsCOM

Communication initializationDAS

DASD initialization and termination


DB2DB2 routines

DFSTPFDF support

HFSALCS Web Server and Hierarchical File System (HFS)

INTInitialization

KPTKeypoint routines

LDEModule load routines

LU6APPC/MVS routines

MQBMQSeries bridge

MQMMQSeries routines

PGMProgram management

SEQSequential file initialization

DMPSystem error routines

TIMTimer routines

SYSSystem routines

• Off-line programsXRF

ALCS cross reference facility (DXCXREF)DTP

ALCS diagnostic file processor program (DXCDTP)OCM

Communication report generator program (DXCCOMOL)SRG

Statistical report generator program (DXCSRG)STC

System test compiler programs (DXCSTC, DXCSTCED, DXCSTCDR)


Chapter 2. Online monitor messages (MVS console):DXC000-DXC479

DXC000E Logic error - Invalid messagenumber 'cccnnn'

ExplanationAn ALCS monitor routine or offline program attemptedto send an error message with an invalid messagenumber. ccc is the subcomponent code, and nnn isthe message number (in an internal format used byDXCEMSG and DXCEMSGO).

System actionALCS sends this error message and then proceedsnormally.

User responseIf this error occurs, ask your system programmer toinform your IBM programming support representative.

Note:

Not in GUPI: The next message is not intended forautomated operations.

ModuleDXCEMSG, DXCEMSGO

DXC001E Logic error - Invalidsubcomponent code 'cccnnn'

ExplanationAn ALCS monitor routine or offline programattempted to send an error message with an invalidsubcomponent code. ccc is the subcomponent code,and nnn is the message number (in an internal formatused by DXCEMSG and DXCEMSGO).



ModuleDXCEMSG, DXCEMSGO

DXC030E TPFDF initialization failed - Notenough storage for DB table

ExplanationSelf-explanatory.

System actionALCS continues processing normally. TPFDF isunusable.

User responseAllocate more storage and try again.

ModuleDXCDFS

DXC031W TPFDF initialization failed - Notenough storage for DF statistics


System actionALCS continues processing normally. TPFDF is usable,but TPFDF data collection is unusable.

User responseAllocate more storage and try again.

ModuleDXCDFS

DXC032E TPFDF initialization failed - Notenough storage for static fastlinktable



System actionALCS continues processing normally. TPFDF isunusable.

User responseRestart ALCS with more private storage.

ModuleDXCDFS

DXC040T Timer initialization failed - TODclock error

ExplanationDuring ALCS initialization, the processor time-of-day( TOD ) clock is in not-set, error, stopped, or not-operational state.

System actionALCS terminates abnormally.

Operator responseEnsure that the TOD clock is operational and set.Activate the alternate ALCS if there is one, or restartALCS. If this is an isolated instance, follow your normalprocedure for a non-urgent problem. If it happensrepeatedly, inform your system programmer.

ModuleDXCTIM

DXC041W ALCS loop detected -- addressX'aaaaaaaa'

ExplanationA possible loop condition for a cpu loop subtask hasbeen detected. aaaaaaaa is an address within theloop. If this condition persists, four similar messagesare sent out.

System actionALCS is possibly in a loop.

User responseIf the loop condition is confirmed, cancel and restartALCS, and ask your system programmer to inform yourIBM programming support representative.

Problem determinationUse information from messages DXC041W andDXC042I for diagnostic purposes.

ModuleDXCTIR

DXC042I R00 - xxxxxxxx R01 - xxxxxxxx R02- xxxxxxxx R03 - xxxxxxxx R04 -xxxxxxxx R05 - xxxxxxxx R06 -xxxxxxxx R07 - xxxxxxxx R08 -xxxxxxxx R09 - xxxxxxxx R10 -xxxxxxxx R11 - xxxxxxxx R12 -xxxxxxxx R13 - xxxxxxxx R14 -xxxxxxxx R15 - xxxxxxxx

ExplanationA possible loop condition for a cpu loop subtaskhas been detected. The contents of each generalregister at the time of the detection are represented byxxxxxxxx. Message DXC042I always follows messageDXC041W.

System actionALCS is possibly in a loop.

User responseIf the loop condition is confirmed, cancel and restartALCS, and ask your system programmer to inform yourIBM programming support representative.

Problem determinationUse information from messages DXC041W andDXC042I for diagnostic purposes.

ModuleDXCTIR

DXC051T Sequential file initialization failed- Not enough sequential filesavailable

ExplanationALCS initialization must allocate and open data setsfor:

• ALCS diagnostic file• ALCS database update log

but either:

Chapter 2. Online monitor messages (MVS console): DXC000-DXC479 9

• A definition is omitted from the sequential filegeneration,

or:• An error occurred during allocate or open of one of

the data sets.

System actionALCS ends abnormally.

User responseCheck that the ALCS sequential file generation definessufficient sequential files for system use. Examine anyALCS messages on the MVS console to determinewhich data set caused the error, and examine it.Ensure that there is sufficient space to allocatesequential files on DASD.

ModuleDXCINTS

DXC052T Can not read seq file configurationtable TN-'name' Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

ExplanationAn error occurred when ALCS initialization tried to read(MVS LOAD macro) the sequential file configurationtable.


Problem determinationMVS System Codes lists LOAD system completion andreason codes.

ModuleDXCINTS

DXC054I Seq file SEQN-'name' DsnameDSN-'data_set_name' VolumeVS-'volume_serial' allocated

ExplanationALCS has allocated and opened a data set for asequential file. Name is the symbolic name of thesequential file. data_set_name is one of the following:

• The data set name of a physical sequential file dataset, up to a maximum of 44 characters.

• The partitioned data set (PDS) name, up to amaximum of 34 characters, followed by the PDSmember in the format pdsname(pdsmem).

• The data set name of a general data set, upto a maximum of 34 characters, followed bythe absolute generation number in the formatdsname.VnnnnGmm.

System actionALCS continues processing. The sequential file isavailable.

ModuleDXCINTS, DXCSEQ

DXC055I Seq file SEQN-'name' DsnameDSN-'data_set_name' VolumeVS-'volume_serial' deallocated

ExplanationALCS has deallocated a data set for a sequential file.Name is the symbolic name of the sequential file.data_set_name is one of the following:




System actionALCS continues processing.

Operator responseFollowing this message, the operator can rename thedata set, migrate it, delete it, and so on; and caninitiate other jobs or tasks that use the data set.

ModuleDXCSEQ

DXC056E Sequential file SEQN-'name'allocate/open failed - Return codeRC-X'return_code'


ExplanationALCS was unable to allocate or open a data set fora sequential file. Name is the symbolic name of thesequential file. Return_code is 6 hexadecimal digits.The first 2 digits are a type code and the last 4 digitsare the return code. The meaning of the return codedepends on the type code as follows:

TypeMeaning of Return Code

01Error return from MVS SVC 99 function (DYNALLOCmacro). The return code is the SVC 99 error reasoncode.

MVS Authorized Assembler Services Guidedescribes these error reason codes.

02Error return from MVS GETMAIN macro. ALCS wasunable to obtain storage for I/O buffers for thedata set. The return code is the contents of generalregister 15 on return from GETMAIN.

MVS Authorized Assembler Services Guidedescribes these return codes.

03Error return from MVS PGSER macro. ALCS wasunable to page fix the I/O buffers for the data set.The return code is the contents of general register15 on return from PGSER.


04Error return from MVS OPEN macro. ALCS wasunable to open the data set. The return code iszero (there is no return code from OPEN).

05System ABEND. The ALCS subtask that allocatesand opens the data sets ended abnormally. Thereturn code is the system completion code.

MVS System Codes describes system completioncodes.

06User ABEND. The ALCS subtask that allocates andopens the data sets ended abnormally. The returncode is the user completion code. This conditionshould not occur. If it does, ask your systemprogrammer to inform your IBM programmingsupport representative.

07ALCS was unable to use this data set as the blocksize is invalid. The return code is the invalid blocksize.

System actionALCS continues processing. The sequential file is notavailable.

ModuleDXCINTS, DXCSEQ

DXC070E Hiperspace initialization failed- Return code RC-X'return_code'Reason code RSC-X'reason_code'

ExplanationDuring initialization ALCS was unable to createhiperspace.

System actionALCS continues with initialization, but cannot usehiperspace.

Problem determinationSee description of DSPSERV in MVS AuthorizedAssembler Services Reference for the meanings ofreturn_code and reason_code.

ModuleDXCHYP

DXC071E Hiperspace initialization failed -Not enough storage for controlblock

ExplanationALCS requires storage for hiperspace initialization. Itissues the MVS GETMAIN macro to obtain this storage.There was not enough storage for MVS to satisfy theGETMAIN.

System actionALCS continues with initialization, but cannot usehiperspace.

User responseIncrease the storage allocation for the ALCS region.

ModuleDXCHYP

DXC072E Dataspace creation failed- DSPNAME-'dataspace_name'


Return code RC-X'return_code'Reason code RSC-X'reason_code'

ExplanationSelf-explanatory

System actionALCS continues, but cannot use the database.

Problem determinationRefer to the description of DSPSERV in MVS AuthorizedAssembler Services Reference for the meanings ofreturn_code and reason_code.

ModuleDXCHYP

DXC073E ALET Add failed --DSPNAME-'dataspace_name'Return code RC-X'return_code'


System actionALCS continues, but cannot use the database.

Problem determinationRefer to the description of ALESERV in MVS AuthorizedAssembler Services Reference for the meaning of theALESERV ADD return_code.

ModuleDXCHYP

DXC074E ALET Delete failed— DSPNAME-'dataspace_name'Return code RC-X'return_code'


System actionALCS continues.

Problem determinationRefer to the description of ALESERV in MVS AuthorizedAssembler Services Reference for the meaning of theALESERV DELETE return_code.

ModuleDXCHYP

DXC080E DB2 initialization failed - Notenough storage

ExplanationDuring initialization ALCS was unable to obtain thestorage required to support DB2 calls.

System actionALCS continues with initialization, but cannot use DB2.


ModuleDXCSQL

DXC081E DB2 CAF entry point load failed- Abend code AC-X'abend_code'Reason code RSC-X'reason_code'

ExplanationAn error occurred when ALCS initialization tried toload (MVS LOAD macro) the entry point DSNALI orDSNALI2 for the DB2 call attach facility (CAF). Theabend_code and reason_code are those issued by MVSLOAD.

System actionALCS continues with initialization, but cannot use DB2.


ModuleDXCSQL

DXC090E APPC/MVS initialization failed -Not enough storage


ExplanationDuring initialization ALCS was unable to obtain thestorage required to support Advanced Program-to-Program Communications/MVS (APPC/MVS) calls.

System actionALCS continues without the APPC/MVS facility.


ModuleDXCCOLF

DXC091E APPC/MVS initialization failed -Not enough SQA storage

ExplanationDuring initialization ALCS was unable to obtainthe MVS system queue area ( SQA ) storagerequired to support Advanced Program-to-ProgramCommunications/MVS (APPC/MVS) calls.


User responseIncrease the SQA storage allocation (sub-pool 245).

ModuleDXCCOLF

DXC092E APPC/MVS join failed - Returncodes RC1-X'join_return_code'RC2-X'XCF_return_code' RC3-X'XCF_reason_code'

ExplanationDuring initialization ALCS was unable to join theXCF group used by Advanced Program-to-ProgramCommunications/MVS (APPC/MVS).


Problem determinationSee MVS Application Development: Authorized CallableServices for details of the return and reason codes.

ModuleDXCCOLF

DXC093W APPC/MVS identify failed - Returncode RC-X'return_code'

ExplanationDuring initialization ALCS was unable to identifyitself as an Advanced Program-to-ProgramCommunications/MVS (APPC/MVS) scheduler.

System actionALCS continues processing normally.

User responseIf APPC/MVS is inactive, start it. Otherwise check yourAPPCPMxx parmlib member; if this is correct ask yoursystem programmer to inform your IBM programmingsupport representative.

Problem determinationSee MVS Application Development: Authorized CallableServices for details of the return code. The mostcommon return codes are:

X'08'APPC/MVS has found that the APPCPMxx parmlibmember specifies no LU names that are controlledby the transaction scheduler

X'10'The scheduler name is already in use by someother address space

X'2C'APPC/MVS is not active.

ModuleDXCCOLF

DXC103T Invalid system configuration tableTN-table_name

ExplanationDuring initialization, the system configuration tabletable_name has been loaded, but it is not in the correctformat.



User responseCheck that the system configuration table is correctlygenerated and that the correct table name is specified.

ModuleDXCINT

DXC104T Initialization failed - Availablestorage NR-'valueK' minimumrequired NR2-'valueK'

ExplanationALCS does not have enough storage to page fix thestorage that needs to be page fixed.


User responseIncrease the storage allocation for the region. If yourVFA buffers are above the bar then enough virtual andreal storage must be available. (See the descriptionof the SCTGEN macro AMODE64 parameter in ALCSInstallation and Customization). You must define thez/OS MEMLIMIT for ALCS. The default of MEMLIMITis 0, which means no storage above the bar can beallocated.

ModuleDXCINT

DXC106T Initialization failed - Returncode RC-'return_code' from userinitialization routine

ExplanationThe user-written installation-wide initialization exitroutine, USRINIT, returned a non-zero value ingeneral register 15 (the return code). Return_code isthe value (decimal) that USRINIT returned in generalregister 15. ALCS initialization treats any non-zeroreturn code as a terminating error.


Problem determinationRefer to user-written documentation about the user-written initialization exit routine for information aboutthe meaning of the return code.

ModuleDXCINT

DXC107T Can not read system configurationtable TN-'table_name' - Abendcode AC-X'abend_code' Reasoncode RSC-X'reason_code'

ExplanationAn error occurred when ALCS initialization tried toread (MVS LOAD macro) the system configuration tabletable_name.



ModuleDXCINT

DXC108T Initialization failed - Parameterformat invalid

ExplanationThe format of the ALCS parameters is invalid, forexample:

There are too many parametersOne or more parameters exceed 8 charactersThe character that separates the parameters is nota comma.

The parameter_name parameter of the job controlEXEC statement specifies the ALCS parameters.


ModuleDXCINT

DXC109T Initialization failed - Invalid TCBcount parameter

ExplanationThe task control block ( TCB ) count(s) in the ALCSparameters is or are invalid. The TCB count(s) must bein the format nnn or nnn-mmm, and must have a value


in the range 1 through 32, whereby nnn is less thanor equal to mmm. The parameter_name parameterof the job control EXEC statement specifies the ALCSparameters.


ModuleDXCINT

DXC110R Standby state - Reply withrequired system state (RESTORE,IDLE, CRAS, MESW, or NORM) orCANCEL

ExplanationThe ALCS system is in standby state. ALCS allowsmore than one ALCS job to start. One of these is theprime (also called active) ALCS. The other ALCSs arealternate (also called standby) ALCSs. The prime ALCSprocesses transactions.

Alternate ALCSs wait (MVS long wait) until the primeALCS terminates. When the prime ALCS terminates,one of the alternate ALCSs can take over. That ALCSthen becomes the prime.

All ALCSs (prime and alternate) issue this message.Reply to only one of them; that ALCS then becomes theprime. It completes initialization and starts to processtransactions. Do not reply to any other at this time; theremaining ALCSs are alternates.

If the prime terminates then reply to message numberDXC110R for one of the alternate ALCSs; that ALCSthen becomes the prime.

ALCS Operation and Maintenance describes prime andalternate ALCSs and standby state in more detail.

System actionALCS waits for a reply to the message.

Operator responseIf this message is for an alternate ALCS, then do notreply until the prime ALCS terminates. Otherwise replywith one of:

IDLE or IALCS completes initialization and proceeds directlyto IDLE state.

CRAS or CALCS completes initialization and proceeds directlyto CRAS state.

MESW or MALCS completes initialization and proceeds directlyto MESW state.

NORM or NALCS completes initialization and proceeds directlyto NORM state. ALCS accepts U as a synonym forthis reply.

RESTORE or RALCS completes initialization and proceeds to IDLEstate. Long Term pool records are dispensed fromPDAR first.

CANCELALCS terminates immediately. It does notcomplete initialization.

ALCS Operation and Maintenance describes the ALCSsystem states: IDLE, CRAS, MESW, and NORM .

ModuleDXCINT

DXC111I Cancel request accepted

ExplanationThe operator reply to message number DXC110R wasCANCEL.

System actionALCS terminates immediately. It does not completeinitialization.

ModuleDXCINT

DXC112R Can not obtain exclusive controlfor database - Reply U to proceed

ExplanationThe operator replied to message number DXC110R,but ALCS detected that another ALCS is using thedatabase. This can be because, for example:

The reply to message number DXC110R wasa mistake. The other (prime) ALCS is correctlyprocessing transactions.The reply to message number DXC110R wascorrect. The other ALCS is no longer processingtransactions but cannot terminate correctly.

ALCS Operation and Maintenance describes prime andalternate ALCSs.



Operator responseIf the reply to message number DXC110R wasa mistake, then do not reply U. Instead, reply N(actually, any reply other than U will do). ALCS returnsto standby; that is, it reissues message numberDXC110R.

If the reply to message number DXC110R wascorrect, then reply U. ALCS completes initialization andproceeds directly to the requested state (the reply tomessage number DXC110R).

Attention an incorrect reply U to this message cancause database corruption.

ModuleDXCINT

DXC113E Reply invalid - Ignored

ExplanationThe operator reply to message number DXC110R wasinvalid.

System actionALCS ignores the reply and reissues message numberDXC110R.

User responseRespond to DXC110R with one of:

IDLE or IALCS completes initialization and proceeds directlyto IDLE state.

CRAS or CALCS completes initialization and proceeds directlyto CRAS state.

MESW or MALCS completes initialization and proceeds directlyto MESW state.

RESTORE or RALCS completes initialization then continues toIDLE state. Long term pool records will bedispensed from PDAR first.

NORM or NALCS completes initialization and proceeds directlyto NORM state. ALCS accepts U as a synonym forthis reply.

CANCELALCS terminates immediately. It does notcomplete initialization.

ModuleDXCINT

DXC114I Initialization complete

ExplanationALCS initialization is complete.

System actionALCS proceeds to the requested system state (thereply to message number DXC110R) and starts toprocess transactions.

ModuleDXCINT

DXC115T Initialization failed -- Databasealready in use by another ALCSsystem

ExplanationYou have attempted to start an ALCS system but one ormore of the data sets you require is already in use byanother ALCS system.


User responseIdentify the ALCS system which is using your data sets,and if necessary terminate that system before retryingyour own.

ModuleDXCINT

DXC116D Can not obtain exclusive controlfor database - ALCS takeover isnow waiting - Reply C to canceltakeover

ExplanationThe alternate ALCS is enabled for automatic systemtakeover. It continues to check the status of theALCS database every second until the prime ALCS


terminates. When the prime ALCS terminates, thisalternate ALCS can take over immediately.

ALCS Operation and Maintenance describes prime andalternate ALCSs and standby state in more detail.

Only reply to this message if you want to cancel thealternate ALCS job. System action: The alternate ALCSchecks the status of the ALCS database every second.When the prime ALCS terminates, the alternateALCS automatically commences state change to therequired system state and the outstanding reply isdeleted.

Operator responseOnly reply if the alternate ALCS must be cancelled.

ModuleDXCINT

DXC117T Initialization failed - Another ALCStakeover is waiting

ExplanationOnly one alternate ALCS enabled for automatic systemtakeover is allowed.


ModuleDXCINT

DXC120I Log on OK

ExplanationYou have successfully logged on to ALCS.

DXC121I Log on OK - Password changed

ExplanationYou have successfully logged on to ALCS and changedyour password.

DXC122E You must enter your newpassword twice

ExplanationYou attempted to change your logon password, butyou only provided one copy of the new password.

User responseRetry with two copies of the new password.

DXC123E New password copies differ

ExplanationYou attempted to change your logon password, but thetwo copies of the new password are not the same.

User responseRetry with two identical copies of the new password.

DXC124E Access denied - Unable to verify

ExplanationYou attempted to log on to ALCS, but ALCS cannotdetermine whether or not you are authorized to log on.

User responseContact the person in your organization who hasresponsibility for allocating user IDs and so on. Thisperson may be called your security coordinator, yoursystem programmer, or may have some other title.

DXC125E Access denied - ALCS error

ExplanationThere is an error in the ALCS logon processing.

User responseThis should not occur. If it does, ask your systemprogrammer to contact your IBM programming servicerepresentative.

DXC126E Your password has expired - Youmust change it now

ExplanationYou attempted to log on to ALCS, but your password isexpired.

User responseYou must change your password before you cancomplete this logon. To do so, you must supply youruser ID, your existing password, and two copies ofyour new password. The way you do this depends onthe type of terminal equipment you are using.

DXC127E New password invalid - Try again


ExplanationYou attempted to change your password, but the newpassword that you provided is invalid.

User responseRetry with a different new password. If the problempersists, check the rules that your installation imposeson the selection of passwords. To do this, you mayneed to contact the person in your organization whohas responsibility for allocating user IDs and so on.This person may be called your security coordinator,your system programmer, or may have some othertitle.

DXC128E Access denied - User revoked

ExplanationYou attempted to log on to ALCS, but the user ID yousupplied has been revoked.

User responseIf you believe you should be authorized to access thesystem, then contact the person in your organizationwho has responsibility for allocating user IDs andso on. This person may be called your securitycoordinator, your system programmer, or may havesome other title.

DXC129E Access denied to this ALCS

ExplanationYou attempted to log on to ALCS, but the user ID yousupplied is not authorized to access this ALCS system(it may be authorized to access other facilities).

User responseIf you believe you should be authorized to access thesystem, then contact the person in your organizationwho has responsibility for allocating user IDs andso on. This person may be called your securitycoordinator, your system programmer, or may havesome other title.

DXC130E Access denied

ExplanationYou attempted to log on to ALCS, but the user ID andpassword you supplied do not authorize you to accessthe system.

User responseIt is possible that you entered your user ID orpassword incorrectly. Retry the logon, taking care toenter your user ID and password correctly.

If the problem persists, and you believe you shouldbe authorized to access the system, then contact theperson in your organization who has responsibilityfor allocating user IDs and so on. This person maybe called your security coordinator, your systemprogrammer, or may have some other title.

DXC131R Please enter your logon details:

ExplanationThis message is part of the ALCS logon prompt displayfor IBM 3270 and compatible terminals.

User responseComplete the user-ID field (unless it already showsyour user ID) and the password field and press Enter.Alternatively (to terminate the SNA session with ALCS)press PF3 or Enter 'LOGOFF' in the user-ID field andpress Enter.

DXC132R To change your password, enteryour new password twice:

ExplanationThis message is part of the ALCS logon prompt displayfor IBM 3270 and compatible terminals.

User responseIf you want to change your password, enter the newpassword in both the new-password input fields andpress Enter. Alternatively (to leave your passwordunchanged) do not enter anything in either of the new-password input fields.

DXC133E You must supply your user ID andpassword

ExplanationYou press Enter at the ALCS logon prompt displaywithout first completing the user-ID and passwordinput fields.

User responseComplete the user-ID field and the password fieldand press Enter. Alternatively (to terminate the SNAsession with ALCS) press PF3 or Enter 'LOGOFF' in theuser-ID field and press Enter.


DXC134E You must supply your password

ExplanationYou press Enter at the ALCS logon prompt displaywithout first completing the password input field.

User responseComplete the password field and press Enter.Alternatively (to terminate the SNA session with ALCS)press PF3 or Enter 'LOGOFF' in the user-ID field andpress Enter.

DXC135I Log on OK - PWE-'pwe' days topassword expiry

ExplanationYou have successfully logged-on to ALCS. Thepassword you used will expire in pwe days.

DXC136E Access denied to CT-'cras_type'CRAS

ExplanationYou attempted to log on to an ALCS CRAS, but the userID you supplied is not authorized to use this CRAS (itmay be authorized to use other terminals).

User responseIf you believe you should be authorized to use thisCRAS, then contact the person in your organizationwho has responsibility for allocating user IDs andso on. This person may be called your securitycoordinator, your system programmer, or may havesome other title.

DXC137E Unable to access ALCSAUTHprofiles - Return code RC-X'rc'Reason code RSC-X'rsn'

ExplanationALCS was unable to access the profiles in theALCSAUTH class.

System actionALCS will not check authority to access the resourcesthat these profiles protect. In general this means thatALCS will allow access to the resources.

System programmer responseEnsure that your external security manager (forexample, RACF®) is active. If you intend to protect

resources with profiles in the ALCSAUTH class, ensurethat the ALCSAUTH class is defined and active.

Problem determinationThe RACF return code (rc) and RACF reason code(rsn) are the values returned by the RACROUTEREQUEST=LIST macro. See External Security Interface(RACF) Macro Reference.

DXC138E RACF Callable Services entry pointload failed - Abend code AC -x'abend_code' and Reason codeRSC - x'reason_code

ExplanationDuring initialization, an error occurred when ALCS triedto load (MVS LOAD macro) the ESM callable servicesentry point - IRRSEQ00 for GSAFC macro calls. Theabend code and reason code are issued by MVS LOAD.

System actionALCS continues with initialization, but any GSAFCmacro call will fail with a ctl-000156.

System programmer responseMVS System Codes lists LOAD abend and reasoncodes.

Module:DXCSAF

DXC140E ENF initialization failed - Notenough SQA storage

ExplanationDuring initialization, ALCS was unable to obtain thestorage required for the MVS event notification facility.ALCS uses the MVS event notification facility tosupport its PDU facility.

System actionALCS continues with initialization but cannot use theMVS event notification facility.

System programmer responseAllocate more storage to the ALCS job or started task.

ModuleDXCENF

DXC141E Invalid ENF event code number


ExplanationALCS detected an invalid event code in its user exit forthe MVS event notification facility. ALCS uses the MVSevent notification facility to support its PDU facility.

System actionALCS ignores the event completion.

System programmer responseContact your IBM programming representative.

ModuleDXCENF

DXC162T DASD initialization failed - Notenough storage

ExplanationALCS requires storage temporarily during DASDinitialization. It issues the MVS GETMAIN macro toobtain this storage. There was not enough storage forMVS to satisfy the GETMAIN.


User responseIncrease the storage allocation for the region.

ModuleDXCINTD

DXC160W CDS copy 1 and copy 2 do notmatch - Using most recent copy c

ExplanationThis message occurs when ALCS reads the DASDconfiguration data set during restart, and one copy ofthe data set is more recent than the other.

This is not necessarily an error. It can indicate that onecopy of the configuration data set was offline whenZDASD LOAD/CONFIRM/COMMIT was done and ALCSwas restarted without varying the other copy online.

System actionALCS closes the older copy of the configuration dataset and continues processing normally.

Operator responseUse ZDASD VARY,ONLINE to make the other copy ofthe configuration data set available to ALCS if required.

ModuleDXCINTT

DXC161W DASD table name on startupparameters TN1-'name1' doesnot match name in CDSTN2-'name2'

ExplanationThis message occurs when ALCS reads the DASDconfiguration data set during restart, and the DASDtable name in the configuration data set does notmatch the DASD table name specified on the ALCSstartup parameters.

This is not necessarily an error. For example, it mayreflect your normal operating procedure for runningALCS test systems.

If you specify an old version of the DASD table on theALCS job it can have the following effects:

• If the database has been expanded, ALCS will haveto allocate some data sets after STANDBY statewhich can slow down restart.

• If general files have been deleted or renamed laterthen ALCS will not apply these changes.

• If extended configuration data sets CDS1 and CDS2have been added later then ALCS will not use them.

System actionALCS uses the information in the configuration data setand continues processing normally.

Operator responseUpdate the ALCS job to specify the most recent DASDtable name if required.

ModuleDXCINTT

DXC163T Can not read DASD configurationtable TN-'name' - Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'


ExplanationALCS was unable to load the DASD configurationmodule name, the MVS LOAD request for this loadmodule failed.


Problem determinationMVS System Codes lists LOAD abend and reason codes.

ModuleDXCINTD

DXC164T Can not continue - Not enoughdata sets available for database

ExplanationALCS could not access any copy of one or moredatabase data sets. ALCS requires at least one copy ofeach database data set. If the database is duplicated,there are two copies of each database data set; atleast one copy of each must be available. If thedatabase is not duplicated there is only one copy ofeach database data set, so every data set must beavailable.


User responseCheck why the datasets are not available, correct theerror, and restart ALCS.

ModuleDXCINTD

DXC165W DYNALLOC (A) Return code0 Error code EC-X'error_code'DSN-'data_set_name'

ExplanationAn attention condition occurred when ALCS attemptedto allocate a database data set using the MVSDYNALLOC (SVC 99), dsname allocation function. ALCSwas able to allocate the data set. Error_code is theinformation reason code from DYNALLOC.

System actionALCS processing continues. The data set is available toALCS.

Problem determinationMVS Authorized Assembler Services Guide listsDYNALLOC (SVC 99) information reason codes.

ModuleDXCINTD, DXCDAI

DXC166E FN-'function' Return code RC-X'return_code' EC-X'error_code'DSN-'data_set_name'

ExplanationAn error occurred when ALCS attempted to allocatethe database data set data_set_name. ALCS was notable to allocate the data set.

Function is the function that detected the error, one of:CATALOG QUERY

MVS partitioned data set extended ( PDSE )serialization protocol interlock, catalog queryfunction. See the associated IGWnnnn message inthe MVS console.

CATLG CONNECTMVS media manager services (MMSERV) connectfor the data set.

Return_code is the return code from MMSERVconnect. Error_code is 0. Usually there is anassociated message giving more details. Forexample, messages from the resource accesscontrol facility ( RACF ) for unauthorized access tothe data set.

CI SIZE CHECKALCS checks the control interval size against thecontrol interval sizes that the ALCS generationspecifies.

Return_code is 8, indicates that the control intervalsize does not match the control interval sizespecified in the generation. Error_code is the actualcontrol interval size.

DASD CB BUILDMVS MMINIT macro (media manager INITfunction).

Return_code is the return code from MMINIT.Error_code is 0.

DASD CB FIXMVS PGSER macro to page fix storage for ALCScontrol blocks associated with the data set.


Return_code is the return code from PGSER.Error_code is 0.

DASD CB OBTAINMVS GETMAIN macro to obtain storage for ALCScontrol blocks associated with the data set.

Return_code is the return code from GETMAIN.Error_code is 0.

DEVTYPEMVS DFP DEVTYPE macro.

Return_code is the DEVTYPE return code.

DS EXTENT CHECKALCS checks that the data set is a single extentdata set.

Return_code is 4 indicates a multiple extent dataset.

DS SIZE CHECKALCS checks the number of records against thenumber that the ALCS DASD generation specifies.

Return_code is 4, indicates that the number ofrecords in the data set is less than the number thatthe generation specifies. Error_code is 0.

DYNALLOC (A)MVS DYNALLOC macro (SVC 99), dsnameallocation function.

Return_code is the return code from DYNALLOC.Error_code is the error reason code fromDYNALLOC.

GETMAIN ERRORMVS GETMAIN macro and PGSER macro to obtainand page fix buffer storage for copying recordsfrom one data set copy to another.

MVS could not satisfy these requests. Return_codeis a reason code associated with the error.Error_code is a system completion code thatidentifies the error.

VTOC SEARCHMVS CVAFDIR macro to search the volume table ofcontents ( VTOC ) for the data set.

Return_code is the return code from CVAFDIR.Error_code is the CVSTAT code from CVAFDIR.

System actionALCS processing continues. The data set is notavailable to ALCS.

Problem determinationMVS Authorized Assembler Services Guide listsDYNALLOC (SVC 99) error reason codes and returncodes from GETMAIN, and PGSER.

MVS/DFP: System Programming Reference listsCVAFDIR return codes and CVSTAT codes. MVS/DFPMedia Manager Diagnosis Guide and Referencecontains information about media manager and mediamanager services. MVS System Codes lists systemcompletion codes and associated reason codes.


DXC167I Data set DSN-'data_set_name'allocated

ExplanationALCS successfully allocated the data set.



DXC168I Data set DSN-'data_set_name'copy complete

ExplanationALCS successfully copied all records to this databasedata set.


ModuleDXCDAI

DXC169E Data set DSN-'data_set_name'copy failed

ExplanationALCS was unable to copy records from this databasedata set.

Probably caused by a hardware error. You will receivethis message if you vary off a data set which is still inthe process of being copied up following a vary on. Inthis case you can ignore this message.


System actionALCS deallocates the data set, then it continuesprocessing. The data set is not available to ALCS.

User responseTry again with a new data set, and get the unitserviced. If this is an isolated instance, follow yournormal procedure for a non-urgent problem. If ithappens repeatedly, inform your system programmer.

Problem determinationNormally preceded by another message, usually an I/Oerror message. Act as appropriate for this precedingmessage.

ModuleDXCDAI

DXC170T Can not read either copy of controlrecord

ExplanationALCS could not access any copy of the data set controlrecord. ALCS uses the first record of the first size L3data set to record which data sets are online andwhich are off line. If the database is duplicated, thereare two copies of the control record; at least one copymust be available. If the database is not duplicated,there is only one copy of the control record; it must beavailable.

System actionALCS issues message number DXC164T, and thenterminates abnormally.

User responseCheck why the datasets are not available, correct theerror, and restart ALCS.

ModuleDXCINTD

DXC171W PDAR dispensing stopped for LTL'n' - 'stopping reason'

ExplanationALCS detected a reason to stop dispensing long termpool record size n from the PDAR structure.

System actionPool record size n dispensing proceeds with the ALCSstandard mechanism. The PDAR structure is ignored.

User responseThis is a normal message if the PDAR reserved recordsare exhausted. For any other reason the cause mustbe investigated and the PDAR structure must be re-created.

ModuleDXCGFR

DXC172E GETMAIN error - Can not obtainwork block for DASD termination

ExplanationALCS requires storage temporarily during DASDtermination. It issues the MVS GETMAIN macro toobtain this storage. There was not enough storage forMVS to satisfy the GETMAIN.

System actionALCS proceeds with job termination.

User responseThe user can usually safely ignore this message. If thisis an isolated instance, follow your normal procedurefor a non-urgent problem. If it happens repeatedly,inform your system programmer.

ModuleDXCTRMD

DXC173I PDAR dispensing started for LT L'n'

ExplanationALCSdetected the restore state parameter atinitialization and started dispensing long term poolrecord size n from the PDAR structure.

System actionPool record size n is dispensed from the PDARstructure.

ModuleDXCINTG

DXC174E PDAR initialization failed for LT L'n'- 'failing reason'


ExplanationALCS detected the restore state parameter atinitialization but failed to start dispensing long termpool record size n from the PDAR structure.

System actionPool record size n dispensing proceeds with the ALCSstandard mechanism. The PDAR structure is ignored.

User responseThe cause must be investigated and the PDARstructure must be re-created.

ModuleDXCINTG

DXC175W DYNALLOC (U) Return code0 Error code EC-X'error_code'DSN-'data_set_name'

ExplanationAn attention condition occurred when ALCS attemptedto deallocate a database data set using the MVSDYNALLOC (SVC 99), dsname deallocation function.ALCS was able to deallocate the data set. Error_codeis the information reason code from DYNALLOC.

System actionALCS processing continues. The data set is notavailable to ALCS.

Problem determinationMVS Authorized Assembler Services Guide listsDYNALLOC (SVC 99) information reason codes.

ModuleDXCINTD, DXCDAI, DXCTRMD

DXC176E FN-'function' Return code RC-X'return_code' EC-X'error_code'DSN-'data_set_name'

ExplanationAn error occurred when ALCS attempted to deallocatethe database data set data_set_name. ALCS was notable to deallocate the data set.

Function is the function that detected the error, one of:

DYNALLOC (U)MVS DYNALLOC macro (SVC 99), dynamicdeallocate function.

Return_code is the return code from DYNALLOC.Error_code is the error reason code fromDYNALLOC.

CATLG DISCONNECTMVS media manager services (MMSERV) disconnectfor the data set.

Return_code is the return code from MMSERVdisconnect. Error_code is 0. Usually there is anassociated message giving more details.

INVALID ADSDAn ALCS control block associated with the data setis corrupted.

Return_code is 16. Error_code is 0.

If this error occurs, ask your system programmerto inform your IBM programming supportrepresentative.

System actionALCS processing continues. ALCS cannot determinethe data set status, it does not use the data set.

Problem determinationMVS Authorized Assembler Services Guide listsDYNALLOC (SVC 99) error reason codes.

MVS/DFP Media Manager Diagnosis Guide andReference contains information about media managerservices.

ModuleDXCINTD, DXCDAI, DXCTRMD

DXC177I Data set DSN-'data_set_name'deallocated

ExplanationALCS successfully deallocated the data set.

System actionALCS processing continues. The data set is no longeravailable to ALCS.



DXC179T Test data set FN-'PUT' Returncode RC-'return_code' Reason codeRC-'reason_code'

ExplanationAn error occurred when ALCS was writing to the testdata set. Return_code and reason_code are the returncode and reason code from the VSAM PUT macro.


Problem determinationMVS/DFP: Macro Instructions for Data Sets lists VSAMmacro return codes and reason codes.

ModuleDXCTDB

DXC180T Initialization failed - Test dataset FN-'function' Return codeRC-'return_code' Reason codeRSC-X'reason_code'

ExplanationAn error occurred when ALCS was preparing to usethe test data set. ALCS uses the test data set whenthe parameter_name parameter of the job controlEXEC statement specifies TEST. In this case, the jobcontrol statements that initiate ALCS must include aDD statement for the test data set. The DDNAME isDXCTEST. Function is the function that detected theerror, one of:

VSAM OPENThe VSAM OPEN macro completed with a returncode greater than 4.

Return_code is the return code from OPEN.

Reason_code is the reason code from OPEN.

DATA-SET CHECKFollowing OPEN, ALCS detected that the test dataset characteristics are invalid.

Return_code is 8.

Reason_code is one of:

04The key displacement is not 4.

08The key length is not 4.

0CThe maximum logical record length is less thanthe largest ALCS control interval ( CI ) size.

INITIAL PUTFollowing OPEN, ALCS detected that the test dataset was empty. To allow direct access to thedata set, ALCS writes (VSAM PUT macro) a singlerecord that is eight bytes of binary zeros. This PUTcompleted with a non-zero return code.

Return_code is the return code from PUT.

Reason_code is the reason code from PUT. This isnot meaningful when return_code is 4.

SIGNATURE GETFollowing OPEN, ALCS attempted to read asignature record from the test data set to checkthat the test data set is at a compatible level. TheVSAM GET failed.

Return_code is the return code from VSAM GET.

Reason_code is the reason code from VSAM GET.

SIGNATURE CHECKALCS determined that the test data set isincompatible with the current version of ALCS.

Return_code is 8.

Reason_code is one of:

04The signature record length is incorrect.

08The ALCS version/release/modification level inthe signature record is not compatible with thecurrent ALCS.



ModuleDXCTDB

DXC181E Test data set FN-'function' Returncode RC-'return_code' Reason codeRSC-X'reason_code'

ExplanationAn error occurred when ALCS was accessing the testdata set. Function is the name of the VSAM macro(GET or PUT) that detected the error. Return_code is


the return code from the macro. Reason_code is thereason code from the macro.

System actionALCS processing continues as for an uncorrectable I/Oerror.


ModuleDXCTDB

DXC182W Test data set FN-'function' Returncode RC-'return_code' Reason codeRSC-X'reason_code'

ExplanationA severity 4 (Attention) error condition occurred whenALCS was accessing the test data set. Function is oneof:

VSAM OPENThe VSAM OPEN macro completed with a returncode of 4.

Return_code is the return code from OPEN (4).

Reason_code is the reason code from OPEN.

VSAM CLOSEThe VSAM CLOSE macro completed with a non-zeroreturn code.

Return_code is the return code from CLOSE.

Reason_code is the reason code from CLOSE.

System actionALCS ignores the error condition and continuesprocessing.


ModuleDXCTDB

DXC183I Configuration data set initialized

ExplanationThis message occurs immediately after allocating anew configuration data set as part of the migrationto ALCS V2.4.1. It copies the initial data from theconfiguration tables to the configuration data set. Thismessage should only occur once during the lifetime ofthe configuration data set.


Operator responseIf this message occurs frequently, inform your systemprogrammer.

ModuleDXCINTT

DXC184T Configuration data set cannot beaccessed

ExplanationThe configuration data set is corrupted or unavailable.If an offset value is given, the error was detected inmodule DXCINTT at the stated offset. If the offsetvalue is zero the error was detected in moduleDXCINTD and could indicate that you are running witha test data set and both configuration data sets needpreformatting.


Operator responseCheck that at least one configuration data set isallocated. If it is newly allocated ensure that thefirst time it is used you are not using a test dataset. If an offset value is given, the configuration dataset is probably corrupted and you should considerrestoring it from a previous backup. If the problempersists contact your IBM programming supportrepresentative.

ModuleDXCINTD, DXCINTT

DXC185I Data set DSN-'data_set_name'Preformat started


ExplanationThis message provides information on an ALCSprocess. The Operator does not need to respond to themessage. The process may take several minutes for alarge data set.


ModuleDXCINTD

DXC186I Data set DSN-'data_set_name'Preformat complete

ExplanationThis message provides information on an ALCSprocess. The Operator does not need to respond to themessage.


ModuleDXCINTD, DXCDAV

DXC187T No memory available for DASDtables -- DXCINTT offset nnnn

ExplanationThere is not enough memory allocated to ALCS for theDASD tables.


System programmer responseCheck that you have coded the SCTGEN macrocorrectly. If you have then you should liaise withyour MVS System Programmer to obtain more memorybefore starting ALCS again.

ModuleDXCINTD

DXC188W Invalid item ignored in DASDconfig - Action data X'action

ExplanationThere is a problem with some information in the DASDtables.

System actionThis message is sent to the MVS log. ALCS ignores theerror and continues to create the DASD tables.

ModuleDXCINTT

DXC189T Configuration data set cannot beinitialized -- not initial config


System programmer responseRerun the job using a new configuration.

ModuleDXCINTT

DXC190W Can not determine 3270 displaysize for CRN-'crn' Return code RC-X'rr' FDBK2 FB2-X'ff '

ExplanationALCS has detected a non-zero return code or a non-zero feedback code from VTAM after issuing a Sendrequest to find out the display size for a VTAM terminalwith CRN crn.

rrVTAM return code

ffVTAM feedback 2 code

System actionALCS uses a default display size of 24 rows x 80columns for this terminal.

Operator responseAsk your network operator to investigate the relevantterminal for possible malfunction.


Problem determinationVTAM Programming and VTAM Reference Summary forthe installed version and release of VTAM describethese return codes and feedback 2 codes.

ModuleDXCCOM3

DXC191E NetView user ID CRN-crn notauthorized- Entry cannot beprocessed

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationspecified a Tivoli® NetView communication resourceuser ID that is not authorized.

System actionThe communication table is not set up correctly forthis resource. ALCS proceeds with the next request.

System programmer responseEnsure that your external security manager (forexample, RACF) is active, and ensure that the defaultuser ID is defined in the USER class. If you have anapplication profile for ALCS defined in the APPL class,ensure that the default user ID has READ access tothe profile. If you have a NOLOG profile defined in theALCSAUTH class, ensure that the default user ID hasREAD access to the profile. If the resource is a CRAS,and if you have a corresponding CRAS profile definedin the ALCSAUTH class, ensure that the default user IDhas READ access to the profile.

ModuleDXCCOMU

DXC192T Can not read communication loadlist MODN-'name' Abend code AC-X'abend_code' Reason code RSC-X'reason_code'

ExplanationAn error occurred when ALCS tried to read (MVS LOADmacro) the name communication load list.



ModuleDXCINTC, DXCOCTM

DXC193T Invalid communication load listMODN-'name'

ExplanationDuring ALCS communication table build, the namecommunication load list has been loaded but it is notin the correct format for a communication load list.


Problem determinationCheck that the communication load list is correctlygenerated and that the correct load list name isspecified.


DXC194E Resource CRN-'crn' default userID table full - Entry cannot beprocessed

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationspecified a default user ID that ALCS could not processbecause the default user-ID table is full. The defaultuser-ID table can hold up to 255 different defaultuser-IDs.


System programmer responseReview your use of default user IDs. ALCS supports amaximum of 255 different default user IDs.

ModuleDXCCOMU


DXC195E Resource CRN-'crn' default userID table full - Reset to force logon

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationspecified a default user ID that ALCS could not processbecause the default user-ID table is full. The defaultuser-ID table can hold up to 255 different default userIDs.

System actionThe communication table entry for this resource isreset to show that the end-user must log on beforethey can use the resource.

System programmer responseReview your use of default user IDs. ALCS supports amaximum of 255 different default user IDs.

ModuleDXCCOMU

DXC196E Resource CRN-'crn' default userID not authorized - Entry cannotbe processed

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationspecified a default user ID that is not authorized.



ModuleDXCCOMU

DXC197E Resource CRN-'crn' default userID not authorized - Reset to forcelogon

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationspecified a default user ID that is not authorized.

System actionThe communication table entry for this resource isreset to show that the end-user must log on beforethey can use the resource.


ModuleDXCCOMU

DXC198E GETMAIN error - Can not obtainstorage for TCPIP resourceCRN-'crn'

ExplanationDuring initialization, ALCS cannot obtain enoughstorage to build the communication table for a TCP/IPresource.

System actionALCS terminates with an abnormal completion code.

User responseRestart ALCS with a larger region size for the job.

ModuleDXCSOCO


DXC199E GETMAIN error - Can notobtain storage for APPC resourceCRN-'crn'

ExplanationDuring initialization, ALCS cannot obtain enoughstorage to build the communication table for an APPCresource.



ModuleDXCCOLH

DXC200R Open VTAM ACB LUN-'acbname'failed, Return code RC-X'return_code' - Reply U to retry, orC to cancel

ExplanationALCS cannot contact VTAM prior to initializing thecommunication network. Return_code is the accessmethod control block ( ACB ) error return code.


Operator responseReply with one of:

UDetermine why ALCS cannot contact VTAM, correctthe problem, then reply U. ALCS tries again tocontact VTAM. If it fails then ALCS reissues thismessage.

C or CANCELIf you are unable to determine why ALCS cannotcontact VTAM, or you cannot correct the problem,then reply C or CANCEL. ALCS ends abnormally.

Problem determinationVTAM Programming for the installed version andrelease of VTAM explains return_code.

ModuleDXCINTC

DXC201W CRAS CT-'cras_type' CRI-'cri'CRN-'crn' not available -Return code RC-X'rr' FB2-X'ff' SC-X'ssmmuuuu'

ExplanationDuring initialization of the communication network,ALCS cannot acquire the CRAS with CRI cri and CRNcrn. ALCS has detected a non-zero return code or non-zero feedback code from VTAM, where:

rrVTAM return code


ssSystem sense

mmSystem sense modifier

uuuuUser sense.

System actionALCS proceeds with the next CRAS.

Problem determinationVTAM Programming and VTAM Reference Summary forthe installed version and release of VTAM describethese return codes, feedback 2 codes, and sense data.

ModuleDXCINTC

DXC203T Initialization failed - No VTAMnetwork available - Return codeRC-X'rr' FDBK2 FB2-X'ff'

ExplanationALCS cannot start the VTAM communication network.ALCS has detected a non-zero return code or non-zerofeedback code from VTAM, where:

rrVTAM return code






DXC204A VTAM operator has issued halt- Halt ALCS with 'ZASYS HALT'command

ExplanationThe VTAM operator has halted the VTAMcommunication network. VTAM cannot completetermination until all sessions with ALCS areterminated.

System actionALCS processing continues. ALCS sends messageDXC2554A to RO CRAS (see “DXC2554A” on page156).

Operator responseHalt ALCS as soon as possible.

ModuleDXCCOME

DXC205E Resource CRN-'crn' -- Ordinalnumber already in use

ExplanationYou have explicitly allocated an ordinal number to acrn but this ordinal number has already been used.

Programmer responseSee ALCS Installation and Customization for a fullexplanation of how ALCS allocates LDIs.

DXC209E Resource CRN-'crn' not defined -Can not be deleted or replaced

ExplanationDuring ALCS communication table build, a deleteor replace request in the communication generationrefers to a resource that is not known to ALCS.

System actionALCS does not delete or replace the resource; itproceeds with the next request.

User responseCheck that the communication resource is correctlyspecified in the communication generation. RunDXCCOMOL to verify that the communication resourcesare correctly specified and generated.

ModuleDXCCOMU

DXC210E Resource CRN-'crn' alreadydefined - Can not be added

ExplanationDuring ALCS communication table build, an addrequest in the communication generation refers to aresource that is already known to ALCS.

System actionALCS does not add the resource; it proceeds with thenext request.


ModuleDXCCOMU

DXC211E Resource CRN-'crn' is currentlyactive -- Entry can not be deletedor replaced

ExplanationDuring ALCS communication table build, a replace ordelete request in the communication generation refersto a resource that is currently active or in use byanother process.

System actionALCS does not add the resource; it proceeds with thenext request.



ModuleDXCCOMM

DXC212E Resource CRN-'crn' is a differentdevice type from replace entry -Entry cannot be replaced

ExplanationDuring ALCS communication table build, a replacerequest in the communication generation refers to aresource that is known to ALCS and is defined with adifferent device type from the entry replacing it.

System actionALCS does not replace the resource; it proceeds withthe next request.


ModuleDXCCOMU

DXC213E Resource CRN-'crn' has duplicateother-system identificationspecified - Entry cannot beprocessed

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationrefers to a resource with an other-system identification(OSID) that is already defined to ALCS.

System actionALCS does not add or replace the resource; it proceedswith the next request.

User responseCheck that the communication resource is correctlyspecified in the communication generation. Run

DXCCOMOL to verify that the communication resourcesare correctly specified and generated.

ModuleDXCCOMV

DXC214E Resource CRN-'crn' - No room inDXCRIT table to add other-systemidentification

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationrefers to a resource with an other-system identification(OSID) that is not defined to ALCS, but ALCS cannotadd the OSID into the communication DXCRIT table.


User responseCheck that the communication resources are correctlyspecified in the communication generation. TheENTRIES parameter on the COMGEN macro mayneed to be increased in the first communicationload module. Run DXCCOMOL to verify that thecommunication resources are correctly specified andgenerated. Otherwise ask your system programmer toinform your IBM programming support representative.

ModuleDXCCOMV

DXC215E Resource CRN-'crn' has duplicateHEX/TCID/IA/TA specified - Entrycannot be processed

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationrefers to a resource with an SLC-ID that is alreadydefined to ALCS.

System actionALCS does not add or replace the resource; it proceedswith the next request.




ModuleDXCCOMV

DXC216E Resource CRN-'crn' - No roomin DXCSLCTB table to add HEX/TCID/IA/TA

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationrefers to a resource with an SLC-ID that is not alreadydefined to ALCS, but ALCS cannot add the SLC-ID intothe communication DXCSLCTB table.



ModuleDXCCOMV

DXC217E Resource CRN-'crn' has duplicatename specified - Entry cannot beadded

ExplanationDuring ALCS communication table build, an addrequest in the communication generation refers to aresource with a CRN that is already defined to ALCS.




ModuleDXCCOMV

DXC218E Resource CRN-'crn' - No room intable DXCNHT to add entry

ExplanationDuring ALCS communication table build, an addrequest in the communication generation refers to aresource with a CRN that is not already defined toALCS, but ALCS cannot add the CRN because thecommunication DXCNHT table is full.



ModuleDXCCOMU

DXC219E Resource CRN-'crn' specifies anunknown terminal type

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationrefers to a resource with an unrecognized device type.

System actionALCS ignores the new resource definition; it proceedswith the next request.



ModuleDXCCOMU

DXC220E SLC link CRN-'crn' not replaced/deleted - At least one terminal stillaccessed through it

ExplanationDuring ALCS communication table build, a replace ordelete request in the communication generation refersto an SLC link that has at least one terminal accessedthrough it.

System actionALCS does not replace or delete the SLC link; itproceeds with the next request.


ModuleDXCINTC

DXC221E LU 6.1 link CRN-'crn' not found

ExplanationThe ALCS communication load module containsa communication resource specified asLDTYPE=ALCSLINK and a terminal specified asTERM=PARSESS, but the LU 6.1 link that supports thisparallel session is not known to ALCS.

System actionThe ALCS communication tables are not set upcorrectly for this resource. ALCS proceeds with thenext request.


ModuleDXCCOMV

DXC222E Resource CRN-'crn' cannot beadded to communication tables

ExplanationDuring ALCS communication table build, an addrequest in the communication generation refersto a LDI type that is not specified in the basecommunication load module. This occurs when:

A resource for which the cri is specified is of thewrong type to be added to an existing LDI .An attempt is made to add an SLC WTTY resourcewith a specified cri and the REI is greater than X'FF'.Only 255 resources may be defined for SLC andWTTY.A resource for which the cri is specified cannot beadded as the cri is already in use.There is insufficient storage available for theresource entry being added to the communicationstable.

System actionALCS ignores the new resource definition; it proceedswith the next request.

User responseCheck that all required LDI types are specifiedin the base communication generation table. RunDXCCOMOL to verify that the communication resourcesare correctly specified and generated.

ModuleDXCCOMU

DXC223E Resource crn -- Ordinal numbergreater than maximum allowed

ExplanationYou have explicitly specified an ordinal number whichis greater than that allowed by the MAXORD parameterof the COMDEF macro.

System programmer responseSee ALCS Installation and Customization for a fullexplanation of the MAXORD parameter then try again.You will need to be recreate the communication tablesagain.

DXC224T Invalid communication loadmodule MODN-'name'


ExplanationDuring ALCS communication table build, the namecommunication load module has been loaded but itis not in the correct format for a communication loadmodule.

System actionIf this error occurs during initialization, ALCS endsabnormally. Otherwise, ALCS ignores the contents ofthe load module.

User responseCheck that the communication load module(s) arecorrectly generated and that the correct load modulename(s) are specified.


DXC225T Too many resources specified

ExplanationDuring ALCS communication table build, there are somany add requests in the communication generationthat more than 256 LDI values are required to addressthem.


User responseCheck that the communication resources are correctlyspecified in the communication generation. TheENTRIES parameter on the COMGEN macro may needto be reduced in the first communication load module.Run DXCCOMOL to verify that the communicationresources are correctly specified and generated.Otherwise ask your system programmer to inform yourIBM programming support representative.

ModuleDXCINTC

DXC226T Too many SLCLINK and WTTYresources specified

ExplanationDuring ALCS communication table build, the totalnumber of SLC links and WTTY resources is more than255.


User responseCheck that the communication resources are correctlyspecified in the communication generation. TheENTRIES parameter on the COMGEN macro may needto be reduced in the first communication load module.Run DXCCOMOL to verify that the communicationresources are correctly specified and generated.Otherwise ask your system programmer to inform yourIBM programming support representative.

ModuleDXCINTC

DXC227T Unknown LDTYPE specified

ExplanationDuring ALCS communication table build,the communication load module contains acommunication resource type (LDTYPE) that ALCSdoes not recognize.

System actionIf this error occurs during initialization, ALCS endsabnormally. Otherwise, ALCS issues system error000335.

User responseCheck that the communication resources are correctlyspecified in the communication generation. RunDXCCOMOL to verify that the communication resourcesare correctly specified and generated.

ModuleDXCINTC

DXC228E SLC link CRN-'crn' not found

ExplanationThe communication load module containsa communication resource specified asLDTYPE=SLCALC, which is accessed through an SLClink that is not known to ALCS.

System actionThe communication tables are not set up correctly forthis resource. ALCS cannot access this resource. ALCSproceeds with the next request.



ModuleDXCCOMU

DXC229E ALCI LU CRN-'crn' not found

ExplanationThe communication load module containsa communication resource specified asLDTYPE=VTAMALC, which is accessed through an ALCILU that is not known to ALCS.

System actionThe communication tables are not set up correctly forthis resource. ALCS will fail when trying to access thisresource. ALCS proceeds with the next request.


ModuleDXCCOMU

DXC230T Can not read communicationload module MODN-'name'- Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

ExplanationAn error occurred when ALCS tried to read (MVS LOADmacro) the name communication load module.

System actionIf this error occurs during initialization, ALCS endsabnormally. Otherwise, ALCS terminates loading thecommunication load module.


ModuleDXCCOMM, DXCINTC, DXCOCTM

DXC231W Associated resource ACRN-'crn1'not found for resource CRN-'crn2'

ExplanationThe resource crn2 has an associated resource crn1specified in the communication generation but theassociated resource is not known to ALCS.

System actionALCS treats crn2 as if it had no associated device.ALCS processing continues.

User responseCheck that the communication generation contains allrequired communication resources and that they areall correctly specified. Run DXCCOMOL to verify that thecommunication tables are built correctly.

ModuleDXCCOMU

DXC232E Logical unit presentation servicesprofile NR-X'profile_number' notsupported for resource CRN-'crn'

ExplanationThe bind image, used while initiating a SNA sessionbetween ALCS and a resource, contains a logicalunit presentation services profile that ALCS does notsupport.

System actionALCS rejects the logon request.

User responseCheck that the VTAM logon mode table contains thecorrect values for the resource that is requesting asession with ALCS.

ModuleDXCCOME

DXC233I SLC line allocation - Unit addressAD-'address' Ddname DDN-'name'


ExplanationALCS has successfully allocated the SLC line withdevice address address and dynamically generatedddname name.

System actionALCS processing continues.

ModuleDXCSLCCI

DXC234I SLC line deallocation - DdnameDDN-'name'

ExplanationALCS has dynamically deallocated the SLC line with addname of name.


ModuleDXCSLCCI

DXC235W SLC line allocation failure - Unitaddress AD-'address' Error codeEC-X'error_code' Reason code RSC-X'reason_code'

ExplanationAn error occurred during the dynamic allocation ofthe SLC line with device address address. The errorand reason_code are the values returned by MVSDYNALLOC (SVC 99).


Problem determinationMVS Authorized Assembler Services Guide describesthe error and reason_code.

ModuleDXCSLCCI

DXC236W SLC line deallocation failure -Ddname DDN-'name' Error codeEC-X'error_code' Reason code RSC-X'reason_code'

ExplanationAn error occurred during the dynamic deallocation ofthe SLC line. The error and reason_code are valuesreturned by MVS DYNALLOC (SVC 99).


Problem determinationMVS Authorized Assembler Services Guide describe theerror and reason_code.

ModuleDXCSLCCI

DXC237W Device is not suitable for SLC- Ddname DDN-'name' UCBTYPUCBT-X'ucbtype_code'

ExplanationA device defined to ALCS as an SLC link is not definedto MVS as a teleprocessing communication device (forexample, an IBM 3705 Communication Controller).Ucbtype_code is the contents of the unit control block(UCB) device type field (UCBTYP) of the MVS UCB.


User responseCheck that the ALCS communication generationspecifies the correct unit addresses for the SLC link.If it does, then check that the MVS I/O generationcorrectly specifies the device type.

Problem determinationMVS Diagnosis: Data Areas describes the UCB format,including the contents of the UCB device type field.

ModuleDXCSLCCI

DXC238W SLC line DCB open failure -Ddname DDN-'name'

ExplanationAn error occurred when trying to open an SLC line withthe dynamically allocated ddname name. ALCS cannotopen the data set control block (DCB) for this ddname.




ModuleDXCSLCCI

DXC239E Resource CRN-'crn' has duplicateLEID specified - Entry cannot beprocessed

ExplanationDuring ALCS communication table build, an addrequest in the communication generation refers to anALCI resource with an LEID that is already defined toALCS.

System actionIf this error occurs during initialization, ALCS endsabnormally. Otherwise, the communication tables arenot set up correctly for this resource and ALCSproceeds with the next request.


ModuleDXCCOMV

DXC240E Resource CRN-'crn' - No room inDXCLEID table to add LEID

ExplanationDuring ALCS communication table build, an addrequest in the communication generation refers to anALCI resource with an LEID that is not already definedto ALCS, but ALCS cannot add the LEID because thecommunication table is full.

System actionIf this error occurs during initialization, ALCS endsabnormally. Otherwise, the communication tables arenot set up correctly for this resource and ALCSproceeds with the next request.


ModuleDXCCOMV

DXC241E LU 6.1 CRN-'crn' not replaced/deleted - At least one parallelsession still defined

ExplanationDuring ALCS communication table build, a replace ordelete request in the communication generation refersto an LU 6.1 link that has at least one parallel sessionstill defined.

System actionALCS does not replace or delete the LU 6.1 link; itproceeds with the next request.


ModuleDXCCOMU

DXC242E Unable to add LDI entry forresource CRN-crn

ExplanationThis occurs when:

An attempt is made to define a resource for SLCWTTY and the specified cri does not reference theexisting SLC WTTY LDI. Only one LDI with 255resources may be defined for SLC.All LDIs are already in use, that is either no LDI waspreviously defined for this resource type or thereare no available cris.There is insufficient storage available for the REIindex table which is required for a new LDI entry.


System actionThe communication tables are not set up correctly forthis resource. ALCS proceeds with the next request.


ModuleDXCCOMU

DXC243E X.25 PVC XCRN-'crn' not found

ExplanationThe ALCS communication load module containsa communication resource specified asLDTYPE=X25ALC which is accessed through an X.25permanent virtual circuit (PVC) that is not known toALCS.

System actionThe communication tables are not set up correctly forthis resource. ALCS proceeds with the next request.


ModuleDXCCOMV

DXC244E X.25 PVC XCRN-'crn' not replaced/deleted - At least one terminal stillaccessed through it

ExplanationDuring ALCS communication table build, a replace ordelete request in the communication generation refersto an X.25 permanent virtual circuit (PVC) that has atleast one terminal accessed through it.

System actionALCS does not replace or delete the X.25 PVC; itproceeds with the next request.


ModuleDXCCOMU

DXC245E Type 2/3 X.25 PVC or MATIPBTCP/IP XCRN-'crn1' not found forSLC link CRN-'crn'

ExplanationThe communication load module containsa communication resource specified asLDTYPE=SLCLINK for a virtual SLC link that isreserved for X.25 or TCP/IP Type B use. However theassociated Type 2 or Type 3 X.25 permanent virtualcircuit (PVC), or Type B TCP/IP link, is not known toALCS.



ModuleDXCCOMU

DXC246I CRAS CRI-'cri' NetView CRN-'crn'acquired

ExplanationDuring initialization of the communication network,ALCS has acquired the cras_type CRAS with CRI cri andCRN crn. It is a NetView resource.



ModuleDXCCOMP

DXC247R Reply invalid - Reply U to retry or Cto cancel

ExplanationThe operator reply to message number DXC200R( “DXC200R” on page 30) was not one of therecognized responses.

System actionALCS ignores the reply and waits for a valid reply tomessage number DXC200R.

ModuleDXCINTC

DXC248T Can not continue - Notenough storage available forcommunication table

ExplanationDuring ALCS communication table build, not enoughstorage was available.

System actionIf this error occurs during initialization, ALCS endsabnormally. Otherwise, ALCS terminates loading thecommunication configuration table.

User responseCheck that the ENTRIES parameter is correctlydefined in the communication generation tables. RunDXCCOMOL to verify that the communication resourcesare correctly specified and generated. If these arecorrect, then increase the storage allocation for theregion.

ModuleDXCINT

DXC249T Load of communication loadmodule MODN-'name' failed -Resource CRN-'crn' in use

ExplanationDuring ALCS communication table build, a replaceor delete request in the communication generationrefers to a resource that is currently active or in

use by another process. Name is the name of thecommunication load module.

System actionThe communication tables in storage are notchanged. ALCS terminates loading the communicationconfiguration table.

User responseEnsure that communication resources to be updatedare all inactive before retrying the load.

ModuleDXCCOMM

DXC250T ALCS system failure - SERRC-error_description

ExplanationA catastrophic ALCS system error occurred.Error_description describes the type of error. It caninclude the following information:

SE-numberDump sequence number. ALCS allocates a unique6-digit decimal number to each system errordump. It allocates these numbers consecutively,starting with 000000. The sequence continuesacross restarts; that is, ALCS does not restart at000000 after an abnormal termination. If ALCSdid not write a system error dump to the ALCSdiagnostic file then number is the character string"NODUMP".

CTL-codeA control error - that is, an error that the onlinemonitor detects. Code is a 6-digit hexadecimalcode that identifies the type of error. Chapter 13,“System error codes: 000000-000FFF,” on page302 lists these error codes.

OPR-codeAn operational error - that is, an error that anapplication program or an ECB-controlled monitorprogram detects. An operational error is notnormally catastrophic. It is only catastrophic if theonline monitor detects a more severe error while itis recovering from the operational error condition.Code is a 6-digit hexadecimal code that identifiesthe type of error.

PSW-pswCorrected Program Status Word (PSW) at the timeof the error. Corrected means that ALCS has resetthe instruction address in the PSW to point to thefailing instruction.


PROG-nameName of the application program or ALCS monitorCSECT that was executing at the time of theerror. The dump header contains this only if ALCScan determine that the error is in a particularapplication program or ALCS monitor CSECT.

OFF-listing-addressOffset of error within the ALCS monitor CSECT, ahexadecimal number. This address corresponds tothe address (LOC) in the assembler listing of theALCS monitor CSECT. The dump header containsthis only if ALCS can determine that the error is in aparticular monitor CSECT.

OFFSET-listing-addressOffset (listing address) in hexadecimal within theapplication program of the failing instruction ormonitor-request macro.

AT-addressAddress in hexadecimal of the failing instruction ormonitor-request macro.

CRN-crnCRN of the originating terminal associated with theerror.

CRI-criCRI of the originating terminal associated with theerror.


Problem determinationRefer to Chapter 13, “System error codes:000000-000FFF,” on page 302 or, if applicable,to user-written documentation to identify the errorcondition. If ALCS was able to write a system errordump to the ALCS diagnostic file, then run the ALCSdiagnostic file processor to print the system errordump. ALCS Operation and Maintenance explains howto run the ALCS diagnostic file processor and how tointerpret the system error dump listing.

ModuleDXCPCH

DXC251W Global area corruption - Not allglobal area dumped

ExplanationWhile placing a diagnostic dump on the diagnosticfile, ALCS has detected corruption in the global areadirectory of directories. No further dumping of theglobal area is possible.


System programmer responseThis problem is almost certainly due to an error in anapplication program. Identify the program and correctthe error as soon as possible; otherwise the globalarea is likely to be corrupted again.

User responseAdvise your system programmer immediately. An ALCSrestart is probably required, but this depends on thenature of the applications.

ModuleDXCDMP

DXC252T Can not read Exception DumpTable

ExplanationALCS cannot read the Exception Dump Table rom thereal-time database, because either the database is notinitialized, or there is a hardware error.

User responseCheck that the initialization completed normally for allDASD data sets. If initialization was successful, checkfor a hardware error on the DASD volumes containingthe data sets, and get the unit serviced if necessary.

ModuleDXCINT

DXC260W Load of module MODN-'name'failed - Unrecognizableapplication CSECT at offset OFS-X'offset'

ExplanationWhen loading ECB-controlled program load modulename, ALCS found an invalid application CSECT atoffset offset (hexadecimal).

System actionALCS terminates the load of this load module. None ofthe ECB-controlled programs in this load module areloaded.


User responseRefer to the linkage editor diagnostic listing for loadmodule name. Ensure that the CSECT at offset offset,and the CSECT immediately preceding it, if any, areALCS ECB-controlled application programs. That is,each CSECT begins with the expansion of the ALCSBEGIN macro, and finishes with the expansion of theFINIS macro.

ModuleDXCINTP

DXC261W Load of module MODN-'name'failed - reason_message

ExplanationALCS cannot load the ECB-controlled program loadmodule name. Reason_message gives the reason, oneof:

DUPLICATE MODULE NAMEMODULE LOAD TABLE FULLPROGRAM TABLE FULL


User responseThis depends on reason_message as follows:

DUPLICATE MODULE NAME:If this occurs during ALCS restart, then remove thisduplicate entry in the ALCS program configurationmodule.

If it occurs following a ZPCTL command, theneither unload the already loaded module of thisname and load this module, or rename this moduleand then load it.

MODULE LOAD TABLE FULL:If this occurs during ALCS restart, then increasethe size of the module load table, parameterNBRMOD of macro CP0DT in the ALCS programconfiguration module definition.

If it occurs following a ZPCTL command, thenincrease the size of the module load table asdescribed above, or free a module load table entryby unloading another load module.

PROGRAM TABLE FULL:If this occurs during ALCS restart, then increasethe size of the program table, parameter NBRPGMof macro CP0DT in the ALCS program configurationmodule definition.

If it occurs following a ZPCTL command, thenincrease the size of the program table as describedabove, or free some program table entries byunloading other load modules.

ModuleDXCINTP

DXC262W MODN-'name' failed - Error duringmodule load, Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

ExplanationAn error occurred when ALCS initialization tried to read(MVS LOAD macro) the ECB-controlled program loadmodule name.



ModuleDXCINTP

DXC263T Load of program config tableTN-'name' failed - Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

ExplanationAn error occurred when ALCS initialization tried to read(MVS LOAD macro) the program configuration module.




ModuleDXCINTP

DXC264T Can not load/build internal tableTN-'name' - Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

ExplanationALCS cannot build internal table name. The MVS LOADor GETMAIN request failed.


Problem determinationMVS System Codes and MVS Authorized AssemblerServices Guide list GETMAIN and LOAD systemcompletion and reason codes.

ModuleDXCINTP

DXC265T Can not load all ALCS installation-wide monitor exit load modules

ExplanationALCS cannot load all the ALCS installation-widemonitor exit load modules.


User responseRefer to the accompanying DXC260W, DXC261W, orDXC262W message(s) for further details.

ModuleDXCINTP

DXC266T Can not load all ALCS entry-controlled monitor programs

ExplanationALCS cannot load all the ALCS ECB-controlled programload modules.


User responseRefer to the accompanying DXC260W, DXC261W, orDXC262W message(s) for further details.

ModuleDXCINTP

DXC270T Can not read CTKB

ExplanationALCS cannot read the system keypoint record B (CTKB)from the data set, because either the data set is notinitialized, or there is a hardware error.

User responseCheck that initialization completed normally for alldata sets. If initialization was successful, check for ahardware error on the DASD volumes containing thedata sets, and get the unit serviced if necessary.

ModuleDXCKPT

DXC271W ID check on file copy - CTKBreplaced

ExplanationThe system keypoint record B (CTKB) does notcontain the expected record ID (CK). The databaseconfiguration data set (CDS) has just been initialized.

System actionALCS initializes CTKB and continues with initialization.

ModuleDXCKPT

DXC272T ID check on file copy - CTKB cannot be replaced

ExplanationThe system keypoint record B (CTKB) does not containthe expected record ID (CK). However, the databaseconfiguration data set (CDS) was not reinitialized.



User responseCheck that the ALCS job or started task specifies thecorrect database load module. If this happens whenyou start using the CDS for the first time, delete thecopies of the existing CDS and then recreate them.You can then restart ALCS. If this happens when youhave been running ALCS for some time, treat it aspossible corruption of your CDS or realtime database.If appropriate, restore the CDS and/or the realtimedatabase, then restart ALCS.

ModuleDXCKPT

DXC273T CDS can not be used with thisCTKB

ExplanationYou have started an ALCS Version 2 Release 2 systemin which the database was last used under ALCSVersion 2 Release 1.1 or ALCS/MVS/XA. Howeverthe database configuration data set (CDS) was notreinitialized.


User responseCheck that the ALCS job or started task specifies thecorrect database load module. If this happens whenyou start using the CDS for the first time, delete thecopies of the existing CDS and then recreate them.You can then restart ALCS. If this happens when youhave been running ALCS for some time, treat it aspossible corruption of your CDS or realtime database.If appropriate, restore the CDS and/or the realtimedatabase, then restart ALCS.

ModuleDXCKPT

DXC280T GETMAIN for DCBfailed - Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

ExplanationALCS cannot obtain space in which to build requiredMVS data set control blocks (DCBs).


Problem determinationMVS System Codes and MVS Authorized AssemblerServices Guide list GETMAIN system completion andreason codes.

ModuleDXCLDE

DXC281T Can not open DCB DDN-'ddname' -Return code RC-X'return_code'

ExplanationALCS cannot open the data set control block (DCB) forthe ddname data set(s). This message is accompaniedby message IEC146I.


Problem determinationRefer to message IEC146I in MVS System Messages forinformation about the error and for an explanation ofthe return code.

ModuleDXCLDE

DXC290E MQSeries initialization failed --Not enough storage

ExplanationALCS cannot complete the initialization of theMQSeries queue manager session because not enoughstorage has been defined.

System actionALCS continues with initialization, but cannot useMQSeries.

System programmer responseCorrect the error by allocating more storage.

DXC291E MQSeries entry point loadfailed -- Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'


ExplanationALCS cannot complete the initialization of theMQSeries queue manager session.


Problem determinationRefer to the MQSeries documentation for moreinformation about the error and an explanation of thereturn code.

DXC292W MQSeries interface suspended

ExplanationThe MQSeries queue manager has stopped respondingto ALCS.

System actionALCS returns control to any entries that issuedMQSeries calls, with completion code MQCC_FAILEDand reason code MQRC_CONNECTION_BROKEN,providing the call has not been passed to MQSeriesyet. ALCS cannot use MQSeries until the queuemanager responds again.

User responseInform your MQSeries administrator.

ModuleDXCMQI

DXC293W MQSeries interface resumed

ExplanationThe MQSeries queue manager has started respondingto ALCS.


ModuleDXCMQI

DXC294E MQSeries version changed -- MQIOCB has invalid length

ExplanationALCS detected that the installed version of MQSeriescan not use the ALCS IOCBs and therefore will notinitialize MQseries for ALCS.


User responseAsk your system programmer to inform your IBMprogramming support representative.

ModuleDXCMQI

DXC300E TCP/IP initialization failed - Notenough storage

ExplanationDuring initialization, ALCS was unable to obtain thestorage required to support TCP/IP sockets calls.

System actionALCS continues with initialization but cannot useTCP/IP.

System programmer responseAllocate more storage to the ALCS job or started task.

ModuleDXCSOCK

DXC301E TCP/IP entry point load failed- Abend code AC-X'abend_code'Reason code RSC-X'reason_code'

ExplanationDuring initialization, an error occurred when ALCStried to load (MVS LOAD macro) one of the entrypoints EZASOKET, EZACIC04, EZACIC05, EZACIC06,or EZACIC08 for the TCP/IP sockets calls. Theabend_code and reason_code are those issued by MVSLOAD.

System actionALCS continues with initialization but cannot useTCP/IP.


Problem determinationMVS System Codes lists LOAD completion and reasoncodes.

ModuleDXCSOCK

DXC386E MQ queue CRN-'crn' not found

ExplanationThe communication load module containsa communication resource specified asLDTYPE=MQTERM, which is accessed through an MQqueue resource that is not known to ALCS.


User responseCheck that the communication resource is correctlyspecified in the communication generation. RunDXCCOMOL to verify that the communicationresources are correctly specified and generated.

ModuleDXCCOMV

DXC387E MQ queue CRN-'crn' not replaced/deleted - At least one terminal stillaccessed through it

ExplanationDuring ALCS communication table build, a deleteor replace request in the communication generationrefers to an MQ queue resource that has at least oneterminal accessed through it.

System actionALCS does not replace or delete the MQ queueresource.

User responseCheck that the communication resource is correctlyspecified in the communication generation. RunDXCCOMOL to verify that the communicationresources are correctly specified and generated.Delete the terminals before attempting to delete orreplace their owning MQ queue resource.

ModuleDXCCOMU

DXC388E GETMAIN error -- Can not obtainstorage for MQ resource CRN-'crn'

ExplanationDuring initialization, ALCS cannot obtain enoughstorage to build the communication table for an MQresource.



ModuleDXCMQB

DXC389W TCP/IP CRN-'crn' max connectionsnot changed

ExplanationDuring ALCS communication table build, a replacerequest in the communication generation refersto a TCP/IP connection which has a differentmaximum number of concurrent connections (COMDEFMAXCONN parameter).

System actionThe communication tables are set up for this resourceusing the old MAXCONN parameter value.

User responseCheck that the communication resource is correctlyspecified in the communication generation.

ModuleDXCCOMU

DXC390E TCP/IP CRN-'crn' not found

ExplanationThe communication load module containsa communication resource specified asLDTYPE=TCPIPALC, which is accessed through aTCP/IP connection that is not known to ALCS.


System actionThe communication tables are not set up correctly forthis resource. ALCS will fail when it tries to access thisresource. ALCS proceeds with the next request.


ModuleDXCCOMU

DXC391E TCP/IP CRN-'crn' not replaced/deleted - At least one terminal stillaccessed through it

ExplanationDuring ALCS communication table build, a deleteor replace request in the communication generationrefers to a TCP/IP connection that has at least oneterminal accessed through it.

System actionALCS does not replace or delete the TCP/IPconnection.

User responseCheck that the communication resource is correctlyspecified in the communication generation. RunDXCCOMOL to verify that the communicationresources are correctly specified and generated.Delete the terminals before attempting to delete orreplace their owning TCP/IP connection.

ModuleDXCCOMV

DXC392E Resource CRN-'crn' - No room intable DXCMAT to add entry

ExplanationDuring ALCS communication table build, an add orreplace request in the communication generationrefers to a TCP/IP ALC terminal resource with a MATIP-ID that is not already defined to ALCS, but ALCS cannotadd the MATIP-ID into the MATIP-ID communicationtable. The MATIP-ID for a terminal is derived from itsHEX, TCID, IA, and TA values.


User responseCheck that the communication resources are correctlyspecified in the communication generation. Youmay need to increase the ENTRIES parameteron the COMGEN macro in the first communicationload module. Run DXCCOMOL to verify that thecommunication resources are correctly specified andgenerated. Otherwise ask your system programmer toinform your IBM programming support representative.

ModuleDXCCOMV

DXC393I VTAM ACB LUN-'acbname'open failed, Return code RC-X'return_code' - ALCS takeover willretry

ExplanationALCS automatic system takeover requires that thisACB is active. Return_code is the access methodcontrol block ( ACB ) error return code.

System actionALCS will retry once. This allows WTO exits or NetView,for example, to take corrective actions. If it is stillunsuccessful then message DXC200R will be sent.

Problem determinationVTAM Programming for the installed version andrelease of VTAM explains return_code.

ModuleDXCINTC

DXC394I VTAM ACB LUN-'acbname' hasbeen closed

ExplanationVTAM ACB has been closed. ALCS issues this messagewhen it ends contact with VTAM during termination.

System actionThe ALCS system continues.


ModuleDXCTRMC

DXC395I VTAM ACB LUN-'acbname' hasbeen opened

ExplanationVTAM ACB has been opened. ALCS issues thismessage when it contacts VTAM during initialization.

System actionThe ALCS system continues.

ModuleDXCINTC

DXC396E WAS resource CRN-'crn' not found

ExplanationThe communication load module containsa communication resource specified asLDTYPE=WASTERM, which is accessed through a WASresource that is not known to ALCS.



ModuleDXCCOMV

DXC397E WAS CRN-'crn' not replaced/deleted - At least one terminal stillaccessed through it

ExplanationDuring ALCS communication table build, a deleteor replace request in the communication generationrefers to a WAS resource that has at least one terminalaccessed through it.

System actionALCS does not replace or delete the WAS resource.

User responseCheck that the communication resource is correctlyspecified in the communication generation. RunDXCCOMOL to verify that the communicationresources are correctly specified and generated.Delete the terminals before attempting to delete orreplace their WAS resource.

ModuleDXCCOMU

DXC398E GETMAIN error - Can notobtain storage for WAS resourceCRN-'crn'

ExplanationDuring initialization, ALCS cannot obtain enoughstorage to build the communication table for a WASresource.



ModuleDXCWSB

DXC401I Using current slot a inconfiguration data set CDSn

ExplanationALCS is using the current load list in the configurationdata set CDSn during ALCS restart. The current loadlist resides in either slot A or slot B. CDS1 is theprogram configuration data set and CDS2 is thecommunication configuration data set. CDS1 containsa list of the program and installation-wide monitorexit load modules that will be loaded during ALCSrestart. CDS2 contains a list of the communicationconfiguration load modules that will be loaded duringALCS restart.


ModuleDXCINTC, DXCINTP


DXC402I Using alternate slot a inconfiguration data set CDSn

ExplanationALCS is using the alternate load list in the configurationdata set CDSn during ALCS restart. The alternateload list resides in either slot A or slot B. CDS1 isthe program configuration data set and CDS2 is thecommunication configuration data set. CDS1 containsa list of the program and installation-wide monitorexit load modules that will be loaded during ALCSrestart. CDS2 contains a list of the communicationconfiguration load modules that will be loaded duringALCS restart. ALCS normally uses the current loadlist during ALCS restart. The alternate load list isused when that list has been confirmed but not yetcommitted or backed out.


ModuleDXCINTC, DXCINTP

DXC403T Error writing configuration dataset CDSn

ExplanationALCS cannot write to configuration data set CDSn.CDS1 is the program configuration data set and CDS2is the communication configuration data set.

System actionALCS terminates.

Problem determinationCheck that at least one configuration data set isallocated and has read/write access. If it is newlyallocated, ensure that the first time it is used you arenot using the ALCS test data base facility, otherwiseyou should consider restoring it from a previousbackup. If the problem persists, contact your IBMprogram support representative.

ModuleDXCINTC, DXCINTP, DXCINTE

DXC404T Error reading configuration dataset CDSn

ExplanationALCS cannot read from configuration data set CDSn.CDS1 is the program configuration data set and CDS2is the communication configuration data set.

System actionALCS terminates.

Problem determinationCheck for I/O error messages on the ALCS ROCRAS and the z/OS system log. If the I/O error cannot be corrected, you should consider restoring theconfiguration data set from a previous backup. If theproblem persists, contact your IBM program supportrepresentative.


DXC405I Initializing configuration data setCDSn

ExplanationALCS initializes configuration data set CDSn. CDS1 isthe program configuration data set and CDS2 is thecommunication configuration data set.



DXC407T Configuration data set CDSn logicerror

ExplanationA logic error has occurred. The internal tables thatare used by ALCS to manage the configuration datasets have not been initialized. CDS1 is the programconfiguration data set and CDS2 is the communicationconfiguration data set.

System actionALCS terminates

Problem determinationThis is an ALCS logic error. Contact your IBM programsupport representative.


ModuleDXCINTE

DXC408T Configuration data set CDSn cannot read either copy

ExplanationALCS cannot access configuration data set CDSn. Ifyour ALCS data base is fully duplicated, there will betwo copies (copy-1 and copy-2) of each configurationdata set. ALCS can not access either of these twocopies. CDS1 is the program configuration data set andCDS2 is the communication configuration data set.

System actionALCS terminates

Problem determinationCheck that the VSAM job to define the configurationdata set has run successfully. Check the status ofyour configuration data sets. If both copies of yourconfiguration data set are offline, then vary one of thecopies online. If the problem persists, contact yourIBM program support representative.

ModuleDXCINTE

DXC410E ICSF initialization failed -- notenough storage

ExplanationALCS cannot complete the initialization of the ICSFinterface because not enough storage has beendeclared.

System actionALCS continues with initialization, but cannot use ICSF.

Problem determinationCorrect the error by allocating more storage.

ModuleDXCICSF

DXC411E ICSF entry point load failed- Abend code AC-X'abend_code'Reason code RSC-X'reason_code'

ExplanationDuring initialization, an error occurred when ALCStried to load one of the entry points CSFIQA,CSFIQF, CSNBSYD or CSNBSYE for the ICSF calls. Theabend_code and reason_code are those issued by MVSLOAD.

System actionALCS continues with initialization, but cannot use ICSF.

Problem determinationMVS System Codes lists LOAD abend and reason codes.

ModuleDXCICSF

DXC420E HTTP Client initialization failed -not enough storage

Explanation:ALCS cannot complete the initialization of the HTTPClient interface because not enough storage has beendeclared.

System actionALCS continues with initialization, but cannot use theHTTP client.


ModuleDXCHTTP

DXC421E HTTP Client entry point load failed- Abend code AC-x'abend_code'Reason code RS-x'reason_code'

ExplanationDuring initialization an error occurred when ALCS triedto load (MVS LOAD macro) one of the entry points forthe HTTP client calls.The abend_code and reason_code are those issued byMVS LOAD.

System actionACLS continues with initialization, but cannot use theHTTP client services.


System programmer responseMVS system Codes lists LOAD abend and reasoncodes.

ModuleDXCHTTP

DXC422E HTTP Client BPX1SDD call failed- Abend code AC-x'abend_code'Reason code RS-x'reason_code'

ExplanationDuring initialization an error occurred when ALCS triedto set the DUB OPTION for HTTP client calls.The abend code and reason code are those issued byUnix System Services.

System actionALCS continues with initialization, but cannot use theHTTP client services.

System programmer responseUnix System Messages and Codes lists BPX1SDDabend and reason codes.

ModuleDXCHTTP

DXC430E JSON Parser initialization failed -not enough storage

ExplanationALCS cannot complete the initialization of the JSONParser interface because not enough storage has beendeclared.

System actionALCS continues with initialization, but cannot use theJSON Parser services.


ModuleDXCJSON

DXC431E JSON Parser entry pointload failed - Abend code AC-x'abend_code' Reason code RS-x'reason_code'

ExplanationDuring initialization an error occurred when ALCS triedto load (MVS LOAD macro) one of the entry points forthe JSON parser calls.The abend code and reason code are those issues byMVS LOAD.

System programmer responseMVS system Codes lists LOAD abend and reasoncodes.

ModuleDXCJSON


Chapter 3. Offline program messages: DXC480-DXC799

DXC480W The following keys have beendiscarded

ExplanationThis message is followed by a list of the search stringsthat XREF could not handle in this run. The reason isgiven in a subsequent message (DXC481W, DXC482W,or both).

System actionProcessing continues with the remaining search keys.

User responseRun XREF a second time specifying the discardedsearch keys.

ModuleDXCXREF

DXC481W More than 63 initial characters -Resubmit keys listed above

ExplanationXREF first sorts the search keys and builds an indexstructure. It can only handle up to 63 initial characters(more than enough for most cases, and not restrictingthe number of search keys), and the limit wasexceeded.

System actionProcessing continues using those search keys thatstart with the first 63 initial characters. (This maywell be more than 63 search keys). The remainder arediscarded. Message DXC483I lists the keys used.

User responseRun XREF a second time specifying the keys listed inmessage DXC480W.

ModuleDXCXREF

DXC482W More than n search keys specified- Resubmit keys listed above

ExplanationAs supplied, XREF can only search for up to 99 keysat any one time (though this limit may have beenchanged by your system programmer). This limit wasexceeded.

System actionProcessing continues using the first n keys supplied.Message DXC483I lists these keys.

User responseRun XREF a second time specifying the keys listedin message DXC480W. Alternatively ask your systemprogrammer to increase this limit.

ModuleDXCXREF

DXC483I Search will use the following keys

ExplanationThis message is followed by a sorted list of the lengthsand values of the search strings that will be used, oneper line.

System actionProcessing continues.

ModuleDXCXREF

DXC484E No search keys specified - Runterminated

ExplanationNo search keys were specified for XREF to process.The DD statement may be spelt incorrectly, or theassociated data set may be empty.


System actionProcessing ends abnormally.

User responseRerun XREF ensuring the search keys are specifiedcorrectly.

ModuleDXCXREF

DXC485W More than n ambiguous memberspecifications - The following havebeen discarded - Please resubmit

ExplanationAs supplied, XREF only supports up to 99 ambiguousmember specifications at any one time (thoughthis limit may have been changed by your systemprogrammer). This limit was exceeded.

System actionProcessing continues using the first n ambiguousmember specifications supplied. Message DXC487Ilists these.

User responseRun XREF a second time using the listed ambiguousmember specifications. Alternatively ask your systemprogrammer to increase this limit.

ModuleDXCXREF

DXC486I No ambiguous memberspecifications - All members willbe searched

ExplanationMembers of the partitioned data sets to search werenot specified. This may have been deliberate, or theDD statement may have been spelt incorrectly, or theassociated data set may have been empty.

System actionProcessing continues. All members will be searched.

User responseIf not deliberate, rerun XREF ensuring the membersare specified correctly. Alternatively post-process theoutput obtained to extract the members of interest.

ModuleDXCXREF

DXC487I Members matching the followingambiguous specifications will besearched

ExplanationThis message is followed by a list of the ambiguousmember specifications that XREF will attempt tomatch members of the search data sets against.


ModuleDXCXREF

DXC490T Parameter format invalid

ExplanationThe format of the ALCS statistical reports generatorparameter is invalid, for example the parameterexceeds 8 characters. The parameter_name parameterof the job control EXEC statement specifies thestatistical reports generator parameter.

System actionALCS statistical reports generator ends abnormally.

Problem determinationALCS Installation and Customization describes theformat.

ModuleDXCSRG

DXC491T Can not load DASD configtable table_name - Returncode X'return_code', Reason codeX'reason_code'

ExplanationAn error occurred when the ALCS statistical reportsgenerator tried to read (MVS LOAD macro) the DASD

Chapter 3. Offline program messages: DXC480-DXC799 53

configuration table table_name. Return_code is thesystem completion code and reason_code is thereason code associated with the error.

System actionALCS statistical reports generator ends abnormally.

Problem determinationMVS System Codes lists LOAD system completioncodes and reason codes.

ModuleDXCSRG

DXC492W Return code X'return_code' fromsort

ExplanationThe sort program returned a non-zero return code tothe ALCS statistical reports generator.

System actionThe ALCS statistical reports generator continuesprocessing. Depending on the condition that causedthe non-zero return code, the reports may be incorrector incomplete.

Problem determinationDFSORT Application Programming Guide lists returncodes from DFSORT.

ModuleDXCSRG

DXC501E Columns 1-58 blank - Ignored


System actionSTC DRIL CREATE ignores the input statement andcontinues processing.

Programmer responseCorrect the DRIL definition statement in accordancewith the description in ALCS Installation andCustomization, and rerun STC DRIL CREATE.

ModuleDXCSTCDR

DXC502E No OPCODE




ModuleDXCSTCDR

DXC503E No data field




ModuleDXCSTCDR

DXC504E No label field





ModuleDXCSTCDR

DXC505E Label field length > 8 characters

ExplanationThe label field is too long.



ModuleDXCSTCDR

DXC506W No MEND - MEND assumed

ExplanationSTC DRIL CREATE has read a MACRO statement butit did not read a MEND statement for the previousmember.

System actionSTC DRIL CREATE continues processing as if there wasa MEND statement.

Programmer responseCorrect the DRIL definition by adding a MENDstatement in accordance with the description in ALCSInstallation and Customization, and rerun STC DRILCREATE.

ModuleDXCSTCDR

DXC508E No blanks between fields

ExplanationThere are no blanks in card columns 1 through 58.



ModuleDXCSTCDR

DXC509E Invalid record identifier - Allrecords for this macro ignored

ExplanationThe statement following the macro statement does nothave a 5-character name in the operation code field.

System actionSTC DRIL CREATE does not create the DRIL member.


ModuleDXCSTCDR

DXC510E Invalid record length specification- All records for this macro ignored

ExplanationOne of the following:

The statement that follows the member namestatement does not have an operation code of DS.The operand field is incorrect; it must be 0CLn,where n is the record length (number of bytes) indecimal.




ModuleDXCSTCDR

DXC511E Data type not in table

ExplanationThe data type is invalid.



ModuleDXCSTCDR

DXC512E Data type missing




ModuleDXCSTCDR

DXC513E Invalid length specification

ExplanationThe length subfield of the operand field is not Lnwhere n is a self-defining decimal term.



ModuleDXCSTCDR

DXC514E No field length specified




ModuleDXCSTCDR

DXC515E Non-numeric field length




ModuleDXCSTCDR

DXC516E Non-numeric multiplicity factor

ExplanationThe multiplicity factor is also known as the duplicationfactor.




ModuleDXCSTCDR

DXC517E Field length > implied length

ExplanationThe field length is greater than the length implied bythe data type. ALCS Installation and Customizationdescribes how to code the field length, and listsimplied lengths for the various data types.



ModuleDXCSTCDR

DXC518W Field has been aligned

ExplanationThe implied or specified length indicates halfword,fullword, or doubleword alignment but the currentvalue of the location counter is not on a halfword,fullword, or doubleword boundary.

System actionSTC DRIL CREATE aligns the field by inserting zerosbefore the field.


ModuleDXCSTCDR

DXC519E Fields extend beyond record -Current offset value

ExplanationSome field definition statements define fields beyondthe end of the record.



ModuleDXCSTCDR

DXC520W Columns 59-62 ignored


System actionSTC DRIL CREATE ignores the information in columns59 through 62 and continues processing.


ModuleDXCSTCDR

DXC521E Columns 64-68 non-numeric


System actionSTC DRIL CREATE ignores the information in columns64 through 68 and continues processing.



ModuleDXCSTCDR

DXC522W File address indicator ignored

ExplanationThere is a non-blank character in column 71, but thelength of the field is not 4 bytes.

System actionSTC DRIL CREATE assumes that the field is not a fileaddress and continues processing.


ModuleDXCSTCDR

DXC523E No sign (+ or -) for adjustment

ExplanationThere is no sign for the adjustment of the offset on anORG or EQU statement.



ModuleDXCSTCDR

DXC524E Non-numeric adjustment

ExplanationThe adjustment on an ORG or EQU statement is notnumeric.



ModuleDXCSTCDR

DXC525E Label not previously defined

ExplanationThe label on an ORG or EQU statement is not defined.



ModuleDXCSTCDR

DXC526E Invalid adjustment - Outsiderecord

ExplanationThe adjustment on an ORG or EQU statement producesan offset that is either less than 0 or greater than thelength of the member.



ModuleDXCSTCDR


DXC527E Number of fields exceedsmaximum (285)

ExplanationThere are more than 285 fields in one DRIL member.



ModuleDXCSTCDR

DXC528W Label field invalid with 'ORG'

ExplanationAn ORG statement must have a blank label field.

System actionSTC DRIL CREATE ignores the label field and continuesprocessing.


ModuleDXCSTCDR

DXC529E Invalid adjustment

ExplanationThe operand of an ORG or EQU statement is invalid.



ModuleDXCSTCDR

DXC530E Invalid OPCODE - Not ORG, EQU,DS or DC




ModuleDXCSTCDR

DXC531W Duplicate label - Already defined

ExplanationAnother field in the member has the same label.



ModuleDXCSTCDR

DXC532E Field length not equal to slot info

ExplanationThe length of a field that has multiple items mustequal the item length multiplied by the number ofitems.




ModuleDXCSTCDR

DXC541T Error in sort - Return codereturn_code

ExplanationThe sort program returned a non-zero return code toSTC DRIL CREATE.

System actionSTC DRIL CREATE ends abnormally.

Problem determinationDFSORT Application Programming Guide lists returncodes from DFSORT.

ModuleDXCSTCDR

DXC542I End of DRIL CREATE - InputRecords number, Output recordsnumber, Number of outputmembers number

ExplanationSTC DRIL CREATE completed successfully.

ModuleDXCSTCDR

DXC543T Sequence error in sortedtemporary file - Keycode keycode

ExplanationThe sort program returned a zero return code to STCDRIL CREATE. However, the sorted data set is out ofsequence. Keycode is the numeric key of the out-of-sequence record.



ModuleDXCSTCDR

DXC544T Error copying sorted temporaryfile to DRIL file - Keycode keycode

ExplanationThe PL/I KEY condition was raised while copying thesorted work data set (SORTOUT) to the DRIL data set(DXCDRIL). Keycode is the PL/I ONCODE.


Problem determinationRefer to PL/I Language Reference.

ModuleDXCSTCDR

DXC550T Immediate end of file reached oninput file - Job terminated

ExplanationThere are no STC input statements.

System actionSTC ends abnormally.

User responseCheck why the input statements were not found,correct the error, and rerun the job.

ModuleDXCSTC

DXC551T Severe error - Job terminated

ExplanationPreviously reported error condition(s) make continuedexecution of STC impossible.



User responseCorrect the previously reported errors, and rerun thejob.

ModuleDXCSTC

DXC552E Record ignored due to invalidGSTAR record


System actionSTC does not generate records for this set ofgeneration statements.

Programmer responseCorrect the STC input in accordance with thedescription in ALCS Installation and Customization,and rerun STC Edit and STC.

ModuleDXCSTC

DXC553E Invalid offset offset - Recordlength of length

ExplanationThe label field specifies an invalid displacementwithin the record(s). For an ORG statement, the offsetspecified is either less than 8 or greater than therecord length minus 3. For other operation codes, theoffset is greater than the record length.

System actionSTC ignores this statement and continues processing.


ModuleDXCSTC

DXC554E Input data extends beyond record- Offset offset - Record lengthlength




ModuleDXCSTC

DXC555E Invalid fixed file record type type

ExplanationA file address specifies a fixed file record type that isnot defined in the DXCRID macro.



ModuleDXCSTC

DXC556E No DRIL for record ID name

ExplanationA GSTAR statement specifies the name of a DRILmember that does not exist.


Programmer responseEither correct the STC input and rerun STC Edit andSTC; or correct DRIL and rerun STC DRIL CREATE. Seethe appropriate description in ALCS Installation andCustomization.


ModuleDXCSTC

DXC557E No entry in DRIL for label label

ExplanationLabel is not defined in the DRIL member for this groupof records.



ModuleDXCSTC

DXC558E Slot number of slot greater thanmax specified in DRIL

ExplanationThe slot number (that is, entry number in a data table)in the parameter subfield of an ENTIT, REPST,ADDST, or SUBST is greater than the number of tableentries that the DRIL member specifies.



ModuleDXCSTC

DXC559E F.A. indic in DRIL for label labelbut data entered is not a fileaddress

ExplanationDRIL defines label as a file address field, but the dataspecified is not a file address.



ModuleDXCSTC

DXC560W No F.A. indic in DRIL for field field -Input data is data

ExplanationDRIL does not define field as a file address field, butthe data specified is a file address.

System actionSTC accepts the statement, but the field is notconverted to a file address when the record is loadedto the real time database.


ModuleDXCSTC

DXC561E Field length in DRIL of length -Must be 4 bytes for a file address

ExplanationDRIL does not define the field as a 4-byte field, but thedata specified is a file address (8 hexadecimal digits).




ModuleDXCSTC

DXC562W Data type in DRIL for field field isnot char but char data entered

ExplanationDRIL does not define field as a character field, but thedata specified is character data.

System actionSTC puts the data left-justified in the field and padswith blanks if required.


ModuleDXCSTC

DXC563W Data type in DRIL for field field ischar but non-char data entered

ExplanationDRIL defines field as a character field, but the dataspecified is not character data.

System actionIf the data is the correct length, STC puts it in the field.If the data length is shorter than DRIL expects, STCpads the data with blanks. If the data length is longerthan DRIL expects, STC deletes low-order bytes andsends message DXC566W.


ModuleDXCSTC

DXC564W Data entered is longer than lengthin DRIL - Low order number bytesused

ExplanationData is longer than DRIL expects, but data has leadingzeros.

System actionSTC deletes high-order bytes.


ModuleDXCSTC

DXC565E Data entered is longer than lengthin DRIL - DRIL length of length

ExplanationData is longer than DRIL expects, and data does nothave leading zeros.



ModuleDXCSTC

DXC566W Data entered is longer than lengthin DRIL - First number bytes used

ExplanationDRIL expects character data that is number bytes long,but the data is non-character and the data length islonger than DRIL expects.

System actionSTC deletes low-order bytes.



ModuleDXCSTC

DXC579E Slot number of slot specified forlabel but not a slot field in DRIL

ExplanationIn the DRIL definition, slot is not a subfield.



ModuleDXCSTC

DXC580W Embedded X'00' in text ofmessage number number

ExplanationThe character count for the message is greater thanthe number of text characters.

System actionSTC pads the message to the right with hexadecimalzeros.

Programmer responseCorrect the STC input before the next STC run inaccordance with the description in ALCS Installationand Customization. If the action taken by STC is notwhat you intended, rerun STC Edit and STC.

ModuleDXCSTC

DXC581W Text beyond end of message willbe lost on output - Msg numbernumber - Text length length

ExplanationEither the character count is less than the number oftext characters or the character count is not specified.

System actionSTC assumes that the first byte of hexadecimal zerosis the end of the message (usually the first byte ofhexadecimal zeros is uninitialized storage that followsthe last character of the input message).


ModuleDXCSTC

DXC582W No text in message numbernumber - Message not written toTUT


System actionSTC ignores the message.


ModuleDXCSTC

DXC583E Length of length for allocate > maxblock size of max

ExplanationEither STC input or DRIL allocates a length that islarger than the maximum block length allowed (max).

System actionSTC ignores the input.



ModuleDXCSTC

DXC584I End of STC run - Number of inputrecords number


System actionSTC completes normally.

ModuleDXCSTC

DXC585T Invalid type of run statement'type' - must be 'DATA' or 'MSG'




ModuleDXCSTC

DXC586T Invalid RUNID statement

ExplanationThe input statement following the STC statement isnot a valid RUNID control statement. ALCS Installationand Customization gives the format of the RUNIDcontrol statement.



ModuleDXCSTC

DXC587T TUT message and pilot datageneration cannot be mixed - Endof input assumed


System actionSTC processes the message generation or the pilotdata generation (whichever comes first). Then STCends abnormally.


ModuleDXCSTC

DXC588E Char count of count for messagenumber number > max block sizeof max

ExplanationThe message length exceeds the maximum block sizeallowed (1024).

System actionSTC ignores the input.


ModuleDXCSTC

DXC589T Can not load DASD tablesmodule name - Return code


system_completion_code Reasoncode reason_code

ExplanationAn error occurred when STC tried to read (MVS LOADmacro) the DASD configuration table. Name is themember name of the DASD configuration table.



ModuleDXCSTC

DXC595E Invalid GSTAR statement - GSTARlabel

ExplanationThe format of the GSTAR data definition statementwith label label is invalid.

System actionSTC ignores the GSTAR statement.


ModuleDXCSTC

DXC600E Neither compress or expandspecified in parm field -- no actiontaken


System programmer responseCorrect the typing or syntax error and retry thecommand.

ModuleDXCCMPR

DXC601S Unable to invoke compress/expand query service


System programmer responseCorrect the typing or syntax error and retry thecommand.

ModuleDXCCMPR

DXC602S Unable to invoke compress/expand service RC=nn

ExplanationThere is a problem with the CSRCESRV macro.

System programmer responseConsult the appropriate MVS System Codes for anexplanation of reason code RC=nn.

ModuleDXCCMPR

DXC603I Compressing dataset name,blocksize nn on yy/ddd hh:mm:ss


ModuleDXCCMPR

DXC604I Function complete nn recordsprocessed. Longest record was nnbytes



ModuleDXCCMPR

DXC605I Bytes in:nn. Bytes out:nn.


ModuleDXCCMPR

DXC606I Expanding dataset name


ModuleDXCCMPR

DXC607I Original name was name,blocksize nn compressed onyy/ddd hh:mm:ss


ModuleDXCCMPR

DXC608S Sorry, but the input dataset namename was not compressed by thisprogram

ExplanationThe dataset was not compressed by the DXCCMPRutility and therefore cannot be expanded by it.

ModuleDXCCMPR

DXC611W Continuation statement but CC1not blank

ExplanationData on a continuation statement starts in column1. Continuation data can start in any column exceptcolumn 1.

System actionSTC interprets the statement as a continuation of theprevious statement.


ModuleDXCSTCED

DXC612W Leading zeros inserted in binaryfield

ExplanationA binary data item is not a multiple of 8 bits.

System actionSTC inserts the required number of zeros.


ModuleDXCSTCED

DXC613W Missing 'GEND' statementsupplied

ExplanationSTC Edit has read a GSTAR statement (indicating thestart of a new set of generation statements), but therewas no GEND statement to indicate the end of theprevious set.

System actionSTC continues processing as though the required GENDstatement were there.



ModuleDXCSTCED

DXC614W No numeric operand for GSTAR -'1' supplied

ExplanationThe GSTAR statement does not specify the numberof records to generate for this set of generationstatements.

System actionSTC generates one record. It flags as an error any datarecord definition statement in the set that specifies arecord number greater than 1.


ModuleDXCSTCED

DXC615W GSTAR operand too large - numbersubstituted

ExplanationThe number of records that the GSTAR statementspecifies exceeds the maximum allowed. DXCSTCEDcurrently allows up to 999 records.

System actionSTC generates number records.


ModuleDXCSTCED

DXC616W Possible unmatched quotes - Datatruncated

ExplanationThere is an unexpected character (that is, not adelimiter) following a closing quote.

System actionSTC ignores all characters that follow the closingquote.


ModuleDXCSTCED

DXC617W Only 1 data item allowed - Excesstruncated

ExplanationYou cannot specify more than one data item foroperation codes ADD, ADDST, SUB, and SUBST.

System actionSTC ignores the extra data items, and processingcontinues.

ModuleDXCSTCED

DXC618W Data exceeds maximum of numberbytes - Data truncated

ExplanationThe length of the data item exceeds the maximumdata length allowed. The maximum data length is themaximum record length minus the length of the prefix.

System actionSTC truncates the data to number bytes.


ModuleDXCSTCED

DXC619W Too many data items orcontinuations - Maximum number- Excess not processed

ExplanationNumber is the maximum number of data items, orcontinuations of a single data item, that are allowed.

System actionSTC processes the first number data items orcontinuations, and ignores the rest.

ModuleDXCSTCED

DXC620W Field definition and GSTARstatement inconsistent - Excessrecords not written

ExplanationThe number of records specified in a field definitionstatement exceeds the number of records that theGSTAR statement specifies.

System actionSTC generates data for records up to the maximum.

ModuleDXCSTCED

DXC621W BSTA06 field label missing -Record generated without fileaddress

ExplanationFor each record there must be a BSTA06 statementthat specifies the file address where the record isloaded.

System actionSTC generates a record with no file address. This willcause an error when the data file is loaded.

ModuleDXCSTCED

DXC622W STC inserted before RUNIDstatement

ExplanationThe statement that specifies the type of run (STC) wasomitted.

System actionSTC assumes an STC statement, and processingcontinues.

ModuleDXCSTCED

DXC623W Too many data items or invalidcontinuation - Data truncated

ExplanationFor operation codes ADD, ADDST, SUB, and SUBST,you can specify only one data item, and it cannotcontinue on to another statement.

System actionSTC ignores any continuation statement(s) and extradata items, and processing continues.

ModuleDXCSTCED

DXC624W Control statement ignored

ExplanationThere is an unnecessary or unknown controlstatement.

System actionSTC ignores the control statement, and processingcontinues.

ModuleDXCSTCED

DXC625W Type of input missing - 'DATA'assumed

ExplanationThere is no DATA or MSG control statement.


System actionSTC assumes a DATA control statement, andprocessing continues.

ModuleDXCSTCED

DXC626W Leading zero inserted in hex field

ExplanationAn odd number of digits was specified in ahexadecimal data item.

System actionSTC inserts a leading zero, and processing continues.

ModuleDXCSTCED

DXC627W No '+' at end of message

ExplanationThe last character in a free-format message is not anend-of-message character (hexadecimal 4E).

System actionSTC assumes an end-of-message character, andprocessing continues.

ModuleDXCSTCED

DXC628T More than number interrupts -Program terminated

ExplanationDXCSTCED contains a PL/I on-unit that handles thePL/I ERROR condition. The on-unit has been calledmore than number times. DXCSTCED currently allowsa maximum of 10 calls.


Programmer responseAsk your system programmer to inform your IBMprogramming support representative.

ModuleDXCSTCED

DXC629I Statements sequencedstart_number through end_numbernot written to the output file

ExplanationDue to previously reported errors, STC is not writinginput statements (from start_number to end_number)to the output file.

System actionSTC Edit continues editing the input.

Programmer responseDeal with the previous error messages, and then rerunSTC Edit and STC.

ModuleDXCSTCED

DXC630I Error condition raised numbertimes during run

ExplanationDXCSTCED contains a PL/I on-unit that handles thePL/I ERROR condition. The on-unit was called numbertimes.


ModuleDXCSTCED

DXC656W No continuation statement andend of file reached - Statement notwritten

ExplanationThe last input statement contains a non-blankcharacter in column 72.

System actionSTC does not write out the last statement, andprocessing continues.


ModuleDXCSTCED

DXC657W GSTAR missing - 'GSTAR 1' withdummy field label supplied


System actionSTC supplies a GSTAR statement with a label of"DUMMY" and an operand field of 1, and processingcontinues.

ModuleDXCSTCED

DXC658W Invalid line address

ExplanationThe first 6 characters of a free-format messagegeneration statement were not a valid terminaladdress.

System actionSTC ignores the message generation statement,and any others relating to the same message, andprocessing continues.

ModuleDXCSTCED

DXC659W SUB/SUBST operation givesnegative value

ExplanationWhen processing a SUB or SUBST operation code, thedata was decremented to a negative value.

System actionSTC does not initialize any field that has a negativevalue, and processing continues.

ModuleDXCSTCED

DXC660W Invalid numeric

ExplanationEither a numeric data item does not contain validdecimal digits or the operand of a GSTAR statementis not numeric.

System actionIf a numeric data item is invalid, STC does not initializethe field. If a GSTAR operand is invalid, STC assumes"GSTAR 1". Processing continues.

ModuleDXCSTCED

DXC661W Invalid binary number

ExplanationA binary data item does not contain valid binary digits.

System actionSTC does not initialize the field, and processingcontinues.

ModuleDXCSTCED

DXC662W Parameters in error

ExplanationOne of the following:

There is an invalid parameter on the operand fieldof a field definition statement.The operand field of the GSTAR statement is invalid.It must be a 1- or 2-digit decimal number.

System actionIf there is an invalid parameter, STC ignores the fielddefinition statement. If a GSTAR operand is invalid,STC assumes "GSTAR 1". Processing continues.

ModuleDXCSTCED

DXC663W Parameter missing

ExplanationThere is a parameter missing in the operand field of afield definition statement.



Problem determinationRefer to "Running the ALCS system test compiler" inALCS Installation and Customization for the format ofthe operand field.

ModuleDXCSTCED

DXC664W Invalid file address format

ExplanationThe data subfield of the operand field contains a fileaddress that is invalid for one of the following reasons:

Fixed file type symbol is undefinedRecord ordinal is too high for this fixed file typeThe format is not(fixed_file_type_symbol)record_ordinal.


Problem determinationRefer to ALCS Installation and Customization for theformat of the data subfield. Refer to the ALCS DASDgeneration for details of fixed file types and numbersof records defined for each.

ModuleDXCSTCED

DXC665W Data missing

ExplanationThere is a field definition statement that has anoperation code but no data.


ModuleDXCSTCED

DXC666W Invalid hexadecimal number

ExplanationA hexadecimal data item contains one or morecharacters that are not valid hexadecimal digits.

System actionSTC does not initialize the field, and processingcontinues.

ModuleDXCSTCED

DXC667W No recognizable OPCODE orcontrol statement



ModuleDXCSTCED

DXC668W Field label missing

ExplanationThe operation requires either a field label or a numericoffset, but neither is present.


ModuleDXCSTCED

DXC669W SDMF control statement notsupported - Ignored

ExplanationThere is a standard data and message file ( SDMF )control statement in the input. ALCS, however, doesnot support SDMF .


ModuleDXCSTCED


DXC670S Invalid sequence of controlstatements


System actionSTC produces no more output.

Problem determinationRefer to "Running the ALCS system test compiler" inALCS Installation and Customization for the requiredsequence.

ModuleDXCSTCED

DXC671S No 'RUNID' found


System actionSTC produces no more output.

Problem determinationRefer to "Running the ALCS system test compiler" inALCS Installation and Customization for the requiredstatements.

ModuleDXCSTCED

DXC672W Invalid format for data item

ExplanationThe data subfield of the operand field is invalid.


Problem determinationRefer to "Running the ALCS system test compiler" inALCS Installation and Customization for the format ofthe operand field.

ModuleDXCSTCED

DXC691T Run type already found

ExplanationThere is more than one run-type (STC) statement.

System actionSTC Edit ends abnormally.


ModuleDXCSTCED

DXC692T Run type cannot be determined

ExplanationThe first input statement following the print controlstatements must contain the characters STC incolumns 2 through 4.

System actionSTC Edit ends abnormally.


ModuleDXCSTCED

DXC750I Opening dataset DDname for mode

ExplanationThe dataset identified by the ddname DDname is beingopened for mode of input or output.

System actionProcessing continues

ModuleDXCBCLPP, DXCBGTAG


DXC751T Cannot open dataset DDname

ExplanationThe dataset identified by the ddname DDname cannotbe opened.

System actionProcessing terminates abnormally.

User responseCheck that the DD statements are coded correctly. Forinput mode check that the dataset exists and containsthe expected data.

Problem determinationCheck the job log for any additional messages fromMVS or LE.


DXC752I nnn: inputtext

ExplanationDXCBCLPP is processing input line number nnn whichcontains the text inputtext. The entry points definitionfile statement is displayed for information and to aidproblem diagnosis. Line 000 is a scale showing columnoffsets.


ModuleDXCBCLPP

DXC753E Parameter keyword omitted

ExplanationThe keyword parameter is required but has beenomitted from the previous entry points definition filestatement.

System actionProcessing continues but the output is not valid.

Programmer responseAdd the missing parameter to the statement andrerun the job. ALCS Application Programming Guidedescribes how to code the entry points definition file.

Problem determinationCheck the statements displayed in the previousDXC752I messages.

ModuleDXCBCLPP

DXC754E Parameter keyword not recognized

Explanationkeyword was invalid in the position that it occurred oris incorrectly spelled or is not supported.


Programmer responseCorrect the statement and rerun the program. ALCSApplication Programming Guide describes how to codethe entry points definition file.

Problem determinationCheck the statements displayed in the previousDXC752I message.

ModuleDXCBCLPP

DXC755E At least one TRANV must be coded

ExplanationAt least one TRANV statement must be coded followinga BEGIN statement in the entry points definition file.


Programmer responseCode a TRANV statement and rerun the program. ALCSApplication Programming Guide describes how to codethe entry points definition file.


Problem determinationCheck the statements displayed in the previousDXC752I message.

ModuleDXCBCLPP

DXC757T File I/O error occurred

ExplanationAn error occurred when reading, writing orrepositioning on a dataset.


User responseCheck that the input was produced correctly by theprevious job step. Rerun the job.

Problem determinationCheck the job log for any additional messages fromMVS or LE.


DXC758T Error in input file - text

ExplanationAn error was detected while processing the input file.The additional description text indicates how the errorwas detected.


User responseRerun the program. For input from an assembler listingfile check that this is created with a record size of 121and a format of FBM.

Problem determinationAsk your system programmer to inform your IBMprogramming support representative.

ModuleDXCBGTAG

DXC759T Cross reference not found in inputfile

ExplanationNo cross reference was found in the assembler listinginput file.


User responseCheck that the input is a listing assembled usingXREF(FULL).

Problem determinationAsk your system programmer to inform your IBMprogramming support representative.

ModuleDXCBGTAG

DXC760T Not enough storage

ExplanationRequired working storage was not available.


User responseIncrease the region size for the job in the JCL thenrerun the job.

ModuleDXCBGTAG

DXC761T Error(s) detected - Structureunusable

ExplanationIt is not possible to create a valid C language structurebecause of a previous error.



User responseCorrect the previously reported errors.

ModuleDXCBGTAG

DXC765E Only one keyword parameterallowed

ExplanationThe entry points definition file statement containsmore that one occurrence of the parameter keyword.

System actionThis occurrence of the parameter is ignored.Processing continues but the output is not valid.

User responseCorrect the statement and rerun the job. ALCSApplication Programming Guide describes how to codethe entry points definition file.

Problem determinationCheck the statements displayed in the previousDXC752I messages.

ModuleDXCBCLPP

DXC766E HLASM sysadata editionNumberxx not supported

ExplanationThe DXCBGTAG does not support the HLASM version xxused to produce input.

System actionProgram terminates with return code 8.

User responseVerify you are using a valid sysadata file. If thefile is valid, contact your IBM programming supportrepresentative.

ModuleDXCBGTAG

DXC780I No options specified

ExplanationThere were no options specified for the ALCSdiagnostic file processor.

ALCS Operation and Maintenance describes the ALCSdiagnostic file processor options.

System actionThe ALCS diagnostic file processor uses defaultoptions, and processing continues.

ModuleDXCDTP

DXC781T Invalid keyword - Rest ofstatement ignored

ExplanationAn input statement (option) for the ALCS diagnostic fileprocessor contained an invalid keyword.


System actionThe ALCS diagnostic file processor checks theremaining input statements (if any) and then endsabnormally without printing the contents of thediagnostic file(s).

Problem determinationThe ALCS diagnostic file processor prints:

1. The statement that contains the invalid dumpnumber.

2. A line that contains a single asterisk (*) directlyunder the invalid dump number. This line identifiesthe dump number that is invalid.

3. This error message.

ModuleDXCDTP

DXC782T Invalid operand - Rest ofstatement ignored

ExplanationAn input statement (option) for the ALCS diagnostic fileprocessor contained an invalid operand.








ModuleDXCDTP

DXC783T Invalid delimiter - Rest ofstatement ignored

ExplanationAn input statement (option) for the ALCS diagnostic fileprocessor contained an invalid delimiter.







ModuleDXCDTP

DXC784E Too many dump numbers - Rest ofstatement ignored

ExplanationInput statements (options) for the ALCS diagnosticfile processor contained dump numbers, ranges ofdump numbers, or both. There is an upper limiton the total number of dump numbers and rangesof dump numbers. This limit has been exceeded.ALCS Operation and Maintenance describes the ALCSdiagnostic file processor options.

System actionThe ALCS diagnostic file processor uses the optionsincluding dump numbers from the input statement, upto but excluding the number or range of numbers thatexceeded the limit. It ignores any information on therest of the input statement. If there are more inputstatements, then the ALCS diagnostic file processorprocesses them normally.





ModuleDXCDTP

DXC785T Invalid time - Rest of statementignored

ExplanationAn input statement (option) for the ALCS diagnostic fileprocessor contained an invalid time (hours, minutes,and seconds). ALCS Operation and Maintenancedescribes the ALCS diagnostic file processor options.







ModuleDXCDTP

DXC786E Too many times - Rest ofstatement ignored

ExplanationInput statements (options) for the ALCS diagnosticfile processor contained times (hours, minutes, andseconds). There is an upper limit on the totalnumber of times, and this limit has been exceeded.ALCS Operation and Maintenance describes the ALCSdiagnostic file processor options.

System actionThe ALCS diagnostic file processor uses the optionsincluding times from the input statement, up to butexcluding the time that exceeded the limit. It ignoresany information in the rest of the input statement.If there are more input statements, then the ALCSdiagnostic file processor processes them normally.

User responseRun DTP more than once, with subsets of the timesrequired.





ModuleDXCDTP

DXC787T Logic error - Rest of statementignored

ExplanationThere is a program error in the ALCS diagnostic fileprocessor.




1. The statement that contains the invalid keyword2. A line that contains a single asterisk (*) directly

under the point where the program error wasdetected


ModuleDXCDTP

DXC788T Invalid dump number range - Restof statement ignored

ExplanationInput statements (options) for the ALCS diagnosticfile processor contained one or more ranges of dumpnumbers. One of these ranges is not in ascendingsequence.






ModuleDXCDTP


DXC789T Can not obtain storage for inputbuffer - Program terminated

ExplanationThe ALCS diagnostic file processor could not obtainstorage (MVS GETMAIN macro) for the input buffer forthe ALCS diagnostic file.

System actionThe ALCS diagnostic file processor ends abnormally.

User responseIncrease the space allocation on the job controlEXEC statement and resubmit the ALCS diagnostic fileprocessor job.

ModuleDXCDTP


Chapter 4. ALCS generation macro MNOTEs: DXC800-DXC999

DXC800W Number of assigned fixed filetypes cannot exceed 4094 --Please inform IBM that you havereached 3500


System programmer responseInform your IBM programming support representative

DXC801E COMID must be a single alphabeticcharacter


System actionThe stage 2 deck is not created.

System programmer responseCorrect the error and rerun the generation.

DXC802E Parameter v1 conflicts withparameter v2




DXC803E Parameter v1 must be v2hexadecimal digits in range v3through v4




DXC804E Subparameter(s) for parameter v1must be v2 hexadecimal digits inrange v3 through v4




DXC805W No resources defined

ExplanationThis generation does not contain any COMDEFmacroinstructions.



DXC806W Resource v1 has ordinal v2 greaterthan MAXORD





DXC807E v1 has been specified more thanonce

ExplanationThe specified resource v1 has already been specifiedin this communication generation. It can only bespecified once.



DXC808E CRAS CRI v1 not allowed for CRIparameter




DXC809W Return code v1 from uservalidation - User data will bediscarded

ExplanationThe user macro DXCZCUSR has set the global setsymbol USERR to v1. This indicates that the user datais in error.

System actionProcessing continues. No user data is generated forthis resource.

System programmer responseCorrect the error if necessary, and rerun thegeneration.

DXC810E v1 is not valid for v2 parameter




DXC812E v1 is invalid with v2

ExplanationThe specified parameters v1 and v2 are incompatible.One parameter conflicts with the other.



DXC813I v1 is implemented as v2 for v3

ExplanationA parameter that is not required (v1) was specified oran implementation restriction is in effect.

System actionThe values specified are assumed. Processingcontinues.

DXC814I v1 is not implemented - Set to v2

ExplanationALCS does not implement v1.

System actionThe default value v2 is used. Processing continues.

DXC817E Number of terminal-ids must beequal to the number of terminaladdresses specified

ExplanationThe number of entries for the parameters CSID and TAmust be the same.

Chapter 4. ALCS generation macro MNOTEs: DXC800-DXC999 81



DXC819E WTTY full-duplex resource namesmust not be identical

ExplanationThe send and receive sides of a full-duplex WTTYresource must have different LU names.



DXC820E Either parameter v1 or parameterv2 of macro v3 must be specified,but not both

ExplanationParameters v1 and v2 are mutually exclusive. Specifyonly one of them.



DXC821E v1 must not be greater than v2




DXC823E Length of user data was specifiedas '0' on COMGEN macro - Userdata ignored

ExplanationThe USERDAT or USERmm parameter was specifiedwith user data, but the length of the user data fieldspecified by the USERLEN parameter of the COMGENmacro is zero.

System actionThe user data is ignored. The stage 2 deck is notcreated.


DXC824E Return code v1 from uservalidation

ExplanationThe user macro DXCZCUSR has indicated the user datais seriously in error.

System actionThe user data is ignored. The stage 2 deck is notcreated.


DXC825E Total number of WTTY and SLClink resources must not exceed255




DXC827W No corresponding SLC link definedfor remote ALC terminal v1accessed by link v2

ExplanationThis generation does not contain a definition for theSLC link v2 which is required to access v1. This isnot an error if the SLC link was defined in a previouscommunication generation.




DXC828E Parameter COMID must specifyanother system

ExplanationThe parameter COMID must specify the system at theremote end of a link.



DXC829W No corresponding ALCI LU definedfor ALC terminal v1 accessedthrough v2

ExplanationThis generation does not contain a definition for theALCI LU v2 which is required to access v1. This isnot an error if the ALCI LU was defined in a previouscommunication generation.



DXC831W Remote ALC terminal v1 with non-zero IA does not specify a TYPE6X.25 PVC

ExplanationAn X.25 ALC terminal with a non-zero interchangeaddress (IA) can only be accessed through an X.25PVC that is TYPE6.



DXC832W Remote ALC terminal v1 with zeroIA does not specify a TYPE1 X.25PVC

ExplanationAn X.25 ALC terminal with a zero interchange address(IA) can only be accessed through an X.25 PVC that isTYPE1.



DXC833E Remote ALC terminal v1 does notspecify a TYPE1 or TYPE3 SLC link

ExplanationA remote ALC terminal can only be accessed throughan SLC link that is TYPE1 or TYPE3.



DXC834E Duplicate resource name v1

ExplanationThe UPDATE parameter is ADD, but resource v1 isalready defined in this generation.



DXC835E Resource name v1 has duplicateCRI -- v2





DXC836E Resource name v1 has duplicateordinal - v2




DXC837W No message router path specifiedfor ALCS application v1 owned bysystem v2

ExplanationThere is no path specified, in this generation, betweenthis system and the system v2 which owns theapplication v1. This is not an error if the messagerouter path was defined in a previous communicationgeneration.



DXC838W CRI address conflicts withCOMGEN CRIRANGE

ExplanationThe COMGEN macro has specified ranges of CRIaddresses (in the CRIRANGE parameter) that are forthe exclusive use of the ALCS off-line communicationgeneration, but the CRI address is not within any of thespecified ranges.



DXC839W Resource ordinal number conflictswith COMGEN ORDRANGE

ExplanationThe COMGEN macro has specified ranges ofcommunication resource ordinal numbers (in theORDRANGE parameter) that are for the exclusive useof the ALCS off-line communication generation, butthe resource ordinal number is not within any of thespecified ranges.



DXC840S Class clash in generation tablesfor record type v1 - Expected v2;found v3

ExplanationThe ALCS generation macros detected an internal logicerror.


System programmer responseIf this error occurs, inform your IBM programmingsupport representative.

DXC841E Database Lv1 records -Addressability too large -- v2segment(s) required

ExplanationThe number of records of this size has exceeded thesegment addressability capacity.

System actionThe stage 2 deck is not produced.


System programmer responseCorrect the error and rerun the generation. Checkthe SEGMENTS parameter in the DBGEN and DBSPACEmacros. If it is correct, add more segments ofaddressability according to v2.

DXC842E No v1 records allocated

ExplanationALCS requires record types #KPTRI and #CPRCR.For information about these record types, see ALCSInstallation and Customization.



DXC843W Duplicate definition for general filev1 - This definition ignored




DXC844I Number of allocated v1 records(v2) less than migrating records(migrating v1 v3, migratingduplicated v1 v4) - Allocationincreased to v5

ExplanationRefer to ALCS Installation and Customization for anexplanation of pool records migration.


DXC845E General file 0 must be defined forALCS Recoup use

ExplanationRefer to ALCS Installation and Customization forRecoup requirements.



DXC846E Database Lv1 records - Data settoo large - v2 data sets required

ExplanationThe number of records in this data set has exceededVSAM addressing capacity.



System programmer responseCheck the NUMBER parameter in the USRDTA macro. Ifit is correct, split the data set according to v2.

DXC847W Parameter v1 in macro v2defined for pool-type record v3 -Parameter ignored

ExplanationThe specified parameter does not apply to pool-typerecords.



DXC848E Neither v1 nor v2 specified inmacro v3 for record type v4 - Oneof these required





DXC849E Both v1 and v2 specified in macrov3 for record type v4 - Only one ofthese permitted




DXC850E v1 parameter not valid with actionv2 - Macro v3, record type v4




DXC851W VFA options not specified in macrov1 for fixed record type v2 - Fileimmediate assumed




DXC852E Band information specified inmacro v1 not valid - Must be 2, 4,or 6 hexadecimal digits




DXC853E Band information specified inmacro v1 not valid - Must not beall zeros




DXC854E Band information specified inmacro v1 not valid - Conflicts withprevious band information




DXC855S The value of symbol v1 is greaterthan 255 - Can not allocate defaultband





System programmer responseSpecify the fixed record type explicitly, instead oftrying to use the defaults.

DXC856E Action v1 for type v2 in macrov3 conflicts with previous spillrequest




DXC857E No band specified for record typev1




DXC858E v1 records requested for type v2 -Band ordinal(s) chosen allow onlyup to v3




DXC859W Record ID(s) defined but norecords allocated for type v1



System programmer responseCorrect the error if necessary and rerun thegeneration. You can delete record IDs that are nolonger required; ALCS Installation and Customizationexplains how to do this.

DXC860E Percentage change specified onzero record allocation for recordtype v1




DXC861E Band information specified inmacro v1 not valid -- Bands v2 tov3 reserved for system records




DXC862E No band specified for allocatablepool size v1

ExplanationFor the DBGEN macro BAND parameter, there is noband specified for record size v1.


System programmer responseCorrect the error and rerun the generation. Check theBAND parameter in the DBGEN macro. If it is correct,add a band for record size v1.


DXC863E Update to long term poolallocation not allowed afterDBHIST DEFINE_MIGRATE_FROMor DEFINE_NEW

ExplanationSelf-explanatory. See ALCS Installation andCustomization for a full explanation of how to use theDBHIST macro.



DXC864E DBHIST v1 not permitted beforeDBHIST v2




DXC865E You are attempting to delete moretype v1 records than are allocated




DXC866E Only one DBHIST v1 macropermitted




DXC867E DBHIST v1 not permitted withoutDBHIST v2




DXC868E v1 only permitted on first DBHISTmacro




DXC869E One of DBHIST DEFINE_NEW orDBHIST DEFINE_MIGRATE_FROMmust be specified




DXC870E v1 change not permitted

ExplanationA USRDTA ACTION=ADD or ACTION=REPLACEinstruction in the DASD stage 1 generation specifiesa different record size to the original record allocation.




DXC871E Not enough Lv1 LT pool to allow foradditional fixed file and ST records

ExplanationSelf-explanatory. See ALCS Installation andCustomization for a full explanation of how to use theDBHIST macro.



DXC872E Database Lv1 records -- No datasets specified -- v2 data set(s)required

ExplanationFor the DBGEN macro VOLUMES parameter, there is noequal vols specified for record size v1.


System programmer responseCorrect the error and rerun the generation. Check theVOLUMES parameter in the DBGEN macro.

DXC873W Attention - Number of calls ofDBSPACE for any size cannotexceed 475 -- please inform IBMyou have exceeded 400



System programmer responseIf this message occurs inform your IBM programmingsupport representative.

DXC874S Implementation restriction -number of calls of DBSPACE forany size cannot exceed 475



DXC875E Not enough size L3 records forthe whole of allocatable pool -- v2segment(s) required

ExplanationALCS reserves some size L3 records for system use.There are not enough logically-addressable size L3records to enable ALCS to physically access all theaddressable records on the real-time database.


System programmer responseUse the DBSPACE macro to add more addressabilityfor size L3 records if required and rerun thegeneration.

DXC876E Database v1 records -- Data settoo large -- v2 data sets requiredwith maximum of v3 segments ineach

ExplanationThe number of logically-addressable records in thisdata set has exceeded VSAM addressing capacity.



DXC877E Record ID not defined - cannot bedeleted





DXC878E General file v1 not defined -cannot be deleted or replaced




DXC879E General file delete or replacenot allowed before DBHISTDEFINE_MIGRATE_FROM orDEFINE_NEW




DXC880W Attention - Number of assignedfixed file types cannot exceed4094 - Please inform IBM that youhave reached v1




DXC881E ACTION=UNDELETE orACTION=PURGE expected

ExplanationACTION=UNDELETE or ACTION=PURGE are the onlyvalues allowed after ACTION=DELETE for the samerecord type.



DXC882E No preceding ACTION=DELETE

ExplanationACTION=UNDELETE or ACTION=PURGE are onlyallowed after ACTION=DELETE for the same recordtype.



DXC883E v1 not allowed beforeDBHIST DEFINE_MIGRATE_FROMor DEFINE_NEW




DXC884E ACTION=SPILL notallowed after DBHISTDISPENSE_TYPE2_LONG_TERM





DXC885E Spill request conflicts withprevious add/delete request




DXC886E Spill request is only allowed forfixed file




DXC887W A record type v1 with only 1 recordmay cause invalid return fromFACE

ExplanationYou can define a fixed file type having only onerecord. However this can result in ambiguous returnconditions from FACE. On return from FACE registerR00 contains zero if an error occurred or the highestvalid ordinal if it did not. However if there is only 1record in the type then R00 will contain zero in eithercase and it is then impossible to determine if an errorhas occurred.

System programmer responseNo action is required if your application programs donot test for an error return from FACE. However IBMrecommends that you define all fixed file types withmore than one record.

DXC888W Attention - No addressability hasyet been defined for this recordsize.

ExplanationYou have added a new record size using theDBSPACE macro but you need to specify both theVOLUMES and SEGMENTS parameters in order to defineaddressability for the data sets.



DXC889E v1 segments requested for typev2 - Band ordinal(s) chosen allowonly up to v3




DXC890E v1 records requested for type v2 -ST pool directories allow only upto v3



System programmer responseReduce the number of short-term pool records for thissize and rerun the generation.


DXC895E You are attempting to delete moretype v1 records than are allocated




DXC901S Macro v1 missing

ExplanationALCS requires the v1 macro in the stage 1 deck.



DXC902E Subparameter(s) of parameter v1missing

ExplanationRefer to ALCS Installation and Customization for adescription of parameter v1.



DXC903E Parameter v1 missing




DXC904E Parameter v1 invalid or missing

ExplanationFor the USRDTA macro, parameter v1 is invalid ormissing for the record being generated. Ensure thatthe corresponding record size has been definedthrough parameters CISIZE and RECSIZE of the ALCSgeneration macro.

For other macros this message is self-explanatory.



DXC905E Parameter v1 must be an integerin range v2 through v3




DXC906E Parameter v1 must be a positiveinteger




DXC907E Parameter v1 less than v2 orgreater than v3





DXC908E Parameter v1 less than v2

ExplanationParameter v1 must be equal to or greater than v2.



DXC909E Parameter v1 greater than v2

ExplanationParameter v1 must be equal to or less than v2.



DXC910E Parameter v1 must be a validhexadecimal number




DXC911E Invalid subparameter(s) forparameter v1




DXC912E Maximum length for parameter v1is v2 characters




DXC913E Subparameter(s) of parameter v1must be positive integer(s)




DXC914E Parameter v1 has too manysubparameters




System programmer responseDepending on the macro, you may be able todistribute the subparameters between more than onemacroinstruction.

DXC915S Implementation restriction -Dimension v1 of set symbol arrayv2 exceeded executing macro v3


ExplanationThe ALCS generation detected an implementationrestriction. The dimension of an assembler languageset symbol array was not high enough to contain thevariables for this generation.



DXC916W Parameter v1 ignored

ExplanationParameter v1 was not appropriate; ALCS ignores it.



DXC917W Parameter v1 invalid - Default ofv2 assumed




DXC918W Duplicate v1 macro - Ignored




DXC919S Invalid sequence of ALCSgeneration macros

ExplanationThe correct sequence of ALCS generation macros is:

1. ALCS2. JOBCARD3. Macros that describe components (for example,SCTGEN, COMGEN, and so on)

4. ALCSGEN.



DXC920E Parameter v1 must be a decimalnumber with one decimal digit(format N.N or NN.N)




DXC921W Maximum length for parameter v1is v2 characters - Default v3 used




DXC922I Parameter v1 less than v2


ExplanationParameter v1 is usually equal to or greater than v2.


User responseCheck that you do want these values for v1 and v2.

DXC923I Parameter v1 greater than v2

ExplanationParameter v1 is usually equal to or less than v2.


User responseCheck that you do want these values for v1 and v2.

DXC924I Default value v1 used forparameter v2



DXC925S Logic error - Parameter v1 withinvalid value v2 in macro v3

ExplanationThe ALCS generation detected an internal logic error.A generation macro called macro v3 with an incorrectparameter value.



DXC926S Logic error - Invalid parameterspassed to punch macro DXCZV

ExplanationThe ALCS generation detected an internal logic error.A generation macro called macro DXCZV with anincorrect parameter value.



DXC927E Format of parameter v1 must bev2




DXC928E Parameter v1 must be one of v2 ...v10




DXC929E Parameter v1 must not specifyv2 ... v10





DXC930E Subparameters of parameter v1must be hexadecimal numbers




DXC931E Parameter v1 must be v2hexadecimal digits




DXC932E Subparameter v1 of parameter v2invalid

ExplanationRefer to ALCS Installation and Customization for adescription of subparameters for parameter v2.



DXC933W Parameter v1 and parameter v2specified - v2 ignored




DXC934E Parameter v1 must be an integerequal to v2 or greater




DXC935E Parameter v1 omitted - Parameterv2 ignored




DXC936W Parameter v1 must be an integerin range v2 through v3 - Set to v4




DXC937E Neither v1 nor v2 specified inmacro v3 --





DXC938E Both v1 and v2 specified in macrov3 -- Onl




DXC939E Inconsistent number ofsubparameters of parameter v1with subparam

ExplanationThe number of subparameters of v1 and v2 must beequal.



DXC950T ALCS generation terminated due topreviously detected errors




Problem determinationCheck the assembler listing for severity E or Sgeneration messages preceding this one.

DXC951W Too many jobcards specified - Onlythe first v1 used

ExplanationThere are too many parameters (JCL statements) forthe ALCS JOBCARD generation macro.

System actionProcessing continues. The stage 2 deck includes onlythe first v1 JOBCARD macro parameters.


DXC952E Invalid v1 size v2 bytes for size v3records




DXC961S Macro v1 has been called morethan v2 times

ExplanationThere cannot be more than v2 sequential files.



DXC963E File v1 already specified in aprevious call of v2 macro

ExplanationSequential file is already defined.




System programmer responseChange the name of the sequential file or delete thisdefinition.

DXC964E Parameter v1 omitted - Parameterv2 rejected




DXC965W Parameter v1 already specified -This call ignored

ExplanationThis parameter can only be specified once.



DXC965W Parameter v1 already specified -This call ignored

ExplanationThis parameter can only be specified once.



DXC966E v1=v2 conflicts with v3=v4




DXC967W Block size must be exact multipleof record length - BLKSIZE set tov1




DXC968E File specified in the USEparameter is the same as the filespecified in the NAME parameter

ExplanationUSE parameter must refer to another sequential file.



DXC969E Sequential file generation requiresa v1 file

ExplanationALCS requires one (and only one) v1 file in everysequential file generation.




DXC970E Sequential file generation requiresat least one v1 file

ExplanationALCS requires one or more v1 files in every sequentialfile generation.



DXC971E Sequential file v1 cannot use filev2

ExplanationSequential file v1 cannot use file v2 because that file:

• Is the log file, or• Is the diagnostic file, or• Has itself specified USE.



DXC972E v1=v2 conflicts with v3 sequentialfile

ExplanationWhen v3 is INPUT, INPUT data sets:

• Cannot have disposition NEW or MOD• Can only be GENERAL files.

For other values of v3, this message is self-explanatory.



DXC973I 'USE' parameter specified - Filedescription parameters ignored

ExplanationSpecifying a USE parameter on the SEQGEN macroresults in overruling the sequential file's owndescription parameters by those of the sequential filespecified in the USE parameter.


DXC974E Duplicate sequential file_type filedefined in generation

ExplanationYou have tried to code two sequential files on theSEQGEN macro and ALCS does not allow this. Wherefile_type is one of:

DiagnosticLoggingData collection



DXC980E Storage unit size, v1 bytes, mustbe larger than any specifiedcontrol interval size

ExplanationRefer to ALCS Installation and Customization for adescription of storage units.



DXC981E POOLCTL-1 must be less thanPOOLCTL-2

ExplanationThe first subparameter of POOLCTL must be less thanthe second one.




DXC982W Attention - No v1 limit in effect

ExplanationNo limit has been set for variable v1 and the systemlimit is now in effect. This may cause unexpectedresults or adversely affect system performance.



DXC983E Parameter v1 must be specifiedfirst

ExplanationParameter v1 must be the first parameter specified inthe parameter list.



DXC984W DATEFORM parameter is too longfor an IBM 3270 display

ExplanationThe installation default date format defined by theSCTGEN DATEFORM parameter is too long to fit on thebottom line of the IBM 3270 display layout used byALCS.

ALCS will use the date format DD.MM.YY for thedisplay layout instead. The installation default dateformat is not affected.


System programmer responseIf an installation default date format is required onthe bottom line of the IBM 3270 display layout used

by ALCS, then shorten the DATEFORM parameter andrerun the generation.

DXC994S Logic error - Message numberunknown in call to message macro

ExplanationThe ALCS generation detected an internal logic error.A generation macro called the message macro with anunknown message number.



DXC995S Logic error - Invalid component oncall to message macro

ExplanationThe ALCS generation detected an internal logic error.A generation macro called the message macro with anunknown subcomponent code.



DXC996S Logic error - Message numbermust be 3 digits in call to messagemacro

ExplanationThe ALCS generation detected an internal logic error.A generation macro called the message macro with anunknown message number.



DXC997S Logic error - Non-numeric messagenumber in call to message macro


ExplanationThe ALCS generation detected an internal logic error.A generation macro called the message macro with anon-numeric message number.



DXC998S Logic error - Parameter missing incall to message macro

ExplanationThe ALCS generation detected an internal logic error. Ageneration macro called the message macro but therewas a parameter missing.



DXC999S Logic error - Invalid message textin message macro

ExplanationThe ALCS generation macro that generates MNOTEshas detected invalid text in an MNOTE. This is aninternal logic error in the macro.




Chapter 5. ALCS application macro MNOTEs:DXC1000-DXC1999

DXC1001E v1 parameter invalid or omitted

ExplanationParameter v1 is mandatory. The macroinstructioneither omits the parameter or specifies it incorrectly.

System actionThe macro does not expand or expands incorrectly.

Programmer responseCorrect the macroinstruction and resubmit theassembly.

DXC1002W v1 parameter invalid or omitted -v2 used

ExplanationParameter v1 is mandatory. The macroinstructioneither omits the parameter or specifies it incorrectly.

System actionThe macrogeneration proceeds as if themacroinstruction specified v2.


DXC1003I v1 used

ExplanationThis message follows another message.

System actionThe macrogeneration proceeds as if themacroinstruction specified v1.

Programmer responseCorrect the macroinstruction identified by thepreceding message, and resubmit the assembly.

DXC1004E v1 parameter invalid or omitted




DXC1005E Label omitted or invalid

ExplanationThe macroinstruction requires a valid label in the namefield.

System actionThe macroinstruction does not expand or expandsincorrectly.


DXC1010E v1 parameter invalid - Must bealphabetic

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be one or more alphabeticcharacters (A-Z).



DXC1011E v1 parameter invalid - Must benumeric


ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be one or more decimal digits(0-9).



DXC1012E v1 parameter invalid - Must behexadecimal

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be one or more hexadecimal digits(0-9 and A-F).



DXC1013E v1 parameter invalid - Must bebinary

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be one or more binary digits (0 and1).



DXC1014E v1 parameter invalid - Must bealphameric

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be one or more alphabeticcharacters or decimal digits (A-Z and 0-9).



DXC1015E v1 parameter invalid - Firstcharacter must be alphabetic

ExplanationThe macroinstruction specifies parameter v1incorrectly. The first character must be alphabetic (A-Z).



DXC1016E v1 parameter invalid - Too manyentries in sublist

ExplanationSelf explanatory.



DXC1017E v1 parameter invalid - Not enoughentries in sublist

ExplanationSelf explanatory.



Chapter 5. ALCS application macro MNOTEs: DXC1000-DXC1999 103

DXC1020E v1 parameter invalid - Must benumber characters

ExplanationThe macroinstruction specifies parameter v1incorrectly. Its length must be exactly numbercharacters.



DXC1021E v1 parameter invalid - Must benumber1 to number2 characters

ExplanationThe macroinstruction specifies parameter v1incorrectly. Its length must be in the range number1through number2 characters.



DXC1022E v1 parameter invalid - Must bemore than number characters

ExplanationThe macroinstruction specifies parameter v1incorrectly. Its length must be more than numbercharacters.



DXC1023E v1 parameter invalid - Must be lessthan number characters

ExplanationThe macroinstruction specifies parameter v1incorrectly. Its length must be less than numbercharacters.



DXC1024E v1 parameter invalid - Must benumber1 or number2 characters

ExplanationThe macroinstruction specifies parameter v1incorrectly. Its length must be either number1 ornumber2 characters.



DXC1025E v1 parameter invalid - Must benumeric in range number1 throughnumber2

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be specified as one or moredecimal digits (0-9). The value must be in the rangenumber1 through number2.



DXC1030E v1 parameter invalid - Must be'YES' or 'NO'


ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be either YES or NO - ALCS doesnot accept abbreviations Y or N.



DXC1031E v1 parameter invalid - Must be oneof option1 option2 ...

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be one of the listed options,option1, option2, and so on.



DXC1050E Both v1 and v2 parametersspecified

ExplanationThe macroinstruction specifies both parameters v1and v2. The macro allows one or the other, but notboth. ALCS ignores both parameters.



DXC1051W Both v1 and v2 parametersspecified - v2 ignored

ExplanationThe macroinstruction specifies both parameters v1and v2. The macro allows one or the other, but notboth.

System actionThe macrogeneration proceeds as if themacroinstruction omitted v2.


DXC1052E Both v1 and v2 parameters invalidor omitted

ExplanationThe macroinstruction either:

• Specifies both parameters v1 and v2 incorrectly• Omits both parameters v1 and v2• Specifies one of the parameters v1 and v2

incorrectly and omits the other.

The macro requires either one or the other or both.



DXC1053E v1 parameter specified but v2parameter omitted

ExplanationIf you specify parameter v1, you must also specifyparameter v2.



DXC1054E Parameters v1 and v2 conflict





DXC1055E Both positional and keywordparameters specified

ExplanationThe macroinstruction specifies both positionalparameters and keyword parameters. The macroallows one or the other, but not both.



DXC1056E Both positional and keywordparameters specified for v1

ExplanationThe macroinstruction specifies both a positionalparameter and a keyword parameter for v1. The macroallows one or the other, but not both.



DXC1057E Do not combine the followingparameters - Use only one of v1v2 ...




DXC1058E At least one of the followingparameters is required - v1 ... v8




DXC1060W v1 parameter ignored




DXC1061I v1 parameter ignored



DXC1070E No parameters specified

ExplanationThe macroinstruction has no operands.



DXC1071W No parameters specified



System actionThe macroinstruction expands to nothing.


DXC1072I No parameters specified


System actionThe macroinstruction expands to nothing.

Programmer responseIf necessary, correct the macroinstruction andresubmit the assembly.

DXC1073E Too many positional parametersspecified

ExplanationMore positional parameters were specified on themacroinstruction than were expected by the macro.


DXC1080E Register reg not allowed for v1parameter

ExplanationThe macroinstruction specifies register reg forparameter v1. The macro does not allow this register.



DXC1081E v1 not allowed for v2 parameter




DXC1082E v1 not allowed if v2 v3 v4




DXC1083E v1 required if v2 v3 v4




DXC1084E v1 not allowed for v2 v3 v4




DXC1085E v1 required for v2 v3 v4





DXC1086E v1 macro not allowed before firstv2 macro




DXC1087E v1 invalid - Length must bebetween v2 and v3




DXC1090I Dummy macro

ExplanationThe macro is a dummy. That is, the macro does notgenerate any instructions.

System actionNone, the macro does not generate executableinstructions.

DXC1101E Base register invalid or omitted

ExplanationEither the macroinstruction specifies the base registerincorrectly or it omits the parameter that specifies thebase register for the DSECT.



DXC1102W Suffix more than one character -First character used

ExplanationThe macroinstruction incorrectly specifies the suffixfor the DSECT labels. The suffix must be a singlecharacter.

System actionThe macrogeneration proceeds as if themacroinstruction specified only the first character ofthe suffix.


DXC1103E Suffix must not be one of suffix1suffix2 ...

ExplanationThe macroinstruction specifies one of the list ofsuffixes (suffix1 suffix2 ...). The macro does not allowany of these suffixes.



DXC1104E Suffix must not be suffix1





DXC1105W Register 13 (RLD) not specified asbase


System programmer responseIf the error is in an IBM-supplied program, inform yourprogramming support representative.

Programmer responseThis macro is not intended to be called by user-writtenprograms. If you have called it, replace the call;otherwise inform your system programmer.

ModuleMN0SV

DXC1110E Data level invalid or omitted

ExplanationEither the macroinstruction specifies the ECB datalevel incorrectly or it omits the parameter thatspecifies the data level.



DXC1111E Storage level invalid or omitted

ExplanationEither the macroinstruction specifies the ECB storagelevel incorrectly or it omits the parameter thatspecifies the storage level.



DXC1112E ECB level invalid or omitted

ExplanationEither the macroinstruction specifies the ECB data andstorage level incorrectly or it omits the parameter thatspecifies the level.



DXC1113E v1 is not a valid ECB level

ExplanationThe macroinstruction specified v1 for an ECB data orstorage level but v1 is not valid.



DXC1120E Block size invalid or omitted

ExplanationEither the macroinstruction specifies the block sizeincorrectly or it omits the parameter that specifies theblock size.



DXC1121E Record ID invalid or omitted

ExplanationEither the macroinstruction specifies the recordidentifier (ID) incorrectly or it omits the parameter thatspecifies the record ID.




DXC1122E Pool type invalid or omitted

ExplanationEither the macroinstruction specifies the pool recordtype incorrectly or it omits the parameter thatspecifies the pool record type.



Problem determinationSee ALCS Installation and Customization for adiscussion of pool types.

DXC1123W Record ID ambiguous - id used

ExplanationA macro parameter specified the record ID as 2 or4 decimal digits. The macro cannot determine if 2decimal digits represent a 2-character ID or a decimalnumber. Similarly the macro cannot determine if 4decimal digits represent a 4-digit hexadecimal recordID, or a decimal number.

System actionThe macrogeneration proceeds as if the macrospecified ID id.

Programmer responseChange the macroinstruction to specify the recordID in the format X'xxxx' or C'cc', and resubmit theassembly.

DXC1130E Wait error routine invalid oromitted

ExplanationEither the macroinstruction specifies the wait errorroutine incorrectly or it omits the parameter thatspecifies the wait error routine.



DXC1131E Program name invalid or omitted

ExplanationEither the macroinstruction specifies the applicationprogram name incorrectly or it omits the parameterthat specifies the name.



DXC1132E Action invalid or omitted

ExplanationEither the macroinstruction specifies the macro actionincorrectly or it omits the parameter that specifies theaction.



DXC1140E Program prog invalid with macromacro

ExplanationThe macroinstruction refers to application programprog. prog is not a valid application program name formacro macro.




DXC1501W CINFC type invalid or omitted - 'R'used

ExplanationEither the macroinstruction specifies the CINFC typeincorrectly or it omits the parameter that specifiesthe type. Note that the ALCS CINFC monitor-requestmacro does not support CINFC type W (set PSW key tozero).

System actionThe macrogeneration proceeds as if the macrospecified R.

Programmer responseCorrect the macroinstruction, or preferably change theprogram so that it does not use CINFC (see ALCSApplication Programming Guide), and resubmit theassembly.

ModuleCINFC

DXC1502E Parameter n of keypoint listignored

ExplanationThe macroinstruction specifies CINFC type K(keypoint). The nth parameter following the CINFCtype specifies an invalid system keypoint record.

System actionThe macrogeneration proceeds as if themacroinstruction omitted the invalid keypoint.

Programmer responseNote that there is only one ALCS keypoint, systemkeypoint B (CTKB). Specify keypoint B as KEYB.Correct the macroinstruction, or preferably change theprogram so that it does not use CINFC (see ALCSApplication Programming Guide), and resubmit theassembly.

ModuleCINFC

DXC1503E CINFC label invalid or omitted

ExplanationThe macroinstruction specifies CINFC type R (read-only access). The parameter label following the CINFCtype is not a valid CINFC label.



ModuleCINFC

DXC1504E Fast link parameter invalid -ignored

ExplanationThe third positional parameter on the CINFCmacroinstruction is not valid. The only value allowedfor this parameter (if it is specified) is F.



ModuleCINFC

DXC1505W Invalid key restore parameter - 'R'used

ExplanationThe macroinstruction either omits the key restoreparameter, or it specifies the parameter incorrectly.


System actionThe macrogeneration proceeds as if the macrospecified R.


ModuleFILKW

DXC1507E BEGIN macroinstruction invalid oromitted

ExplanationThe application program does not contain a validBEGIN macroinstruction. Every ALCS applicationprogram must include a BEGIN macroinstruction asthe first instruction.



ModuleFINIS

DXC1508E CSECT name changed from name1to name2

ExplanationThe BEGIN macroinstruction at the start of theapplication program started an executable controlsection (CSECT) with name name1. But theFINIS macroinstruction is not in that CSECT.Between the BEGIN macroinstruction and the FINISmacroinstruction there is a CSECT, DSECT, DXD,or COM instruction that starts or continues a controlsection with name name2.


Programmer response• If name2 is the name of a common control section

or an external dummy control section, then modify

the program so that it does not define these controlsections (they are not allowed in ALCS applicationprograms).

• If name2 is the name of an executable controlsection, then modify the program so that it doesnot define the control section (ALCS applicationprograms must not include more than one CSECT).Note that the program may contain a CSECTinstruction that is intended to continue the originalCSECT (for example, following a DSECT) but thatspecifies the wrong CSECT name. To avoid thisproblem, replace the CSECT instruction with anRSECT macroinstruction.

• If name2 is the name of a dummy control section(DSECT), then include an RSECT macroinstructionfollowing the DSECT.

After correcting the program, resubmit the assembly.

Problem determinationALCS Application Programming Guide describes theRSECT macro.

ModuleFINIS

DXC1511W No return - Hardware error branchignored

ExplanationThe macroinstruction requests exit (not return), butincludes a routine address to process the hardwareerror on return from the macro.

System actionThe macrogeneration proceeds as if the hardwareerror branch parameter was omitted.

Programmer responseChoose between the mutually incompatible coursesof action that you have specified, recode the macroaccordingly, and reassemble it. Get the unit serviced.

ModuleSYSRA

DXC1512W No return - File address errorbranch ignored


ExplanationThe macroinstruction requests exit (not return), butincludes a routine address to process the file addresserror on return from the macro.

System actionThe macrogeneration proceeds as if the file addresserror branch parameter was omitted.

Programmer responseChoose between the mutually incompatible coursesof action that you have specified, recode the macroaccordingly, and reassemble it.

ModuleSYSRA

DXC1515E ID table section invalid

ExplanationThe second positional parameter (the ID table section)is invalid.



ModuleRIDIC

DXC1516E Action action invalid for ID tablesection section

ExplanationThe first positional parameter (action) is invalid for theID table section (section) that the second positionalparameter specifies.



ModuleRIDIC

DXC1517E Address parameter only valid foraction set




ModuleRIDIC

DXC1520E Incorrect use of SAVEC macro- program does not use a localprogram work area

ExplanationThe SAVEC macro cannot be used in a program thatdoes not use a local program work area.


Programmer responseSpecify LPW=YES on the BEGIN macro or do not issueSAVEC in this program. Then resubmit the assembly.

ModuleSAVEC

DXC1524E GETMAIN/FREEMAIN not allowedfor v1


ExplanationGETMAIN or FREEMAIN was entered as one of theaction parameters, but the operating system v1 doesnot support the GETMAIN or FREEMAIN function.


System programmer responseIf the error is in an IBM-supplied program, inform yourIBM programming support representative.


ModuleDXCSAVE

DXC1525E Label required for action namelist

ExplanationThe action NAMELIST was entered, but themacroinstruction has no label to define the start of thelist.




ModuleDXCSAVE

DXC1530E Subset token not defined inDXCSER

ExplanationThe SHR or XCL parameter specifies a token (token)that the DXCSER macro does not support. The

tokens that DXCSER supports depend on installationdependent modifications to the DXCSER macro.


Programmer responseIf the token is incorrect, then correct themacroinstruction and resubmit the assembly.

If the token is correct, ask your system programmer tomodify the DXCSER macro to include it.

ALCS Installation and Customization describes how todo this.

ModuleBEGIN

DXC1540E v1 parameter invalid with MF=I

ExplanationThe macroinstruction specifies an in-line parameterlist ("MF=I"). Some parameter specifications areinvalid with an in-line parameter list because theygenerate instructions that update the parameter list.This violates re-entrancy.

The following v1 specifications are invalid with "MF=I":

NUMA, LETA, PREFIXA

The following v1 specifications may be used with"MF=I" provided they do not use register notation:

NUM, LET, PREFIX, TEXTA, BUFFA

Parameter SUB may be used with "MF=I" provided itdoes not specify more than one substitution.


Programmer responseChange the macroinstruction either to use the executeform - default MF or specify MF=(E) - or to avoidregister notation. Then resubmit the assembly.

ModuleWTOPC

DXC1541E Invalid substitution type type


ExplanationThe macroinstruction SUB operand specifies type asa substitution type code. type is not one of the validcodes. Valid type codes are:

HEX, HEXA, HEX4A, DEC, DECA, CHARA, CHAR8A



ModuleWTOPC

DXC1542E Length not allowed withsubstitution type type

ExplanationThe macroinstruction SUB operand specifies a lengthfor substitution data type type. Length is valid only fortypes:

HEX4A, CHARA, CHAR8A



ModuleWTOPC

DXC1543E Format error in substitution datatype,data

ExplanationThe macroinstruction SUB operand specifies invalidformat substitution data data. Valid formats are:

type,datatype,(data,length)

Where data and length can be either an absoluteexpression or a register name in parentheses.



ModuleWTOPC

DXC1544E XNUM parameter conflicts withprevious WTOPC or DCTMSG

ExplanationYou coded different XNUM parameters on WTOPC orDCTMSG macroinstructions in your programs. Do notcode the XNUM parameter on any WTOPC or DCTMSGmacroinstruction other than the first.



ModuleWTOPC

DXC1545E Too many substitution parametersspecified

ExplanationA maximum of 55 substitution specifications areallowed when the macroinstruction specifies theexecute form (MF defaults or MF=(E)).




ModuleWTOPC

DXC1549E The KEYPT parameter must be thesame for all records in a logicalglobal

ExplanationThe KEYPT parameter (by default or as specified byyou) has a different value to the KEYPT parameteron the preceding GO1GO macroinstructions for thislogical global record.

System actionThe macro expands but this logical global will not beloaded successfully by the global record load program.


ModuleGO1GO

DXC1550W Record length is v1 bytes

ExplanationThe length of the record exceeds the size of a 4Krecord.

System actionThe macrogeneration proceeds.

Programmer responseDetermine whether the specified length is correct.

ModuleGO1GO

DXC1551I Global area v1, bytes to load = v2

ExplanationALCS shows the size of each global area.

System actionThe macrogeneration proceeds.

ModuleGO1GO

DXC1552E v1 must be v2 number v3 throughv4

ExplanationThe macroinstruction specifies parameter v1incorrectly. It must be a value between numbers v3and v4, with v2 characteristics.



ModuleGO1GO

DXC1553E END action must be last GO1GOcall

ExplanationThe END parameter is only valid on the last GO1GOmacroinstruction in a program.



ModuleGO1GO

DXC1554E v1 v2 specified more than once

ExplanationYou specified parameter v1 with subparameter v2more than once. You may specify this parametercombination once only in a program.




ModuleGO1GO

DXC1555E START action omitted

ExplanationYou specified a GO1GO macroinstruction before theGO1GO START macroinstruction.



ModuleGO1GO

DXC1556E Minimum length of record is 8bytes

ExplanationThe record length as specified in the LENGTH=parameter is less than the minimum length of 8 bytes.



ModuleGO1GO

DXC1557E Directory slot needed for keypoint

ExplanationYou specified the KEYPOINT=YES parameter, but didnot code the SLOT parameter as well.



ModuleGO1GO

DXC1558E If NUMBER not one then SLOTmust be NONE

ExplanationIf you specify the NUMBER parameter with a valueother than 1 then you must specify the SLOTparameter with a value of NONE.



ModuleGO1GO

DXC1559E There must be at least one LOADaction before any FIELD_SYNCHactions can be processed.

ExplanationYou included a FIELD_SYNCH request but there isno preceding LOAD request for the global recordcontaining the field.



ModuleGO1GO

DXC1560E Last ordinal lower than startordinal


ExplanationYou coded the METHOD=SEQ parameter, but thesecond numeric value, representing the last ordinal,is lower than the first numeric value, representing thestart ordinal.



ModuleGROUP

DXC1561E METHOD=ID is not allowed forprime group




ModuleGROUP

DXC1562E No group refers to this index

ExplanationYou coded an INDEX macroinstruction, but did notdefine a reference in a GROUP macroinstruction.



ModuleINDEX

DXC1570E TIMEC action code v1 not allowedfor specified or defaulted fieldcode




ModuleTIMEC

DXC1575E E-mail parameters omitted

ExplanationThe SOCKC macroinstruction specifiesACTION=EMAILSET but it omits the parameters fore-mail values.



Programmer responseThis macro is not intended to be called by user-writtenprograms. If you have called it, replace the call,otherwise inform your system programmer.

ModuleSOCKC

DXC1576E Too many e-mail parametersspecified

ExplanationThe SOCKC macroinstruction specifiesACTION=EMAILSET but it specifies more than oneparameter for e-mail values.





ModuleSOCKC

DXC1901S Macro logic error - description

ExplanationThere is a logic error in the macrodefinition.Description identifies the error.


Programmer responseIf this error occurs, ask your system programmer toinform your IBM programming support representative.

DXC1902S Macro logic error - DXCCMONrequest code invalid

ExplanationThere is a logic error in a macrodefinition. The macrogenerated a DXCCMON macroinstruction with invalidparameters.



ModuleDXCCMON

DXC1903S Macro logic error - DXCCMONaction invalid or omitted

ExplanationThere is a logic error in a macrodefinition. The macrogenerated a DXCCMON macroinstruction with invalidparameters, or without parameters.



ModuleDXCCMON

DXC1910S DXCURID error - #KPTRI definitioncorrupted

ExplanationDXCURID has modified either or both of thesubscripted global set symbols &DXCFV(1) or&DXCFN(1). These set symbols are reserved forthe ALCS fixed file record type #KPTRI. (The hash(#) character is represented differently by someequipment and it is the EBCDIC X''7B'' character.)


System programmer responseCorrect the DXCURID macrodefinition for yourinstallation.

ALCS Installation and Customization describes how tocode this macrodefinition.

Programmer responseInform your system programmer. This error must becorrected before you attempt to assemble any ECB-controlled program.

DXC1911S DXCURID error - Element countinvalid

ExplanationDXCURID has set the global set symbol &DXCFMincorrectly.






DXC1912S DXCURID error - Value 0 invalid forapplication record type v1

ExplanationDXCURID has set the value 0 for the fixed file recordtype v1. The value 0 is reserved for ALCS fixedfile record type #KPTRI. (The hash (#) character isrepresented differently by some equipment and it isthe EBCDIC X''7B'' character.)





DXC1913S DXCURID error - #CPRCR notdefined

ExplanationDXCURID has not defined the fixed file record type#CPRCR. ALCS requires this fixed file record type. (Thehash (#) character is represented differently by someequipment and it is the EBCDIC X''7B'' character.)





DXC1994S Macro logic error - Messagenumber unknown in call to DXCYU

ExplanationThere is a logic error in a macrodefinition. The macrogenerated a DXCYU macroinstruction with invalidparameters.



ModuleDXCYU

DXC1995S Macro logic error - Messagenumber out of range in call toDXCYU




ModuleDXCYU


DXC1996S Macro logic error - Messagenumber must be 3 digits in call toDXCYU




ModuleDXCYU

DXC1997S Macro logic error - Non-numericmessage number in call to DXCYU




ModuleDXCYU

DXC1998S Macro logic error - Parametermissing in call to DXCYU




ModuleDXCYU

DXC1999S Macro logic error - Invalidmessage text in DXCYU




ModuleDXCYU


Chapter 6. Online monitor messages (ALCS printer):DXC2000-DXC2999

DXC2000E Logic error - Invalid messagenumber or prefix EC-'cccnnn'

ExplanationALCS attempted to send a message with an invalidmessage code, where ccc is the prefix and nnn is themessage number (in an internal format used by CXA0).Either the prefix or the message number is invalid.


System programmer responseCheck that AXA3 is loaded and that the user messageexit program allows this combination of prefix andmessage.

ModuleCXA0

DXC2001E Logic error - Invalid messageparameters

ExplanationALCS attempted to send a message with an invalidparameter list address.


User responseThis message should not occur. If it does, ask yoursystem programmer to inform your IBM programmingsupport representative.

Note:


ModuleCXA0

DXC2002I ALCS V2 System i Version number -System_name

ExplanationALCS sends this message to RO CRAS at systemrestart. The variables are as defined in the ALCSsystem generation.


ModuleCVSN

DXC2003I ALCS state change fromSS1-'state1' to SS2-'state2'starting

ExplanationALCS state change from state1 to state2 is starting.


ModuleCVSN

DXC2004I ALCS in SS-'state' state

ExplanationALCS state change to state has completed.


User responseNone.


ModuleCVSN

DXC2005E Invalid global load message indexNR-'number'

ExplanationA program entered the ALCS ECB-controlled programCGL2 with an invalid application global load messageindex number number.

System actionApplication global area load continues.


Programmer responseThis program is not intended to be called by user-written programs. If you have called it, replace thecall; otherwise inform your system programmer.

ModuleCGL2

DXC2006I Global record load complete

ExplanationThe application global area load routines havecompleted successfully.

ModuleCGL2

DXC2007E Invalid global record type/ordinal- Slot SN-'slot_number' DirectoryDN-'directory_number'

ExplanationThe record address specified for loading into slotslot_number of directory directory_number is an invalidaddress.

"SLOT SN-'NONE'" means that this is the second orsubsequent record of a logical global. (Only the firstrecord has a global area directory slot.)

System actionALCS does not load this record. Application global areaload continues.

Operator responseAsk your system programmer whether this globalrecord is required for successful execution. If it is, thenterminate ALCS using the ZASYS HALT command.

System programmer responseAlter the global load definition programGOAdirectory_number to correct the record addressfor the record to be loaded into slot slot_numberof directory directory_number (ORDINAL and TYPEparameters of the GO1GO macro). Refer to ALCSInstallation and Customization for more details of theapplication global area.

ModuleCGL2

DXC2008E Can not read globalrecord - Fixed file typeFT-'filetype' Ordinal ORD-'ordinal'Slot SN-'slot_number' DirectoryDN-'directory_number'

ExplanationThe application global area load routines were unableto read the record address specified for loading intoslot slot_number of directory directory_number.


System actionNo record is loaded into this slot of directorydirectory_number. Application global area loadcontinues.


System programmer responseDetermine the reason why the read failed: I/O error,record identifier (ID) wrong, or record code check(RCC) wrong. If record ID is wrong, check the ID orIDSYM parameters of the GO1GO macro for this record

Chapter 6. Online monitor messages (ALCS printer): DXC2000-DXC2999 123

in program GOAdirectory_number. Use the ZDFILcommand to display the actual record ID and RCCcharacters in the record.

ModuleCGL2

DXC2009E Can not find global load programPN-'name'

ExplanationThe application global area load routines were unableto find the global load definition program name.

System actionNo records are loaded into the global area directorydefined by this program. Application global area loadcontinues.

Operator responseAsk your system programmer whether these globalrecords are required for successful execution. If theyare, then terminate ALCS using the ZASYS HALTcommand.

System programmer responseEnsure that the global load definition program nameis link-edited into one of the application program loadmodules that are loaded for system-wide use whenapplication global area load is performed.

ModuleCGL2

DXC2010I Global record load starting

ExplanationThe application global area load routines have started.

ModuleCGL2

DXC2011E Invalid directory slot number -Slot SN-'slot_number' DirectoryDN-'0'

ExplanationSlot numbers 0 through 7 in directory 0 are notavailable for application program use.




System programmer responseAlter the global load definition program GOA0 toremove references to slots 0 through 7 of directory 0.Refer to ALCS Installation and Customization for moredetails of the application global area.

ModuleCGL2

DXC2012E Not enough space in globalarea AN-'area_number' -Slot SN-'slot_number' DirectoryDN-'directory_number'

ExplanationThe amount of storage allocated to global areapart area_number is not enough to contain all therequested records. The length of the record to beloaded into slot number slot_number of directorydirectory_number exceeds the free storage available inthis part of the application global area.




System programmer responsePerform another ALCS system configuration generationto redefine the size of this part of the global area.


Or reduce the size and/or number of global recordsloaded by altering the global load definition programsGOA0, GOA1, ... GOAE. Refer to ALCS Installationand Customization for more details of the applicationglobal area and ALCS system configuration generation.

ModuleCGL2

DXC2014E Invalid header strip requestfor keypointable record -Slot SN-'slot_number' DirectoryDN-'directory_number'

ExplanationThe global load definition for slot slot_number ofdirectory directory_number requests header strippingfor a keypointable record that is not the second orsubsequent record of a logical global.




System programmer responseAlter the global load definition programGOAdirectory_number. Correct the header strippingrequest for record to be loaded into slot slot_numberof directory directory_number (HDSTRIP parameter ofthe GO1GO macro). Refer to ALCS Installation andCustomization for more details of the applicationglobal area.

ModuleCGL2

DXC2015E Global load only allowed in idlestate

ExplanationALCS has received a message from a terminal askingfor reload of the application global area but the systemis not in IDLE state.

System actionALCS discards the input message.

Operator responseIf the global area reload is required, change to IDLEstate and repeat the message.

ModuleCGL2

DXC2016E No ALCS globals defined - CheckCGAF

ExplanationThe application global area load routines determinedthat the ALCS global load control program CGAF wasempty.

System actionNo ALCS global records are loaded. Some importantALCS functions, including Recoup, will therefore notwork.

User responseUse the version of CGAF supplied by IBM. If this is atfault, ask your system programmer to inform your IBMprogramming support representative.

Note:


ModuleCGL2

DXC2017I Shared printer acquired - ALCSV2 System i Version number -System_name

ExplanationThe ALCS system called system_name has acquiredthe shared printer on which this message appears.The variables are as defined in the ALCS systemgeneration.



ModuleCPQC

DXC2020E Check entry and retry - If problempersists call supervisor Problemreference information followsSE-number {CTL|OPR}-code PROG-name OFFSET-listing_addressCRN-crn VOLUME volume_serialDSNAME data_set_name MSG-message

ExplanationALCS, an ECB-controlled program, or an applicationprogram has detected an error that causes thetermination of an entry created to service an inputmessage from a display terminal. To prevent theterminal from locking up, this message is sent to theoriginating terminal.

If the entry is terminated by ALCS, or an ECB-controlled program that used a SERRC or a snapcmacro, the problem reference information is a copyof the system error information that ALCS sends toRO CRAS. For an entry terminated by an applicationprogram which used a SYSRA macro, no problemreference information is sent.

NumberDump sequence number, a 6-digit decimalnumber. SE-NODUMP means that there is no dump(usually because the error duplicates a previousdump).

CodeSystem error code; a 6-digit hexadecimal code thatidentifies the type of error.

NameName of the program or ALCS monitor CSECTthat was executing at the time of the error. IfALCS cannot determine the program or monitorCSECT, ALCS prints PSW=psw instead of theprogram name and listing address, where psw isthe corrected program status word (PSW) at thetime of the error. "Corrected" means that ALCS hasreset the instruction address in the PSW to point tothe failing instruction.

Listing_addressOffset of error within the program, a hexadecimalnumber. This address corresponds to the address(LOC) in the assembler listing of the program. Ifan ALCS monitor CSECT was executing at the timeof the error, ALCS prints /kwd>==listing_address,where listing_address is the offset of the errorwithin the ALCS monitor CSECT, a hexadecimalnumber. This address corresponds to the address

(LOC) in the assembler listing of the ALCS monitorCSECT.

crnCRN of the originating terminal. If the CRN is notavailable, ALCS prints CRI-cri instead, where cri isthe CRI of the originating terminal.

Volume_serialVolume serial of the DASD volume that containsthe data set. If there is no dump (number isNODUMP) the volume_serial is not included in themessage.

Data_set_nameData set name of the data set that contains thedump. If there is no dump (number is NODUMP) thedata_set_name is not included in the message.

MessageOptionally, an explanatory message associatedwith the error.

If the program that detected the error used a SERRCor snapc macro instruction with an indirect programname (PROGRAM parameter of the SERRC macro or thePROG parameter of the snapc macro), then:

NameIs the indirect program name (PROGRAM operand),not the name of the program that issued theSERRC macro.

OFFSET-listing_addressIs omitted from the message.

User responseRefer to system error number code in Chapter 13,“System error codes: 000000-000FFF,” on page 302to identify the error condition, or if applicable to anyuser-written documentation.

ModuleCEA2

DXC2021E SE-number CTL-code PROG-nameOFFSET-listing_address CRN-crnVOLUME volume_serial DSNAMEdata_set_name MSG-message

ExplanationALCS has detected an error and written a dump to theALCS diagnostic file.





Listing_addressOffset of error within the program, a hexadecimalnumber. This address corresponds to the address(LOC) in the assembler listing of the program. Ifan ALCS monitor CSECT was executing at the timeof the error, ALCS prints /kwd>==listing_address,where listing_address is the offset of the errorwithin the ALCS monitor CSECT, a hexadecimalnumber. This address corresponds to the address(LOC) in the assembler listing of the ALCS monitorCSECT.





User responseRefer to system error number code in Chapter 13,“System error codes: 000000-000FFF,” on page 302to identify the error condition.

DXC2022E SE-number OPR-code PROG-nameOFFSET-listing_address CRN-crnVOLUME volume_serial DSNAMEdata_set_name MSG-message

ExplanationAn application program or an ECB-controlled monitorprogram has detected an error and ALCS has written adump to the ALCS diagnostic file.




Listing_addressOffset of error within the program, a hexadecimalnumber. This address corresponds to the address(LOC) in the assembler listing of the program. Ifan ALCS monitor CSECT was executing at the timeof the error, ALCS prints /kwd>==listing_address,where listing_address is the offset of the errorwithin the ALCS monitor CSECT, a hexadecimalnumber. This address corresponds to the address(LOC) in the assembler listing of the ALCS monitorCSECT.





If the program that detected the error used a SERRCor snapc macro instruction with an indirect programname (PROGRAM parameter of the SERRC or snapc


macro) then OFFSET-listing_address is omitted fromthe message.

User responseRefer to system error number code in Chapter 13,“System error codes: 000000-000FFF,” on page 302or, if applicable, to user-written documentation toidentify the error condition.

DXC2023E Invalid field synch request- record already synchronized- field displacement fd-field_displacement directory dn-directory_number

ExplanationThe global load definition for the synchronizable globalfield with displacement field_displacement in directorydirectory_number follows the definition of a globalrecord that is synchronizable.

System actionALCS does not set this global field as synchronizable.Application global area load continues.

Operator responseAsk your system programmer whether this field mustbe synchronizable for successful execution. If itmust, then terminate ALCS using the ZASYS HALTcommand.

System programmer responseAlter the global load definition programGOAdirectory_number. Either remove the requestto synchronize the global field with displacementfield_displacement or remove the request tosynchronize the record in the preceding recordload definition. Refer to ALCS Installation andCustomization for more details of the applicationglobal area.

ModuleCGL2

DXC2024E Invalid field synch request -field not contained in last recordloaded - field displacement fd-field_displacement directory dn-directory_number

ExplanationThe main storage address for the synchronizableglobal field with displacement field_displacement indirectory directory_number does not fall within themain storage address range of the previously loadedrecord in directory directory_number.

System actionALCS does not set this global field as synchronizable.Application global area load continues.

Operator responseAsk your system programmer whether this field mustbe synchronizable for successful execution. If itmust, then terminate ALCS using the ZASYS HALTcommand.

System programmer responseAlter the global load definition programGOAdirectory_number. Ensure that each global fieldsynchronization request follows the record loaddefinition for the global record that the global fieldis contained within. Refer to ALCS Installation andCustomization for more details of the applicationglobal area.

ModuleCGL2

DXC2025E Incomplete logical global record- slot sn- 'slot_number' directorydn-'directory_number'.

ExplanationThe global load definition for slot slot_number ofdirectory directory_number is for a record which ispart of a logical global. One or more of the precedingglobal load definitions for this logical global has beenrejected in error, so although this definition is not inerror, ALCS can not load the complete logical global.

System actionALCS does not load this record and no part of thislogical global will be keypointed regardless of theKEYPT parameter value. Application global area loadcontinues.

Operator responseAsk your system programmer whether this logicalglobal is required for successful execution. If it is, thenterminate ALCS using the ZASYS HALT command.


System programmer responseAlter the global load definition programGOAdirectory_number. Examine the previous errormessages relating to this logical global and correctthe errors identified. Refer to ALCS Installation andCustomization for more details of the applicationglobal area.

ModuleCGL2

DXC2026E Inconsistent keypointable settingfor logical global record -slot sn- 'slot_number' directorydn-'directory_number'.

ExplanationThe global load definition for slot 'slot_number ofdirectory_number is for a record which is part of alogical global. This definition has a different value forthe KEYPT parameter to that in preceding global loaddefinitions for this logical global.

System actionALCS does not load this record and no part of thislogical global will be keypointed regardless of theKEYPT parameter value. Application global area loadcontinues.

Operator responseAsk your system programmer whether this logicalglobal is required for successful execution. If it is, thenterminate ALCS using the ZASYS HALT command.

System programmer responseAlter the global load definition programGOAdirectory_number. Examine the previous errormessages relating to this logical global and correctthe errors identified. Refer to ALCS Installation andCustomization for more details of the applicationglobal area.

ModuleCGL2

DXC2030I Pool scan - restart awaited

ExplanationThe ALCS data base scan utility was running whenALCS terminated. It is waiting for a restart entry fromthe user's application.

Operator responseIf it is not convenient to restart the scan, then the scancan be cancelled with the ZDATA CANCEL command.

DXC2031E Pool scan - invalid entry to restartprogram

ExplanationThe restart function of the ALCS data base scan utilitywas entered while restart was not pending.

System actionThe entry is terminated by ALCS.

DXC2032I Pool scan - restarted

ExplanationThe ALCS data base scan utility has been restartedautomatically.

DXC2033E Pool scan - restart error - userprogram PROG-'prog' not loaded

ExplanationThe ALCS data base scan utility is unable to restartautomatically because one or more of the userprograms is not loaded.

Operator responseAfter loading the missing program(s), the scan can berestarted by the ZDRIV CAP6 command. Alternativelythe scan can be cancelled with the ZDATA CANCELcommand.

DXC2034E Pool scan - restart error - errorreturn from user program

ExplanationThe ALCS data base scan utility is unable to restartautomatically because the user's start of scan programis returning the return code 4 (do not proceed withscan).

Operator responseCorrect the error and then restart the scan with theZDRIV CAP6 command. Alternatively the scan can becancelled with the ZDATA CANCEL command.

DXC2035I Pool scan - restart delayed untilNORM state


ExplanationThe ALCS data base scan utility is waiting for anautomatic restart. As the scan was not originallystarted in IDLE state the automatic restart is delayeduntil NORM state is reached.

Operator responseBring ALCS up to NORM state or restart the scan withthe ZDRIV CAP5 command before changing to NORMstate.

DXC2036E Pool scan - restart error - unableto recreate parameter list

ExplanationThe ALCS data base scan utility is unable to restart.There has been corruption of one or both of the loaddump keypoints.

Operator responseCancel the scan with the ZDATA CANCEL command.

DXC2351E MQ Bridge - MQ queue resource isnot active MQ resource CRN-'crn'Queue name QN-'queue_name'

ExplanationThe ALCS MQ bridge facility cannot process a triggermessage because the matching MQ communicationresource is not active.

System actionALCS discards the MQ trigger message.

Operator responseUse the ZACOM command to start the MQcommunication resource.

ModuleDXCMQB

DXC2352E MQ Bridge - MQGET fromrequest queue failed MQresource CRN-'crn' Queuename QN-'queue_name' MQGETCompletion code RC-'return_code'Reason code RSC-'reason_code'

ExplanationThe ALCS MQ bridge facility cannot get a messagefrom the MQ queue queue_name. completion_code andreason_code are the completion code and reason codefrom the MQ MQGET call.

Problem determinationSee the WebSphere MQ for z/OS Messages and Codesfor lists of completion codes and reason codes.

ModuleDXCMQB

DXC2354E MQ Bridge - MQCLOSE failedMQ resource CRN-'crn' Queuename QN-'queue_name' MQCLOSECompletion code RC-'return_code'Reason code RSC-'reason_code'

ExplanationThe ALCS MQ bridge facility cannot close theMQ queue queue_name. completion_code andreason_code are the completion code and reason codefrom the MQ MQCLOSE call.

Problem determinationWebSphere MQ for z/OS Messages and Codes listscompletion codes and reason codes.

ModuleDXCMQB

DXC2356E MQ Bridge - MQOPEN failedMQ resource CRN-'crn' Queuename QN-'queue_name' MQOPENCompletion code RC-'return_code'Reason code RSC-'reason_code'

ExplanationThe ALCS MQ bridge facility cannot open theMQ queue queue_name. completion_code andreason_code are the completion code and reason codefrom the MQ MQOPEN call.


ModuleDXCMQB


DXC2357E MQ Bridge - No CRI found inCorrelId MQ resource CRN-'crn'

ExplanationThe ALCS MQ bridge facility cannot process an inputmessage because there is no terminal CRI.


User responseCheck that the message is being sent to the correctresource, and that all resources are defined in thecommunication generation. Check that the remotesystem is using the correct terminal addressingscheme. By default, ALCS expects the terminal CRI inthe low-order 3 bytes of the MQ correlation identifierfor the input message.

ModuleDXCMQB

DXC2358E MQ Bridge - Invalid CRI foundin CorrelId MQ resource CRN-'crn'CRI-'cri'

ExplanationThe ALCS MQ bridge facility cannot process an inputmessage because either the CRI does not exist inthis system or it does not specify a communicationresource defined by LDTYPE=MQTERM.


User responseCheck that the message is being sent to the correctresource, and that all resources are defined in thecommunication generation. Check that the remotesystem is using the correct terminal addressingscheme. By default, ALCS expects the terminal CRI inthe low-order 3 bytes of the MQ correlation identifierfor the input message.

ModuleDXCMQB

DXC2359E MQ Bridge - Terminal not routed toapplication MQ resource CRN-'crn'Terminal CRN-'crn'

ExplanationThe ALCS MQ bridge facility has received a messagefrom a terminal. The terminal is not routed to anapplication.


Operator responseRoute the terminal to the correct ALCS applicationusing the ZACOM command.

ModuleDXCMQB

DXC2360E MQ Bridge - Application is invalidor inactive MQ resource CRN-'crn'Terminal CRN-'crn' ApplicationCRN-'crn'

ExplanationThe ALCS MQ bridge facility has received a messagefrom a terminal. The terminal is routed to anapplication and either the application name is notdefined to ALCS or the application is inactive.


Operator responseUse the ZDCOM command to check that the MQterminal is routed to the correct application. Usethe ZACOM command to activate the application ifrequired.

ModuleDXCMQB

DXC2361E MQ Bridge - System is notin required state MQ resourceCRN-'crn' Terminal CRN-'crn'Application CRN-'crn'

ExplanationThe ALCS MQ bridge facility has received a messagefrom a terminal. The terminal is routed to anapplication that does not accept messages in thecurrent system state. The SYSSTATE parameter of theCOMDEF macro can specify, for each application, the


minimum system state for the receipt of messages(the default is NORM state).


Operator responseUse the ZDCOM command to check that the MQterminal is routed to the correct application. Use theZACOM command to inactivate the MQ resource toprevent further input messages until ALCS reaches theappropriate system state.

ModuleDXCMQB

DXC2362W MQ Bridge - MQ is not supportedby this ALCS

ExplanationThe ALCS MQ bridge facility cannot process messagesbecause the ALCS system configuration table does notspecify support for MQ.

System actionALCS continues normally but the MQ bridge facility isunavailable.

Operator responseSee ALCS Installation and Customization forinformation on how to configure MQ.

ModuleDXCMQB

DXC2363W MQ Bridge - MQ is not connected toALCS

ExplanationThe ALCS MQ bridge facility cannot process messagesbecause ALCS is not currently connected to MQ.


Operator responseUse the ZCMQI command to connect ALCS to MQ.

ModuleDXCMQB

DXC2364E MQ Bridge - Response queue isnot defined Terminal CRN-'crn' MQresource CRN-'crn'

ExplanationThe ALCS MQ bridge facility cannot send an outputmessage because there is no MQ response queue. Ifthere is an input message associated with this outputmessage, ALCS uses the reply-to queue specified inthe MQ message descriptor for the input message;otherwise ALCS uses the response queue defined inthe communication table for the MQ resource.

System actionALCS discards the output message.

User responseCheck that the MQ resource is correctly specified inthe communication generation.

ModuleDXCMQB

DXC2365W MQ Bridge - MQ interfacesuspended

ExplanationThe ALCS MQ bridge facility cannot process messagesbecause the MQ queue manager has stoppedresponding to ALCS.


Operator responseInform your MQ administrator.

ModuleDXCMQB

DXC2367E MQ Bridge - MQPUT1 failedMQ resource CRN-'crn' Queuename QN-'queue_name' MQPUT1Completion code RC-'return_code'Reason code RSC-'reason_code'


ExplanationThe ALCS MQ bridge facility cannot put a messageon the MQ queue queue_name. completion_code andreason_code are the completion code and reason codefrom the MQ MQPUT1 call.



ModuleDXCMQB

DXC2368E MQ Bridge - Invalid CRIfrom installation-wide exit MQresource CRN-'crn' Queue nameQN-'queue_name' CRI-'cri'

ExplanationThe ALCS MQ bridge facility cannot process aninput message from MQ queue queue_name becauseinstallation-wide monitor exit USRMQB0 returned aninvalid terminal CRI.


User responseCorrect the installation-wide monitor exit.

ModuleDXCMQB

DXC2369E MQ Bridge - MQINQ failedMQ resource CRN-'crn' Queuename QN-'queue_name' MQINQCompletion code RC-'return_code'Reason code RSC-'reason_code'

ExplanationThe ALCS MQ bridge facility started an MQcommunication resource but it cannot getthe attributes of the MQ queue queue_name.completion_code and reason_code are the completioncode and reason code from the MQ MQINQ call.


ModuleDXCMQB

DXC2369E MQ Bridge - MQINQ failedMQ resource CRN-'crn' Queuename QN-'queue_name' MQINQCompletion code RC-'return_code'Reason code RSC-'reason_code'

ExplanationThe ALCS MQ bridge facility started an MQcommunication resource but it cannot getthe attributes of the MQ queue queue_name.completion_code and reason_code are the completioncode and reason code from the MQ MQINQ call.


ModuleDXCMQB

DXC2380E WAS Bridge - WAS ResourceCRN-'crn' ALCS WAS support is notenabled

ExplanationThe ALCS WAS Bridge facility cannot processmessages because the ALCS system configurationtable does not specify support for WAS.

System actionThe WAS Bridge facility is unavailable.

System programmer responseSee ALCS Installation and Customization forinformation on how to configure WAS support.

ModuleDXCWSB

DXC2381E WAS Bridge - WAS ResourceCRN-'crn' ALCS is not connected toWAS


ExplanationThe ALCS WAS Bridge facility cannot processmessages because ALCS is not currently connected toWAS.

System actionThe WAS Bridge facility is unavailable.

System programmer responseUse the ZCWAS command to connect ALCS to WAS.

ModuleDXCWSB

DXC2382E WAS Bridge - WAS ResourceCRN-'crn' (In)activation inprogress

ExplanationThe ALCS WAS resource cannot be activated orinactivated because (In)activation is already inprogress.

Operator responseWait until (in)activation is finished.

ModuleDXCWSB

DXC2383E WAS Bridge - WAS ResourceCRN-'crn' Already active

ExplanationThe ALCS WAS resource cannot be activated becausethe resource is already active.

System actionALCS continues normally.

ModuleDXCWSB

DXC2384E WAS Bridge - WAS ResourceCRN-'crn' Already inactive

ExplanationThe ALCS WAS resource cannot be inactivatedbecause the resource is already inactive.

ModuleDXCWSB

DXC2385E WAS Bridge - WAS ResourceCRN-'crn' Not enough IOCBsavailable

ExplanationThe ALCS WAS resource cannot be activated becausethere are not enough IOCBs available.

System actionThe WAS resource cannot be activated.

Operator responseIf it happens repeatedly, inform your SystemProgrammer.

System programmer responseIncrease the total number of I/O control blocks(IOCBs) in the ALCS system. (See the descriptionof the SCTGEN macro NBRIOB parameter in ALCSInstallation and Customization).

ModuleDXCWSB

DXC2386E WAS Bridge - WAS ResourceCRN-'crn' Register failed Returncode RC-'rc' Reason code RSC-'rsn'

ExplanationThe ALCS WAS resource cannot be activated becausethe OLA Register service failed. Note that the Registername must be an CEC complex unique name.Otherwise the Register will fail with return code 8 andreason code 8.


Problem determinationFor the return codes and reason codes for OLAcallable services see the IBM Information Center forWebSphere® and search for OLA calls return code.

ModuleDXCWSB


DXC2387E WAS Bridge - WAS ResourceCRN-'crn' Register abended

ExplanationThe ALCS WAS resource cannot be activated becausethe OLA Register service abended. See also systemerror 00006B for more details.


System programmer responseInform your IBM local representative.

ModuleDXCWSB

DXC2388E WAS Bridge - WAS ResourceCRN-'crn' Get Connector failedReturn code RC-'rc' Reason codeRSC-'rsn'

ExplanationThe ALCS WAS resource cannot be activated becausethe OLA Get Connector service failed.


Problem determinationFor the return codes and reason codes for OLAcallable services see the IBM Information Center forWebSphere Application Server - Network Deployment(z/OS) and search for OLA calls return code.

ModuleDXCWSB

DXC2389E WAS Bridge - WAS ResourceCRN-'crn' Get Connector abended

ExplanationThe ALCS WAS resource cannot be activated becausethe OLA Get Connector service abended. See alsosystem error 00006B for more details.



ModuleDXCWSB

DXC2390E WAS Bridge - WAS ResourceCRN-'crn' Unregister failed Returncode RC-'rc' Reason code RSC-'rsn'

ExplanationThe OLA Unregister service failed during inactivation ofthe WAS resource.

System actionThe WAS resource will be forcibly inactivated.

Problem determinationFor the return codes and reason codes for OLAcallable services see the IBM Information Center forWebSphere Application Server - Network Deployment(z/OS) and search for OLA calls return code.

ModuleDXCWSB

DXC2391E WAS Bridge - WAS ResourceCRN-'crn' Unregister abended

ExplanationThe OLA Unregister service abended duringinactivation of the WAS resource. See also systemerror 00006B.

System actionThe WAS resource will be inactivated.


ModuleDXCWSB

DXC2392E WAS Bridge - WAS ResourceCRN-'crn' Invalid CRI-'cri'

ExplanationThe ALCS WAS Bridge facility cannot process an inputmessage from WAS resource crn because installation-


wide monitor exit USRWAS3 returned an invalidterminal CRI.



ModuleDXCWSB

DXC2393E WAS Bridge - WAS ResourceCRN-'crn' Send failed Return codeRC-'rc' Reason code RSC-'rsn'Request type RQT-'rqt'

ExplanationThe OLA Send service failed for either RQT 4 - OLASend Request, or RQT 5 - OLA Get Message Data (ALCSresponse).


Problem determinationReturn code 99 indicates that the Send wassuccessful, but the subsequent WAS response wasinvalid. For the return codes and reason codes for OLAcallable services see the IBM Information Center forWebSphere Application Server - Network Deployment(z/OS) and search for OLA calls return code.

ModuleDXCWSB

DXC2394E WAS Bridge - WAS ResourceCRN-'crn' Receive failed Returncode RC-'rc' Reason code RSC-'rsn'Request type RQT-'rqt'

ExplanationThe OLA Receive service failed for either RQT 1 - OLAReceive Request Specific, or RQT 2 - OLA Get MessageData, orRQT 3 - OLA Send Response.


Problem determinationFor the return codes and reason codes for OLAcallable services see the IBM Information Center forWebSphere Application Server - Network Deployment(z/OS) and search for OLA calls return code. Notethat the message "Return code RC-'8' Reason codeRSC-'40' Request type RQT-2" means that the inputmessage cannot fit in any ECB storage. It is likely thateither there is no heap storage available or your heapstorage is too small.

ModuleDXCWSB

DXC2395E WAS Bridge - WAS ResourceCRN-'crn' Receive abendedRequest type RQT-'rqt'

ExplanationThe OLA Receive service abended for either RQT 1 -OLA Receive Request Specific, or RQT 2 - OLA GetMessage Data, or RQT 3 - OLA Send Response. Seealso system error 00006B.



ModuleDXCWSB

DXC2396E WAS Bridge - WAS ResourceCRN-'crn' Send abended Requesttype RQT-'rqt'

ExplanationThe OLA Send service abended for either RQT 4 - OLASend Request, or RQT 5 - OLA Get Message Data (ALCSresponse). See also system error 00006B.




ModuleDXCWSB

DXC2397E WAS Bridge - WAS ResourceCRN-'crn' Invalid TCRN-'crn'

ExplanationThe ALCS protocol type 2 WAS Bridge facility cannotprocess an input message from WAS Resource crnbecause the remote WAS application returned anincorrect subordinate terminal CRN in the correlator.


User responseCorrect the remote WAS application.

ModuleDXCWSB

DXC2400I Message rejected from CRN-crn

ExplanationALCS has received a message from the LU6.1 parallelsession with CRN crn. ALCS cannot pass the messageto the application for one of the following reasons:

• The LU6.1 link is routed to an application and theapplication name is not defined to ALCS.

• The LU6.1 link is routed to an inactive application.• The LU6.1 link is not routed to an application.• The LU6.1 link is routed to an application that does

not accept messages in the current system state.• The SYSSTATE parameter of the COMDEF macro can

specify, for each application, the minimum systemstate for the receipt of messages (the default isNORM state).


Operator responseUse the ZDCOM command to check that the LU6.1 linkis routed to the correct application. Use the ZACOMcommand to activate the application if required. Oruse the ZACOM command to inactivate the LU6.1 link toprevent further input messages until ALCS reaches theappropriate system state.

ModuleDXCOPZ

DXC2401W Application name does not exist

ExplanationALCS has received a message from a terminal. Theterminal is routed to an application and the applicationname is not defined to ALCS.


Operator responseThis error should not occur. If it does, inform yoursystem programmer.

System programmer responseCheck and correct the ALCS communicationgeneration.

ModuleDXCOPZ

DXC2402W Application name not active

ExplanationALCS has received a message from a terminal routedto an inactive ALCS application, and the message is nota CLEAR or PA key entry, or ALCS command.


Operator responseUse the ZROUT command to check that the terminalis routed to the correct ALCS application, and activatethe application, before retrying the message.

ModuleDXCOPZ

DXC2403W Not routed to an application

ExplanationALCS has received a message from a terminal notrouted to an application, and the message is not aCLEAR or PA key entry, or ALCS command.



Operator responseRoute the terminal to the correct ALCS applicationusing the ZACOM or ZROUT commands beforeretrying the message. Refer to ALCS Operation andMaintenance for details of the ZACOM and ZROUTcommands.

ModuleDXCOPZ

DXC2404W Request not processed - Systemrestricted

ExplanationALCS has received a message from a terminal that isrouted to an active application that does not acceptALCS commands in the current system state, andthe message is not a CLEAR or PA key entry, ALCScommand, or answerback. The SYSSTATE parameterof the COMDEF macro can specify for each applicationthe minimum system state for the receipt of messages(default NORM).


User responseWait until ALCS reaches the appropriate state beforeretrying the message.

ModuleDXCOPZ

DXC2405W Logon rejected from LU CRN-'crn' -Unknown LU name

ExplanationAn agent has tried to log on to ALCS (or the networkoperator has issued a VARY LOGON) for the terminalwith LU name crn, but the CRN is not defined to ALCS.


Operator responseAsk your system programmer to check thecommunication generation.

ModuleDXCCOME

DXC2406W Logon rejected from LU CRN-'crn' -Unsupported PS profile

ExplanationAn agent has tried to log on to ALCS (or the networkoperator has issued a VARY LOGON) for the terminalwith LU name crn, but the terminal has an VTAMpresentation services ( PS ) profile that ALCS does notsupport.


Operator responseAsk your VTAM system programmer to check the LUdefinition.

ModuleDXCCOME

DXC2407W Logon rejected from LU CRN-'crn' -Display width not 80 columns

ExplanationAn agent has tried to log on to ALCS (or the networkoperator has issued a VARY LOGON) for the terminalwith LU name crn, but the display width is not 80columns.



ModuleDXCCOME

DXC2408W Logon rejected from LU CRN-'crn' -Requested by installation exit


ExplanationAn agent has tried to log on to ALCS (or thenetwork operator has issued a VARY LOGON) for theterminal with LU name crn, but the installation-widecommunication logon exit routine requested that thelogon is rejected.


System programmer responseIf the attempted logon was legitimate, correct the exitroutine.

User responseContact your airline representative.

ModuleDXCCOME

DXC2409W Logon rejected from LU CRN-'crn' -Incompatible PS profile

ExplanationA logon request was received from ALCSLINK crn,but the link has an VTAM presentation services ( PS )profile that is not valid for an LU type 6.1.



ModuleDXCCOLA

DXC2410W Logon rejected from LU CRN-'crn' -No session available

ExplanationA logon request was received from ALCSLINK crn, butthere are no available parallel sessions.

Or, a logon request was received from a 3270display CRN, but it is defined as an alternate CRASprinter in the communication generation (COMDEFCRAS=APnnn).


Operator responseAsk your VTAM system programmer to check that:

1. LU 6.1 sessions are defined compatibly in ALCS andin the system they communicate with, or

2. 3270 device is defined correctly in ALCS and VTAM.

ModuleDXCCOLA

DXC2411W Logon rejected from LU CRN-'crn' -Response bind unacceptable

ExplanationThis ALCS and the system it communicates with acrossan ALCSLINK are unable to agree on communicationparameters.


Operator responseAsk your VTAM system programmer to check that theLU 6.1 sessions are defined compatibly in ALCS and inthe system they communicate with.

ModuleDXCCOLA

DXC2412W X25PVC XCRN-'crn' unknownTCID-'tcid' IA-'ia' TA-'ta'

ExplanationA message was received on X.25 link crn from aremote terminal, but the terminal is not defined toALCS.

Note: The TCID tcid value is only used for terminaladdressing when the X.25 link is defined with COMDEFPRTCOL=TYPE7. The IA ia value is only used forterminal addressing when the X.25 link is defined withCOMDEF PRTCOL=TYPE6 or TYPE7.

System actionALCS discards the message.



ModuleDXCCOMX

DXC2413W SLC link CRN-'crn' unknownHEX-'hex' TCID-'tcid' IA-'ia' TA-'ta'

ExplanationA message was received on SLC link crn from a remoteALC terminal, but the terminal is not defined to ALCS.An SLC-ID for the remote terminal is constructed usingthe link CRI, high-level network exit address (hex),TCID (tcid), IA (ia), and TA (ta) - the SLC-ID is usedto scan the ALCS DXCSLCTB communication table toretrieve the terminal CRI.



ModuleDXCSLCID

DXC2414W ALCI LU CRN-'crn' unknownLEID-'leid'

ExplanationA message was received on ALCI LU crn from a remoteterminal, but the terminal with LEID leid is not definedto ALCS.



ModuleDXCCOMR

DXC2415W APPC/MVS re-identify failure

ExplanationALCS is unable to re-identify itself as an AdvancedProgram-to-Program Communications/MVS (APPC/MVS) scheduler after an APPC/MVS failure.


User responseStop APPC/MVS and restart it. Otherwise, check yourAPPCPMxx member.

ModuleDXCCOLF

DXC2416I APPC/MVS APPC-LU LUN-'luname'deactivated

ExplanationThe Advanced Program-to-ProgramCommunications/MVS (APPC/MVS) base logical unitwith CRN crn became inactive.


ModuleDXCCOLF

DXC2417I APPC/MVS APPC-LU LUN-'luname'activated

ExplanationThe Advanced Program-to-ProgramCommunications/MVS (APPC/MVS) base logical unitwith CRN crn became active.


ModuleDXCCOLF

DXC2418E APPC/MVS define TP-ID failure

ExplanationALCS is unable to define a local TP-ID.



User responseIf Advanced Program-to-ProgramCommunications/MVS (APPC/MVS) is inactive, start it.Otherwise check your APPCPMxx parmlib member; ifthis is correct, ask your system programmer to informyour IBM programming support representative.

ModuleDXCCOLF

DXC2419E VTAM request to release LULUN-'luname' rejected - LU notVTAM 3270 printer

ExplanationVTAM requested ALCS through the RELREQ exit torelease an LU which is not a 3270-type printer.

System actionALCS ignores the request and returns to VTAM.

Operator responseIf this error occurs, ask your system programmer toinform your IBM programming support representative.

ModuleDXCCOME

DXC2420E VTAM request to release LULUN-'luname' rejected - UnknownLU name

ExplanationVTAM requested ALCS through the RELREQ exit torelease an LU which is not known to ALCS.

System actionALCS ignores the request and returns to VTAM.


ModuleDXCCOME

DXC2421E LU LUN-'luname' logged off -Timeout expired

ExplanationALCS issued a VTAM SEND but VTAM was unable toinitiate the SEND. However VTAM does not inform ALCSof this.

System actionALCS initiates a session termination for this LU.


Note:

GUPI: The next message is also intended forautomated operations.

ModuleDXCCOME

DXC2422W NetView unknown CRN-'crn'

ExplanationA message was received on the NetView Program-to-Program Interface (PPI), but the NetView device is notdefined to ALCS.



ModuleDXCCOMP

DXC2427W Logon rejected from LU CRN-crn -Defined as test resource

ExplanationAn agent has tried to log on to ALCS (or the networkoperator has issued a VARY LOGON) for the terminalwith LU name crn, but the CRN is defined to ALCS as atest resource.




ModuleDXCCOME

DXC2428E VTAM resource CRN-'crn' inactive -nnn messages were queued

Explanationnnn ECB-controlled programs issued a ROUTC orSENDC monitor-request macro to send messages to aVTAM resource. The messages were queued waitingfor transmission, but the resource was inactivatedbefore these messages could be transmitted.

System actionFor each message that was waiting to be transmitted,ALCS detaches the message block from the ECB andreturns control to the entry.

User responseCheck that the resource is correctly defined inthe communication generation. Also check thatall required communication resources are correctlystarted.

ModuleDXCCOME

DXC2429W Request not processed - Largemessage

ExplanationALCS has received a large message in extended formatfrom a terminal which is routed to an applicationowned by another system, and the message is nota CLEAR or PA key entry, or ALCS command. Largemessages are only allowed for applications which areowned by this system.


Operator responseRoute the terminal to the correct ALCS applicationusing the ZACOM or ZROUT commands before retryingthe message.

ModuleDXCOPZ

DXC2430W VTAM resource CRI-cri deleted -logon rejected

ExplanationALCS has received a logon request from CRI cri whilethe resource is being deleted. The logon request isrejected.

System actionALCS ignores the logon request.

Operator responseIdentify the VTAM resource and terminate its sessionwith ALCS using VTAM commands.

ModuleDXCCOME

DXC2480W CRI and/or ORD ranges differ

ExplanationThe ranges of CRI addresses and/or the rangesof resource ordinal numbers defined in thecommunication generation COMGEN macro (forexclusive use by the offline communicationgeneration) have been modified and no longer matchthe ranges that OCTM is inhibited from using.

System actionThe OCTM policing function continues.

User responseIf the ranges of CRI addresses and/or ordinal numbershave been reduced in the ALCS communicationsgeneration, then no action is required (the ranges usedby OCTM will not though change). If the ranges havebeen expanded, they may now include CRIs and/orordinals that are used by communication resourcesmanaged by OCTM. Contact your IBM programmingsupport representative for assistance in resolving anyissues that arise by this change in the CRI and/orordinal ranges.


ModuleCOTE

DXC2481W action is still in progress for CRN-crn

ExplanationThe Online Communication Table Maintenance (OCTM)policing function has identified that this action is stillin progress for CRN crn. This action was submitted toOCTM via the COMTC macro.


User responseA COMTC macro, with this action, should be issuedagain for the CRN crn.

ModuleCOTE

DXC2482W action is still in progress forGROUP-grp

ExplanationThe Online Communication Table Maintenance (OCTM)policing function has identified that this action is still inprogress for GROUP grp. This action was submitted toOCTM via the COMTC macro.


User responseA COMTC macro, with this action, should be issuedagain for the GROUP grp.

ModuleCOTE

DXC2483W record_type records nearlydepleted

ExplanationThe Online Communication Table Maintenance (OCTM)database contains two types of record (record_type).They are Base records and Change records. WhenCOMTC macros are used to add new communicationresources, additional Base and Change records are

required. Although OCTM still has space left foradditional Base and Change records, that space isalmost depleted (less than 100 physical records areavailable).


User responseObtain assistance from your ALCS system programmer.The problem could be caused by insufficient availablesize L3 long-term pool records, or it could becaused by insufficient spare ordinal numbers forcommunication resources. If additional resourceordinals are required, then increase the range ofordinal numbers defined on the MAXORD parameter ofthe ALCS communication generation COMGEN macroand rebuild the initial communication configurationload module. If additional size L3 long-term poolrecords are needed, then run Recoup. If not enoughsize L3 long-term pool records are returned byRecoup, then increase the number of available size L3long-term pool records by expanding the database.

ModuleCOTE

DXC2484I action is still outstanding for CRN-crn

ExplanationThe Online Communication Table Maintenance (OCTM)policing function has identified that this COMTC actionhas been outstanding for CRN crn for more than 48hours.


User responseA COMTC macro, with this action should be issued forthe CRN crn. This message will be repeated every 8hours until this COMTC action has been performed forthis CRN crn.

ModuleCOTE

DXC2485I action is still outstanding forGROUP-grp


ExplanationThe Online Communication Table Maintenance (OCTM)policing function has identified that this COMTC actionhas been outstanding for GROUP grp for more than 48hours.


User responseA COMTC macro, with this action should be issued forthe GROUP grp. This message will be repeated every 8hours until this COMTC action has been performed forthis GROUP grp.

ModuleCOTE

DXC2486I ACOM Communication loadmodule module confirmed audittrail

ExplanationThis message is a normal response to the ZACOMCONFIRM command.


DXC2487I ACOM Communication loadmodule module backed out audittrail

ExplanationThis message is a normal response to the ZACOMBACKOUT command.


DXC2488I ACOM Communication loadmodule module loaded audit trail

ExplanationThis message is a normal response to the ZACOMLOAD command.


DXC2489I CRAS status removed fromCRN-'crn' CRI-'cri' CRAS statuswas CT2-'old_cras_type' - Changedby name

ExplanationThe ALCS operator used the ZACOM command toremove CRAS status (old_cras_type) from the resourcewith CRN crn and CRI cri. name is the CRN of thedisplay terminal where the ZACOM command wasentered.)

System actionALCS processing continues with the new CRAS status.

ModuleCOMB

DXC2490I CT-'cras_type' is now on CRN-'crn'CRI-'cri' CRAS status wasCT2-'old_cras_type' - Changed byname

ExplanationOne of the following has occurred:

• ALCS has detected that the Prime or RO CRAS(cras_type) terminal has been lost, and has fallenback to an alternative terminal with CRN crn and CRIcri (name is ALCS.)

• b) The ALCS operator used the ZACOM commandto assign or transfer CRAS status (cras_type) to theresource with CRN crn and CRI cri. (name is the CRNof the display terminal where the ZACOM commandwas entered.)

System actionALCS processing continues with the new CRAS status.

Operator responseIf name is ALCS then ask your network operator toinvestigate the relevant line or terminal for possiblemalfunction.

ModuleCOMB

DXC2501E No fallback available for PrimeCRAS CRN-'crn'


ExplanationAn error has occurred on Prime CRAS with CRN crn andALCS cannot find a suitable alternate CRAS terminalfor fallback.

System actionALCS sends this message to the current RO CRASterminal and terminates CRAS fallback processing.

User responseCheck that the CRASs are correctly specified in thecommunication generation tables, and that at leastone display and one printer with alternate CRAS AT1through AT16 status are available for fallback whileALCS is running.

ModuleCXE0

DXC2502W CRI-'cri' CRN-'crn' RC-'rr' FB2-'ff'SC-'ssmmuuuu' - Negativeresponse received

ExplanationALCS has detected a negative response in the ALCScommunication receive post-interrupt routine for aVTAM terminal or WTTY link with CRI cri and CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.

System actionALCS attempts to recover from the error. This actioncan include, but is not restricted to, the following:

Bracket errorThe bracket state is reset.

State errorThe session is reset.

Some errors may cause the session to be terminatedor become unusable.

Operator responseAsk your network operator to investigate the relevantLU 6.1 link for possible malfunction.


ModuleDXCCOMR

DXC2503W CRI-cri CRN-crn RC-'rr' FB2-'ff'SC-'ssmmuuuu' - Non-zeroRTNCD/FDBK2 received

ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication receive (synchronous data flow) post-interrupt routine for a VTAM terminal or WTTY link withCRI cri and CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.








ModuleDXCCOMR

DXC2504W CRI-'cri' CRN-'crn' RC-'rr' FB2-'ff'SC-'ssmmuuuu' - Non-zeroRTNCD/FDBK2 received

ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication receive (asynchronous data flow) post-interrupt routine for a VTAM terminal or WTTY link withCRI cri and CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.







ModuleDXCCOMR


ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication receive (response) post-interruptroutine for a VTAM terminal or WTTY link with CRI criand CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.







ModuleDXCCOMR

DXC2506W CRI-'cri' CRN-'crn' RC-'rr' FB2-'ff'SC-'ssmmuuuu' - Non-zeroRTNCD/FDBK2 received on CLEARrequest - LU logged off


ExplanationALCS has detected a non-zero return code or a non-zero feedback code from VTAM after issuing a Clearrequest during error recovery for a VTAM terminal withCRI cri and CRN crn.

rrVTAM return code


ssSystem sense


uuuuUser sense.

System actionALCS terminates the session with the LU.

Operator responseAsk your network operator to investigate the relevantline or terminal for possible malfunction.


ModuleDXCCOMS

DXC2507W CRI-'cri' CRN-'crn' RC-'rr' FB2-'ff'SC-'ssmmuuuu' - Non-zeroRTNCD/FDBK2 received on SDTrequest - LU logged off

ExplanationALCS has detected a non-zero return code or a non-zero feedback code from VTAM after issuing a StartData Traffic request during error recovery for a VTAMterminal with CRI cri and CRN crn.

rrVTAM return code


ssSystem sense


uuuuUser sense.

System actionALCS terminates the session with the LU.

Operator responseAsk your network operator to investigate the relevantline or terminal for possible malfunction.


ModuleDXCCOMS


ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication send post-interrupt routine for a VTAMterminal with CRI cri and CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.








ModuleDXCCOMS

DXC2509W CRI-'cri' CRN-'crn' RTNCD-'rr'FDBK2-'ff' SENSE-'ssmmuuuu' -Non-zero RTNCD/FDBK2 receivedon CLSDST or TERMSESS

ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication session termination post-interruptroutine for a resource with CRI cri and CRN crn.

rrACF/VTAM return code

ffACF/VTAM feedback 2 code

ssSystem sense


uuuuUser sense.

Operator responseContact your network operator to investigate therelevant line or terminal for possible malfunction.


ModuleDXCCOME


ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication WTTY send post-interrupt routine fora WTTY link with CRI cri and CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.







ModuleDXCCOMS

DXC2511W CRI-'cri' CRN-'crn' SC-'ssmmuuuu'LEID-'leid' - ALCI - Sense datareceived

ExplanationALCS has received sense data for an ALCI supportedterminal with CRI cri and CRN crn:

ssSystem sense



uuuuUser sense

leidALCI logical end-unit identifier (LEID).

System actionALCS ignores the sense data.

Operator responseIf this message occurs frequently, ask your networkoperator to investigate the relevant line or terminal forpossible malfunction.

Problem determinationVTAM Programming and VTAM Reference Summary forthe installed version and release of VTAM describethe sense data. See also ALCI Diagnosis Guide andReference for the meaning of sense code PIU.

ModuleDXCCOMR


ExplanationALCS has detected a non-zero return code or anon-zero feedback code from VTAM in the ALCScommunication ALCSLINK post-interrupt routine foran LU 6.1 link with CRI cri and CRN crn:

rrVTAM return code


ssSystem sense


uuuuUser sense.







ModuleDXCCOMR, DXCCOMS

DXC2513W CRI-'cri' BATAP retry limitexceeded

ExplanationBATAP for resource CRI cri did not receive any BATAPacknowledgment (IMA). As a result, the number ofretries exceeded the threshold value determined in thebilateral agreement with SITA and set by means of theZACOM command.

System actionALCS processing continues and BATAP continues.

User responseThis error should only occur if the SITA high-level network ( HLN ) is not available; ask yoursystem programmer to inform your high-level-networksupport representative.

ModuleCBQC

DXC2514E CRI-'cri' BATAP lockout

ExplanationBATAP for resource CRI cri cannot transmit messagesbecause of a lockout condition.

System actionALCS processing continues but BATAP is unusable.


User responseTerminate and re-establish the session.

ModuleCBQC

DXC2515I CRI-'cri' BATAP connected

ExplanationThe session for resource CRI cri is established.


ModuleCBQC

DXC2516W CRI-'cri' BATAP disconnected

ExplanationThe session for resource CRI cri is terminated.


ModuleCBQC

DXC2517I CRN-'crn' KCN-'kcn' line out ofservice

ExplanationChannel kcn of SLC link crn has gone down.

System actionALCS brings the channel back into service when thechannel down timeout expires.

ModuleDXCSLCIN

DXC2518I CRN-'crn' link in control state -Data suspended

ExplanationA stop link control block (LCB) was received for thelast operating channel of SLC link crn. The link cannot

transmit or receive link data blocks (LDBs) until aresume LCB is received.

ModuleDXCSLCIN

DXC2519W CRN-'crn' lost AML for messagelabel LBL-'mm' type MT-'t'

ExplanationAfter transmitting a multiblock type t message on SLClink crn with output message label mm, no AML wasreceived during the timeout interval after all blocks ofthe message were acknowledged.

System actionFor Type A messages, ALCS clears the output messagelabel and discards the message. For Type B messages,ALCS clears the output message label and retransmitsthe message with possible duplicate message ( PDM )indication.

Operator responseIf this message occurs frequently, ask your systemprogrammer to inform your high-level-networksupport representative.

ModuleDXCSLCIN

DXC2520W CRN-'crn' KCN-'kcn' LCB receivedwith illogical or reset ATSI

ExplanationA link control block (LCB) was received on channel kcnof SLC link crn. The LCB has a transmission sequencenumber ( TSN ) in the ATSI field that is not in the range'last acknowledged TSN ' to 'last sent TSN '. That is,the LCB acknowledges a block, but either ALCS hasalready received an acknowledgment or ALCS has notyet sent the block.

System actionALCS discards the LCB. If it is an enquiry, ALCS setsthe link down.



ModuleDXCSLCIN

DXC2521I CRN-'crn' KCN-'kcn' line in service

ExplanationExchange of idle link control blocks (LCBs) has beenestablished on channel kcn of SLC link crn.

ModuleDXCSLCIN

DXC2522I CRN-'crn' data transmissionrestarted

ExplanationExchange of resume link control blocks (LCBs) hasbeen established on at least one channel of SLC linkcrn. The link is able to transmit or receive link datablocks (LDBs).

ModuleDXCSLCIN

DXC2523I CRN-'crn' stop all received

ExplanationA 'stop all channels' link control block (LCB) wasreceived on SLC link crn.

System actionALCS sends an enquiry LCB on each operating channelof the link.

ModuleDXCSLCIN

DXC2524I CRN-'crn' KCN-'kcn' stop received

ExplanationA stop link control block (LCB) was received forchannel kcn of SLC link crn. The channel cannottransmit or receive LDBs until a resume LCB isreceived.

ModuleDXCSLCIN

DXC2525I CRN-'crn' link down

ExplanationEither:

• ALCS has stopped the link in response to a ZLSTP (orpossibly a ZASYS) command

or:• ALCS detected a condition on the SLC link that

requires ALCS to stop the link temporarily. In thiscase, ALCS automatically restarts the link when thechannel down timeout expires.

System actionALCS stops transmitting or receiving on the link.Depending on the reason, ALCS may restart the linkwhen the channel down timeout expires.

ModuleDXCSLCIN, CMC1

DXC2528I CRN-'crn' resume all received

ExplanationA 'resume all channels' link control block (LCB) wasreceived on SLC link crn.

System actionALCS processes the LCB as if a resume LCB wasreceived on each channel of the link.

ModuleDXCSLCIN

DXC2529W CRN-'crn' block found after blockwith last block set - Type MT-'t'

ExplanationDuring receipt of a multiblock type t message on SLClink crn, a block was received with the 'last block'indicator on in the link envelope, before the blockwhich completed the message.

System actionALCS discards the message and clears the relevantinput message label.



ModuleDXCSLCIP

DXC2530W CRN-'crn' incomplete type MT-'t'message received

ExplanationDuring receipt of a multiblock type t message onSLC link crn, no block was received with the 'lastblock' indicator set on in the link envelope, during thetimeout interval after receiving the previous block.

System actionALCS discards the message and clears the relevantinput message label.


ModuleDXCSLCIP

DXC2531W CRN-'crn' type MT-'t' output MBIexhaustion

ExplanationA multiblock type t message is ready to be transmittedon SLC link crn, but there is no free type t outputmessage label available for ALCS to use in themessage block indicator (MBI).

System actionALCS replaces the multiblock message on the SLC linkoutput queue, for subsequent transmission when anoutput message label becomes available.


ModuleDXCSLCOU

DXC2532W CRN-'crn' KCN-'kcn' invalid LCBreceived - LSI-'lsi'

ExplanationA link control block (LCB) was received on channelkcn of SLC link crn. The LCB has an invalid link statusidentifier ( LSI ). The contents of the LSI field are lsi.

System actionALCS discards the LCB.


ModuleDXCSLCIN

DXC2533W CRN-'crn' KCN-'kcn' lost ETB

ExplanationA synchronous (SYN) character was found withinmessage data received on channel kcn of SLC linkcrn, or an end-of-message (ETB) character was notreceived within 255 characters from the start-of-message (DLE) character.

System actionALCS discards the data.


ModuleDXCSLCIP

DXC2534W CRN-'crn' KCN-'kcn' lost DLE

ExplanationMessage data received channel kcn of SLC link crn wasnot preceded by a start-of-message (DLE) character.

System actionALCS discards the data.



ModuleDXCSLCIP

DXC2535W CRN-'crn' message received withinvalid MBI - MBI-'mbi'

ExplanationA message block was received on SLC link crn. Themessage block has an invalid message block indicator(MBI). The contents of the MBI field are mbi.

System actionALCS acknowledges the message block, then discardsit.


ModuleDXCSLCIP

DXC2536W CRN-'crn' KCN-'kcn' line in loop

ExplanationA link control block (LCB) was received on channel kcnof SLC link crn. The LCB has the loop test bit value foroutgoing LCBs.


User responseCheck the ALCS communication generation todetermine the value and use of the loop test bit forthe link. Use the ZLTST command to bypass the loopbit test for the link if required.

ALCS Operation and Maintenance describes the ZLTSTcommand.

ModuleDXCSLCIN

DXC2537I CRN-'crn' all channels non-functioning - Cycled down

ExplanationThe last operating channel of SLC link crn has beenstopped by the operator, or by ALCS during systemstate change.

System actionALCS stops transmitting or receiving on the link. Otherprocessing continues (depending on the system state).

ModuleCMC5

DXC2538W CRN-'crn' KCN-'kcn' EIB-'eib'received on LCB

ExplanationA link control block (LCB) was received on channel kcnof SLC link crn. The LCB has a non-zero error indexbyte ( EIB ). The contents of the EIB field are eib.



ModuleDXCSLCIP

DXC2539W CRN-'crn' KCN-'kcn' short blockreceived - X'hex_data'

ExplanationA block of less than 4 bytes was received on channelkcn of SLC link crn. The contents of the block arehex_data.

System actionALCS discards the block.



ModuleDXCSLCIP

DXC2540W CRN-'crn' KCN-'kcn' AML receivedfor unused MBI-'mm'

ExplanationAn acknowledge message label ( AML ) link controlblock (LCB) was received on channel kcn of SLC linkcrn. The AML refers to unused output message blockindicator (MBI) mm.


ModuleDXCSLCIN

DXC2543W CRN-'crn' KCN-'kcn' block receivednot LCB or LDB - X'hex_data'

ExplanationA block was received on channel kcn of SLC link crn.The block is not a link control block (LCB) or a link datablock (LDB). The contents of the block are hex_data.

System actionALCS discards the block.


ModuleDXCSLCIP

DXC2544W CRN-'crn' KCN-'kcn' repeatedNAK received and discarded -X'hex_data'

ExplanationTwo negative acknowledgment link control blocks(LCBs) have been received on channel kcn of SLC linkcrn with the same value in the ATSI field and withoutany other intervening LCB. The contents of the LCB arehex_data.



ModuleDXCSLCIP

DXC2545I CRN-'crn' no messages receivedduring previous 15 mins

ExplanationNo message has been received on SLC link crn duringthe previous 15 minutes, and at least one channelof the link has been operating for the whole of thatperiod.

Operator responseInform your network operator.

ModuleDXCSLCTM

DXC2546I CRN-'crn' no messages sent duringprevious 15 mins

ExplanationNo message has been sent on SLC link crn during theprevious 15 minutes, and at least one channel of thelink has been operating for the whole of that period.

Operator responseInform your network operator.

ModuleDXCSLCTM

DXC2547I SLC send side error - Recovered -KCN-'kcn' LINK CRN-'crn' OP-'oo'SC-'ss' CC-'cc' CSW-'csw'

ExplanationThe send side channel program for channel kcn of SLClink crn has terminated with a recoverable I/O error:

ooOperation code of failing operation

ssOne byte of sense data from the communicationcontroller


ccSTART IO ( SIO ) condition code for channelprogram

cswChannel status word (CSW) for the failingoperation.

System actionALCS restarts the channel program.


Problem determination3705 EP Generation and Logic Manual for LICRAdescribes these operation codes, sense data, and CSWstatus indicators.

ModuleCML2

DXC2548W SLC send side error - Line closed- KCN-'kcn' LINK CRN-'crn' OP-'oo'SC-'ss' CC-'cc' CSW-'csw'

ExplanationThe send side channel program for channel kcn of SLClink crn has terminated with a unrecoverable I/O error:





System actionALCS closes the channel.



ModuleCML2

DXC2549I SLC receive side error - Recovered- KCN-'kcn' LINK CRN-'crn' OP-'oo'SC-'ss' CC-'cc' CSW-'csw'

ExplanationThe receive side channel program for channel kcn ofSLC link crn has terminated with a recoverable I/Oerror:





System actionALCS restarts the channel program.



ModuleCML2

DXC2550W SLC receive side error - Line closed- KCN-'kcn' LINK CRN-'crn' OP-'oo'SC-'ss' CC-'cc' CSW-'csw'


ExplanationThe receive side channel program for channel kcn ofSLC link crn has terminated with a unrecoverable I/Oerror:





System actionALCS closes the channel.



ModuleCML2

DXC2551E Invalid action code ACT-'x' inemergency exit

ExplanationThe emergency exit was entered with incorrect entryconditions. Action code x is invalid.

User responseThe emergency exits are not intended for use in user-written programs. If the error is in an IBM-suppliedprogram then ask your system programmer to informyour IBM programming support representative.

ModuleCLQC

DXC2552E No response from link CRN-'crn'

ExplanationALCS has received no response from an LU 6.1 linkwith CRN crn.

System actionALCS updates its communication tables to indicatethat the link is unusable.


ModuleCLQC

DXC2553E No response from printerCRN-'crn'

ExplanationALCS has received no response from VTAM for aprinter with CRN crn, after transmitting the lastmessage segment three times.

System actionALCS updates its communication tables to indicatethat the printer is unusable. If the printer is an ALCdevice, then ALCS sends it a test message at intervalsto solicit a possible response.


ModuleCPQC

DXC2554A VTAM operator has issued halt- Halt ALCS with 'ZASYS HALT'command

ExplanationThe VTAM operator has halted the VTAMcommunication network. VTAM cannot completetermination until all sessions with ALCS areterminated.


System actionALCS processing continues. ALCS sends messageDXC204A to the MVS console (see “DXC204A” on page31).

Operator responseHalt ALCS as soon as possible.

ModuleDXCCOME

DXC2555I Test message - Please ignore

ExplanationALCS received no response from an ALC or NetViewprinter on the VTAM network after transmitting the lastmessage segment three times.

System actionALCS has updated its communication tables to indicatethat the printer is unusable, and sends this messageto solicit a possible response from the printer. ALCSrepeats this message at intervals until a responseis received or until the LU that controls the printerbecomes inactive.

ModuleCPQC

DXC2557W Incorrect CRI in RCR record - CRN-crn Old CRI-oldcri, New CRI-newcri

ExplanationWhen ALCS verified the status of the resource controlrecord (RCR) it just retrieved, it encountered the wrongCRI inside the record.

Attention: This error can have serious consequences.

System actionALCS re-initializes the record according to the resourcedefinition in the ALCS communication generation.

User responseCheck the ALCS communication generation for apossible shift in ordinals allocated during ALCS start.Check with your system programmer whether toshutdown the ALCS system immediately to correctthe error in the ALCS communication generation or tocontinue.

If the ALCS communication generation does not showany ordinal shift, ask your system programmer toinform your IBM programming support representative.

ModuleCQS1

DXC2650E Sequential file seq I/O errordev,ty,ddname,operation,error,address,BSAM DSN-'data_set_name'VS-'volume_serial'

ExplanationAn unrecoverable I/O error occurred during a reador write operation for an ALCS sequential file dataset. seq is the symbolic name of the sequential file;data_set_name and volume_serial are the name andvolume serial of the data set. data_set_name is one ofthe following:




This message includes the error description returnedby the MVS SYNADAF macro, where:

devUnit address, or 'JES' if the data set is SYSIN orSYSOUT

tyDevice type, as follows:UR

Unit recordTA

Magnetic tapeDA

DASDddname

DD name (allocated by MVS)operation

Failing I/O operationerror

Description of erroraddress

Depends on device type, as follows:Unit record

Not applicable (asterisks)


Magnetic tapeDecimal relative block number

DASDHexadecimal record address (BBCCHHR).

System actionALCS continues processing normally. If the sequentialfile is a system or real time sequential file then ALCSswitches the sequential file to a new data set. Ifthe error occurred when an ECB-controlled programissued a TOURC, TOUTC, or TWRTC monitor-requestmacro then ALCS terminates the entry. If the erroroccurred when an ECB-controlled program issued aTPRDC or TDTAC monitor-request macro then ALCSsets indicators in the ECB I/O error indicator fieldsEBCSDn and CE1SUG for the entry.

Operator responseCheck the EREP listing for more information about theI/O error and if necessary get the unit serviced.

ModuleDXCSEQP

DXC2651I Sequential file seq switchcomplete DSN-'data_set_name'VS-'volume_serial'

ExplanationALCS has switched real-time sequential file outputfrom one data set to another. seq is the symbolicname of the sequential file; data_set_name andvolume_serial are the data set name and volume serialof the old (switch from) data set. This message ispart of the normal response to the ZSSEQ command.ALCS also displays this message on the RO CRASwhen an automatic sequential file switch completes.An automatic sequential file switch happens whenALCS writes more than a specified number of blocksto a sequential file data set. The number of blocks isspecified in the ALCS sequential file generation.

ModuleDXCSEQP

DXC2652E Sequential file seq switch faileddue to allocate error Return code-X'nnnnnn'

ExplanationAn error occurred when ALCS attempted to switchreal-time sequential file output from one data set to

another. seq is the symbolic name of the sequentialfile. This message is an error response to the ZSSEQcommand. ALCS also displays this message on the ROCRAS when an automatic sequential file switch fails.An automatic sequential file switch happens whenALCS writes more than a specified number of blocksto a sequential file data set. The number of blocks isspecified in the ALCS sequential file generation. Seemessage DXC056E for an explanation of return_code.

ModuleDXCSEQP

DXC2653I LOGALL now active, all databaseupdates are being logged

ExplanationThis message is part of the normal response to theZSSEQ LOGALL command.

ModuleCTSW

DXC2654I LOGALL inactive, database loggingis normal

ExplanationThis message is part of the normal response to theZSSEQ NOLOGALL command.

ModuleCTSW

DXC2750W Attempted access to unavailablegeneral file NR-'gf_number' -Program PN-'name'

ExplanationAn ECB-controlled program issued a request to reador write general file gf_number. This general file is notavailable to ALCS, that is the data set is not allocatedto the ALCS system.

System actionALCS treats this read or write request as if the fileaddress was invalid.

Operator responseIf the application has not already terminated, cancelthe application issuing the read or write request. Thenuse the ZDASD VARY ONLINE command to make


the general file available to ALCS and restart theapplication function.

ModuleDXCFAR

DXC2751I DASD data set allocated,Volume VS-'volume_serial',DSN-'data_set_name'

ExplanationMVS has allocated data set data_set_name on volumevolume_serial to ALCS as requested by a ZDASD VARYONLINE command.

System actionIf this data set is a general file data set, the general fileis now available for application programs to use. If thisdata set is a database data set, ALCS initiates a copy ofthe records from the other (already online) copy of thedata set. This data set is not available until the copycompletes.

ModuleCDAM

DXC2752I DASD data set copy complete,Volume VS-'volume_serial',DSN-'data_set_name'

ExplanationMVS has allocated database data set data_set_nameon volume volume_serial to ALCS as requested by aZDASD VARY ONLINE command and the copy of therecords from the other (already online) copy of thedata set has completed.

System actionThis data set is now available.

ModuleCDAM

DXC2753E DASD data set copyfailed - Data set offline,Volume VS-'volume_serial',DSN-'data_set_name'

ExplanationMVS has allocated database data set data_set_nameon volume volume_serial to ALCS as requested by

a ZDASD VARY ONLINE command and started thecopy of the records from the other (already online)copy of the data set. During this copy operation MVShas deallocated the data set from ALCS. The copyoperation could not complete successfully.

System actionThe data set is not available.

User responseDetermine the reason why the data set wasdeallocated from ALCS. Retry the ZDASD VARYONLINE command.

ModuleCDAM

DXC2754E DASD data set copy failed - I/Oerror, Volume VS-'volume_serial',DSN-'data_set_name'

ExplanationMVS has allocated database data set data_set_nameon volume volume_serial to ALCS as requested by aZDASD VARY ONLINE command and started the copyof the records from the other (already online) copyof the data set. An I/O error has occurred duringthis copy operation. The copy operation could notcomplete successfully.

System actionThe data set is not available.

User responseDetermine the cause of the I/O error, and if necessaryget the unit serviced. Retry the ZDASD VARY ONLINEcommand.

ModuleCDAM

DXC2755E DASD data set deallocated- Too many I/O errors,Volume VS-'volume_serial',DSN-'data_set_name'

ExplanationThere have been ten consecutive I/O requests to dataset data_set_name on volume volume_serial whichhave resulted in I/O errors.


System actionALCS requests MVS to deallocate this data set. If thisis a database data set and the other copy of the dataset is available, or if this is a general file data set, ALCScontinues processing normally. If this is a databasedata set and the other copy of the data set is notavailable, ALCS ends abnormally.

User responseDetermine the cause of the I/O errors, and if necessaryget the unit serviced.

ModuleCDAM

DXC2756I DASD data set deallocated- ZDASD VARY request,Volume VS-'volume_serial',DSN-'data_set_name'

ExplanationMVS has deallocated data set data_set_name onvolume volume_serial from ALCS as requested by aZDASD VARY OFFLINE command.

System actionThis data set is now unavailable for ALCS applicationprograms to use.

ModuleCDAM

DXC2757E DASD operation error, FA-file_address, ID-record_id,RRN-relative_record_number,RBA-relative_byte_address,CCHHR-cylinder/head/record,Volume VS'-volume_serial',DSN-'data_set_name'

ExplanationA DASD I/O error has occurred, where:

OperationOne of:

READWRITE

File_address4-byte ALCS file address of the record.

Record_id2-byte record identifier of the record.

Relative_record_numberRelative record number of the record within thedata set.

Relative_byte_addressRelative byte address of the record within the dataset.

Cylinder/head/recordCKD DASD hardware address of the record.

Volume_serialVolume serial of the DASD volume that containsthe data set.

Data_set_nameData set name of the data set that contains therecord.

System actionALCS continues processing normally. If the operationis a read for a database record, and the other copyof the data set is available, then ALCS tries to readthe other copy. In all other cases, an I/O error returncondition is returned to the routine requesting the reador write.

User responseGet the unit serviced.

ModuleCDAM

DXC2759W PT-'pool_type' pool recycledHH-'hhh' hours MM-'mm' minutesbefore recycle due

Explanationpool_type short-term pool is exhausted and is beingrecycled before the time limit. The initial system STpool recycle time limit is 24 hours; this may be alteredusing the ZPOOL command. As a result of recycling,data in short-term pool may be corrupted.

System actionALCS re-uses pool_type short-term pool records.

Operator responseInform your system programmer as soon as possible,because this condition may cause data to becorrupted.


User responseCheck that sufficient short-term pool to cope withany application program requirements was allocated,taking into account the system transaction rate.Ensure that applications are correctly releasing short-term pool after usage, and that applications are notusing ST pool to keep data longer than the systemrecycle time. Also ensure that ST pool is not beingused in applications where the LT pool would be moreappropriate.

ModuleCVEC

DXC2761I Backout complete

ExplanationThis is a normal response to the ZDASD command. Fora full explanation see ALCS Operation and Maintenance

DXC2762I Commit complete

ExplanationThis is a normal response to the ZDASD command. Fora full explanation see ALCS Operation and Maintenance

DXC2763I PT-'pool_type' PDU is dispensing

ExplanationALCS has activated the emergency pool recovery (PDU)facility for long-term pool file pool_type because thereare no records available for this pool type.

System actionALCS starts to dispense long-term pool file addressesfor this pool type using the online PDU facility, insteadof using the normal dispense mechanism. The onlinePDU facility dispenses long-term pool file records thathave been released since the last Recoup run.

Operator responseRun Recoup as soon as possible.

User responseDetermine if any application programs are using poolfile records at an excessive rate. Consider allocatingmore pool file records of this type, or run Recoup morefrequently.

ModuleDXCPDU

DXC2764I PT-'pool_type' PDU is collecting

ExplanationALCS has inactivated the online emergency poolrecovery (PDU) facility for long-term pool file pool_typebecause there are records available for this pool typeagain.

System actionALCS stops using the online PDU facility to dispenselong-term pool file records of this type, and reverts tothe normal dispense mechanism.

ModuleDXCPDU

DXC2765I PT-'pool_type' PDU is enabled

ExplanationALCS has connected to the MVS log stream definedfor long-term pool file pool_type in the ALCS systemgeneration. ALCS uses the MVS log stream to savedata about long-term pool file records that have beenreleased since the last Recoup run. When this pooltype is depleted, ALCS will activate the emergencypool recovery (PDU) facility to dispense records usingdata from the MVS log stream.


ModuleDXCPDU

DXC2766W PT-'pool_type' PDU is disabled

ExplanationALCS is no longer able to access the MVS log streamdefined for long-term pool file pool_type in the ALCSsystem generation, due to a previous error condition.

System actionALCS stops saving data about released records on theMVS log stream. When this pool type is deleted, ALCSwill not activate the emergency pool recovery (PDU)facility. ALCS will try to access the MVS log streamagain the next time Recoup completes.


Operator responseCheck the ALCS Read Only CRAS log for additionalmessages related to emergency pool recovery (PDU).

ModuleDXCPDU

DXC2767W PT-'pool_type' System loggercall failed MVS log streamLS-'name' call_type Return codeRC-X'return_code' Reason codeRSC-X'reason_code'

ExplanationAn error occurred when ALCS attempted to access theMVS log stream with name name, using one of the MVSsystem logger callable services. call_type is the nameof the MVS system logger callable service, one of:

IXGCONNIXGBRWSEIXGWRITEIXGDELET

return_code is the return code from call_type.reason_code is the reason code from call_type.

System actionIf the return code is 0 or 4 then ALCS ignores theerror. Otherwise ALCS disconnects from the MVS logstream and disables the emergency pool recovery(PDU) facility for long-term pool file pool_type.

Problem determinationMVS Programming: Assembler Services Referencedescribes these return codes and reason codes.

ModuleDXCPDU

DXC2768I PT-'pool_type' System loggerconnected OK MVS log streamLS-'name' IXGCONN Return codeRC-X'return_code' Reason codeRSC-X'reason_code'

ExplanationALCS successfully connected to the MVS log streamwith name name, for pool_type long-term pool, usingthe MVS IXGCONN callable service. return_code is thereturn code from IXGCONN. reason_code is the reasoncode from IXGCONN.

ModuleDXCPDU

DXC2769I PT-'pool_type' System loggerdisconnected OK MVS log streamLS-'name' IXGCONN Return codeRC-X'return_code' Reason codeRSC-X'reason_code'

ExplanationALCS successfully disconnected from the MVS logstream with name name, for pool_type long-term pool,using the MVS IXGCONN callable service. return_codeis the return code from IXGCONN. reason_code is thereason code from IXGCONN.

ModuleDXCPDU

DXC2770I PDU is waiting for ENF event code48

ExplanationALCS is temporarily unable to access any MVS logstreams because the associated Coupling Facilitystructure is being rebuilt.

System actionALCS waits for ENF event code 48 to occur when theCoupling Facility structure has been rebuilt. When thathappens, the emergency pool recovery (PDU) facilitycontinues to collect or redispense file addresses.

ModuleDXCPDU

DXC2771E PT-'pool_type' MAXBUFSIZE mustbe at least 4096 bytes MVS logstream LS-'name'

ExplanationALCS successfully connected to the the MVS logstream with name name, for pool_type long-term pool,using the MVS IXGCONN callable service. However,the value returned in the MAXBUFSIZE parameter ofIXGCONN is not large enough for the emergency poolrecovery (PDU) facility.


System actionALCS disconnects from the MVS log stream anddisables the emergency pool recovery (PDU) facility forthis pool size.

System programmer responseMAXBUFSIZE is the size, in bytes, of the largestlog block that can be written to the CouplingFacility structure associated with this log stream.MAXBUFSIZE is defined in the LOGR policy for theCoupling Facility. Change the value of MAXBUFSIZE to4096 bytes for the MVS log streams.

ModuleDXCPDU

DXC2772W PT-'pool_type' Pool is depleted

Explanationpool_type long-term pool is depleted.

System actionIf this ALCS supports emergency pool recovery (PDU),then the PDU facility may be redispensing long-termpool file addresses from the MVS log stream.

Operator responseIf Recoup is not already running, then consider startingRecoup as soon as possible.

User responseDetermine if any application programs are using poolfile records at an excessive rate. Consider allocatingmore pool file records of this type, or run Recoup morefrequently.

ModuleCVEM

DXC2773W PT-'pool_type' Pool warningAvailable records NR-'number'below minimum threshold

ExplanationThe number of available records for long-term pool filepool_type is less than the minimum threshold set bythe ZPOOL command.


Operator responseIf this condition persists, consider reducing theminimum threshold value for this pool by the ZPOOLcommand. If the pool will be depleted very soon thenconsider running Recoup immediately.

ModuleCVEM

DXC2774W PT-'pool_type' Pool warningAvailable records NR-'number'Dispense rate over lastMM-'mm' minutes wasNR-'number_of_records' persecond At this rate pool will beexhausted in HH-'hh' hours

ExplanationThe average rate of dispense requests for long-termpool file pool_type over the last mm minutes isnumber_of_records per second. If the current rate ofdispense requests is maintained, then this pool file willbe depleted within hh hours.

Either the rate of dispense requests has exceeded theshort or long threshold rate for this pool file, or thetime to exhaustion has dropped below the short orlong threshold time for this pool file. The thresholdvalues are set using command ZPOOL


Operator responseIf this condition persists, consider modifying theexpected threshold values for this pool by the ZPOOLcommand. If the pool will be depleted very soon thenconsider running Recoup immediately.

ModuleCVEM

DXC2775W PT-'pool_type' Long-term poolmonitor thresholds are not set

ExplanationAt least one of the long-term pool usage thresholdvalues is currently set to zero.


System actionALCS continues to accumulate long-term pool activitydata, but does not check the usage rate or time todepletion.

Operator responseUse the ZPOOL command to set appropriate thresholdvalues for your installation.

ModuleCVEM

DXC2776W Long-term pool monitor interval isnot set

ExplanationThe long-term pool monitor interval is currently set tozero.

System actionALCS continues to accumulate long-term pool activitydata, but does not check the usage rate or time todepletion.

Operator responseUse the ZPOOL command to set the appropriatemonitor interval for your installation.

ModuleCVEM

DXC2808I PCTL Module MODN-moduleunload started by CRN-crn audittrail

ExplanationThis message is a normal response to the commandZPCTL.


ModuleCPCT

DXC2809I PCTL Module MODN-moduleunload force started by CRN-crnaudit trail



ModuleCPCT

DXC2810I PCTL Module MODN-moduleloaded by CRN-crn audit trail



ModuleCPCT

DXC2811I PCTL Module MODN-modulepromoted by CRN-crn audit trail



ModuleCPCT

DXC2812I PCTL Module MODN-moduleconfirmed by CRN-crn audit trail



ModuleCPCT


DXC2813I PCTL List Module MODN-moduleloaded by CRN-crn audit trail



ModuleCPCT

DXC2814I PCTL List Module MODN-moduleconfirmed by CRN-crn audit trail



ModuleCPCT

DXC2815I PCTL List Module MODN-modulecommitted by CRN-crn audit trail



ModuleCPCT

DXC2816I PCTL List Module MODN-modulebacked out by CRN-crn audit trail



ModuleCPCT

DXC2818I All load modules of loadset LSET='load_set' successfullyloaded Load set information:load_set text Load modules:load_module_1 ...

ExplanationThis message is a normal response to the ZPCTLload set command. The modules listed inmodule_1: ... of the load set are loaded.

The load_set text is audit information created by theload set generation.

System actionALCS completed loading all the load modules of thisload set.

ModuleCPCO

DXC2819E Duplicate load modules of loadset LSET='load_set' Load setinformation: load_set text Loadmodules: load_module_1 ...

ExplanationThis message is an error response to the ZPCTL loadset command. Load_module_1 ... of load_set werepreviously loaded.


System actionALCS did not load any load modules of this load set.

ModuleCPCO

DXC2820E Unloadable load modules of loadset LSET='load_set' Load setinformation: load_set text Loadmodules: load_module_1 nnnnnninvalid format load_module_2aaaaaa bbbb error during load ...


ExplanationThis message is an error response to the ZPCTL loadset command. Modules of load set could not beloaded. Either

• The load modules contain data at offset nnnnnn thatis not a valid ALCS application program or

• The modules failed to load.

See MVS System Messages and Codes. manual for anexplanation of the return (aaaaaa) and reason (bbbb)codes.

Check that the module is in the application programload module library that is defined in the JCL to runALCS.


System actionALCS did not load any load modules of this load set.

ModuleCPCO

DXC2875W CTKB replaced - reason

ExplanationALCS was unable to read system keypoint record B(CTKB) during restart processing. Reason is one of:

ERROR READING CTKB FILE COPYAn I/O error occurred reading CTKB.

ID CHECK ON CTKB FILE COPYThe first 2 characters of the record read are not'CK.' This is normal (not an error) when ALCS firstaccesses an uninitialized database.

WRONG VERSION IN CTKB FILE COPYThe CTKB record on the database is not atthe same functional level as the ALCS monitorprogram. This indicates that a change to the ALCSmonitor code, for example a new release of ALCS,requires a different format of CTKB.

System actionALCS initializes CTKB from the copy in the systemconfiguration table and writes this copy to thedatabase.

ModuleDXCKPT

DXC2900I ALCS connected to DB2 subsystemSBS-'ssnm'

ExplanationALCS has established a connection to DB2 subsystemssnm.

ModuleDXCSQL

DXC2901I ALCS disconnected from DB2subsystem SBS-'ssnm'

ExplanationALCS has terminated its connection to DB2 subsystemssnm.

ModuleDXCSQL

DXC2902I MVS operator has started DB2subsystem

ExplanationA DB2 subsystem - to which ALCS previously could notestablish a connection because it was not yet started -has now been started.

Operator responseUse the ZCSQL command to establish a connection tothe DB2 subsystem.

ModuleDXCSQL

DXC2903I MVS operator has stopped DB2subsystem

ExplanationALCS was previously connected to a DB2 subsystemwhich has just been stopped.

System actionALCS terminates any entry that is waiting for aresponse from DB2.

Operator responseRestart the DB2 subsystem, then use the ZCSQLcommand to establish a connection to it.


ModuleDXCSQL

DXC2904E DB2 subsystem has terminatedabnormally

ExplanationALCS was previously connected to a DB2 subsystemwhich has just terminated abnormally.

System actionALCS terminates any entry that is waiting for aresponse from DB2.

Operator responseRestart the DB2 subsystem, then use the ZCSQLcommand to establish a connection to it.

ModuleDXCSQL

DXC2905E DB2 connection failure -Subsystem SBS-'ssnm' Returncode RC-X'return_code' Reasoncode RSC-X'reason_code'

ExplanationALCS cannot establish a connection to DB2 subsystemssnm. Return_code and reason_code are the return andreason codes from the DB2 call attachment facility(CAF) CONNECT function.

Problem determinationDB2 Messages and Codes lists return codes and reasoncodes.

ModuleDXCSQL

DXC2906E DB2 disconnection failure -Subsystem SBS-'ssnm' Returncode RC-X'return-code' Reasoncode RSC-X'reason-code'

ExplanationALCS cannot terminate a connection to DB2subsystem ssnm. Return-code and reason-code are thereturn and reason codes from the DB2 call attachmentfacility (CAF) DISCONNECT function.


ModuleDXCSQL

DXC2907E DB2 open failure - Applicationplan PLN'plan' Return code RC-X'return-code' Reason code RSC-X'reason-code'

ExplanationDB2 cannot allocate resources to process thespecified plan plan. Return-code and reason-codeare the return and reason codes from the DB2 callattachment facility (CAF) OPEN function.


ModuleDXCSQL

DXC2908E DB2 close failure - Applicationplan PLN-'plan' Return code RC-X'return-code' Reason code RSC-X'reason-code'

ExplanationDB2 cannot deallocate the specified plan plan. Return-code and reason-code are the return and reason codesfrom the DB2 call attachment facility (CAF) CLOSEfunction.


ModuleDXCSQL

DXC2909E DB2 SQL call failure - Return codeRC-X'return_code' Reason codeRSC-X'reason_code'

ExplanationDB2 cannot process an application SQL callsuccessfully. Return_code and reason_code are the


return and reason codes from the DB2 call attachmentfacility (CAF).


ModuleDXCSQL

DXC2910I Waiting for DB2 subsystem ssnmto start

ExplanationDB2 was not started when ALCS tried to connect to it.ALCS will automatically try to connect again when DB2starts.

ModuleDXCMQI

DXC2911I ALCS has stopped waiting for DB2to start

ExplanationALCS was waiting for DB2 to start in order to connectto it. Now ALCS has stopped waiting because theoperator issued ZCSQL DISConnect.

ModuleDXCMQI

DXC2920I ALCS connected toMQ Queue managerQM-'queue_manager_name'

ExplanationALCS has established a connection to MQSeries queuemanager queue_manager_name.

ModuleDXCMQI

DXC2921I ALCS disconnected fromMQSeries Queue managerQM-'queue_manager_name'

ExplanationALCS has terminated its connection to MQSeriesqueue manager queue_manager_name.

ModuleDXCMQI

DXC2922E MQSeries connection failure- Queue managerQM-'queue_manager_name'MQCONN Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot establish a connection toMQSeries queue manager queue_manager_name.completion_code and reason_code are the completioncode and reason code from the MQSeries MQCONN call.


ModuleDXCMQI

DXC2923E MQSeries connection failure- Queue managerQM-'queue_manager_name'MQOPEN Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot establish a connection toMQSeries queue manager queue_manager_name.completion_code and reason_code are the completioncode and reason code from the MQSeries MQOPEN call.


ModuleDXCMQI

DXC2924E MQSeries connection failure- Queue managerQM-'queue_manager_name'MQINQ Completion codeRC-'completion_code' Reason codeRSC-'reason_code'


ExplanationALCS cannot establish a connection toMQSeries queue manager queue_manager_name.completion_code and reason_code are the completioncode and reason code from the MQSeries MQINQ call.


ModuleDXCMQI

DXC2925E MQSeries connection failure- Queue managerQM-'queue_manager_name'MQCLOSE Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot establish a connection toMQSeries queue manager queue_manager_name.completion_code and reason_code are the completioncode and reason code from the MQSeries MQCLOSEcall.


ModuleDXCMQI

DXC2926E Value of MQIA_MAX_HANDLESis zero Queue managerQM-'queue_manager_name'

ExplanationALCS cannot establish a connection to MQSeriesqueue manager queue_manager_name. A previousMQSeries MQINQ call returned a value of zero forMQIA_MAX_HANDLES (maximum number of handles)for the queue manager.

User responseThis error should not occur. If it does, ask yoursystem programmer to inform your IBM programmingrepresentative.

ModuleDXCMQI

DXC2927E Not enough storage for objecthandle table Queue managerQM-'queue_manager_name'

ExplanationThere is not enough memory allocated to ALCS to buildthe MQSeries object handle table.

System actionALCS terminates its connection to MQSeries queuemanager queue_manager_name.


ModuleDXCMQI

DXC2928E MQSeries initiation queue failure- Initiation queue nameQN-'queue_name' Queue managerQM-'queue_manager_name'MQOPEN Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot use the MQSeries initiation queuequeue_name. completion_code and reason_code arethe completion code and reason code from theMQSeries MQOPEN call.


ModuleDXCMQI

DXC2929E MQSeries initiation queue failure- Initiation queue nameQN-'queue_name' Queue managerQM-'queue_manager_name'MQGET Completion codeRC-'completion_code' Reason codeRSC-'reason_code'


ExplanationALCS cannot use the MQSeries initiation queuequeue_name. completion_code and reason_code arethe completion code and reason code from theMQSeries MQGET call.


ModuleDXCMQI

DXC2930E MQSeries input queue failure- Input queue nameQN-'queue_name' Queue managerQM-'queue_manager_name'MQOPEN Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot use the MQSeries input queuequeue_name. completion_code and reason_code arethe completion code and reason code from theMQSeries MQOPEN call.


ModuleDXCMQI

DXC2931E MQSeries input queue failure- Input queue nameQN-'queue_name' Queue managerQM-'queue_manager_name'MQGET Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot use the MQSeries input queuequeue_name. completion_code and reason_code arethe completion code and reason code from theMQSeries MQGET call.


ModuleDXCMQI

DXC2932E MQSeries disconnectionfailure - Queue managerQM-'queue_manager_name'MQDISC Completion codeRC-'completion_code' Reason codeRSC-'reason_code'

ExplanationALCS cannot terminated its connection toMQSeries queue manager queue_manager_name.completion_code and reason_code are the completioncode and reason code from the MQSeries MQDISC call.


ModuleDXCMQI

DXC2933E MQSeries initiation queue failure- Initiation queue name QN-queue_name Queue manager QM-queue_manager_name MQCLOSECompletion code RC-return_codeReason code RSC-reason_code

ExplanationALCS cannot use the MQSeries initiation queuequeue_name. completion_code and reason_code arethe completion code and reason code from theMQSeries MQCLOSE call.


ModuleDXCMQI

DXC2934E MQSeries input queue failure- Input queue name QN-queue_name Queue manager QM-queue_manager_name MQCLOSECompletion code RC-return_codeReason code RSC-reason_code


ExplanationALCS cannot use the MQSeries input queuequeue_name. completion_code and reason_code arethe completion code and reason code from theMQSeries MQCLOSE call.


ModuleDXCMQI

DXC2935I MQSeries initiation queue openQN-queue_name

ExplanationALCS has opened the MQSeries initiation queue.

ModuleDXCMQI

DXC2936I MQSeries initiation queue closedQN-queue_name

ExplanationALCS has closed the MQSeries initiation queue.

ModuleDXCMQI

DXC2937I MQSeries input queue open QN-queue_name

ExplanationALCS has opened the MQSeries input queue.

ModuleDXCMQI

DXC2938I MQSeries input queue closed QN-queue_name

ExplanationALCS has closed the MQSeries input queue.

ModuleDXCMQI

DXC2940E APPC/MVS receive allocate failed- CRN-'crn' ALCS return codeRC1-return_code APPC/MVS returncode RC2-return_code

ExplanationALCS attempted to allocate a conversation for theAPPC resource with CRN crn, but either ALCS orAPPC/MVS gave an error return code.

System actionALCS does not set the APPC resource active.

Problem determinationIf the ALCS return code is non-zero then contactyour IBM programming support representative. Referto MVS Programming: Writing Transaction Programsfor APPC/MVS for return codes from the APPC/MVSATBALC2 callable service.

ModuleDXCCOLH

DXC2941E APPC/MVS send allocate failed- CRN-'crn' ALCS return codeRC1-return_code APPC/MVS returncode RC2-return_code

ExplanationALCS attempted to allocate a conversation for theAPPC resource with CRN crn, but either ALCS orAPPC/MVS gave an error return code.

System actionALCS does not set the APPC resource active.

Problem determinationIf the ALCS return code is non-zero then contactyour IBM programming support representative. Referto MVS Programming: Writing Transaction Programsfor APPC/MVS for return codes from the APPC/MVSATBALC2 callable service.

ModuleDXCCOLH

DXC2942E APPC/MVS receive failed -CRN-'crn' ALCS return code RC1-return_code APPC/MVS returncode RC2-return_code


ExplanationALCS attempted to receive data on a conversation forthe APPC resource with CRN crn, but either ALCS orAPPC/MVS gave an error return code.

System actionALCS stops receiving data from the APPC connection.

Problem determinationIf the ALCS return code is non-zero then contactyour IBM programming support representative. Referto MVS Programming: Writing Transaction Programsfor APPC/MVS for return codes from the APPC/MVSATBRCVW callable service.

ModuleDXCCOLH

DXC2943E APPC/MVS send failed - CRN-'crn'ALCS return code RC1-return_codeAPPC/MVS return code RC2-return_code

ExplanationALCS attempted to send data on a conversation forthe APPC resource with CRN crn, but either ALCS orAPPC/MVS gave an error return code.

System actionALCS discards the message data.

Problem determinationIf the ALCS return code is non-zero then contactyour IBM programming support representative. Referto MVS Programming: Writing Transaction Programsfor APPC/MVS for return codes from the APPC/MVSATBSEND callable service.

ModuleDXCCOLH

DXC2944E APPC/MVS receive deallocatefailed - CRN-'crn' ALCS return codeRC1-return_code APPC/MVS returncode RC2-return_code

ExplanationALCS attempted to deallocate a conversation for theAPPC resource with CRN crn, but either ALCS orAPPC/MVS gave an error return code.

System actionALCS continues processing as if the conversation wasdeallocated.

Problem determinationIf the ALCS return code is non-zero then contactyour IBM programming support representative. Referto MVS Programming: Writing Transaction Programsfor APPC/MVS for return codes from the APPC/MVSATBDEAL callable service.

ModuleDXCCOLH

DXC2945E APPC/MVS send deallocate failed- CRN-'crn' ALCS return codeRC1-return_code APPC/MVS returncode RC2-return_code

ExplanationALCS attempted to deallocate a conversation for theAPPC resource with CRN crn, but either ALCS orAPPC/MVS gave an error return code.

System actionALCS continues processing as if the conversation wasdeallocated.

Problem determinationIf the ALCS return code is non-zero then contactyour IBM programming support representative. Referto MVS Programming: Writing Transaction Programsfor APPC/MVS for return codes from the APPC/MVSATBDEAL callable service.

ModuleDXCCOLH

DXC2948I APPC/MVS receive conversationstarted - CRN-'crn'

ExplanationALCS has allocated a conversation for the APPCresource with CRN crn.



ModuleDXCCOLH

DXC2949I APPC/MVS send conversationstarted - CRN-'crn'



ModuleDXCCOLH

DXC2950I APPC/MVS receive conversationstopped - CRN-'crn'

ExplanationALCS has deallocated a conversation for the APPCresource with CRN crn.


ModuleDXCCOLH

DXC2951I APPC/MVS send conversationstopped CRN-'crn'

ExplanationALCS has deallocated a conversation for the APPCresource with CRN crn.


ModuleDXCCOLH

DXC2952I APPC/MVS inbound receiveconversation started CRN-'crn'



ModuleDXCCOLH

DXC2953I APPC/MVS inbound sendconversation started CRN-'crn'



ModuleDXCCOLH

DXC2954I APPC/MVS inbound allocateignored CRN-'crn'

ExplanationALCS has received an inbound allocate request for theAPPC resource with CRN crn, but the resource:

• is not an APPC resource, or• is already active, or• already has an inbound conversation.

System actionALCS ignores the inbound allocate request andcontinues processing normally.

ModuleDXCCOLH

DXC2955I APPC/MVS inbound allocate doesnot match partner LU nameCRN-'crn'

ExplanationALCS has received an inbound allocate requestfor the APPC resource with CRN crn, but theinformation provided by APPC/MVS does not matchthe information in the ALCS communication generationfor this resource.


System actionALCS ignores the inbound allocate request andcontinues processing normally.

System programmer responseCheck that the ALCS communication generation iscorrect for this APPC resource. Check that theAPPC/MVS TP profile and side information files containthe correct data.

ModuleDXCCOLH

DXC2956W APPC/MVS inbound allocate failed- CRN-'crn' undefined or inactive

ExplanationALCS received an inbound APPC/MVS allocate request.The corresponding APPC/MVS TP profile informationspecifies a CRN that is not defined to ALCS or is notactive.

System actionALCS ignores the inbound allocate.

System programmer responseCorrect your APPC/MVS TP profiles and/or the ALCScommunication generation.

Problem determinationCheck your APPC/MVS TP profiles and the ALCScommunication generation.

ModuleDXCCOLF

DXC2957W APPC/MVS inbound allocate failed- No match for partner LU nameLUN-'name'

ExplanationALCS received an inbound APPC/MVS allocate request.The corresponding APPC/MVS TP profile informationspecifies CRN=* but there is no APPC connectiondefined in the ALCS communication table with amatching partner LU name.

System actionALCS ignores the inbound allocate.

System programmer responseCorrect your APPC/MVS TP profiles and/or the ALCScommunication generation.

Problem determinationCheck your APPC/MVS TP profiles and the ALCScommunication generation.

ModuleDXCCOLF

DXC2958I APPC/MVS issuing send allocate -CRN-'crn'

ExplanationALCS is allocating an outbound conversation for theAPPC resource with CRN crn.


ModuleDXCCOLH

DXC2959I APPC/MVS issuing receive allocate- CRN-'crn'

ExplanationALCS is allocating an outbound conversation for theAPPC resource with CRN crn.


ModuleDXCCOLH

DXC2960I ALCS concurrent server(Listener) n started PortPO-'tcpip_port_number'

ExplanationSelf-explanatory. n is the index number of theconcurrent server (1 to 8).

ModuleDXCSOCK


DXC2961I ALCS concurrent server(Listener) n stopped PortPO-'tcpip_port_number'

ExplanationSelf-explanatory. n is the index number of theconcurrent server (1 to 8).

ModuleDXCSOCK

DXC2962E TCP/IP connection failure- INITAPI for socketssubtask Address spaceAS-'tcpip_address_space_name'Error code EC-'error_code'

Problem determinationSee Communications Server IP API Guide for anexplanation of the return code and error number.

ModuleDXCSOCK

DXC2963E TCP/IP connection failure- INITAPI for ConcurrentServer subtask Address spaceAS-'tcpip_address_space_name'Port PO-'tcpip_port_name'Return code RC-'return_code'Error number EC-'error_number'

Problem determinationSee z/OS Communications Server IP API Guide for anexplanation of the return code and error number.

ModuleDXCSOCK

DXC2964E TCP/IP connection failure -INITAPI for Child Serversubtask Address spaceAS-'tcpip_address_space_name'Return code RC-'return_code'Error number EC-'error_number'

Problem determinationSee z/OS Communications Server IP API Guide for anexplanation of the return code and error number.

ModuleDXCSOCK

DXC2965I ALCS disconnected from TCPIPaddress space AS-'name'

ExplanationALCS is now disconnected from TCP/IP.

ModuleDXCSOCK

DXC2966E TCP/IP connection failure No ECBavailable for Child Server subtask

ExplanationA new client attempted to connect to the ALCSconcurrent server (Listener) but ALCS does not haveenough resources to create a new entry for this client.

System actionALCS waits for another connection request.

ModuleDXCSOCK

DXC2967I ALCS connected to TCPIP addressspace AS-'name'

ExplanationALCS is now connected to the TCP/IP address spacecalled name.

ModuleDXCSOCK

DXC2968I TCPIP resource active - CRN-'crn'

ExplanationALCS has established a TCP/IP connection for theresource with CRN crn.


ModuleDXCSOCO


DXC2969I TCPIP resource inactive -CRN-'crn'

ExplanationALCS has terminated the TCP/IP connection for theresource with CRN crn.


ModuleDXCSOCO

DXC2970E TCPIP resource CRN-'crn''call_type' call failed forcommunication subtask Returncode RC-'return_code' Errornumber EC-'error_number'

ExplanationAn error occurred when ALCS issued a TCP/IP'call_type' sockets call.

System actionALCS stops the TCP/IP connection for the resourcewith CRN crn.

Problem determinationSee Communications Server IP API Guide for anexplanation of the return code and error number.

ModuleDXCSOCO

DXC2972E TCPIP resource CRN-'crn' No IOCBavailable to add dynamic server

ExplanationA new client attempted to connect to the TCP/IPserver connection with CRN crn but ALCS does nothave enough resources to dynamically create a newcommunication table entry for this client.


System programmer responseIncrease the total number of I/O control blocks(IOCBs) in the ALCS system. (See the description

of the SCTGEN macro NBRIOB parameter in ALCSInstallation and Customization.)

ModuleDXCSOCO

DXC2973E TCPIP resource CRN-'crn' Unableto start - TCP/IP not supported

ExplanationIn order to use TCP/IP connections, you must enablethe ALCS support for TCP/IP (see the descriptionof the SCTGEN macro in ALCS Installation andCustomization).

ModuleDXCSOCO

DXC2974E TCPIP resource CRN-'crn' Unableto start - TCP/IP not connected

ExplanationIn order to use TCP/IP connections, you must establisha connection between ALCS and a TCP/IP addressspace in the same MVS system (see the descriptionof the ZCTCP command in ALCS Operation andMaintenance).

ModuleDXCSOCO

DXC2975I TCPIP dynamic server resourceactive - CRN-'crn'

ExplanationALCS has established a connection with a new clienton the TCP/IP server connection with CRN crn.


ModuleDXCSOCO

DXC2976I TCPIP dynamic server resourceinactive - CRN-'crn'

ExplanationALCS has terminated a connection with one of theclients on the TCP/IP server connection with CRN crn.



DXC2977W TCPIP resource CRN-'crn'Unknown terminal CRN-'crn'

ExplanationDuring TCP/IP input message processing, installation-wide monitor exit USRTCP4 returned an invalid CRN.



ModuleDXCSOCO

DXC2978W TCPIP resource CRN-'crn'Unknown terminal CRI-'cri'

ExplanationDuring TCP/IP input message processing, installation-wide monitor exit USRTCP4 returned an invalid CRI.



ModuleDXCSOCO

DXC2979W TCPIP resource CRN-'crn' OriginCRN-'crn' is not a terminal

ExplanationDuring TCP/IP input message processing, installation-wide monitor exit USRTCP4 returned a CRN or CRI thatdoes not correspond to a display or printer terminal.



ModuleDXCSOCO

DXC2983W TCPIP resource CRN-'crn'Unknown HEX-'hex' TCID-'tcid'IA-'ia' TA-'ta'

ExplanationA message was received on TCP/IP communicationresource crn from a remote ALC terminal, but theterminal is not defined to ALCS. A MATIP-ID for theremote terminal is constructed from the high-levelnetwork exit address (hex), TCID (tcid), IA (ia),and TA(ta). ALCS uses the MATIP-ID to scan theALCS MATIP-ID communication table to retrieve theterminal CRI.



ModuleDXCSOCA

DXC2984I TCPIP resource CRN-'crn' MATIPsession opened - Type t IP addressof remote host iii.iii.iii.iii

ExplanationA MATIP session has opened on TCP/IPcommunication resource crn. The MATIP session type tis one of:

AType A terminal-to-host

A H-TO-HType A host-to-host

BType B

The IP address of remote host or gateway is iii.iii.iii.iii(dotted decimal notation).


ModuleDXCSOCA


DXC2985I TCPIP resource CRN-'crn' MATIPsession closed - Close codeX'hh' IP address of remote hostiii.iii.iii.iii

ExplanationA MATIP session has closed on TCP/IP communicationresource crn. The MATIP close code hh is currently:

00OK


ModuleDXCSOCA

DXC2986I TCPIP resource CRN-'crn' MATIPsession reconfiguration

ExplanationA MATIP session is being reconfigured on TCP/IPcommunication resource crn.


ModuleDXCSOCA

DXC2987E TCPIP resource CRN-'crn' MATIPsession rejected - Reject codeX'hh' IP address of remote hostiii.iii.iii.iii Packet length llll dd...dd

ExplanationA MATIP Session Open command was rejected onTCP/IP communication resource crn. Either ALCSreceived a Session Open packet and sent the rejectcode in an Open Confirm packet, or ALCS received anOpen Confirm packet containing the reject code. TheMATIP reject code hh is one of:

01No matching traffic type

05Protocol unavailable at destination

41No matching traffic type

43Inconsistent end-to-end protection

44Unknown client

48Packet length is too short

49Packet length is too long

4AUnknown or unsupported coding

84ASCU identification is not valid

85ASCU is unknown

86ASCU is already assigned

88Unknown or unsupported coding

89Unknown or unsupported subtype

8BIncompatible MPX/HDR combination

8CUnknown or unsupported presentation

8DPacket length is too short

8EPacket length is too long

91Mo matching ASCU

92No ASCU configured

94Session mismatch

The IP address of remote host or gateway is iii.iii.iii.iii(dotted decimal notation).

llllThe length of the packet.

dd...ddThe first 32 bytes of the packet in hexadecimal.


ModuleDXCSOCA

DXC2988E TCPIP resource CRN-'crn' MATIPpacket has incorrect characteristicPacket length llll dd...dd


ExplanationA MATIP packet has been received on TCP/IPcommunication resource crn but the packet header isinvalid.



characteristicIndicates the error, one of:

LengthVersionCommandTraffic TypeTraffic SubtypeCodingMPX or HDRPresentationNumber of ASCUs

System actionALCS discards the packet.

ModuleDXCSOCA

DXC2989E TCPIP resource CRN-'crn'Unexpected MATIP mmmm Packetlength llll dd...dd

ExplanationA MATIP packet has been received on TCP/IPcommunication resource crn but the packet is out ofsequence.



mmmmThe type of packet, one of:

DataSession OpenOpen ConfirmSession CloseStatus QueryStatus ResponseStop TransmissionResume Transmission

System actionALCS rejects the MATIP command.

ModuleDXCSOCA

DXC2990E TCPIP resource CRN-'crn' inactive- nnn messages were queued

Explanationnnn ECB-controlled programs issued a ROUTC orSENDC monitor-request macro to send messagesto a TCP/IP resource. The messages were queuedwaiting for transmission, but the TCP/IP connectionwas inactivated before these messages could betransmitted.

System actionFor each message that was waiting to be transmitted,ALCS detaches the message block from the ECB andreturns control to the entry.

User responseCheck that the resource is correctly defined inthe communication generation. Also check thatall required communication resources are correctlystarted.

ModuleDXCSOCO

DXC2991E TCPIP resource CRN-'crn' Nomatching MATIP client

ExplanationALCS received an inbound connection request for theTCP/IP communication resource with CRN crn whichis defined as a MATIP Type A or Type B server.ALCS cannot find any TCP/IP communication resourcedefined as a MATIP Type A or Type B client whichmatches the remote host trying to connect to ALCS.

System actionALCS closes the inbound TCP/IP connection.

ModuleDXCSOCO


DXC2992E TCPIP resource CRN-'crn'Matching MATIP clientCRN2-'crn2' already active

ExplanationALCS received an inbound connection request for theTCP/IP communication resource with CRN crn whichis defined as a MATIP Type A or Type B server. ALCSfound a TCP/IP communication resource defined asa MATIP Type A or Type B client which matchesthe remote host trying to connect to ALCS, but thisresource is already in use. crn2 is the CRN of thematching client.

System actionALCS closes the inbound TCP/IP connection.

ModuleDXCSOCO

DXC2993W TCPIP resource CRN-'crn'Disconnected - Blocked sendtimeout expired

ExplanationThe IP stack was blocked for sending on the TCP/IPcommunication resource with CRN crn for the durationof the blocked send timeout interval. Installation-widemonitor exit USRTCPA requested ALCS to close theconnection.

ModuleDXCSOCO

DXC2994W TCPIP resource CRN-'crn'Disconnected - Idle connectiontimeout expired

ExplanationNo data was received on the TCP/IP communicationresource with CRN crn for the duration of theidle connection timeout interval. ALCS closed theconnection.

ModuleDXCSOCO

DXC2995E TCP/IP connection failure No childserver subtask available

ExplanationA new client attempted to connect to the ALCSconcurrent server (Listener) but ALCS does not haveenough resources to accept this connection.


System programmer responseConsider increasing the number of concurrent serversockets threads for the Listener. (See the descriptionof the SCTGEN macro TCPLIST parameter in ALCSInstallation and Customization.)

ModuleDXCSOCL

DXC2996W E-mail output is stopped - nnnnnmessages on queue

ExplanationThe ALCS outbound e-mail queue handler has noticedthat there are messages on the queue, but the queueis currently stopped.

Operator responseUse the ZMAIL QUEUE,START command to startsending messages from the outbound e-mail queue,if required.

ModuleCSMB

DXC2997W E-mail output is unable to contactMTA - nnnnn messages on queue

ExplanationThe ALCS outbound e-mail queue handler was not ableto send an e-mail SMTP message to the local messagetransfer agent (MTA). Accompanying error messagesdescribe the error condition.

This message can also indicate that ALCS is notcurrently connected to TCP/IP.

System actionALCS leaves the messages on queue. ALCS will try tocontact the MTA again at regular intervals while thereare messages on queue.


Operator responseUse the ZMAIL DISPLAY command to check the IPaddress and port number for the MTA. Use the ZMAILSET command to change these values if required.Use the ZCTCP DISPLAY command to check if ALCSis connected to TCP/IP. Use the ZCTCP CONNECTcommand to connect ALCS to the TCP/IP addressspace if required.

ModuleCSMB

DXC2998W E-mail output message rejected

ExplanationThe ALCS outbound e-mail queue handler was not ableto send an e-mail SMTP message to the local messagetransfer agent (MTA). Accompanying error messagesdescribe the error condition.

System actionALCS discards the rejected message and tries to sendthe next message from the queue.

Operator responseReport the error to your system programmer.

ModuleCSMB

DXC2999I message

ExplanationALCS has passed an unnumbered message to NetView.(For example, the message may have originated froma user-written application program that did not takeadvantage of the range DXC3000-DXC3999).

Note: The destination for this message is the NetViewlog.

System actionNone.


Chapter 7. User-written application programmessages: DXC3000-DXC3999

DXC3000 - DXC3999

ExplanationReserved for user-written application programs.

See ALCS Installation and Customization for details.


Chapter 8. Responses to ALCS commands: DXC5000-DXC5999

DXC5000I Command complete - messagesent

ExplanationThis is a normal response to the command ZMAIL.

DXC5001E Command failed - message notsent

ExplanationThis is an error response to the command ZMAIL.Accompanying error messages describe the errorcondition.

Operator responseIf the accompanying error messages indicate thatALCS could not send the message because of an errorin the message (for example, you did not include anyrecipients for the message), reenter the command witha corrected message. Otherwise report the error toyour system programmer.

DXC5003E No message text

ExplanationYou attempted to send an e-mail SMTP message withno message text.

Operator responseReenter the command, including some text in themessage.

DXC5004E Incorrect header line

ExplanationYou attempted to send an e-mail SMTP message withan incorrect header line.

Operator responseReenter the command with a corrected message.

DXC5005E Unknown conversion selector

ExplanationYou attempted to send an e-mail SMTP message froman ALCS terminal, but you specified a conversionselector that is not known to ALCS.

Operator responseReenter the command with a corrected message.

DXC5006E Unable to retrieve e-mail values --TCP/IP not supported

ExplanationThis is an error response to ZMAIL DISPLAY. TheALCS system configuration table does not includesupport for TCP/IP.

DXC5007E Unable to update e-mail values -Not authorized

ExplanationExplanation: This is an error response to ZMAIL SET.ZMAIL SET is restricted to Prime CRAS authorizedterminals and Alternate CRAS AT1 through AT16authorized terminals.

DXC5008E Unable to update e-mail values --TCP/IP not supported

ExplanationThis is an error response to ZMAIL SET. The ALCSsystem configuration table does not include supportfor TCP/IP.

DXC5009I E-mail value updated

ExplanationThis is a normal response to ZMAIL SET.

DXC5010I E-mail operating values ALCS maildomain d MTA IP address e ori MTA port number n Inboundtimeout t1 Outbound timeout t2Postmaster name crn


ExplanationThis is a normal response to ZMAIL DISPLAY.

dALCS mail domain name.

eDomain name of the local message transfer agent(MTA) for outbound e-mail.

iIP address of the local message transfer agent(MTA) for outbound e-mail.

nPort number of the local MTA for outbound e-mail.

t1Connection timeout for inbound e-mail.

t2Connection timeout for outbound e-mail.

crnDestination for inbound e-mail messagesaddressed to Postmaster@domain_name, wheredomain_name is your ALCS domain name.

DXC5011I E-mail queue is status nnnnnmessages on queue

ExplanationThis is a normal response to the command ZMAILQUEUE,DISPLAY.

DXC5012I E-mail queue is purged nnnnnmessages deleted

ExplanationThis is a normal response to the command ZMAILQUEUE,PURGE or ZMAIL QUEUE,PURGE,ALL.

DXC5013I E-mail queue is now started

ExplanationThis is a normal response to the command ZMAILQUEUE,START.

DXC5014E Email queue is already started

ExplanationThis is an error response to the command ZMAILQUEUE,START

DXC5015I E-mail queue is now stopped

ExplanationThis is a normal response to the command ZMAILQUEUE,STOP.

DXC5016E E-mail queue is already stopped

ExplanationThis is an error response to the command ZMAILQUEUE,STOP.

DXC5017E Unable to access e-mail queue -Error retrieving keypoint record

ExplanationThis is an error response to the command ZMAILQUEUE.

DXC5018E Unable to access e-mail queue -Error retrieving message record

ExplanationThis is an error response to the command ZMAILQUEUE,PURGE.

DXC5019E Unable to access e-mail queue- Message queue control fieldscorrupted

ExplanationThis is an error response to the command ZMAILQUEUE,PURGE.

DXC5020E Sockets call calltype failed - Errornumber error_number

ExplanationWhile attempting to send an e-mail SMTP messageto the local message transfer agent (MTA), a TCP/IPsockets call of type calltype failed with error numbererror_number.


DXC5021E Unexpected SMTP reply codereply_code

ExplanationWhile attempting to send an e-mail SMTP message tothe local message transfer agent (MTA), the local MTAresponded with SMTP reply code reply_code.


DXC5022E Connection timed out


ExplanationWhile attempting to send an e-mail SMTP message tothe local message transfer agent (MTA), the MTA failedto respond within a reasonable time.


DXC5023E Connection closed by MTA

ExplanationWhile attempting to send an e-mail SMTP messageto the local message transfer agent (MTA), the MTAclosed the TCP/IP connection.


DXC5025E No message body

ExplanationYou attempted to send an e-mail SMTP message withno message body.

Operator responseIf you used the ALCS ZMAIL command to send themessage, reenter the command, including a body inthe message. If you used an ALCS application inputmessage, refer to your documentation for that inputmessage.

DXC5026E Incorrect header line

ExplanationYou attempted to send an e-mail SMTP message withan incorrect header line.

Operator responseIf you used the ALCS ZMAIL command to send themessage, reenter the command with a correctedmessage. If you used an ALCS application inputmessage, refer to your documentation for that inputmessage.

DXC5027E No message recipient

ExplanationYou attempted to send an e-mail SMTP message withno recipients.

Operator responseIf you used the ALCS ZMAIL command to send themessage, reenter the command with at least onerecipient. If you used an ALCS application inputmessage, refer to your documentation for that inputmessage.

DXC5028E Reverse path invalid or omitted

ExplanationYou attempted to send an e-mail SMTP message withan invalid reverse path.

Operator responseIf you used the ALCS ZMAIL command to sendthe message, report the problem to your systemprogrammer. If you used an ALCS application inputmessage, refer to your documentation for that inputmessage. If your documentation does not explainhow to correct the problem, report it to your systemprogrammer.

Programmer responseIf the ALCS ZMAIL command generates this response,inform your IBM programming support representative.If an ALCS application input message generates thisresponse, there is an error in your application.

DXC5029E MTA response too long

ExplanationWhile attempting to send an e-mail SMTP message tothe local message transfer agent (MTA), the local MTAresponded with an SMTP reply which was longer thanthe maximum (1024 characters) which ALCS supports.


DXC5040I Trace - Call type calltype

ExplanationYou attempted to send an e-mail SMTP message andrequested trace information. ALCS has issued theTCP/IP call calltype.

DXC5041I Trace - Call type calltype data

ExplanationYou attempted to send an e-mail SMTP message andrequested trace information. ALCS has issued the

Chapter 8. Responses to ALCS commands: DXC5000-DXC5999 185

TCP/IP call calltype. The call sent or received datastarting with the characters data.

DXC5085W Throttle Application police routinehas been aborted

ExplanationThe Throttling Application police routine hasterminated abnormally.

System programmer responseInvestigate the dump of the problem that causedthe process abortion. Use ZDRIV CTH4 to restart theThrottling Application police routine.

ModuleCTH4

DXC5086I normal response

ExplanationThis message is a normal response to the ZCTHRDisplay command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCTH1


ExplanationThis message is a normal response to the ZCTHRDisplay command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCTH1

DXC5088I Throttle Application updated

ExplanationThis message is a normal response to either the ZCTHRUpdate, or ZCTHR THRS, or ZCTHR ALT command. SeeALCS Operation and Maintenance for a full explanationof the command response.

ModuleCTH1

DXC5089I Throttle Application not found

ExplanationThis message is a response to the ZCTHR command.You entered the command, but this throttle applicationdoes not exist.

Operator responseIf this is an error, then correct the error and retry thecommand.

ModuleCTH1

DXC5090E Invalid ZCTHR zzzzzz parameter

ExplanationThis message is a response to the ZCTHR command.You entered the command with invalid parameterzzzzzz.

Operator responseCorrect the error and retry the command.

ModuleCTH1

DXC5091I Throttle Table empty

ExplanationThis message is a response to the ZCTHR Displaycommand. There are no applications in the throttletable.

ModuleCTH1

DXC5092I Throttle Table initialized

ExplanationThis message is a normal response to the ZCTHR Initcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCTH1

DXC5093E Invalid CRAS authorisation


ExplanationThe ZCTHR commands except ZCTHR Display areallowed only from Prime CRAS.


ModuleCTH1

DXC5094E Invalid ZCTHR command

ExplanationThis message is a response to the ZCTHR command.You entered the ZCTHR command but the syntax of thecommand was wrong.


ModuleCTH1

DXC5095I Throttle Application added

ExplanationThis message is a normal response to the ZCTHR Addcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCTH1

DXC5096I Throttle Application deleted

ExplanationThis message is a normal response to theZCTHR DELete command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCTH1

DXC5097W Throttle Table full

ExplanationThis message is a response to the ZCTHR Addcommand.

Operator responseDelete non used Throttle applications and retry thecommand.

ModuleCTH1

DXC5098W Throttle Application exists already

ExplanationThis message is a response to the ZCTHR Addcommand. You entered the ZCTHR Add command, butthe Throttle application already exists.


ModuleCTH1

DXC5100E Invalid ZOCTM command

ExplanationYou entered an invalid ZOCTM command.

Operator responseCorrect the typing or syntax error and retry thecommand.

DXC5101I BUILD started

ExplanationThis message is a normal response to the ZOCTMBUILD command.

DXC5102I BUILD completed

ExplanationThis message is a normal response to the ZOCTMBUILD command.

DXC5103E BUILD failed RC=return_codeRSN=reason_code

ExplanationThe ZOCTM BUILD command failed with unexpectedreturn and reason codes.


Operator responseSee ALCS Operation and Maintenance for a fullexplanation of the command format and retry thecommand. Inform your system programmer if notsuccessful.

System programmer responseDetermine if any system errors have occurred andinform your IBM programming support representative.

DXC5104I Access allowed

ExplanationThis message is a normal response to the ZOCTMSTART command.

DXC5105E Access not allowedRC=return_code RSN=reason_code

ExplanationThe ZOCTM START command failed with unexpectedreturn and reason codes.


System programmer responseDetermine if any system errors have occurred andinform your IBM programming support representative.

DXC5106I Access not allowed

ExplanationThis message is a normal response to the ZOCTMSTOP command.

DXC5107E Request failed RC=return_codeRSN=reason_code

ExplanationThe ZOCTM STOP command failed with unexpectedreturn and reason codes.


System programmer responseInvestigate if any system errors have occurred andinform your IBM programming support representative.

DXC5108I BACKUP started

ExplanationThis message is a normal response to the ZOCTMBACKUP command.

DXC5109E BACKUP failed RC=return_codeRSN=reason_code

ExplanationThe ZOCTM BACKUP command failed with unexpectedreturn and reason codes.



DXC5110I BACKUP finished

ExplanationThis message is a normal response to the ZOCTMBACKUP command.

DXC5111E Invalid sequential file

ExplanationThe Online Communication Table Maintenance (OCTM)BACKUP or RESTORE functions can not proceed as thesequential file is not valid.


System programmer responseVerify that the OCTM sequential file is correctlydefined in the ALCS system (see the description ofthe SEQGEN generation macro in ALCS Installation andCustomization).


DXC5112I FORCE accepted

ExplanationThis message is a normal response to theZOCTM BACKUP FORCE or ZOCTM RESTORE FORCEcommand.

DXC5113E FORCE failed

ExplanationThe ZOCTM BACKUP FORCE or ZOCTM RESTOREFORCE command failed as a previous ZOCTM BACKUPor RESTORE had completed successfully.

Operator responseRetry the command without the force parameter.

DXC5114I RESTORE started

ExplanationThis message is a normal response to the ZOCTMRESTORE command.

DXC5115I RESTORE finished

ExplanationThis message is a normal response to the ZOCTMRESTORE command.

DXC5116E RESTORE failed RC=return_codeRSN=reason_code

ExplanationThe ZOCTM RESTORE command failed withunexpected return and reason codes.



DXC5117I OCTM not used by this ALCSsystem

ExplanationThis message is a normal response when aZOCTM command has been entered and OnlineCommunication Table Maintenance (OCTM) is not usedby the ALCS system for managing communicationresources.


ExplanationThis message is a normal response to theZOCTM STATUS command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

DXC5119E Sequential file in use

ExplanationThe OCTM BACKUP or OCTM RESTORE functions cannot proceed as the sequential file is already in use.

Operator responseSee ALCS Operation and Maintenance for a fullexplanation of the command format and retry thecommand when the sequential file is no longer in use.


ExplanationThis message is a normal response to theZOCTM GROUPS command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

DXC5123E GROUPS failed RC=return_codeRSN=reason_code

ExplanationThe ZOCTM GROUPS command failed with unexpectedreturn and reason codes.



DXC5124I No groups allocated


ExplanationThis message is a response to the ZOCTM GROUPScommand when there are no OCTM communicationsgroups allocated.

DXC5125I GROUP is empty

ExplanationThis message is a response to the ZOCTM GROUPcommand when there are no communicationresources belonging to this OCTM communicationsgroup.

DXC5126E GROUP failed RC=return_codeRSN=reason_code

ExplanationThe ZOCTM GROUP command failed with unexpectedreturn and reason codes.




ExplanationThis message is a response to the ZOCTM GROUPcommand. See ALCS Operation and Maintenance fora full explanation of the command response.

DXC5128E GROUP not found

ExplanationThe OCTM communications group could not be found.

Operator responseCheck the name of the OCTM communications groupand submit the command again with the correct groupname.

DXC5130E Invalid ZOCTM parameter

ExplanationYou entered a ZOCTM command with an invalidparameter.


DXC5131E Invalid CRAS authorization

ExplanationThe ZOCTM commands ZOCTM BUILD, BACKUP,RESTORE, START and STOP are allowed only fromPrime CRAS. All other ZOCTM commands are allowedfrom Prime CRAS or high CRAS (AT1-16).

Operator responseSubmit the command on a display that has theappropriate CRAS authority.

DXC5132E OCTM can not be accessed

ExplanationYou are not allowed to enter this ZOCTM commandwhen OCTM is inactive.

Operator responseInform your system programmer.

System programmer responseIf required, restart OCTM with the ZOCTM STARTcommand.

DXC5133E BUILD not allowed anymore

ExplanationThe ZOCTM BUILD command has already been usedto build the OCTM database (and the build completedsuccessfully).

DXC5135E Invalid system state

ExplanationYou are not allowed to enter the ZOCTM RESTOREcommand unless ALCS is in IDLE state.

Operator responseBring the ALCS system down to IDLE state and retrythe command.


DXC5136W Access already allowed

ExplanationYou are not allowed to enter the ZOCTM STARTcommand twice (OCTM has already been started).

DXC5137W Access already not allowed

ExplanationYou are not allowed to enter the ZOCTM STOPcommand twice (OCTM has already been stopped).

DXC5140E Invalid Year

ExplanationYou entered the ZPERF command with a DATEparameter using a year for which no historyinformation was collected.


ModuleCPM6

DXC5141E Invalid Day

ExplanationYou entered the ZPERF command with a DATEparameter using a day for which no history informationwas collected.


ModuleCPM6

DXC5142E No history information

ExplanationYou entered the ZPERF or ZSTAT command with aDATE parameter using a period for which no historyinformation was collected.


ModuleCPM6

DXC5143I Performance Table initialized

ExplanationThis message is a normal response to the ZPERFINITIALIZE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM2

DXC5144I Performance Monitor activated

ExplanationThis message is a normal response to the ZPERFACTIVATE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM3

DXC5145I Performance Monitor deactivated

ExplanationThis message is a normal response to the ZPERFDEACTIVATE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM3

DXC5146E Already active

ExplanationThe performance monitor is already active.

ModuleCPM3

DXC5147E Already inactive

ExplanationThe performance monitor is already inactive.


ModuleCPM3

DXC5148E Invalid Month

ExplanationYou entered the ZPERF command with a DATEparameter using a month for which no historyinformation was collected.


ModuleCPM6

DXC5149E Performance Monitor Applicationnot found

ExplanationYou entered the ZPERF FORCE command, but theperformance Monitor application PERF does not exist.

Operator responseInform your system programmer if the performancemonitor application PERF must be defined.

ModuleCPM2

DXC5150W Performance Monitor is notenabled

ExplanationYou entered a ZPERF or ZCTHR command, but theperformance monitor is not enabled.

Operator responseInform your system programmer if the performancemonitor must be enabled.

ModuleCPM1


ExplanationThis message is a normal response to the ZPERF CPUcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCPM1


ExplanationThis message is a normal response to the ZPERF SYScommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCPM1


ExplanationThis message is a normal response to the ZPERF SPIcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCPM1


ExplanationThis message is a normal response to the ZPERF I/Ocommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCPM4


ExplanationThis message is a normal response to the ZPERFPOOL command. See ALCS Operation and Maintenancefor a full explanation of the command response.

ModuleCPM4



ExplanationThis message is a normal response to the ZPERFTASK command. See ALCS Operation and Maintenancefor a full explanation of the command response.

ModuleCPM4

DXC5161E Invalid Date/Time

ExplanationYou entered the ZPERF command with either anincorrect date or incorrect time.

Operator responseUse correct numeric values for either date or time, andretry the command.

ModuleCPM1, CPM2, CPM4, CPM6

DXC5162E Invalid Performance Monitorapplication

ExplanationYou entered the ZPERF command with aninvalid performance monitor application name.Performance monitor application names consist of fouralphanumeric characters and can not be one of thefollowing reserved names: SYST, DFT1, DFT2, DFT3.


ModuleCPM1, CPM2, CPM4

DXC5163E No Storage Unit information

ExplanationYou entered the ZPERF command with a DATEparameter using a period for which no historyinformation was collected.


ModuleCPMF

DXC5164E Invalid CRAS Authorization

ExplanationThe ZPERF commands ADD, DELETE, INITIALIZE,ACTIVATE, DEACTIVATE, FORCE, AVERAGE, andPURGE are allowed only from Prime CRAS. All otherZPERF commands are allowed from Prime CRAS orAlternate CRAS AT1 to AT16.


ModuleCPM2, CPM3

DXC5165E Invalid ZPERF command

ExplanationYou entered a ZPERF command with an invalidparameter.




ExplanationThis message is a normal response to the ZPERF SUcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCPMF

DXC5167E Invalid ECB address

ExplanationYou entered the ZPERF FORCE command with aninvalid ECB address.



ModuleCPM2

DXC5168E Invalid level

ExplanationYou entered the ZPERF command with an invalid level.The level must be either 1, or 2, or 3.



DXC5169I Performance Monitor Applicationadded

ExplanationThis message is a normal response to the ZPERF ADDcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCPM2

DXC5170I Performance Monitor Applicationdeleted

ExplanationThis message is a normal response to theZPERF DELETE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM2

DXC5171I ZPERF FORCE finished

ExplanationThis message is a normal response to theZPERF FORCE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM2

DXC5172I ZPERF AVERAGE finished

ExplanationThis message is a normal response to the ZPERFAVERAGE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM2

DXC5173I ZPERF PURGE finished

ExplanationThis message is a normal response to theZPERF PURGE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPM2

DXC5174W Performance Monitor Table full

ExplanationThis message is a response to the ZPERF ADDcommand.

Operator responseDelete unused performance monitor applications andretry the command.

ModuleCPM2

DXC5176W Performance Monitor Applicationexists already

ExplanationYou entered the ZPERF ADD command, but theperformance monitor application already exists.


ModuleCPM2

DXC5177W Performance Monitor Applicationnot found


ExplanationYou entered the ZPERF DELETE command, but thisperformance Monitor application does not exist.


ModuleCPM2

DXC5178W Performance Monitor historycollection has been aborted

ExplanationThe Performance Monitor history collection processhas terminated abnormally.

System programmer responseInvestigate the dump of the problem that causedthe process abortion. Use ZDRIV CPM5 to restart thePerformance Monitor history collection process.

ModuleCPM5

DXC5180E Invalid CRAS authorization

ExplanationThe commands ZCTCB ACTIVATE and ZCTCBDEACTIVATE are allowed only from Prime CRAS. Allother ZCTCB commands are allowed from Prime CRASor high CRAS (AT1-16).


ModuleCLCC

DXC5181E Invalid ZCTCB command

ExplanationYou entered a ZCTCB command with an invalidparameter.


ModuleCLCC

DXC5182I One CPU loop activated

ExplanationThis message is a normal response to the ZCTCBACTIVATE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCLCC

DXC5183I One CPU loop deactivated

ExplanationThis message is a normal response to the ZCTCBDEACTIVATE command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCLCC

DXC5184W Can not activate a CPU loop

ExplanationThis message is a response to the ZCTCB ACTIVATEcommand when all CPU loops are already active.

ModuleCLCC

DXC5185W Can not deactivate a CPU loop

ExplanationThis message is a response to the ZCTCBDEACTIVATE command when only one CPU loop isactive.

ModuleCLCC

DXC5186E DYNTCB=NO specified in SCTGEN

ExplanationThe commands ZCTCB ACTIVATE and ZCTCBDEACTIVATE are not allowed as the ALCS dynamicTCB facility is not enabled.


Operator responseInform your system programmer if the ALCS dynamicTCB facility must be enabled.

System programmer responseDetermine if the ALCS dynamic TCB must be enabled(for example, you must not enable this facility if yourapplication programs do not serialize access to theglobal area). See ALCS Installation and Customizationfor information about enabling this facility if it isrequired.

DXC5187E Invalid TASK name

ExplanationYou entered the ZCTCB TASK command with aninvalid NAME parameter.


ModuleCLCC


ExplanationThis message is a normal response to theZCTCB REPORT command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCLCC


ExplanationThis message is a normal response to the ZCTCBTASK command. See ALCS Operation and Maintenancefor a full explanation of the command response.

ModuleCLCC

DXC5200I SAF data for group gnamedddddddd dddddddd dddddddddddddddd *cccccccccccccccc*dddddddd ........ *cccc.... * ⋮

ExplanationThis message is a normal response to the commandZDCOM.

DXC5201I Terminal not logged on

ExplanationZDCOM SAF was issued, but there was no end userlogged on to the resource.

Operator responseIssue ZLOGN command to log on to ALCS if requiredand retry the command.

DXC5202I SAF data not found

ExplanationZDCOM SAF was issued, but no external securitymanager data exists for the resource.

Operator responseIf you expected data to exist, ask your systemprogrammer to check the status of the externalsecurity manager for the end user that is currentlylogged on to the affected resource.

DXC5203I SAF data for group gnamesuppressed by installation-wideexit

ExplanationZDCOM SAF was issued, but the installation-wide exitprogram ASD1 determined that the external securitymanager data should not be displayed.

Operator responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the command.

System programmer responseSee ALCS Installation and Customization for a fulldescription of the installation-wide exit ASD1.

DXC5204I SAF group name not found

ExplanationZDCOM SAF was issued, but no external securitymanager connected GROUP profile was found in theACEE for the resource.


Operator responseAsk your system programmer to check the status ofthe external security manager for the end user that iscurrently logged on to the affected resource.

DXC5205I SAF data for CRN-'crn' cannot beaccessed

ExplanationZDCOM SAF was issued, but ALCS was unable to accessthe external security manager data.

Operator responseIf you expected data to exist, ask your systemprogrammer to check the status of the externalsecurity manager for the end user that is currentlylogged on to the affected resource.

DXC5215E Program not found

ExplanationYou entered a ZALCS PROGRAM to display theinformation of a program that is not currently loaded.

Operator responseRetry the command with an existing program name.

ModuleCAT8

DXC5216E Invalid seq file definition or status

ExplanationYou entered a ZALCS PROGRAM to list programinformation into a sequential file. The sequential filehas an invalid definition or is not available for use.

Operator responseInvestigate and fix the error condition of the sequentialfile and retry the command.

ModuleCAT8

DXC5217I List of programs generated

ExplanationThis is the normal response when you enter aZALCS PROGRAM to list program information into asequential file.

ModuleCAT8

DXC5217I List of programs generated

ExplanationThis is the normal response when you enter aZALCS PROGRAM to list program information into asequential file.

ModuleCAT8

DXC5218I Program counter reset

ExplanationThis is the normal response when you enter a ZALCSPROGRAM to reset the program counter.

ModuleCAT8

DXC5219I Normal response

ExplanationThis is the normal response when you enter a ZALCSPROGRAM to display program information.

ModuleCAT8

DXC5221E Invalid monitor storage area name

ExplanationYou entered a ZALCS S mmmmmmmm command, wheremmmmmmmm is an incorrect monitor storage areaname.

Operator responseCorrect the incorrect name and retry the command.

ModuleCAT2

DXC5222E Invalid monitor save area name

ExplanationYou entered a ZALCS S SAVE=ssss command,where ssss is an incorrect monitor save area name.



ModuleCAT2

DXC5223E Invalid CPU loop number

ExplanationYou entered a ZALCS S SAVE=ssss CPU=llcommand, where ll is an incorrect monitor cpu loopnumber.

Operator responseCorrect the cpu loop number name and retry thecommand.

ModuleCAT2

DXC5224E Monitor storage area not found ornot available

ExplanationYou entered a ZALCS S mmmmmmmm command, wheremmmmmmmm is the name of a monitor storage areathat is not found in the system table or has not beeninitialized yet.


ModuleCAT2

DXC5225E CPU loop number exceedsmaximum

ExplanationYou entered a ZALCS S SAVE=ssss CPU=ll, wherell exceeds the current number of available CPU loop.

Operator responseCorrect the incorrect cpu loop number and retry thecommand.

ModuleCAT2

DXC5226E Invalid csect address

ExplanationYou entered a ZALCS M ADDR=aaaaaaaa command,where aaaaaaaa is an incorrect address.

Operator responseCorrect the incorrect address and retry the command.

ModuleCAT3

DXC5227E Monitor save area name not found

ExplanationYou entered a ZALCS S SAVE=ssss command,where ssss is the name of a monitor save area thatis not found in the system table.


ModuleCAT2

DXC5228E Invalid TOD clock value

ExplanationYou entered a ZALCS M TOD=tttttttt command,where tttttttt is a invalid TOD clock value.

Operator responseCorrect the incorrect TOD clock value and retry thecommand.

ModuleCAT3

DXC5229E Can not convert TOD before 1976

ExplanationYou entered a ZALCS M TOD=tttttttt command,where tttttttt is the value of a TOD clock before the yearof 1976.

Operator responseCorrect the incorrect TOD clock value and retry thecommand.


ModuleCAT3


ExplanationThis is the normal response for ZALCS TOD clockconvertion.

ModuleCAT3

DXC5234E Momb control table not found

ExplanationYou entered a ZALCS M MOMB but the Momb controltable area has not been initialized yet by ALCS.

Operator responseRetry the command when ALCS starts using the Mombcontrol table.

ModuleCAT3

DXC5235E Momb entry table not found

ExplanationYou entered a ZALCS M MOMB but the Momb entrytable area has not been initialized yet by ALCS.

Operator responseRetry the command when ALCS starts using the Mombentry table.

ModuleCAT3

DXC5236E VFA staging buffers not found4

ExplanationYou entered a ZALCS V STAGE but ALCS is not usingVFA staging buffers.

Operator responseRetry the command when ALCS starts using the VFAstaging buffers.

ModuleCAT6

DXC5239E VFA control area not found

ExplanationYou entered a ZALCS V CONTROL but ALCS has notinitialized the VFA control area.


ModuleCAT6


ExplanationThis is the ZALCS command display header for normalresponses.

ModuleCAT3,CAT6

DXC5241E Address outside monitor csectarea range

ExplanationYou entered a ZALCS M ADDR=aaaaaaaa, whereaaaaaaaaaa is an address which is not part of anyALCS monitor csect.

Operator responseCorrect the incorrect address and retry the command.

ModuleCAT3


ExplanationThis is the ZALCS TAG command display header.

ModuleCAT4



ExplanationThis is the normal response for the ZALCS SYS ADDRcommand.

ModuleCAT3


ExplanationThis is a normal response (interface connected) to theZCWAS DISPLAY command.

See ALCS Operation and Maintenance for a fullexplanation of the command response.

ModuleCWAS


ExplanationThis is a normal response (interface disconnected) tothe ZCWAS DISPLAY command.


ModuleCWAS


ExplanationThis is a normal response (interface disconnecting) tothe ZCWAS DISPLAY command.


ModuleCWAS

DXC5253E Can not connect WAS interface

ExplanationYou can not connect as the interface is disconnectingor is already connected.

ModuleCWAS

DXC5254E Can not disconnect WAS interface

ExplanationYou can not disconnect as the interface isdisconnecting or is already disconnected.

ModuleCWAS

DXC5255I WAS interface now connected

ExplanationThis is a normal response to a ZCWAS CONNECTcommand.

ModuleCWAS

DXC5256I WAS interface now disconnecting

ExplanationThis is a normal response to a ZCWAS DISCONNECTcommand.

ModuleCWAS

DXC5257E Invalid ZCWAS command

ExplanationYou entered a ZCWAS command with an invalidparameter.

Operator responseCorrect the typing or syntax error and retry thecommand

ModuleCWAS

DXC5258E Invalid CRAS authorisation

ExplanationThe ZCWAS commands ZCWAS CONNECT and ZCWASDISCONNECT are allowed only from Prime CRAS. TheZCWAS DISPLAY command is allowed from any CRAS.

ModuleCWAS


DXC5259E ALCS - WAS interface not enabled

ExplanationThe ALCS system configuration table does not specifysupport for WAS.


System programmer responseSee ALCS Installation and Customization forinformation on how to configure WAS support.

ModuleCWAS

DXC5300I TCP/IP trace to DIA file started

ExplanationThis is a normal response to the ZCTCPTRACE,START command

DXC5301I TCP/IP trace to DIA file stopped

ExplanationThis is a normal response to the ZCTCP TRACE,STOPcommand.

DXC5302I TCP/IP trace area cleared

ExplanationThis is a normal response to the ZCTCPTRACE,CLEAR command.

DXC5304I No TCP/IP trace data to display

ExplanationThis is a normal response to the ZCTCP TRACE,SHOWcommand.

DXC5305I TCP/IP trace data

ExplanationThis is a normal response to the ZCTCP TRACE,SHOWcommand. See ALCS Operation and Maintenance for afull explanation of the trace display format.


ExplanationThis message is a normal response to the ZPCTLDISPLAY mmmmmm, PROGRAMS command. See ALCSOperation and Maintenance for a full explanation of thecommand response.

ModuleCPCD


ExplanationThis message is a normal response to the ZDPGMpppp,MODULES command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCVAM

DXC5330E Load failed - At least one duplicatemodule name

ExplanationThis message is an error response to the ZPCTL loadset command. At least one load module of the loadset was previously loaded.

System actionALCS will not load any load module of this load set.


System programmer responseSee message DXC2819E on the RO CRAS for details.Correct the load set, re-run the load set generation,and ask the operator to retry.

DXC5331E Load failed - At least one loadmodule could not be loaded

ExplanationThis message is an error response to the ZPCTL loadset command. At least one load module of the loadset could not be loaded.




System programmer responseSee message DXC2820E on the RO CRAS for details.Correct the load set, re-run the load set generation,and ask the operator to retry.

DXC5332W Load failed - Configuration Dataset is locked

ExplanationThis message is an error response to the ZPCTLload set command. This error can occur if ALCS hasreceived simultaneous ZACOM or ZPCTL commandsand ALCS is using a program configuration data set..


Operator responseRetry the command.

DXC5333E Load failed - Incorrect number ofload modules in load set

ExplanationThis message is an error response to the ZPCTL loadset command. The number of load modules of theload set is incorrect.



System programmer responseCorrect the load set, re-run the load set generation,and ask the operator to retry.

DXC5334E Load failed - Incorrect load setname

ExplanationThis message is an error response to the ZPCTL loadset command. The generated load set name is not thesame as load set name used in the ZPCTL load setcommand.



System programmer responseCorrect the load set name in the load set, re-run theload set generation, and ask the operator to retry.

DXC5335E Load failed - Incorrect load setversion

ExplanationThis message is an error response to the ZPCTL loadset command. You tried to load a corrupted load set.



System programmer responseThis problem can not occur. Please contact your IBMprogramming support representative.

DXC5336E Load failed - Incorrect load set tag

ExplanationThis message is an error response to the ZPCTL loadset command. You tried to load a corrupted load setor the referenced module is not a load set at all.



System programmer responseRe-run the load set generation. and ask the operator toretry.

DXC5337E Load failed - At least one duplicatemodule name in load set


ExplanationThis message is an error response to the ZPCTL loadset command. There is at least one duplicate modulename in the generated load set.




DXC5338E Load failed - Error during load setload

ExplanationThis message is an error response to the ZPCTL loadset command. The load set could not be found.




DXC5339E Load failed - No storage -- Tryagain

ExplanationThis message is an error response to the ZPCTL loadset command.


Operator responseRetry the command. If the problem persists, informyour system programmer.

System programmer responseIncrease the total number of I/O control blocks(IOCBs) in the ALCS system. (See the descriptionof the SCTGEN macro NBRIOB parameter in ALCSInstallation and Customization) and ask the operatorto retry.

DXC5340E Load failed - Module load table full




System programmer responseUpdate the program configuration table to increase thenumber of modules expected in the system. Assembleand link-edit the program configuration table, restartALCS and ask the operator to retry.

DXC5341E Load failed - Program table full




System programmer responseUpdate the program configuration table to increasethe number of programs expected in the system.Assemble and link-edit the program configurationtable, restart ALCS and ask the operator to retry.

DXC5342E Load failed - Configuration DataSet full

ExplanationThis message is an error response to the ZPCTLload set command while ALCS is using a programconfiguration data set.




System programmer responseLoad and confirm the alternate program configurationtable load list, restart ALCS, and ask the operator toretry.

DXC5343E Load failed - Request is out ofsequence

ExplanationThis message is an error response to the ZPCTLload set command. You have tried to perform anaction out of sequence while ALCS is using a programconfiguration data set.


Operator responseRefer to ALCS Operation and Maintenance for anexplanation about how to perform the action in thecorrect sequence.

DXC5344I All modules of load setsuccessfully loaded

ExplanationThis message is a normal response to the ZPCTLload set command.

System actionALCS did load all load modules of this load set.

Operator responseSee message DXC2818I on the RO CRAS for details.

DXC5345E Not authorized to request thisfunction

ExplanationThis function is only allowed from Prime CRAS..

Operator responseRetry the command from Prime CRAS.

DXC5400I Table successfully created

ExplanationThis message is a normal response to the ZPDARCREATE command.

ModuleCPDR

DXC5401W Table already exists

ExplanationThis message is a response to the ZPDAR CREATEcommand. The PDAR table already exists.

ModuleCPDR

DXC5402I Table successfully cleared

ExplanationThis message is a normal response to the ZPDARDELETE command.

ModuleCPDR

DXC5403E Table does not exist

ExplanationYou entered a ZPDAR DELETE or DISPLAY commandwithout initializing the PDAR table structure first.

ModuleCPDR


ExplanationThis message is a normal response to theZPDAR DISPAY command. See ALCS Operation andMaintenance for a full explanation of the commandresponse.

ModuleCPDR

DXC5406W Table empty


ExplanationYou entered a ZPDAR DISPLAY command to displaythe PDAR table structure, but the table is empty.

ModuleCPDR


ExplanationThis message is a normal response to theZPDAR DISPAY command. See ALCS Operation andMaintenance for a full explanation

ModuleCPDR

DXC5408W Dispensing is still active

ExplanationYou entered a ZPDAR DELETE or CREATE whilethe system is in restore mode and the PDAR tablestructure is still in use.

Operator responseWait until all reserved records from the PDAR tablestructure are dispensed.

ModuleCPDR


ExplanationThis message is a normal response to the ZCICF QICFcommand. See ALCS Operation and Maintenance for afull explanation of the command response

ModuleCICF


ExplanationThis message is a normal response to the ZCICF QALGcommand. See ALCS Operation and Maintenance for afull explanation of the command response.

ModuleCICF

DXC5492E ICSF call failed withRC-X’return_code’ and RSN-x’reason_code’

ExplanationThis error was produced in response to a ZCICF QALGor ZCICF QICF command.

This error was produced in response to a ZCICF QALGor ZCICF QICF command.

Programmer responseInform your IBM programming support representative.

ModuleCICF

DXC5493I ICSF not supported by this ALCS

ExplanationA ZCICF command has been entered on an ALCSInstallation and Customization system that does nothave ICSF support generated. See ALCS Installationand Customization for information on how to configureICSF.

ModuleCICF

DXC5500I Mapping Data obtained from xxxx

ExplanationThis is an informational message that identifies thesource of the mapping data used to produce theZDMOD output. The three sources of mapping dataare:

1. Binder Module Mapping (BMMP) records loadedwith a module by using the MODMAP=LOADparameter when the module is bound. ALCSsegment DXCBMMP must be included in the bindstep in order to locate the BMMP records in storage.

2. Binder Module Mapping records stored with amodule in a PDS.

3. Reading the individual (RLD, ESD, IDR, etc) records.

Operator responseNone.


Modulecdmprc.c

DXC5501E Program and Address parametersare mutually exclusive

ExplanationThe ZDMOD command was issued with both a programname and the ADDRESS parameter. These parametersare mutually exclusive.

Operator responseReissue the ZDMOD command with either a programname or the ADDRESS parameter.

Modulecdmer1.c

DXC5502E Function and Address parametersare mutually exclusive

ExplanationThe ZDMOD command was issued with both theFUNCTION and the ADDRESS parameter. Theseparameters are mutually exclusive.

Operator responseReissue the ZDMOD command with either theFUNCTION or ADDRESS parameter.

Modulecdmer1.c

DXC5503E Section and Address parametersare mutually exclusive

ExplanationThe ZDMOD command was issued with both theSECTION and the ADDRESS parameter. Theseparameters are mutually exclusive.

Operator responseReissue the ZDMOD command with either theSECTION or ADDRESS parameter.

Modulecdmer1.c

DXC5504E Input message format incorrect.Enter ZDMOD HELP to see thecorrect format

ExplanationThe ZDMOD command was issued with incorrectoperands.

Operator responseReissue the command using the correct syntax.

Modulecdmer1.c

DXC5505E Program pppppppp contains nolink map data

ExplanationThe routine used to gather mapping information aboutprogram pppppppp has not returned any data.

Operator responseContact IBM for programming assistance.

Modulecdmer1.c

DXC5506E Unable to find module table entryfor pppppppp

ExplanationProgram name pppppppp was specified on a ZDMODcommand, but is not a correct program.

Operator responseReissue the ZDMOD command with a valid programname.

Modulecdmer1.c

DXC5507I Install AM33370 to add supportfor ZDMOD command

ExplanationYou entered a ZDMOD command but the ZDMODcommand is not installed on this system. Install APARAM33370 to add support for ZDMOD. Both AM33370and AM22459 are required for ZDMOD support.


Modulecmod.asm

DXC5508E No match found in programpppppppp for function ffffffff

ExplanationThe function name specified using the FUNCTIONoperand on the ZDMOD command was not found inany of the specified programs.

Operator responseReissue the ZDMOD command by widening yoursearch using one or more wildcards. For example:use ZDMOD CMOD f-*sort* instead of ZDMOD CMODf-sort or ZDMOD CMO* f-sort instead of ZDMODCMOD f-sort.

Modulecdmer1.c

DXC5509E No match found in programpppppppp for section ssssssss

ExplanationThe section name specified using the SECTIONoperand on the ZDMOD command was not found inany of the specified programs.

Operator responseReissue the ZDMOD command with a section namethat will be found. You might want to widen yoursearch by using a wildcard. For example: ZDMOD CMODs-*main*.

Modulecdmer1.c

DXC5510E ZDMOD Internal Error: ObjectConstructor failed for modulemmmmmmmm

ExplanationAn error has occurred during the process of gatheringmapping information for module mmmmmmmm.

Operator responseVerify that mmmmmmmm is a valid module. If themodule is valid, contact IBM for assistance.

Modulecdmer1.c

DXC5511E Not enough malloc storageavailable to process all link mapdata for program pppppppp

ExplanationA malloc() function failed.

Operator responseIncrease the amount of storage available to C/C++programs by using the SCTGEN macro with the NBRSUand SUSIZE parameters.

Modulecdmer1.c

DXC5512E Program containing addressaaaaaaaa could not be found

ExplanationThe address specified by the ADDRESS operandon a ZDMOD command does not reside within anidentifiable program.

Operator responseReissue the ZDMOD command with an address that iswithin a loaded program.

Modulecdmer1.c

DXC5513E No matching program could befound

ExplanationA ZDMOD command was issued with a wildcardcharacter in the program name field but no matchingprograms were found.

Operator responseWiden your search by entering the ZDMOD commandagain using wildcards that can result in more matches.For example: instead of using ZDMOD CMO* f-sort,use ZDMOD CM* f-sort or ZDMOD CMO* f-*sort*.

Modulecdmer1.c


DXC5514I The following programs containmatches

ExplanationA ZDMOD command was issued with a wildcardcharacter in the program name that matched morethan one program. The list of possible matchingprograms follows.

Operator responseIf you want information for a single program, reissuethe ZDMOD command with operands that morecompletely identify the desired program. For example,if zdmod dxcax* yields more than one programand you want information on a single program thecommand zdmod dxcax*2 may result in one programname and the desired information. Adding 2 to the endof the name specification describes the same subsetas dxcax* but further eliminates all programs exceptfor those ending in 2.

Modulecdmain.c

DXC5515E Case and Address parameters aremutually exclusive

ExplanationThe ZDMOD command was issued using both the CASEand the ADDRESS parameters. These parameters aremutually exclusive.

Operator responseReissue the ZDMOD command with either a CASE orthe ADDRESS parameter but not both.

Modulecdmer1.c


Chapter 9. ALCS Web Server and Hierarchical FileSystem (HFS) messages: DXC6000-DXC6999

DXC6001I OK

ExplanationThe ALCS HFS command completed normally.

DXC6010E Unknown command

ExplanationThe input command is not supported by the ALCShierarchical file system (HFS) application.

User responseCorrect the typing or syntax error and retry thecommand.

DXC6011E Incorrect command format

ExplanationThe input command format is not correct.

User responseCorrect the typing or syntax error and retry thecommand.

DXC6012E Error processing command

ExplanationThe ALCS hierarchical file system (HFS) applicationwas unable to process the command. For example:

• You attempted to delete or rename a file that doesnot exist.

• You attempted to rename a file to the name ofanother existing file.

• The name you specified on a cd or rd command isnot the name of a directory.

User responseRetry the command using a valid HFS file name ordirectory name.

DXC6013E Unauthorized for this command

ExplanationYou attempted to use the ALCS hierarchical file system(HFS) but your user ID is not authorized to issuecommands which update the HFS.

User responseIf you believe you should be authorized to update theHFS, then contact the person in your organization whohas responsibility for allocating user IDs and so on.This person may be called your security coordinator,your system programmer, or may have some othertitle.

DXC6020E Current directory invalid - reset toroot

ExplanationThe name recorded as your current directory is notvalid. Another user may have deleted the directory.

System actionYour current directory is reset to the root.

DXC6030I ALCS TCP/IP trace data

ExplanationThis message is a normal response to a Web browserrequest to display the contents of the system TCP/IPtrace block. See ALCS Operation and Maintenance for afull explanation of the trace display format.

DXC6032I No ALCS TCP/IP trace data todisplay

ExplanationThis message is a normal response to a Web browserrequest to display the contents of the system TCP/IPtrace block.


Chapter 10. Responses to ALCS commands:DXC8000-DXC8999

DXC8001E Invalid command format

ExplanationYou have made a general error in submitting thecommand. This is probably a typing error or asyntactical error. See ALCS Operation and Maintenancefor a full explanation of how to use the commands.


DXC8002E Unknown command

ExplanationThis command does not exist in ALCS. See ALCSOperation and Maintenance for a full explanation ofhow to use the commands.


DXC8003E Wrong system state

ExplanationALCS is in the incorrect system state to perform thiscommand.

Operator responseChange the ALCS system state with the ZASYScommand or ask your system programmer to informyour IBM programming support representative.

DXC8004E Not authorized to request thisfunction -- Prime CRAS only


Operator responseTry again from Prime CRAS.

DXC8005E CRAS only

ExplanationThis command can only be issued from a CRASterminal.

Operator responseTry again from a CRAS terminal.

DXC8006I Request accepted

ExplanationALCS is processing your request normally.

DXC8007E Unmatched parenthesis


Operator responseReissue the command using the correct syntax.You must use opening and closing parentheses forexample ( message ).

DXC8008E Parameter too long



DXC8009E Keyword invalid or omitted



DXC8010E Keyword too long




DXC8011E Unmatched quote

ExplanationYou have used a single and a double quote in yoursyntax. You must use either 'command' or "command".


DXC8012E Invalid keyword parameter

ExplanationYou have entered an incorrect keyword parameter. SeeALCS Operation and Maintenance for a full explanationof how to use the commands.


DXC8013E Invalid positional parameter

ExplanationYou have entered an incorrect positional parameter.See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


DXC8015E Not authorized to request thisfunction -- CRAS only


Operator responseTry again from a CRAS terminal.


ExplanationThis function is only allowed from certain terminals.

Operator responseCheck which CRAS terminals are allowed to issue thiscommand and retry from the correct CRAS terminal.

DXC8017E CRI parameter invalid or omitted



DXC8018E CRN parameter invalid or omitted



DXC8019E Prime CRAS or AT1 - AT16 only

ExplanationThis command must be issued from Prime CRAS orAT1 -- AT16 only.

Operator responseTry again from the correct terminal.

DXC8020E Required parameter omitted



DXC8021E Both parm1 and parm2 omitted

ExplanationYou have entered a command that requiresparameters and have failed to enter them or you havemisspelled them.



DXC8022E Specified resource is not AT1 -AT16


Operator responseReissue the command after checking that the resourceis one of AT1 -- AT16.

DXC8023E Unable -- Not allowed forcras_type CRAS

ExplanationThis command is not allowed from this CRAS. SeeALCS Operation and Maintenance for a full explanationof how to use the commands.


DXC8024E Unable -- System state change inprogress

ExplanationA system state change has not completed processing.ALCS will not process another state change request(except with the FORCE or RESET parameter) untilsystem state change is complete.

System actionALCS will not accept this entry during a state change.

Operator responseWait until the state change is complete before retryingthe command.

DXC8025E parm parameter invalid or omitted



DXC8026E Invalid CRI/CRN specified



DXC8027E parm parameter invalid

ExplanationYou have used an incorrect parameter or you havemisspelled the parameter.


DXC8028I OK

ExplanationThe command is accepted.


DXC8029I Request completed

ExplanationALCS has completed the process.

System actionALCS waits for the next entry.

DXC8030E Function inhibited by installationrestriction

ExplanationThis function cannot proceed because of a restrictionto your installation imposed by the SystemProgrammer.

Operator responseAsk your system programmer to inform your IBMprogramming support representative.

DXC8031E Too many parameters specified




DXC8032E Not enough parameters specified



DXC8033E Invalid or omitted operand forkeyword name

ExplanationZASEQ seq,... (for example) can update the generalsequential file definition with any correct keywordsand then give this error response.

Operator responseUse ZDSEQ to check the effect of the command.Correct the typing or syntax error and retry thecommand.

DXC8034I parm OK

ExplanationThe command and the parameter have been accepted.

System actionALCS processes the command normally.

DXC8035E Program name invalid or omitted

ExplanationYou have entered an incorrect program name.


DXC8036E System error

ExplanationAn internal error has occurred in ALCS.

Operator responseInform your IBM programming support representative.

DXC8037E Program not loaded

ExplanationThis application program is not available on yourinstallation.


System programmer responseCheck the application program load list.

DXC8038E Comments are missing

ExplanationThis command must include comments. See ALCSOperation and Maintenance for a full explanation ofhow to use the commands.


DXC8039I Started Progress messages onprinter -- CRN-crn CRI-cri

ExplanationThis is a normal response to an ALCS command. SeeALCS Operation and Maintenance for a full explanationof how to use the commands.

DXC8040E Configuration table name invalidor omitted

ExplanationYou have entered an incorrect configuration tablename.


DXC8041E Unexpected keyword parameter




DXC8042E File address invalid or omitted

ExplanationThe address is not a valid 4-byte file address.

Programmer responseCorrect the error and try again.

DXC8043E Unable -- No ROCRAS printer

ExplanationALCS is attempting to send output when the Read OnlyCRAS printer (ROC) is not assigned.

Operator responseAssign the Read Only CRAS printer.

DXC8044E Invalid alternate CRAS number

ExplanationThis is not an alternate CRAS which has been definedin the system configuration.


System programmer responseAdd this alternative CRAS to the ALCS generation.See ALCS Installation and Customization for detailedinstructions.

DXC8045I Output on printer -- CRN-crn CRI-cri

ExplanationThis message is a normal response to the commandZDRIV.

DXC8046E Unable - No associated printer

ExplanationALCS is attempting to send output when no printer hasbeen associated with this display.

Operator responseCheck the syntax of your command; if in error, correctand retry. If syntax is correct, assign a printer to thisdisplay. Otherwise contact your system programmer.

DXC8047I Started

ExplanationALCS has started the process.

System actionALCS continues to process the command normally.

DXC8048I Cancelled

ExplanationThis message is a normal response to the commandZRELO. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8049I Paused

ExplanationALCS has made a temporary stop in the processing of acommand.

System actionALCS waits before continuing to process thecommand.

DXC8050I Restarted

ExplanationALCS continues to process the current entry after atemporary pause.

DXC8051I Being cancelled Progress messageon printer - CRN-crn CRI-cri


DXC8052I Being paused


ExplanationA process is being paused.

System actionALCS pauses and waits for the next entry.

DXC8053I Not active

ExplanationALCS is not available to process the entry.

DXC8054E Seq file is not an output generalseq file

ExplanationThe command did not request an output generalsequential file.

Operator responseUse the ZDSEQ command to display the sequential file.If the information is correct then inform your systemprogrammer.

System programmer responseCheck the ALCS sequential file generation.

DXC8055E Seq file is not an input general seqfile

ExplanationThe command did not request an output generalsequential file.

Operator responseUse the ZDSEQ command to display the sequential file.If the information is correct then inform your systemprogrammer.

System programmer responseCheck the ALCS sequential file generation.

DXC8056E First parameter must be positional



DXC8057I No message on file

ExplanationThis is a normal response to ZSCRL when there isno message to scroll, and to ZSNDU when there is nounsolicited message to retrieve.

Programmer responseCorrect the typing or syntax error and retry thecommand.

DXC8058E Invalid numeric value



DXC8059E Resource is not a terminal



DXC8061E Application is not known to ALCS

ExplanationThis application is not defined in the current ALCSgeneration.


System programmer responseCheck the communications generation. Add thisapplication to the next generation. See ALCSInstallation and Customization for further information.

DXC8062E Resource parameter invalid oromitted




DXC8063E Both parm1 and parm2parameters specified

ExplanationThe two parameters are mutually incompatible.


DXC8064E Sequential file seq not inconfiguration table

Explanationseq is not the symbolic name of a sequential file.

Operator responseUse ZDSEQ with no parameter to display the symbolicsequential file names.

DXC8065E Delimiter invalid or omitted

ExplanationYou have typed an incorrect delimiter.


DXC8066I Parameter parm unknown

ExplanationThis parameter is not accepted by ALCS.


DXC8067I Application name invalid oromitted

ExplanationYou have typed an incorrect application name.

Operator responseUse ZDCOM to display the application. Correct thetyping or syntax error and retry the command.

DXC8068E parm parameter must be numeric

ExplanationYou have typed incorrect parameter information.

Operator responseUse ZDCOM to display the application. Correct thetyping or syntax error and retry the command.

DXC8069E Sequential file name invalid oromitted

ExplanationThe sequential file seq is either misspelled or does notexist.


DXC8070E Command rejected by installation-wide exit ACME

ExplanationALCS called installation-wide exit program ACMEbecause a keyword or positional parameter on theZACOM command was not recognized. However, ACMEwas unable to process the command.

Operator responseCorrect the typing or syntax error and retry thecommand. If the problem persists, contact yoursystem programmer.

System programmer responseCorrect your installation-wide exit program ifnecessary.

DXC8071E Command rejected by installation-wide exit ARO1

ExplanationZROUT appl or ZACOM APPL=appl command wasissued, but the installation-wide exit program ARO1determined that the routing should not be completed.


Operator responseCorrect the typing or syntax error and retry thecommand. If the problem persists, contact yoursystem programmer.

System programmer responseCorrect your installation-wide exit program ifnecessary.

DXC8073E GetHostByName for specifieddomain name failed

ExplanationAn attempt to translate a domain name to an IPaddress using the TCP/IP GetHostByName() functionhas failed

Operator responseVerify that the domain name was specified correctly.

DXC8072E Invalid screen size specified

ExplanationThe screen size value entered is incorrect.


DXC8080E Direction parameter invalided

ExplanationThe direction parameter entered is invalid.

Operator responseCorrect the typing error and retry the command.

ModuleCGTZ

DXC8081E User parameter invalid

ExplanationThe user parameter entered is invalid.


ModuleCGTZ

DXC8082E Begin parameter invalid

ExplanationThe Begin parameter entered is invalid


ModuleCGTZ

DXC8083E End parameter invalid

ExplanationThe end parameter entered is invalid.


ModuleCGTZ

DXC8084W No message found

ExplanationYou entered a ZTRAC msg display command, but nomessage was found.

ModuleCGTY

DXC8085E Size parameter invalid

ExplanationThe Size parameter entered is invalid.


ModuleCGTZ

DXC8086E Top parameter invalid


ExplanationThe top parameter entered is invalid.


ModuleCGTZ

DXC8087E Begin/End parameters invalid

ExplanationThe Begin - End range is incorrect.


ModuleCGTZ


ExplanationThis a normal response to a ZTRAC msg displaycommand.

ModuleCGTY


ExplanationThis a normal response to a ZTRAC msg display totalscommand.

ModuleCGTY

DXC8090E Max number of traces are active

ExplanationEight traces are active at this moment

Operator responseStop a trace and retry the command.

ModuleCGTZ

DXC8091E Already active

ExplanationYou tried to start a trace, which is already active.

Operator responseCorrect and retry the command.

ModuleCGTZ

DXC8092E Not enabled

ExplanationYou entered a ZTRAC msg command, but the onlinemessage trace facility is not enabled.

Operator responseInform your system programmer if the online messagetrace facility must be enabled.

System programmer responseSee ALCS Installation and Customization informationon the SCTGEN MSGTRACE parameter..

ModuleCGTZ

DXC8093E Not found

ExplanationYou tried to stop, clear, or display a trace, which is notactive.


ModuleCGTZ

DXC8095W No active traces

ExplanationYou entered a ZTRAC msg display totals command, butno traces were active.


ModuleCGTY

DXC8096E Must be PRC or AT1-AT16

ExplanationYou are not authorized to request this function.

Operator responseTry again from either Prime CRAS or from alternate(AT1-AT16) CRAS.

ModuleCGTZ

DXC8097E Parameter entered more than once

ExplanationYou entered a ZTRAC parameter more than onceor you entered the mutually exclusive CRN and CRIparameters .


ModuleCGTZ

DXC8100I Invalid associated resource name



DXC8101I Prime CRAS authority assigned, oralternate CRAS authority assigned

ExplanationPrime CRAS or alternate CRAS authority has beensuccessfully assigned.


DXC8102I Resource is not authorized forCRAS status change

ExplanationYou have tried to give CRAS status to a device andthere is no SAF decision, but the device does not havesufficient CRAS authorization to allow the function.

Operator responseCheck that the CRN and CRI of the device youwant to modify are correct. See ALCS Operation andMaintenance for a full explanation of how to use thecommands. If CRAS authorization is required thencontact your security administrator.

DXC8103I No change in CRAS status

ExplanationThe device has not changed from one CRAS type toanother.


DXC8104I Resource is not active

ExplanationYou have tried to use a resource that is not currentlyavailable to the system. For example you have tried todirect output to a printer that is not switched on.

Operator responseCheck the status of the device you wish to use andthen reissue the command.

DXC8105I Invalid channel number

ExplanationThis SLC channel number does not exist. You haveprobably misspelled the channel number.


DXC8106I Invalid NEFLU CRN

ExplanationThis NEFLU CRN does not exist. You have probablymisspelled the entry.



DXC8107I Invalid TOCRN CRN

ExplanationThis CRN does not exist. You have probably misspelledthe entry.


DXC8108I Invalid shadow resource CRN



DXC8109I Invalid sequential file name

ExplanationYou have typed an incorrect sequential file name.

Operator responseUse ZDSEQ with no parameter to display the symbolicnames.

DXC8110I Invalid re-direction CRN



DXC8111I Logoff initiated Please wait -This can take up to 1 minute tocomplete

ExplanationThe request to stop the TCP/IP resource has beenaccepted.


DXC8112I AAA hold set on

ExplanationTerminal hold (sometimes called the message beingprocessed indicator) is switched to on. The applicationcan reject any further input messages from thatterminal.

DXC8113I AAA hold set off

ExplanationTerminal hold (sometimes called the message beingprocessed indicator) is switched to off. The applicationcan reject any further input messages from thatterminal.

DXC8114I Associated resource updated

ExplanationThe ZACOM command has updated the information onthe device as requested.


DXC8115I Terminal routing updated

ExplanationThe routing for input messages for this resource hasbeen updated.


DXC8116I Terminal routing removed

ExplanationThe routing for input messages for this resource hasbeen removed.


DXC8117E Invalid member or list name


ExplanationError response to the command ZACOM. The name ofthe communication configuration load list used in thecommand is incorrect.

Operator responseEnter the command again with the correct name forthe communication configuration load list.

DXC8118I Communication generation loadmodule loaded

ExplanationThis message is a normal response to the commandZACOM load.


DXC8119I Attention -- No entries incommunication generation loadmodule

ExplanationYou have tried to load a communications generationload module that contains no entries.

Operator responseCheck with your system programmer that this is thecorrect load module.

DXC8120I Prime CRAS transferred

ExplanationThe Prime CRAS has been successfully transferred tothe new device.


DXC8121I RO CRAS transferred

ExplanationThe RO CRAS has been successfully transferred to thenew device.


DXC8122I Alternate CRAS updated

ExplanationThe alternate CRAS status has been successfullyassigned.


DXC8123I Logon initiated

ExplanationThe request to log on the device has been accepted.


DXC8124I Resource set active

ExplanationThe command to set the resource to active hassuccessfully completed.


DXC8125I Logoff initiated

ExplanationThe request to log off the device has been accepted.


DXC8126I Resource set inactive

ExplanationThe resource has been set to inactive successfully.


DXC8127I Fallback candidate on

ExplanationThe CRAS is now available as a fallback candidate.


DXC8128I Fallback candidate off


ExplanationThe CRAS device is no longer available as a fallbackcandidate.

DXC8129I SLC channels processed

ExplanationThe SLC channels have been processed as requested.


Operator responseUse ZDCOM to display the SLC channel status.

DXC8130I Owning LU updated

ExplanationThis message is a normal response to the commandZACOM NEFLU.

DXC8131I Error return from printer queueswing

ExplanationThis message is a normal response to the commandZACOM TOCRN.

Operator responseRetry the command or inform your systemprogrammer.

DXC8132I Invalid alternate CRAS resourcespecified

ExplanationYou have tried to give alternate CRAS status orauthority to a device that is not suitable. AT1 toAT16 and AP1 to AP16 can be assigned to IBM 3270terminals or NetView resources only.

Operator responseCheck that the CRN and CRI of the device youwant to modify are correct. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.

DXC8133I Unable to obtain lock for an entry-- Retry

ExplanationThis message is a normal response to the commandZACOM.

System actionALCS waits for you to resubmit the command.


DXC8134I Unable -- Invalid communicationgeneration load module

ExplanationYou have tried to load a communication load modulethat does not exist, or that has the wrong format.For example, the length of the user area in this loadmodule differs from previous load modules.

System actionALCS waits for you to resubmit the command.

Operator responseCorrect the typing or syntax error and retry thecommand. Otherwise create a new load module withthe correct format and load it.

DXC8135I Unable to load communicationgeneration load module


Operator responseCheck the MVS console log for additional messages.Correct the typing or syntax error and retry thecommand.

DXC8136I Unable -- At least one entry in use

ExplanationThe command cannot be processed because one entryis already in use.

Operator responseCheck the MVS console log for additional messages.Correct the typing or syntax error and retry thecommand.


DXC8137I Alternate CRAS status removed



DXC8138I Application is defined aspermanently inactive

ExplanationThe application cannot be used as it has been markedas permanently inactive.


System programmer responseRedefine this application as active.

DXC8139I Resource and associated resourceare the same

ExplanationA resource cannot have itself as its associated device.

Operator responseSelect another device to be the associated device andretry the command.

DXC8140I Application is defined aspermanently active

ExplanationThe application cannot be made inactive as it hasalready been defined as permanently active.

Operator responseCheck with your system programmer and then redefinethe application as not permanently active. You maythen retry the command.

DXC8141I Invalid Prime CRAS resourcespecified

ExplanationYou have tried to give Prime CRAS status or authorityto a device that is not suitable. Prime CRAS canbe assigned to IBM 3270 terminals or NetView

resources only. Prime CRAS can not be assigned to testresources.


DXC8142I Invalid RO CRAS resourcespecified

ExplanationYou have tried to give Read Only CRAS status to adevice that is not suitable. Read Only CRAS can beassigned to IBM 3270 printers or NetView resourcesonly. Read Only CRAS can not be assigned to aresource that is currently unusable.


DXC8143I CRAS authorities removed

ExplanationPrime CRAS and alternate CRAS (or alternate CRAS)authorities have been successfully removed.


DXC8144I Application is already active



DXC8145I Application is already inactive




DXC8146I Unable -- Resource is already insession

ExplanationYou are trying to start to communicate with a devicethat is already connected to ALCS.


DXC8147I Unable -- Resource is not insession

ExplanationThe device is not connected to ALCS.


DXC8148E PRIORITY parameter must be inrange 0 - 14

ExplanationThis is an error response to the command ZACOMPURGE. Sixteen message queues exist but the operatorcan only purge queues with priorities 0 - 14.

Operator responseCorrect the typing and retry the command.

DXC8149I Specified CRN is reserved

ExplanationYou cannot use this CRN because it is reserved.


DXC8150I Resource is not an SLC link



DXC8151I Resource is not an ALCI terminal



DXC8152I Unable -- Resource must beinactive

ExplanationALCS cannot carry out the command because theresource you are trying to use must be inactive.

Operator responseChange the status of the resource to inactive and thenresubmit the command.

DXC8153I Resource is not a terminal, LU 6.1link, or SLC link



DXC8154I Resource is not a printer



DXC8155I Resource is not an X25 PVC



DXC8156I Resource is not an LU6.1 link




DXC8157I Resource is not suitable for CRASfallback

ExplanationYou have selected a device that cannot be used asa CRAS fallback. For example, alternate CRAS AT17through AT255 cannot be used for CRAS fallback.

Operator responseCheck the CRI and CRN of the device; select a suitabledevice and resubmit the command.

DXC8158I Resource is not suitable for logon/logoff request

ExplanationYou have selected a device that cannot be used forlogon/logoff requests. For example, alternate CRASAT17 through AT255 cannot be used for CRASfallback.

Operator responseCheck the CRI and CRN of the device; select a suitabledevice and resubmit the command.

DXC8159E Correct typing, or inactivateresource and retry

ExplanationALCS cannot carry out the command because theresource you are trying to use must be inactive orunusable.

Operator responseChange the status of the resource and then resubmitthe command.

DXC8160I Invalid shadow printer

ExplanationThis device is not suitable as a shadow printer.


DXC8161I Specified shadow resource is not aprinter


Operator responseSelect a printer and resubmit the command.

DXC8162I Already on

ExplanationRedirection is already activated for this resource.


DXC8163I Already off

ExplanationRedirection has not yet been activated for thisresource.


DXC8164I No shadow printers

ExplanationYou must first define a shadow printer before trying tosend information to it.

Operator responseDefine a shadow printer using ZACOM and then retrythe command.

DXC8165I Already maximum number ofshadow printers

ExplanationYou are trying to define more shadow printers than thesystem will allow.



DXC8166I Specified resource is already ashadow printer



DXC8167I No shadow printer found



DXC8168I Invalid redirection printer



DXC8169I Specified redirection resource isnot a printer



DXC8170I Specified resource already aredirection printer



DXC8171I No redirection printer


Operator responseDefine a redirection printer and then retry thecommand.

DXC8172I No redirection printer found


Operator responseDefine a redirection printer and then resubmit thecommand.

DXC8173I Error on queue swing toredirection printer

ExplanationALCS detected an error while moving message queues.


DXC8174I Resource CRN-crn Queues purgedto sequential file seq -- Messagecount number

ExplanationThe message queues for the terminal have beencopied to the sequential file seq and have beendiscarded. There were number messages in the queue.

DXC8175I Resource CRN-crn Message purged

ExplanationThe current message being sent to the terminal, or thefirst message on the queue, has been discarded.

DXC8176I Resource CRN-crn Queues purged-- Message count number


ExplanationThe message queues for the terminal have beendiscarded. There were number messages on thequeue.

DXC8177I Resource CRN-crn Messagerepeated

ExplanationThis message is a normal response to the commandZACOM REPEAT.

DXC8178I From resource CRN-crn Toresource CRN-crn Queue swingcomplete

ExplanationThe message queues have been moved.

System actionThis message provides information on an ALCSprocess. The Operator does not need to respond to themessage.

DXC8181I Resource CRN-crn No messagequeued


Operator responseThis message provides information on an ALCSprocess. The Operator does not need to respond to themessage.

DXC8182I Resource CRN-crn Reset

ExplanationThis message is a normal response to the commandZACOM RESET.


DXC8183I From resource CRN-crn Toresource CRN-crn Error duringqueue swing

ExplanationALCS detected an error while moving the messagequeues.


DXC8184I Timeout value must be in range1-120 seconds


System actionCorrect the typing or syntax error and retry thecommand.

DXC8185I Retry counter must be in range1-64



DXC8186I Input window must be in range1-64



DXC8187I Output window must be in range1-64



DXC8188I Disconnect resource then retry


ExplanationAn error has occurred while trying to carry out thiscommand.


DXC8189I Enter ZACOM CLEAR then retry

ExplanationAn error has occurred while trying to carry out thiscommand.

Operator responseUse ZACOM CLEAR then retry the command.

DXC8190I Resource CRN-crn RCR messagequeue has been purged



DXC8191I Resource CRN-crn RCR messagequeue item number has beenpurged


DXC8192I Resource CRN-crn RCR messagequeue has been reset



DXC8193I Resource CRN-crn Unable --Message in progress

ExplanationThis command cannot be completed because amessage in still being processed.

Operator responseRetry the command.

DXC8194I Resource CRN-crn No message torepeat

ExplanationThis message is a normal response to the commandZACOM REPEAT.

DXC8195I User ID-user-id is not authorizedfor Prime CRAS status

ExplanationThe user user-id does not have the SAF authority to bePrime CRAS.


Operator responseIf Prime CRAS authorization is required for the usercontact your security administrator.

DXC8196I User ID-user-id is not authorizedfor alternate CRAS status

ExplanationThe user user-id does not have the SAF authority to bealternate CRAS.


Operator responseIf alternate CRAS authorization is required for the usercontact your security administrator.


ExplanationThis message is a normal response to the commandZACOR. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.



ExplanationThis message is a normal response to the commandZDCOR. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


ExplanationThis message is a normal response to the commandZAFIL. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8203I Invalid displacement or length

ExplanationA ZAFIL request is attempting to alter data beyondthe end of the record. The starting displacement isincorrect.


DXC8204I Invalid data length

ExplanationFor ZACOR command, the maximum data length is8 bytes (16 hexadecimal digits) when the alterationstarts on a fullword boundary. For ZAPRG and ZAFILcommands, the maximum data length is 16 bytes (32hexadecimal digits) when the alteration starts on afullword boundary. The maximum length reduces by2 digits for each byte displacement from a fullwordboundary.


DXC8205I Invalid data

ExplanationData must be hexadecimal, an even number of up to32 digits.

DXC8206I Comments are too long or tooshort

ExplanationComments must be from 6 to 40 characters.


DXC8207I Storage access violation

ExplanationAlter request is for a storage area that is writeprotected.

Operator responseUse ZACOR or ZAPRG to alter the application globalarea or programs loaded in test mode only.

DXC8208I DASD I/O error

ExplanationA DASD I/O error occurred while attempting to read orwrite the specified record.


DXC8210I Change not allowed Class/type/ordinal mismatch with file address

ExplanationZAFIL You are trying to change a database record.However the file address used does not match the fileaddress and ordinal of the record.

System actionALCS terminates the entry.


DXC8211I Crosses double word boundary

ExplanationAny command to change storage must not cross adouble word boundary.


DXC8212I Global label not recognized


ExplanationGlobal label does not appear in any of the globalarea tag exit programs AGT0, AGT1, and so on.ALCS Installation and Customization describes how tospecify fields in the application global area.

Operator responseCorrect the typing or syntax error and retry thecommand. Or inform your system programmer.

DXC8213I No matching entry for programname and CRI/CRN

ExplanationThe alter request is for a test program that thisterminal does not own.

Operator responseEnter: ZDPRG program_name to display the programname and status.

DXC8214I Invalid displacement

ExplanationA ZAFIL or ZAPRG request is attempting to alter databeyond the end of the record or program. The startingdisplacement is incorrect.

Operator responseRetry the operation with the correct displacement.

DXC8215I Global not loaded

ExplanationA ZDCOR command refers to a global tag but the globalis not loaded.


DXC8216I Invalid address

ExplanationEither the address is missing, or it is not hexadecimal.


DXC8217I Invalid alter request -- Segment isin Read Only storage

ExplanationAlter is allowed only for test programs.

Operator responseEnter ZDPRG program_name to display the programname and its status.

DXC8218I Invalid record type or ordinal

ExplanationALCS has not located a record type or an ordinal thatyou expected.

Operator responseCheck the ALCS DASD generation for a list of validrecord types and ordinal numbers.


ExplanationThis message is a normal response to the commandZDFIL. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


ExplanationThis message is a normal response to the commandZAPRG. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


ExplanationThis message is a normal response to the commandZDPRG. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.



DXC8225I Record not yet allocated


ExplanationThe file address has been defined to the system but norecord has yet been allocated on the database.

You are trying to display a fixed file or short-termpool record that has been defined in the databasegeneration, but which has not been created on thedatabase. When new fixed file or short-term poolrecords are defined in the database generation, theywill be created on the database when a program (otherthan the ZDFIL programs) tries to access them.

DXC8226E Not authorized to change thisrecord

ExplanationYou are trying to change a record which is part of theinternal structure of the ALCS system. Only the systemis authorized to change this record.


ExplanationThis message is a normal response to the commandZAFIL. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.





DXC8235I ALCS State change from name toname starting

ExplanationThis message is a normal response to the commandZASYS.

DXC8236I ALCS already in name state

ExplanationALCS is already in the system state you have requestedit to change to.

Operator responseCheck the ZASYS request and resubmit it specifying adifferent system state to name.

DXC8237I Utilities active...State change request rejected

ExplanationYou have requested a state change with ZASYS whenutilities are active. The command is rejected.

Operator responseResubmit the request with the option to bypass theutility check or halt the utilities and resubmit theoriginal command.

DXC8238I ALCS in name state

ExplanationThis message is a normal response to the commandZASYS.

Operator responseConfirm that the next thing you want to do is possiblewhile ALCS is in name state. If not then change theALCS state with the ZASYS command.

DXC8239I ALCS state change from name toname in progress

ExplanationA system state change has not completed processing.ALCS will not process another state change request(except with the FORCE or RESET parameter) untilsystem change state is complete.

Operator responseWait until the state change is complete before retryingthe ZASYS command. Enter ZASYS name,RESET if aprevious system state change entry has failed or isheld up with the state change incomplete.

DXC8240I name is not a valid ALCS statename

ExplanationYou have probably misspelled the state name.



DXC8242I RESET failed -- ZASYS entry active


Operator responseWait until ALCS has completed the state change that iscurrently in operation and then try again.

DXC8243I FORCE not allowed -- RESET notyet tried

ExplanationYou must try to reset ALCS before resorting to theFORCE parameter.

Operator responseSee your system programmer and explain what hashappened. Resubmit the request using the ZASYSRESET.

DXC8244I State change not in progress

ExplanationALCS expected a state change to be in progress.

Operator responseUse ZASYS. Correct the typing or syntax error and retrythe command.

DXC8245I System state indicator corrupted

ExplanationAn internal error has occurred.


DXC8246I System state change or pendingindicator corrupted




Explanation:This message is a response to the ZBCOR command.See ALCS Operation and Maintenance for a fullexplanation of the command response.

DXC8250I Map changes started

ExplanationALCS is processing the request to change the mapcurrently being used.

System actionALCS continues to process normally.

DXC8251I Added map to map list -- Name-mapname

ExplanationThe new map is added to the ALCS real-time databasefrom the MVS sequential file.


DXC8252I Deleted map from map list --Name-mapname

ExplanationThe map has been deleted from the ALCS real-timedatabase.


DXC8253I Replaced map on map list --Name-mapname

ExplanationThe new map has overwritten the old map of the samename on the ALCS real-time database.



DXC8254I Map changes ended

ExplanationThe command has completed successfully, the map ischanged.


DXC8255I ADD -- Sequential file nameinvalid or omitted

ExplanationThis message is an error response to the commandZCMSP.

Operator responseReenter the command with a valid file name.

DXC8256I Map name invalid or omitted


Operator responseReenter command with a valid map name.

DXC8257I mapname1 mapname2

ExplanationThis message is a normal response to the commandZCMSP. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8258I No map records found

ExplanationThis message is a normal response to the commandZCMSP LIST.

DXC8259I No matching map records found

ExplanationThis message is a normal response to the commandZCMSP LIST,FROM=nnnnnn,TO=nnnnnn.

DXC8260I Workstation trace not active forthis terminal

ExplanationThis message is a normal response to the commandZTRAC.

DXC8261I Workstation trace active for thisterminal


DXC8262E Invalid IP address

ExplanationThis message is an error response to the commandZTRAC.

Operator responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8263E Invalid domain name



DXC8264I OK

ExplanationThe ZTRAC CEP,START|STOP command is accepted.


DXC8265I CEP trace on

ExplanationThis message is a normal response to the ZTRAC CEPcommand.


DXC8266I CEP trace off


ExplanationThis message is a normal response to the ZTRAC CEPcommand.


DXC8267E Invalid DECB address

ExplanationThis message is an error response to ALCSconversational trace commands which refer to DECBs.


DXC8268I Diag trace started

ExplanationThis message is a normal response to the ZTRACcommand.


DXC8269I Diag trace stopped


System actionTrace proceessing completes.


ExplanationThis message is a normal response to the commandZDSER Edt. See ALCS Operation and Maintenance for afull explanation of how to use the commands.

DXC8274E No matching Entries Found

ExplanationThis is an error response to the command ZASEREDT=DEL. There are no matching entries in theException Dump Table. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.



ExplanationThis message is a normal response to the commandZDSER Ddt and shows entries in the Duplicate DumpTable. If the duplicate dump system error optionDUPE=YES is current, then the response shows thetable when DUPE=YES was activated.

DXC8278I No entries in Duplicate DumpTable

ExplanationSelf-explanatory. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.


ExplanationThis message is a normal response to the commandZDSER Edt.

DXC8282I No entries in Exception DumpTable

ExplanationSelf-explanatory. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.

DXC8283E Program and/or Error numberalready exists

ExplanationThis is an error response to the command ZASEREDT=ADD. The program and/or Error number alreadyexists in the Exception Dump Table. See ALCSOperation and Maintenance for a full explanation ofhow to use the commands.


DXC8284E Exception Dump Table Full


ExplanationThis is an error response to the command ZASEREDT=ADD. There are no spare entries in the ExceptionDump Table. See ALCS Operation and Maintenance fora full explanation of how to use the commands.

Operator responseDelete some entries in the Exception Dump Table andretry the command.

DXC8285I Data Collection already active



DXC8286I Data Collection not active



DXC8287I Following data collection optionsname number

ExplanationThe options specified name number have begun datacollection.

System actionALCS collects data, the data-collection output is sentto the data-collection file. If no data-collection file hasbeen specified then the output is sent to the ALCSdiagnostic file.

DXC8288I Data collection stopped

ExplanationData collection has stopped after receiving a ZDCLRSTOP command.



ExplanationThis message is a normal response to the commandZDECB CPU. See ALCS Operation and Maintenance for afull explanation of how to use the commands.

DXC8290I Ws and Conv trace is now active



DXC8291I Ws and Conv trace is now inactive


System actionTrace proceessing completes.

DXC8292I Minimum age parameter invalid

ExplanationThe minimum age parameter is set up at generationtime in the SCTGEN macro.

Operator responseAsk the system programmer to confirm the minimumage and then resubmit the command.

DXC8293I Entries older than numbersecond(s) with at numbersecond(s) CPU -- None





ExplanationThis message is a normal response to the commandZDECB CPU=c. See ALCS Operation and Maintenancefor a full explanation of how to use the commands.

DXC8295I Program program_name startedOutput on printer -- CRN-crn


DXC8296I Program program_name notloaded

ExplanationThis program program_name is not available to therequesting terminal.

Operator responseCheck the program load list and then retry theoperation.

DXC8297I Program completed


DXC8298I Program program_name started


DXC8300E Invalid pool identifier

ExplanationThe pool identifier, if specified, must be LsLTpoolwhere Ls identified the record size.


DXC8301E Invalid record identity

ExplanationThe record ID is not defined for the LsLTpool or, theLsLTpool parameter was omitted, (where Ls is therecord size) for any long-term pool file.

System programmer responseCheck the ALCS DASD generation stage 1 output for alist of record IDs defined for the long-term pool files.

DXC8302E Pool file file_name does not exist



DXC8303E No pool file activity allowed -- Pooldispense function active



DXC8304E DASD I/O error -- Try again

ExplanationAn I/O error occurred while trying to read the record.

Operator responseIf this recurs investigate the I/O error.

DXC8305E Multiple record sizes -- Specifypool identifier

ExplanationThe record ID is defined for more than one long-termpool file.

Operator responseCheck the ALCS DASD generation stage-1 output fora list of all pool files and record IDs and reenterthe ZGAFA command, adding the LsLT parameter tospecify which record size you require.


DXC8306I file_address

ExplanationThis message is a normal response to the commandZGAFA. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8307E Invalid record ID qualifier

ExplanationThe record ID qualifier must be a single digit between0 and 9


DXC8312I topic Help not available -- try:ZHELP INDEX

ExplanationHelp is not available for the topic you specified.


DXC8316I End

ExplanationThis message is a normal response to the commandZLTST.

DXC8317E Link test failed

ExplanationThis is an error response to ZLTST.

Operator responseCorrect the typing or syntax error and retry thecommand. If this recurs investigate the problem.

DXC8319E Invalid test test

ExplanationYou have entered an invalid test on the ZLTSTcommand. See ALCS Operation and Maintenance fora full description of the tests.


DXC8320E Invalid command code n

ExplanationYou have entered an invalid command code onthe ZLTST command. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.


DXC8321E Invalid numeric parameter number

ExplanationYou have entered an invalid parameter on the ZLTSTcommand. See ALCS Operation and Maintenance for afull explanation of how to use the commands.



ExplanationThis is a normal response message to the ZLTSTcommand. See ALCS Operation and Maintenance fora full description of the responses.

DXC8323E Command not implemented -- ccc

ExplanationThis is an error response to the ZLTST command. Itis not possible to run an SLC test. See ALCS Operationand Maintenance for a full description of the tests.


DXC8324E Illogical command -- ccc

ExplanationThis is an error response to the ZLTST command. Youcannot run an SLC test using command ccc. See ALCS


Operation and Maintenance for a full description of thetests.


DXC8325E Error displaying module table --Display cancelled


Operator responseCheck that you have entered the correct module table.If this message occurs frequently, inform your systemprogrammer.

DXC8326E Unknown module name



DXC8327E Load failed -- Module load tablefull


Operator responseUpdate the program configuration table to increase thenumber of modules expected in the system. Assembleand link-edit the program configuration table, restartALCS and try again.

DXC8328E Load failed -- Duplicate modulename

ExplanationYou have tried to load two modules with the samename.


DXC8329E Load failed -- Error during moduleload Return Code X'return_code'Reason code X'reason_code'

ExplanationMVS failed to load the module.

Operator responseSee MVS Messages and Codes manual for anexplanation of the return and reason codes. Check thatthe module is in the application program load modulelibrary that is defined in the JCL to run ALCS.

DXC8330E Load failed Invalid programmodule format -- Offset X'nnnnnn'

ExplanationThe application program load module contains data atoffset X'nnnnnn' that is not a valid ALCS applicationprogram.

Operator responseAsk your system programmer to check the linkageeditor listing for the module.

DXC8331E Load failed -- Program table full


Operator responseUpdate the program configuration table to increasethe number of programs expected in the system.Assemble and link-edit the program configurationtables, restart ALCS and try again.

DXC8332I Test module MODN-module unloadstarted by CRN1-crn1 for CRN2-CRN2

ExplanationThis message is a normal response to commandZPCTL.

DXC8333E Can not unload a permanentmodule

ExplanationIt is not possible for ALCS to unload a module that hasbeen specified as permanently loaded.



DXC8334E Unload not attempted

ExplanationYou can only use UNLOAD FORCE after an attempt toUNLOAD fails.


DXC8335E Programs in use

ExplanationUNLOAD cannot complete because one or more 24-bitaddressing mode programs within the module are inuse.

Operator responseAttempt the operation later.

DXC8336I Module MODN-module unloadstarted by CRN-crn


DXC8337I Module MODN-module unloadforce started by CRN-crn


DXC8338E Can not promote or confirm a testmodule

ExplanationProgram load modules that are loaded as test modulescan not be confirmed or promoted (committed). Thiserror message can also be output if you have tried toconfirm a load module that has been loaded both as atest module and a system-wide module. You can notconfirm a load module that is loaded both as a testmodule and a system-wide module.

Operator responseIf the load module has been loaded both as a testmodule and a system-wide module, unload the testmodule (using the ZPCTL UNLOAD,module,CRN=crnor ZPCTL UNLOAD,module,CRI=cri command) andthen retry the ZPCTL CONFIRM command.

DXC8339E Module already permanent

ExplanationYou have tried to make a module permanent when it isalready defined as permanent.


DXC8340I Module MODN-module loaded byCRN-crn


DXC8341I Module MODN-module committedby CRN-crn


DXC8342I Module MODN-module unloadedfor CRN-crn


DXC8343E Load module name omitted

ExplanationYou have not included the module name in the ZPCTLcommand.


DXC8344E Module MODN-module confirmedby CRN-crn




ExplanationThis is a normal response to the ZPCTL DISPLAYcommand. See ALCS Operation and Maintenance fora full explanation of how to use the commands.

DXC8346I Test module MODN-module unloadforce started by CRN1-crn1 forCRN2-crn2


DXC8347I Test module MODN-module loadedby CRN1-crn1 for CRN2-crn2


DXC8349I Module MODN-module unloadedfor System


DXC8350I SE-nnnnnn CTL-000000PSW-pppppppp ppppppppVOLUME=volser DSNAME=dsnameMSG='ZDUMP <ALL> text

ExplanationThis message is a normal response to the commandZDUMP. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8355I Purge request accepted

ExplanationThis message is a normal response to the commandZPURG.

DXC8356E ECB address invalid or omitted



DXC8357I All VFA records purged

ExplanationThis message is a normal response to the ZPURGVFA command. It appears on RO CRAS and on yourterminal.

DXC8358E FORCE not allowed -- ZPURG notyet tried

ExplanationYou must try to purge the entry with the ZPURGecb_address command before resorting to theZPURG Force parameter.


DXC8360I Message from CRN-crn CRI-cri

ExplanationThis message is a normal response to the commandZRCRS.

DXC8361I Message sent to CRN-crn

ExplanationThis message is a normal response to the commandZRCRS.

DXC8362E Unable -- CRAS terminal must bespecified

ExplanationThis message is an error response to commandZRCRS.


DXC8367I Being paused by system statechange


ExplanationA ZASYS command has been issued; Recoup will stopuntil the system state change has completed and arestart command is issued.

Operator responseIssue the restart command after the system statechange is completed.

DXC8368I Restart awaited

ExplanationALCS has failed and is waiting for a ZRECP command.

Operator responseIssue a ZRECP RESTART command.

DXC8369E Analysis file open error -- Recoupnot (re)started

ExplanationAn internal error has occurred and Recoup will notrestart.


DXC8370I Chain chase complete

ExplanationThis message is a normal response to the commandZRECP.

DXC8371I Directory build complete


DXC8372E Let active utilities finish

ExplanationThis message is an error response to commandZRECP.

Operator responseTry again when the utilities complete.

DXC8373E General file GF-000 not available-- Recoup continues

ExplanationAlthough Recoup cannot find the general file it willcontinue processing.


DXC8374E General file GF-000 full -- Recoupcontinues



DXC8375E General file GF-000 I/O error --Recoup continues

ExplanationAn I/O error has occurred; however the Recoup runcontinues


DXC8376E No group of this name

ExplanationYou have specified a group name that does not exist.


DXC8377W Too many reads this group --Group continues

ExplanationThere are more records chained from one record thanexpected. Either there is an error in the descriptorprogram (the COUNT parameter of the GROUP macromust specify a larger value), or there is an error in thedatabase (a chain is too long).

See ALCS Installation and Customization for anexplanation of GROUP macro operands.


System actionRecoup continues to process records chained withinthis group (that is, within this chain).


DXC8378W Too many reads this prime group --Prime group continues

ExplanationThere are more records chained from one prime grouprecord than expected. Either there is an error in thedescriptor program (the PRIMECT parameter of theGROUP macro must specify a larger value), or there isan error in the database (a structure contains too manyrecords).


System actionRecoup continues to process records chained from thisprime group record (that is, within this structure).


DXC8379W Pool record chain chased twice

ExplanationThe database contains two (or more) references tothe same pool record. The DUPREAD parameter ofthe GROUP macro specifies that this is an unexpected(error) condition.


System actionRecoup stops processing records within this group(that is, within this chain).


DXC8380E Maximum nesting level exceeded

ExplanationThis is an ALCS Recoup implementation restriction.Recoup cannot process a group because it is nestedwithin too many other groups.

System actionRecoup does not process records within this group(that is, within this chain). These records (and otherrecords that they refer to) will be reported as "lostaddresses" and eventually reused.

Operator responseAsk your system programmer to inform your IBMprogramming support representative. Avoid runningRecoup again until this problem has been resolved.

DXC8381E Fixed mode run complete


DXC8382I Partial run complete


DXC8383I Invalid backchain information

ExplanationThere is a mistake in the descriptor program.

Operator responseRun Recoup as soon as the descriptor program hasbeen corrected.

DXC8384E Unable to store group address --unknown RECID

ExplanationA group with METHOD=ID specifies a record ID that isnot known to ALCS.

See ALCS Installation and Customization for anexplanation of METHOD=ID.

System actionRecoup ignores the group.



DXC8385E Unable to load group address --unknown RECID

ExplanationAn index with GROUP=(ID) specifies a reference to arecord ID that is not known to ALCS.

See ALCS Installation and Customization for anexplanation of GROUP=(ID).

System actionRecoup does not process the refer-to record. Therefer-to record (and other records it refers to) will bereported as "lost addresses" and eventually reused.

Operator responseInform your system programmer. Avoid runningRecoup again until this problem has been resolved.

DXC8386I Analysis file closed -- Recoupcontinues



DXC8387E Missing descriptor program --Recoup continues

ExplanationOne of the descriptor programs is missing.

System actionRecoup continues processing.


DXC8388E FACE error in prime group --Recoup continues

ExplanationRecoup has found an invalid record ordinal in a record.



DXC8389E RECID not found in prime group --Recoup continues

ExplanationThe descriptor program has specified a record ID inthe global area which Recoup cannot find.

System actionRecoup continues processing


DXC8390E Invalid file address in prime group-- Recoup continues

ExplanationRecoup has found an invalid file address in the globalarea.


DXC8391E Invalid record ordinal in record --Recoup continues

ExplanationRecoup has found an invalid FACE ordinal in a record.


DXC8392E Invalid CRI in record -- Recoupcontinues

ExplanationRecoup has found an invalid CRI in a record.



DXC8393E Too many reads this group --Group terminated

ExplanationThere are more records chained from one record thanexpected. Either there is an error in the descriptorprogram (the COUNT parameter of the GROUP macromust specify a larger value), or there is an error in thedatabase (a chain is too long).


System actionRecoup stops processing records within this group(that is, within this chain). Any remaining records inthe chain (and other records that they refer to) will bereported as "lost addresses" and eventually reused.


DXC8394E Too many reads this prime group --Prime group terminated

ExplanationThere are more records chained from one prime grouprecord than expected. Either there is an error in thedescriptor program (the PRIMECT parameter of theGROUP macro must specify a larger value), or there isan error in the database (a structure contains too manyrecords).


System actionRecoup stops processing records chained from thisprime group record (that is, within this structure).Any remaining records in the structure (and any otherrecords that they refer to) will be reported as "lostaddresses" and eventually reused.


DXC8395E Partial run -- Prime group notfound

ExplanationThere is a mistake in the descriptor program, Recoupcannot find the Prime group.


DXC8396E No group of this name

ExplanationThere is a mistake in the Descriptor program, Recoupcannot find a group.


DXC8397E I/O error at start of chain

ExplanationAn I/O error has occurred at the start of a chain chase.


DXC8398I Recoup pause timeout - I/O errorat start of chain

ExplanationYou requested ZRECP PAUSE and ALCS has instructedRecoup to stop processing, but 15 seconds later thereare still Recoup ECBs active. This message is repeatedevery 15 seconds until pause completes.

Operator responseEnter ZDECB and attempt to discover why pause willnot complete. This is usually because MVS or ALCSis extremely busy, and Recoup is running slowly. Ifyou cannot wait for pause to complete, then contactyour system programmer who will advise you how toterminate any stuck ECBs, or enter ZRECP CANCEL.However if you cancel Recoup you will be unable torestart it from the point which it has currently reached.

DXC8399W Directory build ** BAD ** -GF-000 I/O error, full or offline


ExplanationThe Recoup general file, GF-000, was not available forthe whole of Recoup chain-chase. The result is that notall the in-use records have their directory bits set. Therecords are safe because ALCS uses the timestamps inthe records to check the availability of the records.

System performance will be slightly degraded becauseALCS uses more CPU cycles and I/O scanning foravailable records and generating pool error records.

Operator responseInform your System Programmer.

System programmer responseDetermine why the Recoup general file is not availableand make it available. Run a full Recoup (ZRECPSTART) as soon as possible to correct the directories.

DXC8400E Invalid START request

ExplanationYou requested ZRECP START but Recoup is alreadyrunning.

Operator responseWait until the current Recoup run completes beforetrying the command again.

DXC8401E Invalid CANCEL request

ExplanationYou requested ZRECP CANCEL but Recoup is alreadycancelled or paused.

DXC8402E Invalid PAUSE request

ExplanationYou requested ZRECP PAUSE but Recoup is already ina paused state.

DXC8403E Invalid RESTART request

ExplanationYou requested ZRECP RESTART but Recoup is notpaused.


ExplanationThis message is a normal response to the commandZRECP. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.











DXC8410W Unable to create new directoriesLn data sets offline

ExplanationALCS is attempting to create a new Ln pool size but thedata sets are offline.

System actionRecoup continues but the new pool size is not created.

DXC8411W Unable to create recoup bitmapdata space - Recoup continues


ExplanationALCS has encountered an error attempting to create adata space to hold a bitmap to indicate which recordshave been processed.

System actionRecoup continues and will occasionally retrieve arecord it has already processed. This may cause anincrease in the time Recoup takes to complete.

DXC8414E Unable to use ZSCRL command

ExplanationScrolling is inhibited for this terminal.

ModuleCSC3

DXC8415E Error retrieving message record

ExplanationA find error on the retrieval of an output file occurred.


DXC8416E Missing or invalid data string

ExplanationThe data string entered with ZSCRL FIND or SCAN wasomitted or incorrect.


DXC8417E Scan data too long

ExplanationThe data string entered with ZSCRL FIND or SCAN wasmore than 50 characters long.


DXC8418I Message sent to printer CRN-crn

ExplanationYour message is sent to printer CRN (this may be aNetview id).

DXC8419I No match found

ExplanationALCS cannot find the character string you specified.


DXC8420E Scroll log mode already started

ExplanationYou can only start the scroll log once.

DXC8421E Scroll log mode already stopped

ExplanationYou have requested scrolling although the scroll logmode has been stopped.

Operator responseReissue the command after starting scroll logging.

DXC8422E Unable to scroll

ExplanationAn internal error has occurred which has resulted inALCS not being able to scroll.

Operator responseCheck that scroll log is operating and then retry thecommand.

DXC8423E Error reading prime unsolicitedmessage block

ExplanationThis message is an error response to commandZSNDU. The message in error, and any more messagesin the same queue, is discarded.

DXC8424E Error reading chain unsolicitedmessage block

ExplanationThis message is an error response to commandZSNDU. The message in error is discarded.


DXC8425E No carriage return

ExplanationThis message is an error response to commandZSNDU.

Operator responseCorrect the error and resubmit the command with thecorrect syntax.

DXC8426E Resource parameter entered twice



DXC8427E LIFETIME parameter enteredtwice



DXC8428E LIFETIME parameter -- invalidlength

ExplanationYou have entered an incorrect parameter on the ZSNDUcommand.


DXC8429E LIFETIME parameter -- invalidoption

ExplanationYou have entered an incorrect option on the ZSNDUcommand.

Operator responseCorrect the error and resubmit the command.

DXC8430E Invalid INCLUDE/EXCLUDEparameter

ExplanationYou have entered incorrect parameters for theuserdata installation-wide exit on the ZSNDUcommand.


System programmer responseCheck the appropriate installation-wide exits that arein operation.

DXC8431E Unknown user parameter(s)specified

ExplanationYou have entered an unknown parameter on theZSNDU command.


DXC8432E Userdata parameter(s) too long

ExplanationYou have entered an incorrect parameter on the ZSNDUcommand.


DXC8433E LIFE parameter value exceedsmaximum

ExplanationThe LIFE parameter (initially set at 3 hours) of theZSNDU command has been exceeded.

Operator responseCheck the value that the system programmer has setfor the LIFE parameter and resubmit the command.


DXC8434I No broadcast messages on queue

ExplanationThis message is a normal response to the commandZSNDU. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8435E Message number does not exist

ExplanationThe unsolicited message number specified on theZSNDU command does not exist.






DXC8440I Sequential file sequential_fileclosed

ExplanationThis message is a normal response to the commandZCSEQ.

DXC8441E Unable to close sequential filesequential_file

ExplanationThis message is an error response to commandZCSEQ.


DXC8442E Sequential file sequential_file inuse


Operator responseUse ZDSEQ to display the current status of thesequential file.

DXC8443E Sequential file sequential_filealready closed


Operator responseUse ZDSEQ to display the current status of thesequential file.

DXC8444E Close not allowed for sequentialfile sequential_file

ExplanationZCSEQ can only close general sequential files, andsequential_file is not a general sequential file.

Operator responseUse ZDSEQ with no parameter to display the types.Correct the typing or syntax error and retry thecommand.

DXC8445E STV in wrong status for requestedaction

ExplanationThe ZTEST request cannot be processed because STVis not in the correct status; for example you may haveentered ZTEST STOP when STV was not active.

Operator responseUse ZTEST to display the current status of STV.

DXC8446E Not authorized to use STV

ExplanationThe ZTEST command is only allowed from PrimeCRAS.

Operator responseEnter the command again from Prime CRAS.


DXC8447E Conflicting options specified

ExplanationYou entered two or more conflicting parameterswhich are mutually exclusive. For example ZTESTSTART,STOP is not possible because STV cannot bestarted and stopped by the same command.

Operator responseTry the command again with acceptable parameters.

DXC8448E Invalid decimal number specified

ExplanationYou have probably made a general typing error.


DXC8449E Keyword entered as a positionalparameter

ExplanationYou have probably made a typing error.


DXC8450E Positional parameter entered as akeyword

ExplanationYou have entered a positional parameter as a keywordon the ZTEST command.

Operator responseSee ALCS Operation and Maintenance for anexplanation of how to enter parameters for the ZTESTcommand.

DXC8451E Invalid value specified for replykeyword

ExplanationThe reply keyword value is incorrect on the ZTESTcommand.

Operator responseSee ALCS Operation and Maintenance for anexplanation of how to enter parameters for the ZTESTcommand.

DXC8452E normal response

ExplanationThis message is a normal response to the commandZTEST. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.





DXC8455I STV started

ExplanationThis message is a normal response to the commandZTEST.

DXC8456I STV restarted


DXC8457I STV paused


DXC8458I STV stopped


DXC8459I STV cancelled



DXC8460E Trace overloaded

ExplanationToo many users are currently using conversationalmode trace. The maximum number of concurrentusers is a generation option.


DXC8461I No block attached

ExplanationThis message is a normal response to commandZTRAC.

DXC8462E Trace already active

ExplanationThis message is an error response to commandZTRAC.

Operator responseUse the ZTRAC command to display the current statusof trace.

DXC8463E Invalid trace mode/action

ExplanationYou have made a mistake in entering the ZTRACcommand.

Operator responseRefer to ALCS Operation and Maintenance for a fullexplanation of the trace command.

DXC8464I Transaction cancelled by tracingagent

ExplanationAnother agent is tracing input from your terminal. Thatother agent cancelled your input message.

User responseEnter the next input message to be traced.

DXC8465E System error -- GTFCC parametersinvalid

ExplanationThis message is an error response to the commandZTRAC. ALCS has detected a program which containsinvalid parameters on the GTFCC macro.


DXC8466E Too many controls in list

ExplanationYou must have 8 or fewer items in a list, or just a singleitem, depending on which control option is specified.


DXC8467E Invalid register



DXC8468E Terminal control not allowed



DXC8469E Display control not allowed




DXC8470E Invalid display control



DXC8471E Invalid value or value range

ExplanationThis message is an error response to command ZTRACor to conversational trace command RUNSTOP.


DXC8472E Invalid macro group


Programmer responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8473E Invalid macro name



DXC8474E Invalid hexadecimal field



DXC8475E Terminal already being traced



DXC8476E Not allowed -- use branch


Programmer responseInform the system programmer to rewrite theprogram to use branching. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.

DXC8477I Conversational trace not active forthis terminal


Operator responseUse ZTRAC to activate trace for this terminal.

DXC8478I Diagnostic trace not active


Operator responseUse ZTRAC to activate diagnostic trace. See ALCSOperation and Maintenance for a full explanation ofhow to use the commands.

DXC8479E Invalid action word




DXC8480E Invalid action parameters



DXC8481E Invalid main storage address



DXC8482E Invalid listing address

ExplanationThis message is an error response to command ZTRACor to conversational trace command RUNSTOP.


DXC8483E Invalid SET action



DXC8484E Invalid register SET value



DXC8485E Invalid instruction address SETvalue



DXC8486E Invalid condition code SET value



DXC8487E Invalid main storage SET value



DXC8488E ADD/REPLACE parameter but nodata given


Operator responseReenter the command including the missing data.


DXC8489A Enter FLUSH then repeat STOPmessage


Operator responseEnter a FLUSH command followed by STOP.

DXC8490I Block trace not active



DXC8491I Block trace active


Operator responsenormal ZTRAC See ALCS Operation and Maintenancefor a full explanation of how to use the commands.

DXC8492E Trace information not available



DXC8493E GETMAIN for buffer failed



DXC8494E Storage access violation


Programmer responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8495E Invalid program alter request



DXC8496E System error -- trace request notaccepted


Operator responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands. If thismessage occurs frequently, inform your systemprogrammer.

DXC8497E No ADSTOP/REFSTOP/REGSTOPcontrols



DXC8498E Not allowed -- use EBW EBX REGETC.

ExplanationThe response to DISPLAY ALL is too large to read onthis terminal.


Operator responseUse DISPLAY EBW, DISPLAY EBX and so on todisplay the information.

DXC8499E Swap not possible -- Resourceheld or tape assigned or no otherentry



DXC8500E Invalid word length

ExplanationYou requested a display of zero fullwords of mainstorage.


DXC8501E Invalid address or length ordelimiter



DXC8502E Invalid or unsupported ECB fieldname



DXC8503E Invalid R (Refer) or S (Store)option



DXC8504E Too many ADSTOP/REFSTOP/REGSTOP controls



DXC8506I C and WS mode trace active forsystem


DXC8507I C and WS mode trace inactive forsystem


DXC8508E Parameter name conflicts withtrace mode name



DXC8509I Press Enter to proceed



System actionALCS pauses until you press the Enter key and then itcontinues processing normally.

Operator responsePress the Enter key.

DXC8510I No block detached at this level


DXC8511I Diagnostic trace active


DXC8512I Conversational trace active for thisterminal


DXC8513I GTF trace active


DXC8514I GTF trace not active


DXC8515I Reenter within 30 seconds toconfirm

ExplanationThis is the command confirmation facility. ALCS isgiving you the chance to reconsider your action. Enterthe command again within 30 seconds to confirm toALCS that you really do want to take this action.

System actionALCS waits for your response before continuing toprocess the command.

Operator responseReenter the command or not as appropriate.

DXC8518I Bad confirmation -- cancelled

ExplanationYou have made a mistake in your confirmation of thecommand.

System actionThe command you entered previously has beencancelled.


DXC8520I Not routed to an ALCS application

ExplanationIt is not possible to route this command to anapplication program.


DXC8521I Routed to ALCS application name


Operator responseThis message provides information on an ALCSprocess. The Operator does not need to respond to themessage.

DXC8522I Terminal routing removed

ExplanationThis message is a normal response to the commandZROUT.

DXC8523I Terminal routing updated

ExplanationThis message is a normal response to the commandZROUT.

DXC8524E Application name is too long


ExplanationThe application name must not be more than 4characters long.

Operator responseCorrect the error and retry.

DXC8525E Application not active

ExplanationA ZROUT appl,text command was issued, but thedestination application is currently inactive.

Operator responseUse the ZACOM command to make the applicationactive, if required.

DXC8526E Specified resource is not anapplication

ExplanationThis message is an error response to commandZROUT.

Operator responseCheck that you have specified the application correctlyand retry the command.


DXC8530I Restore cancelled

ExplanationThis message is a normal response to the commandZRSTR See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8531E Restore already active

ExplanationYou have tried to restore records that are currentlybeing restored. See ALCS Operation and Maintenancefor a full explanation of how to use the commands.

DXC8532W TPFDBR tape - Block with itemsize not 1 (L1) or 2 (L2) or 3 (L4)

ExplanationTPF only supports L1, L2 and L4 size blocks but thistape contains another size. This message is sent once.

System actionALCS ignores this block and continues processing thetape.

DXC8533W TPFDBR tape - Block with nnrecords has item count greaterthan nn

ExplanationThere is a mismatch between the number of recordsand the item count on the TPF tape. This message issent once for each record size.

System actionALCS ignores this block and continues to process therest of the tape.

DXC8534I Seq file reads number DASD writesnumber


DXC8535E Global area is not loaded

ExplanationALCS cannot perform the requested action becauseit cannot retrieve the information it requires from theglobal area.


DXC8536E Too many selections

ExplanationThis message is an error response to commandZDATA.


DXC8537E Restore already in progress


ExplanationALCS allows only one ZRSTR to run.

System actionALCS waits for the current ZRSTR operation tofinish before accepting the next ZRSTR RESTART orCONTINUE command.

Operator responseTry again later.

DXC8538I Restore active -- To restart mountinput sequential file and enterZRSTR CONTINUE

ExplanationThis message is a normal response to commandZRSTR.

Operator responseFollow the instructions in the message. If this messageoccurs frequently, inform your system programmer.

DXC8539E Start time not before end time

ExplanationYou must specify an end time which is later than thestart time. See ALCS Operation and Maintenance for afull explanation of how to use the commands.

Operator responseCorrect the error and retry the operation.

DXC8540I Load complete Run Recoup tovalidate long term pool

ExplanationThis message is a normal response to the commandZRSTR.

Operator responseRun Recoup as soon as possible (after consulting yoursystem programmer).

DXC8541E Dump cancelled because of writeerror

ExplanationALCS is unable to write one or more records to thesequential file because of unrecoverable errors.

System actionALCS cancels the ZDATA DUMP operation.

DXC8542E System not in IDLE state

ExplanationALCS must be in IDLE state for this operation tocomplete.

Operator responseUse ZASYS to change the system state to IDLE.

DXC8543E LOAD/DUMP already active


Operator responseWait until the ZDATA command has finishedprocessing and then resubmit the command.

DXC8544I Restore started


DXC8545I Restore complete


DXC8546I LOAD started

ExplanationThis message is a normal response to the commandZRELO or ZDATA See ALCS Operation and Maintenancefor a full explanation of how to use the commands.

DXC8547I LOAD/DUMP cancelled


DXC8548I DUMP started


ExplanationThis message is a normal response to the commandZDATA. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8549I DUMP complete


DXC8550E LOAD/RESTORE cancelled becauseof EVNWC error Advise systemprogrammer



DXC8551E LOAD active -- ENTER 'ZDATACONTINUE' or 'ZDATA CANCEL'

ExplanationThis response indicates one of the following:

• The first parameter on the ZDATA command is notLOAD, DUMP, CANCEL, RESTART, or CONTINUE;

• Parameters follow the CANCEL, RESTART, orCONTINUE parameter;

• Incorrect parameters follow the LOAD or DUMPparameter.


DXC8552I Cancel request accepted


DXC8553E Cancel request already pending

ExplanationALCS has already accepted a cancel request but hasnot cancelled the data entry. ALCS ignores this ZDATAor ZRELO CANCEL request.


DXC8554E Restore cancelled - Overlengthrecord

ExplanationThe record length exceeds the maximum storage blocksize defined in the SCTGEN macro.

System programmer responseSee ALCS Installation and Customization forinformation on the SCTGEN macro.


ExplanationThis message is a normal response to the commandZRSTR. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8556E Restore not active


Operator responseThis is an error response to ZRSTR. See ALCSOperation and Maintenance for a full explanation ofhow to use the commands.

DXC8557I LOAD/DUMP not active





ExplanationThis message is a normal response to the commandZRSTR.

Operator responseMount the correct sequential file and enter ZRSTRCONTINUE.

DXC8559A End of sequential file Mount nextsequential file and enter 'ZRSTRCONTINUE'


Operator responseMount the next sequential file and enter ZRSTRCONTINUE.

DXC8560I Restore continuing


DXC8561E Sequential file I/O error


Operator responseTry the command again, if the error persists ask yoursystem programmer to inform your IBM programmingsupport representative.

DXC8562E Too many consecutive sequentialfile errors End of file assumed

ExplanationAfter five consecutive read errors during a ZDATA LOADALCS assumes that the sequential file is defective andforces an end-of-file.

Operator responseCheck that you are processing the correct inputsequential file. If so then inform your systemprogrammer.

System programmer responseThe input sequential file is either corrupted or notcorrectly terminated with end-of-file labels. Recreatethe input sequential file and retry the ZDATA LOAD.

DXC8563E Find error - AP type type ordinalordinal

ExplanationAn error occurred on reading a record by the ALCS database scan utility.

System actionThe ALCS data base scan utility ignores this record andcontinues.

Operator responseAsk your system programmer to inform your IBMprogramming representative.

DXC8564A Out of sequence time stampon sequential file Mount correctsequential file and enter 'ZRSTRCONTINUE'

ExplanationThis message is an error response to commandZDATA.

Operator responseMount the correct sequential file and enter ZRSTRCONTINUE.

DXC8565I number type type records loaded

ExplanationThis message is a normal response to the commandZRELO.

DXC8566I Summary of LOAD from filenameTotal records loaded.........nnnTotal records not selected...nnnTotal errors.................nnnNumber of restarts...........nnn


DXC8567I nnn type type records dumped



DXC8568I Summary of DUMP to nnn Totalrecords dumped.........nnn Recordsnot dumped...........nnn Total readerrors............nnn Number ofrestarts...........nnn


DXC8569I Unable - Utilities active utility_list

ExplanationThe ZDATA command cannot complete because one ormore utility programs are running.

Operator responseTry again when the utilities complete.

DXC8570E INCLUDE/EXCLUDE option conflict

ExplanationYou have specified information on the INCLUDE andEXCLUDE parameters which is incompatible.


DXC8571E Record type specification wrong

ExplanationYou have made an error is defining the record types ineither the sequential file or the real-time database.

Operator responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands..

DXC8572E Record ordinal specification wrong

ExplanationYou have made an error in specifying the recordordinals in either the sequential file or the real-timedatabase.


DXC8573E Record ID specification wrong

ExplanationYou have made an error in specifying the record ID ineither the sequential file or the real-time database.


DXC8574E File address specification wrong

ExplanationYou have made an error in specifying the file addressof the records.


DXC8575E Find error - File address address

ExplanationAn error occurred on reading a record by the ALCS database scan utility.

System actionThe ALCS data base scan utility ignores this record andcontinues.

Operator responseAsk your system programmer to inform your IBMprogramming representative.

DXC8576E Read error - Last valid record wasrecord

ExplanationAn error has occurred in reading one or more of therecords that you specified.


DXC8577E Invalid file address - file_address




DXC8578E One or more type type records notloaded Record ordinal numberstoo big

ExplanationYou have made a mistake in specifying the recordordinals. Use ZDFIL to confirm which record ordinalsyou wish to use.


DXC8579E File error - File address address

ExplanationAn error has occurred in locating file address address


DXC8580E Duplicate dump table reset failed -Program not in dump table

ExplanationZASER DUPE=(RESET,prog) was issued, but programprog was not found in the duplicate dump table.



ExplanationThis message is a normal response to the commandZASER. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


ExplanationThis message is a normal response to the commandZASER. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


ExplanationThis message is a normal response to the commandZDSER. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8584E error response

ExplanationZASER was issued, but ALCS was unable to set newsystem error dump options. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.



ExplanationThis message is a normal response to the commandZAACV. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8587E Invalid parameter value parm

ExplanationThis message is an error response to commandZAACV.


DXC8589I Total values cleared

ExplanationThis message is the normal response to the commandZSTAT RESET.



ExplanationThis message is a normal response to the commandZSTAT. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8591I Peak values cleared

ExplanationThis message is the normal response to the commandZSTAT CLEAR.

DXC8592E Program name is both includedand excluded

ExplanationThis message is an error response to the commandZTRAC. You have included and excluded the sameprogram in your trace control options.


DXC8593A Enter FLUSH then repeat message

ExplanationThis message is an error response to the commandZTRAC CONV,INTERCEPT,ON. Asynchronous tracecannot be started when an entry is already beingtraced.

Operator responseEnter a FLUSH command then start asynchronoustracing again.

DXC8594E Program controls required forINTERCEPT

ExplanationThis message is an error response to the commandZTRAC CONV,INTERCEPT,ON. You must include atleast one program in your trace control options beforestarting asynchronous trace.

Operator responseAdd program(s) to the trace control options then retrythe command.

DXC8595E Invalid INTERCEPT option

ExplanationThis message is an error response to the commandZTRAC CONV,INTERCEPT. (See ALCS Operationand Maintenance for a description of the ZTRACcommand.)


DXC8596E INTERCEPT already on

ExplanationThis message is an error response to the commandZTRAC CONV,INTERCEPT,ON. You have tried to startasynchronous trace when it is already started.


DXC8597E INTERCEPT already off

ExplanationThis message is an error response to the commandZTRAC CONV,INTERCEPT,OFF. You have tried tostop asynchronous trace when it is already stopped.


DXC8598E INTERCEPT not allowed withremote terminal trace

ExplanationThis message is an error response to the commandZTRAC CONV,INTERCEPT,ON. Asynchronous tracecannot be used at the same time as remote terminaltrace.

Operator responseStop conversational tracing and start it again withoutany terminal (T=) parameter.

DXC8599A Set INTERCEPT off then repeatmessage

ExplanationThis message is an error response to the commandZTRAC. Trace control options (other than D=) cannot


be changed after asynchronous trace is started until amessage is intercepted.

Operator responseStop asynchronous tracing, retry the command, thenstart asynchronous tracing again.

DXC8601I Not authorized to request thisfunction

ExplanationOnly the Prime CRAS can enter CONNECT orDISCONNECT. Only CRAS terminals can enterDISPLAY. This message is an error response tocommand ZCSQL.


DXC8602I Invalid SSNM

ExplanationThis is an error response to ZCSQL. The name ofthe DB2 subsystem is invalid. It should be up to 4alphanumeric characters.


DXC8603I DB2 not supported by this ALCS

ExplanationThis is an error response to ZCSQL. The ALCS systemconfiguration table does not specify support for DB2.

System programmer responseSee ALCS Installation and Customization forinformation on how to configure DB2.

DXC8604I Not currently connected to DB2

ExplanationALCS must be connected to a DB2 system for thiscommand to process.

Operator responseUse the ZCSQL command to connect to the DB2system. This command is explained in ALCS Operationand Maintenance.

DXC8605I Currently connected to DB2subsystem name

ExplanationThis message is a normal response to the commandZCSQL.

DXC8606I Now connected to DB2 subsystemname

ExplanationALCS is now connected to the DB2 subsystem name.The ZCSQL command has completed successfully.


DXC8607I Unable -- already connected toDB2 subsystem name

ExplanationZCSQL CONNECT was issued, but ALCS is alreadyconnected to DB2.


DXC8608I Now disconnected from DB2subsystem name

ExplanationALCS has successfully disconnected from DB2 name.


DXC8609I Unable -- currently connected toDB2 subsystem name

ExplanationZCSQL DISCONNECT was issued, but ALCS isconnected to a DB2 subsystem other than the onespecified in the command.



DXC8611I DB2 connect failure -- Returncode X'return_code' Reason codeX'reason_code'

ExplanationZCSQL CONNECT was issued, but ALCS failed toestablish the connection to DB2.

Operator responseRefer to IBM DB2 Messages and Codes for anexplanation of the return code and reason code.

DXC8612I DB2 disconnect failure -- Returncode X'return_code' Reason codeX'reason_code'

ExplanationZCSQL DISCONNECT was issued, but ALCS failed toterminate the connection to DB2.

Operator responseRefer to IBM DB2 Messages and Codes for anexplanation of the return code and reason code.

DXC8613I Invalid return code from CSQLCmacro



DXC8614I Unable -- SQL conversation inprogress

ExplanationA ZCSQL DISCONNECT has been received but at leastone entry is waiting for a response from DB2.

Operator responseInform your DB2 administrator. See ALCS Operationand Maintenance for an explanation of the ZCSQLFORCE parameter.

DXC8615I Waiting for DB2 subsystem ssnmto start

ExplanationDB2 was not started when ALCS tried to connect to it.ALCS will automatically try to connect again when DB2starts.

DXC8620E Invalid queue manager name

ExplanationThis is an error response to ZCMQI. You have specifiedan invalid MQSeries queue manager name.


DXC8621E Invalid initiation queue name

ExplanationThis is an error response to ZCMQI. You have specifiedan invalid MQSeries initiation queue name.


DXC8622E Invalid input queue name

ExplanationThis is an error response to ZCMQI. You have specifiedan invalid input queue name.


DXC8623W MQSeries not supported by thisALCS

ExplanationThis is an error response to ZCMQI. The ALCS systemconfiguration table does not specify support forMQSeries.

System programmer responseSee ALCS Installation and Customization forinformation on how to configure MQSeries.

DXC8624W Not currently connected toMQSeries

ExplanationThis command can only be used when MQSeries isconnected to your system.


Operator responseUse the ZCMQI command to connect to the MQSeriesqueue manager. This command is explained in ALCSOperation and Maintenance.

DXC8625I Currently connected to MQSeriesQueue manager queue_managerInitiation queue init_queue Inputqueue input_queue

ExplanationThis message is a normal response to the commandZCMQI. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8626I Now connected to MQSeriesQueue manager queue_managerInitiation queue init_queue Inputqueue input_queue


DXC8627I Now disconnected from MQSeriesQueue Manager queue_manager


DXC8628E Unable -- Already connected toMQSeries Queue manager name

ExplanationThis is an error response to ZCMQI. You have tried toconnect to MQSeries twice, this is not permitted.

DXC8629E Unable -- Currently connected toMQSeries Queue manager name

ExplanationThis ZCMQI command cannot be carried out becauseyou are actually connected to name and you specifiedanother queue manager name.


DXC8630E MQSeries subtask has abended --please retry

ExplanationThis command cannot be processed because aninternal error has occurred.

System actionALCS continues to operate normally.

Operator responseConnect to the MQSeries queue manager again andretry the command.

DXC8631E MQSeries connect failure --Completion code number Reasoncode reason_code

ExplanationALCS is unable to connect to the MQSeries queuemanager.

Operator responseSee MQSeries Messages and Codes Manual for anexplanation of the completion code and reason Code.

DXC8632E MQSeries disconnect failure --Completion code number Reasoncode reason_code

ExplanationAn error has occurred when you tried to disconnectfrom the MQSeries queue manager.

Operator responseSee MQSeries Messages and Codes Manual for anexplanation of the completion code and reason code.

DXC8633E Invalid return code from CMQICmacro

ExplanationAn internal error has occurred while trying to use theMQSeries queue manager.


DXC8634E Unable -- At least one objecthandle is in use


ExplanationThis message is an error response to the commandZCMQI DISCONNECT.

Operator responseCheck which applications are still using the MQSeriesqueue manager. See MQSeries Messages and CodesManual for an explanation of the ZCMQI FORCEparameter. Inform your MQSeries administrator.

DXC8635E MQSeries open failure --Completion code number Reasoncode reason_code

ExplanationAn error has occurred while trying to connect toMQSeries.

Operator responseSee MQSeries Messages and Codes Manual for anexplanation of the completion code and reason code.

DXC8636W MQSeries interface suspended

ExplanationThis is an error response to the command ZCMQI. TheMQSeries queue manager has stopped responding toALCS.

Operator responseInform your MQSeries administrator.

DXC8640I Invalid time/time difference

ExplanationYou have made a mistake in entering the time. Forexample you may have omitted a leading zero.


DXC8641I Invalid Action

ExplanationYou are not permitted to change the time to a previoustime.


DXC8642E Not allowed -- Time/timedifference must be less than 24hours.

ExplanationThe maximum amount of time you are allowed tochange the clock by is 23 hours 59 minutes.


DXC8643E Not allowed Negative local datechange

ExplanationYou are not permitted to change to a previous date.


DXC8644E Not allowed Negative GMT datechange

ExplanationYou are not permitted to change to a previous date.


DXC8645E Not allowed System error -- Clockupdate failed

ExplanationAn internal error occurred while using the ZATIMcommand.


DXC8646E Not allowed Reject by installationexit


ExplanationAn error has occurred when using the ZATIMcommand.

Operator responseSee ALCS Installation and Customization for anexplanation of the ATM1 installation-wide exit.

DXC8647E nnnn Not allowed

ExplanationAn error has occurred when using the ZATIMcommand.



ExplanationThis message is a normal response to the commandZATIM.


ExplanationThis message is a normal response to the commandZDTIM.

DXC8655I Sequential file sequential_fileswitch request accepted

ExplanationThis message is a normal response to the commandZSSEQ.

DXC8656E Switch not allowed for sequentialfile sequential_file

ExplanationYou have tried to switch a general sequential file.


DXC8657E Switch failed -- Configurationtable full



DXC8658E Switch failed -- Error codeX'error_code'



DXC8659E Sequential file sequential_file notin configuration table

ExplanationThis message is an error response to commandZSSEQ.

Operator responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands. Correct thetyping or syntax error and retry the command.

DXC8660E Switch failed -- Previous switchstill in progress

ExplanationThis sequential file is currently being switched fromactive to standby.

Operator responseUse ZDSEQ to confirm that the previously activesequential file is deallocated and then try again.

DXC8661E Switch failed -- Previous allocate/open still in progress

ExplanationA standby sequential file is currently being allocatedand opened and is not yet available for use.

Operator responseUse ZDSEQ to confirm that the standby sequential filehas been allocated and then try again.


DXC8662E Switch failed -- Only allowed onLOG file

ExplanationYou have specified the LOGALL or the NOLOGALLoption on a ZSSEQ command but have specified asequential file name which is not LOG. You may usethese options only when switching the LOG sequentialfile.

DXC8665I Invalid PF key

ExplanationThis message is an error response to commandZAKEY.


DXC8666I Invalid substitution trigger

ExplanationThis message is an error response to commandZAKEY.



ExplanationThis message is a normal response to the commandZDKEY. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8670I LOAD complete


DXC8671I Relocate run complete Imbeddedaddresses relocated address


DXC8672I number1 relocated to number2


DXC8673I Relocate table CLEAR started


DXC8674I Relocate table CLEAR complete


DXC8675I Copy from address to addresscomplete


DXC8676I File address not found in relocatetable

ExplanationThe file address in ZRELO OAD=add is incorrect.


DXC8677I Relocate table not initialized

ExplanationThe relocate table must be initialized before part of thedatabase is relocated.


Operator responseIssue ZRELO LOAD before you issue ZRELO RELOCATEand then try again

DXC8678I Record sizes unequal

ExplanationYou can only relocate records of the same size.

Operator responseCorrect the error and try again.

DXC8679I Error reading relocate table --Relocate abandoned

ExplanationAn error has occurred and ZRELO cannot continue.

Operator responseTry to locate the error, correct it and then resubmit thecommand.

DXC8680I Read error on copy-from record



DXC8681I Invalid restart request



DXC8682I Invalid copy-from address



DXC8683I Invalid copy-to address



DXC8684I Relocate table read error -- Clearcontinues

ExplanationAn internal error has occurred in reading to therelocate table.


Operator responseIf this happens frequently then ask your systemprogrammer to inform your IBM programming supportrepresentative.

DXC8685I Copyallfixed complete -- n recordscopied

ExplanationThis message is the normal response to a ZRELOCOPYALLFIXED command. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.

DXC8686E Recoup active -- Invalid CLEARrequest

ExplanationThis message is an error response to a ZRELO CLEARcommand. The relocate table can not be cleared whileRecoup is active.

Operator responseWait until the ZRECP command has finishedprocessing and then resubmit the command.

DXC8687E LOAD/DUMP active -- InvalidCLEAR request

ExplanationThis message is an error response to a ZRELO CLEARcommand. The relocate table can not be cleared whilethe relocating loader is active.


Operator responseWait until the ZRELO command has finishedprocessing and then resubmit the command.

DXC8692E Invalid size -- not defined in ALCSgeneration

ExplanationThis message is an error response to conversationaltrace command GET. The requested size is not definedin the ALCS generation.

Operator responseCorrect the GET command and retry.

DXC8693E Storage level not in use

ExplanationThis message is an error response to conversationaltrace command REL. The storage level is not in use.

Operator responseCorrect the REL command and retry.

DXC8695E Substep not possible -- instructionstepping must be active

ExplanationThis message is an error response to conversationaltrace command SUBSTEP. Instruction stepping mustbe active for the SUBSTEP command to be accepted.

Operator responseUse the STEP command to turn on instruction steppingthen retry the SUBSTEP command.

DXC8696E Invalid mode -- must be either E orI

ExplanationThis message is an error response to conversationaltrace command RUNSTOP. The mode must be either E(exclusive mode) or I (inclusive mode).

Operator responseCorrect the RUNSTOP command and retry.

DXC8697E Invalid level -- must be in rangeD0 - DF

ExplanationThis message is an error response to conversationaltrace command GET, REL, or FLIP. The storage level isincorrect.

Operator responseCorrect the GET, REL, or FLIP command and retry.

DXC8698E Invalid size -- must be in range L0- L8, or LX

ExplanationThis message is an error response to conversationaltrace command GET. The size is incorrect.


DXC8699E Storage level already in use

ExplanationThis message is an error response to conversationaltrace command GET. The storage level is already inuse.



ExplanationThis message is a normal response to the commandZPOOL. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8718I Attempt to alter a pool which doesnot exist

ExplanationThis message is an error response to commandZPOOL.


DXC8719I SKP must be more than KUL


ExplanationThis message is an error response to commandZPOOL.


DXC8720I ST Event logging is enabled forLnST pool

ExplanationThis message is part of the normal response tothe command ZPOOL. See ALCS Operation andMaintenance for a full explanation of how to use thecommand.

DXC8721I ST event logging already active

ExplanationYou have attempted to start short-term pool eventlogging while it already active.

Operator responseUse the ZPOOL command to determine the recordsize currently being logged. If you wish to start eventlogging for a different record size, you must first stopevent logging for the size which is currently beinglogged.

DXC8722E Cannot create data space for STevent logging

ExplanationALCS has encountered an error attempting to createa data space to hold the short-term pool eventinformation.

Operator responseYou cannot run event logging until this error has beenfixed. Contact your system programmer to determinethe cause of the problem.


ExplanationThis message is a normal response to the commandZPOOL. See ALCS Operation and Maintenance for a fullexplanation of how to use the command.


ExplanationThis message is a normal response to the commandZPOOL. See ALCS Operation and Maintenance for a fullexplanation of how to use the command.

DXC8726I Sequential file configuration tabletable_name load complete

ExplanationThis message is a normal response to the commandZASEQ.

DXC8727I Sequential file configuration tabletable_name load failed -- Returncode X'return_code'


System programmer responseCheck the return code in the appropriate MVSdocumentation.

DXC8728I Sequential file configuration tabletable_name load failed -- Formatinvalid

ExplanationWhere return_code is the system completion code,and the reason code. See the appropriate MVSMessage Library: System Codes.

Operator responseIf you are sure that you entered the commandcorrectly, inform your system programmer.

System programmer responseCheck the ALCS generation options to see if thesequential file exists.

DXC8729I Sequential file sequential_fileupdate complete

ExplanationThe sequential file update has completed successfully.

DXC8730E Sequential file sequential_fileupdate not allowed


ExplanationThis message is an error response to the commandZASEQ. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.


DXC8731I Sequential file sequential_fileupdate failed -- Return codeX'return_code'

ExplanationAn unexpected error occurred. ZASEQ command canupdate the general sequential file definition with anycorrect keywords and then give this error response.

Operator responseUse ZDSEQ to check the effect of the command.

DXC8732I Sequential file name or LOADomitted

ExplanationThe first parameter must be either LOAD or thesymbolic name of a general sequential file.



ExplanationThis message is a normal response to the commandZDSEQ. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8734I Sequential file sequential_filebefore update

ExplanationALCS displays the previous information before ZASEQupdates a sequential file. This is followed by messageDXC8729I, which shows the updated information.


ExplanationThis message is a normal response to the commandZPOOL. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8736E LT pool activity monitor -- keypointretrieval error

ExplanationThis is an error response to command ZPOOL ALCSwas not able to access the long-term pool activitydata.

Operator responseNotify your system programmer. The ALCS pool activitymonitor function is unusable.

System programmer responseEnsure that the record type #KPTRI (system keypointrecord) ordinal number 12 has not been illegallymodified by a user application program. (The hash(#) character is represented differently by someequipment, it is the EBCDIC X'7B' character.) If ithas not, then inform your IBM programming supportrepresentative.

DXC8738I LT Monitor interval is n minutes

ExplanationThis message is a normal response to the commandZDSEQ. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8746E Load failed -- Change in numberof records and record size needsseparate loads

ExplanationYou have attempted to change the record size of afixed file type without first committing the changewhich deleted and purged the records of the previoussize.


Programmer responseCreate a DASD load to delete and purge all the recordsof the type whose record size you wish to change.When this has been loaded, confirmed, and committedwith ZDASD COMMIT then create another load to addrecords of a different record size. For more informationon changing the record size of a fixed file type, refer toALCS Installation and Customization.

DXC8747S Invalid file address return fromrelocate


ExplanationALCS did not recognize the file address of the recordwhich must be relocated.


DXC8748E Error in specified ordinal(s)

ExplanationThe record ordinals you specified in the stripe startcommand are invalid.

Operator responseCheck the correct required ordinals and reenter thecommand.

DXC8749E Insufficient allocatable pool

ExplanationTo run restrict you need sufficient pool records tocontain the relocated records and to continue runningALCS. This message indicates there are fewer than24 hours worth or 500 records over and above thoseneeded for the restrict.

Operator responseRun Recoup to recover any released pool records orinform your system programmer.

Programmer responseConsider splitting a large batch of records intoseveral small batches, running Recoup between eachbatch. Also consider using the installation wide ECB-controlled exit APA1 to modify the requirements.

DXC8750S Global area not loaded

ExplanationThe global record used to track the progress of restripeis not available.

Operator responseCheck whether ALCS started successfully. Errormessages during global restart may indicate there isa problem with global load.

DXC8751E Stripe already paused

ExplanationYou have tried to pause stripe when it was alreadypaused.

Operator responseIf you wish to restart the stripe already paused thenenter ZDASD STRIPE RESTART. If you wish to starta different stripe, then enter ZDASD STRIPE CANCELfirst.

DXC8752E Stripe already running

ExplanationYou have attempted to restart stripe while it wasalready running.

Operator responseAllow the stripe to complete, or cancel it using ZDASDSTRIPE CANCEL.

DXC8753I Stripe restart awaited

ExplanationYou have restarted ALCS which was previouslyterminated while a stripe was running or was in pausestatus.

Operator responseWhen you wish to continue the stripe in progress enterZDASD STRIPE RESTART.

DXC8754E Unable - Another stripe commandbeing processed

ExplanationYou have entered a ZDASD STRIPE command whileALCS was processing a previous ZDASD STRIPEcommand.

Operator responseAllow the previous ZDASD STRIPE command tocomplete. If it does not then inform your systemprogrammer.

DXC8755E Stripe not active

ExplanationYou have attempted to cancel or pause a stripe whilethere is no stripe active.


Operator responseDetermine why the stripe is not active, and ifnecessary start it.

DXC8756E Stripe already active

ExplanationYou have attempted to run a stripe while there isalready one running.

Operator responseAllow the current stripe to complete, or cancel it usingZDASD STRIPE CANCEL.

DXC8758E Record type invalid or omitted

ExplanationYou have attempted to start a stripe, but the file typeyou specified is invalid.

Operator responseDetermine what the file type should be and reenter thecommand.

DXC8759E Table build needed

ExplanationYou have attempted to start a stripe, but the file typeyou specified is still algorithm driven.


Programmer responseBefore using stripe for a specific file type, the file typemust be table driven. You must therefore load andconfirm a DASD configuration in which the BUILD=YESoption is specified for the file type, or there is aDBHIST BUILD_DIRECTORIES signifying all file typesare BUILD=YES.

DXC8760S Error accessing ConfigurationDataset

ExplanationAn I/O error has occurred when trying to access aconfiguration dataset.


DXC8761E Sequence error

ExplanationYou have tried to perform an action out of sequence.This was caused by an attempt to do one of thefollowing:

• Loading a new configuration table withoutcommitting or backing out the previous one.

• Backing out a configuration table without previouslyloading it.

• Confirming a configuration table without previouslyloading it.

• Committing a configuration table without previouslyconfirming it.

Operator responseRefer to ALCS Operation and Maintenance whichexplains how to perform the action in the correctsequence.

DXC8762E Member not found

ExplanationYou have attempted to load a new configuration tablespecifying a member that does not exist.

Operator responseEnsure that the named member is in the load library. Ifit is not then rerun the DASD generation.

DXC8763E Load failed - Does not matchloaded data New item-X'aaaaaaaaaaaaaaaa aaaaaaaa aaaaaaaa'Listing-X'nnnnnnnn' Old item-X'bbbbbbbb bbbbbbbb bbbbbbbbbbbbbbbb'

ExplanationThe data being loaded does not match the dataalready loaded. This could be because you areattempting to load a member that was generated fora different system, for example using different data setnames. Or it could be that in creating the new memberyou have changed the source code used to create thepreviously loaded member.


Operator responseAsk your system programmer to check the source codeused to generate the member to be loaded, and tocompare it with the source code used to generate themember previously loaded. All additions must followthe previous code.

Programmer responseTo aid diagnosis, the first non-matching item is listedin its before and after form and the listing address inthe DASD generation stage 2 output is also given. Ifyou cannot determine the cause of the mismatch fromthis information you may need to contact your IBMprogramming support representative.

DXC8764S Load failed - cannot allocatesystem records

ExplanationALCS cannot allocate the records needed to referencethe fixed-file tables.


DXC8765I Data set now offline

ExplanationThis message is a normal response to the commandZDASD. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8766I Data set vary request accepted



DXC8767I ONLINE/OFFLINE parameterinvalid or omitted



DXC8768I Data set details invalid or omitted



DXC8769I Data set number invalid or omitted



DXC8770I Data set already offline



DXC8771I Data set does not exist



DXC8772I Data set is only online copy




DXC8773I Unexpected return code fromDASCC



DXC8774I Data set already online



DXC8775I Data set allocate failed dsnameReturn code RC-X'return_code'Error Code EC-X'error_code'

ExplanationThere is an error with the data set allocation.This could be caused by the VSAM definition beingincorrectly specified or there may be another problemwith the generation process.

Operator responseCheck the return code and error code in theappropriate MVS documentation. Correct the error andretry the command.

DXC8776I Data set offline

ExplanationYou have attempted to display a file address which islocated on a data set that is offline.

Operator responseCheck the file address and retry the command.

DXC8777I Copy already in progress for thisdata set



Operator responseAllow the copy to complete.

DXC8778I Additional display parameterinvalid or omitted



DXC8779I Data set number range invalid



DXC8780I Vary ONLINE/OFFLINE notallowed for test database

ExplanationYou are trying to allocate or deallocate a testdatabase; this is not allowed.







DXC8783E Load failed - Already Loaded

ExplanationThis message is an error response to commandZDASD. You have tried to load a new database whenthat database is already loaded.

Operator responseCheck the name of the member to be loaded and, ifnecessary, retry the command with the correct name.

DXC8784E Load failed - First update must beDBHIST

ExplanationThere is an error in the DASD generation. Either youhave not coded the DBHIST macro correctly or youhave omitted the DBHIST macro.


System programmer responseRefer to ALCS Installation and Customization for a fullexplanation of the DBHIST macro.

DXC8785I Request rejected

ExplanationYou are trying to load a new database but there aresome utility programs already running.

Operator responseAllow the utility programs to complete or cancel themand then repeat the command.

DXC8786E Load failed -- Format notcompatible

ExplanationThe member you are trying to load is not in the correctformat to be loaded as a DASD configuration table.

Operator responseCheck the name to ensure that you have not made atyping error, otherwise rerun the generation.

DXC8787E Load failed -- not enough memory


System programmer responseCheck that you have coded the SCTGEN macrocorrectly. If you have, you should liaise with your MVSSystem Programmer to obtain more memory beforestarting ALCS again.

DXC8788E Load failed -- Recoup run needed

ExplanationA move to type 2 short term pool support is beingattempted, but the ST pool records have not all beentagged. Recoup performs tagging of ST pool records.

Operator responseRun Recoup and then retry the ZDASD LOADcommand.

DXC8789E Load failed -- Increase in ST poolallocation and move to type 2 STpool need separate loads

ExplanationA move to type 2 ST pool support and an increase in STpool allocation causing an increase in restriction levelare taking place at the same time. This is not permittedbecause the increase in restriction level (low ordinal)can leave insufficient ST records in the pool.

System programmer responseLoad and commit the increased pool sizes and runRecoup before loading the move to type 2 support.












DXC8797I Stripe status Record type .......typeStart ordinal ........aaa Endordinal ..........aaa Currentordinal ......aaa Recordsmoved ........bbb

ExplanationThis message indicates the status of the stripecurrently being processed. It may appear on RO CRAS,or on your terminal in response to a status request.

• status is one of the following:started

- the stripe has startedcomplete

- the stripe has finishedpausing

- the stripe has been pausedpaused

- pause is completebeing cancelled

- the stripe has been cancelledcancelled

- cancel is complete• type is the file type being striped.• aaa is the start, end or current ordinal

• bbb is the number of records actually relocated(moved).

Fixed file records which have never been allocatedare not relocated.

DXC8798I Stripe started

ExplanationYou have successfully started a stripe. The completionsummary will appear on RO CRAS.


ExplanationError response. Only the Prime CRAS can enterCONNECT, DISCONNECT, or LISTEN (with the ZCTCPcommand).

Problem determinationSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8802E Invalid TCP/IP address spacename

ExplanationError response. The name of the TCP/IP addressspace is invalid. It should be up to 8 alphanumericcharacters.

Problem determinationSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8803E TCP/IP not supported by this ALCS

ExplanationError response. The ALCS system configuration tabledoes not specify support for TCP/IP.

Problem determinationSee ALCS Installation and Customization forinformation on how to configure TCP/IP.

DXC8804E Not currently connected to TCP/IP

ExplanationError response. ALCS must be connected to a TCP/IPaddress space for this command to process.


Operator responseUse the ZCTCP command to connect to the TCP/IPaddress space. See ALCS Operation and Maintenancefor a full explanation of how to use the commands.

DXC8805I Currently connected to TCP/IPaddress space AS-'name'

ExplanationNormal response. ALCS is currently connected to theTCP/IP address space name.

DXC8806I Now connected to TCP/IP addressspace AS-'name'

ExplanationNormal response. ALCS is now connected to theTCP/IP address space name.

DXC8807E Unable - Already connected toTCP/IP address space AS-'name'

ExplanationError response. ZCTCP CONNECT was issued, butALCS is already connected to the TCP/IP addressspace name.

DXC8808I Disconnected from TCP/IP addressspace AS-'name'

ExplanationNormal response. ALCS has started to disconnect fromthe TCP/IP address space name. Disconnection cantake up to 1 minute to complete.

DXC8809E Unable - Currently connected toTCP/IP address space AS-'name'

ExplanationError response.

DXC8810E Unable - Listener subtask hasabended


DXC8811E TCP/IP connect failure - Returncode X'return_code' Reason codeX'reason_code'


DXC8812E TCP/IP disconnect failure - Returncode X'return_code' Reason codeX'reason_code'

ExplanationError response

DXC8813E Invalid return code from SOCKCmacro


DXC8814E Unable - sockets thread inprogress

ExplanationA ZCTCP DISCONNECT command was entered butALCS cannot process it for one of the followingreasons:

• At least one TCP/IP communication resource isactive or stopping.

• At least one entry is waiting for a response fromTCP/IP.

Operator responseInactivate any TCP/IP communication resources(ZACOM INACT command) and stop any applicationsthat issue TCP/IP sockets calls before retrying theZCTCP DISCONNECT command.

DXC8815E Invalid PORT number


DXC8816I Starting Listener for TCP/IP portPO-'number'

ExplanationThis message is a normal response to the commandZCTCP. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8817E Unable - Listener already startedfor TCP/IP port PO-'number'



DXC8818E TCP/IP Listener start failure -Return code X'return_code' Reasoncode X'reason_code'


DXC8819I Stopping Listener for TCP/IP portPO-'number'


DXC8820E Unable - Listener is using TCP/IPport PO-'number'


DXC8821E TCP/IP Listener stop failure -Return code X'return_code' Reasoncode X'reason_code'


DXC8822E Listener not started


DXC8823E Unable - Listener must be stopped


DXC8824E Listener not supported by thisALCS

ExplanationError response. The ALCS system configuration tabledoes not specify support for the ALCS ConcurrentServer (Listener).

Problem determinationSee ALCS Installation and Customization forinformation on how to configure TCP/IP.

DXC8825I Currently connected to TCP/IPaddress space AS-'name' Virtual

IP address vipa_status Listener nlistener_status


vipa_status is one of:

virtual_ip_address if an IP address was specifiedon the TCPVIPA parameter of the SCTGEN systemgeneration macro.not defined if TCPVIPA was not specified.

n is the index number of the concurrent server (1 to 8).

listener_status is one of:

not startedstarted on port PO-'number'

DXC8826I Not currently connected to TCP/IPVirtual IP address vipa_status


vipa_status is one of:

virtual_ip_address if an IP address was specifiedon the TCPVIPA parameter of the SCTGEN systemgeneration macro.not defined if TCPVIPA was not specified.

DXC8840I Retrieve not active

ExplanationYou used the ZRETR command to retrieve a messagebut retrieve is not active for your terminal.

User responseUse the ZRETR START command to start the retrievefunction for your terminal.

DXC8841I Retrieve already started

ExplanationYou used the ZRETR command to start retrieve butretrieve is already active for your terminal.

DXC8842I Retrieve already stopped


ExplanationYou used the ZRETR command to stop retrieve butretrieve is not active for your terminal.

DXC8843I No messages to retrieve

ExplanationYou used the ZRETR command to retrieve a previouslysaved message but there are no messages saved.

DXC8844I No messages to display

ExplanationYou used the ZRETR command to display messagessaved by the retrieve facility but there are nomessages saved.

DXC8845E Undefined record ID #RIDCRET forretrieve

ExplanationThis is an error response to the ZRETR STARTcommand. The record ID #RIDCRET that is used bythe retrieve facility is not defined to ALCS.

System actionALCS does not start retrieve for this terminal.

System programmer responseTo enable the retrieve facility, load a DASDconfiguration table which defines pool file recordswith ID #RIDCRET (X'AC08'). See ALCS Installationand Customization for information on ALCS recordrequirements.

ModuleZRETR

DXC8846E Unable to obtain RCR

ExplanationThis is an error response to the ZRETR command. TheRCR can not be obtained and therefore the pool filerecord used by ZRETR can not be obtained.

System actionThe requested function can not be performed.

System programmer responseThe RCR is probably in use by another function. Try thecommand later.

ModuleZRETR

DXC8850R Please enter your user ID or enterLOGOFF to cancel this logon:

ExplanationThis message is part of the ALCS logon prompt for IBMALC and compatible terminals.

User responseEnter your user ID and press Enter. Alternatively enter'LOGOFF' and press enter.

DXC8851R Please enter your password oruse the format OLD/NEW/NEWto change your password or justpress Enter to cancel this logon:

ExplanationThis message is part of the ALCS logon prompt for IBMALC and compatible terminals.

User responseEnter your password and press Enter. If you want tochange your password, enter your existing password,followed by a slash (/) character, followed by your newpassword, followed by a slash character, followed byyour new password (again) and press Enter.

DXC8852I Logged off press Enter to startlogon:

ExplanationYou are no longer logged on to ALCS.

User responseIf you want to start or continue using ALCS then pressEnter; ALCS will prompt for your user ID and password,if required. If not then you can ignore this message.

DXC8853I No change in CRAS authority

ExplanationThe device has not changed from one CRAS authorityto another.



DXC8854E Remove current CRAS authorityand retry

ExplanationYou have tried to give CRAS status to a device thatcurrently has CRAS authority.

Operator responseCheck that the CRN and CRI of the device you wantto modify are correct. Use ZACOM CRASAUTH=NONEcommand to remove CRAS authority from the device,then retry the command.

DXC8855E Cannot remove Prime CRAS status

ExplanationYou have tried to remove Prime CRAS status from adevice without assigning it to another device.

Operator responseCheck that the CRN and CRI of the device you wantto modify are correct. Use ZACOM PRC=crn to assignPrime CRAS status to another device, then retry thecommand.

DXC8856E Originator is not authorized

ExplanationYou have tried to give CRAS authority to your ownterminal and there is no SAF decision, but yourterminal does not have sufficient CRAS authorizationto perform the function.

Operator responseSee ALCS Operation and Maintenance for a fullexplanation of how to use the commands. If CRASauthorization is required then contact your securityadministrator.

DXC8857E Remove current CRAS status andretry

ExplanationYou have tried to give CRAS authority to a device thatcurrently has CRAS status.

Operator responseCheck that the CRN and CRI of the device you want tomodify are correct. Use ZACOM NOCRAS=crn commandto remove CRAS status from the device, then retry thecommand.

DXC8858E Cannot remove Read Only CRASstatus

ExplanationYou have tried to remove Read Only CRAS status froma device without assigning it to another device.

Operator responseCheck that the CRN and CRI of the device you wantto modify are correct. Use ZACOM ROC=crn to assignRead Only CRAS status to another device, then retrythe command.

DXC8859E Resource is not a display


Operator responseCorrect the typing or syntax error, then retry thecommand.

DXC8899E Input message format not correct

ExplanationThe format of your input message is not correct.

User responseCorrect the typing or syntax error and retry the inputmessage. If you are unsure of the correct format,consult your supervisor or refer to your installation'sdocumentation.


ExplanationThis message is a normal response to thecommand ZDCOM or ZACOM. See ALCS Operation andMaintenance for a full explanation of how to use thecommands.

DXC8901I No matching resources found



DXC8902I User data for CRN-crn does notexist


DXC8903I User data for CRN-crn suppressedby installation-wide exit

ExplanationZDCOM USERDATA was issued, but the installation-wide exit program ACD1 determined that the user datashould not be displayed.


System programmer responseSee ALCS Installation and Customization for a fulldescription of the installation-wide exit ACD1.

DXC8904I User data for CRN-crn cannot beaccessed

ExplanationZDCOM USERDATA was issued, but ALCS was unable toaccess the user data.




DXC8906I Resource is not the correct type

ExplanationThis is a response to one of:

• ZDCOM CHANNELS, when the specified resource isnot an SLC link

• ZDCOM ALL, when the specified resource is notan X.25 PVC link, a TCP/IP connection, or an MQconnection.

• ZACOM to set or clear BATAP variables, when thespecified resource is not an X.25 PVC link or aTCP/IP connection.

• ZACOM RHOST or RHOSTn, when the specifiedresource is not a TCP/IP terminal or a TCP/IPconnection.

• ZACOM SCRSZE, when the specified resource is notan ALC terminal.



ExplanationThis message is a normal response to the commandZDCOM. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.

DXC8908I Alternate CRAS number ATnnn isavailable


DXC8909I Alternate CRAS number APnnn isavailable


DXC8910W No available alternate CRASnumber found


DXC8911W No available alternate CRASprinter number found








ExplanationThis message is a normal response to the ZDCOMREDIRECT command.

DXC8920E No matching module found

ExplanationThis message is an error response to the ZPCTLDISPLAY command.

DXC8921I Communication load moduleMODN-module loaded

ExplanationThis message is a normal response to the ZACOMLOAD command.

DXC8922I Communication load moduleMODN-module confirmed

ExplanationThis message is a normal response to the ZACOMCONFIRM command.

DXC8923I Communication load moduleMODN-module committed

ExplanationThis message is a normal response to the ZACOMCOMMIT command.

DXC8924I Communication load moduleMODN-module backed out

ExplanationThis message is a normal response to the ZACOMBACKOUT command.

DXC8925I List MODN-module loaded

ExplanationThis message is a normal response to the ZACOMLOAD LIST and ZPCTL LOAD LIST commands.

DXC8926I List MODN-module confirmed

ExplanationThis message is a normal response to the ZACOMCONFIRM LIST and ZPCTL CONFIRM LISTcommands.

DXC8927I List MODN-module committed

ExplanationThis message is a normal response to the ZACOMCOMMIT LIST and ZPCTL COMMIT LIST commands.

DXC8928I List MODN-module backed out

ExplanationThis message is a normal response to the ZACOMBACKOUT LIST and ZPCTL BACKOUT LISTcommands.

DXC8929E CDS is locked

ExplanationThis message is an error response to the ZACOM orZPCTL command. This error can occur if ALCS hasreceived simultaneous ZACOM or ZPCTL commands.

Operator responseRetry the command. If the problem persists, contactyour IBM program support representative.

DXC8930I No CDS defined

ExplanationThis message is a normal response to the ZPCTLREPORT or ZACOM REPORT command. When thismessage is a response to the ZPCTL REPORTcommand, your ALCS system does not have a programconfiguration data set (CDS1) defined. When thismessage is a response to the ZACOM REPORTcommand, your ALCS system does not have acommunication configuration data set (CDS2) defined.


ExplanationThis message is a normal response to the ZPCTLREPORT or ZACOM REPORT command. See ALCS


Operation and Maintenance for a full explanation ofhow to use the commands.

DXC8937E No CDS defined

ExplanationThis message is an error response to the ZPCTL orZACOM command. When this message is a responseto the ZPCTL command, your ALCS system doesnot have a program configuration data set (CDS1)defined. When this message is a response to theZACOM command, your ALCS system does not have acommunication configuration data set (CDS2) defined.

DXC8938E Request is out of sequence

ExplanationThis message is an error response to the ZPCTL orZACOM command.

DXC8939E Unable to update CDS

ExplanationThis message is an error response to the ZPCTL orZACOM command. If the command was ZPCTL, ALCSwas unable to update the program configuration dataset (CDS1). If the command was ZACOM, ALCS wasunable to update the communication configurationdata set (CDS2).

Operator responseIf a program configuration table is being loaded ontoCDS1, or a communication configuration load list isbeing loaded onto CDS2, one of the load modulesreferenced by the load list may be missing from thez/OS load library. Use the ZPCTL Report or ZACOMReport command to check for missing module namesin the load list. Alternatively, check for I/O errormessages on the ALCS RO CRAS and the z/OS systemlog. If no I/O errors have been reported, retry theZPCTL or ZACOM command. If the problem persists,contact your IBM program support representative.

DXC8940E Invalid command format

ExplanationThis message is an error response to commandZACOM.


DXC8941E Unrecognisable request



DXC8942E No SLC network



DXC8943E Invalid link CRN



DXC8944E Invalid link channel number



DXC8945E Unable -- System state change inprogress

ExplanationThis command can only progress after the ZASYScommand has completed.

Operator responseCheck the status of ALCS with ZDSYS and thenresubmit the command.


DXC8946E Unable -- Network operation inprogress

ExplanationThis command cannot progress until the networkchange has completed.


DXC8947E Unable -- Link cycling

ExplanationA ZACOM OPEN, CLOSE, START or STOP command isalready being performed on this channel.

Operator responseWait until the previous command has completed andtry again.

DXC8948E Unable -- Line(s) not open


Operator responseEnter ZACOM OPEN to open the channel or link.

DXC8949E Unable -- Line(s) must be stopped

ExplanationThis command cannot be processed until the lines arestopped.

Operator responseEnter ZACOM STOP to stop the lines.

DXC8950W No lines to display

ExplanationYou have requested a display of lines but none areavailable.


DXC8951W No lines to open

ExplanationYou have requested that some lines should be openedbut none are available.


DXC8952W No lines to close

ExplanationYou have requested that some lines should be closedbut none are open.


DXC8953W No lines to start

ExplanationYou have requested that some lines should be startedbut none are ready.


DXC8954W No lines to stop

ExplanationYou have requested that some lines should be stoppedbut none are open.


DXC8955W Already open

ExplanationYou have tried to open a line that is already open.


DXC8956W Already closed


ExplanationYou have tried to close a line that is already closed.


DXC8957W Already started

ExplanationYou have tried to start a line that is already started.


DXC8958W Already stopped

ExplanationYou have tried to stop a line that is already stopped.


DXC8959I Open OK

ExplanationThe line has opened successfully. This message is anormal response to the command ZACOM.

DXC8960I Closed OK

ExplanationThe line has closed successfully. This message is anormal response to the command ZACOM.

DXC8961I Started OK

ExplanationThe line has started successfully. This message is anormal response to the command ZACOM.

DXC8962I Stopped OK

ExplanationThe line has stopped successfully. This message is anormal response to the command ZACOM.

DXC8963E Open failure

ExplanationAn error has occurred in trying to open a line using thecommand ZACOM.

Operator responseCorrect the typing or syntax error and retry thecommand. If this message occurs frequently, ask yoursystem programmer to inform your high-level-networksupport representative.

DXC8964E Close failure

ExplanationAn error has occurred in trying to close a line using thecommand ZACOM.

Operator responseCorrect the typing or syntax error and retry thecommand. If this message occurs frequently, ask yoursystem programmer to inform your high-level-networksupport representative.

DXC8965I Links processed OK


DXC8966I Started OK

ExplanationThis message is a normal response to the commandZLKTR.

DXC8967I Stopped OK


DXC8968W Already started

ExplanationYou have tried to start a line that is already started.This is an error response to command ZACOM.


DXC8969W Already stopped


ExplanationYou have tried to stop a line that is already stopped.This is an error response to command ZACOM.


DXC8970E Start failed

ExplanationAn error has occurred in starting a line. This is an errorresponse to command ZACOM.


DXC8971E Stop failed

ExplanationAn error has occurred in stopping a line. This is anerror response to command ZACOM.


DXC8972I Options set ON OK


DXC8973I Options set OFF OK

ExplanationThis message is a normal response to the commandZLKTR

DXC8974E TERM/DIAG/BLOCK omitted

ExplanationYou must specify which terminal, diagnostic file ormacro trace block you wish to trace to. This is an errorresponse to command ZLKTR.

Programmer responseCorrect the typing or syntax error and retry thecommand.

DXC8975E Link CRN/CRI omitted

ExplanationThis message is an error response to commandZLKTR.


DXC8976E Invalid terminal CRN



DXC8977E Invalid parameter on TYPEkeyword



DXC8978E No SLC network

ExplanationThere is no SLC network installed. This is an errorresponse to command ZLKTR.


DXC8979E Invalid link channel number




DXC8980E Invalid parameter on DATAkeyword



DXC8981E Invalid link CRN



DXC8982E Invalid link CRI



DXC8983W Open failure -- Timeout expired



DXC8984W Open failure -- Timeout expiredSLC open processing stopped atlink name channel name




ExplanationThis message is a normal response to the commandZLKST. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.



DXC8991I No SLC link trace block entries inuse



ExplanationThis message is a normal response to the commandZLKTR. See ALCS Operation and Maintenance for a fullexplanation of how to use the commands.





DXC8995I SLC link trace status for CRN-crnOff


DXC8996E Invalid IP address


ExplanationThis message is an error response to the commandZACOM RHOST. You have entered an incorrect IPaddress.


DXC8997E Resource is not a TCP/IP ALCterminal

ExplanationThis message is an error response to the commandZACOM RHOST. You have entered the CRI or CRN ofa communication resource that is not an ALC terminalconnected through TCP/IP.


DXC8998I Remote IP address updated

ExplanationThis message is a normal response to the commandZACOM RHOST.

DXC8999I MATIP sessions ...



Chapter 11. NetView interface program messages:DXC9000-DXC9099

DXC9000I Task TSK-'task_id' - DXCPPI active

ExplanationThe NetView Program-to-Program Interface (PPI)module DXCPPI is started.

System actionDXCPPI continues.

ModuleDXCPPI

DXC9001W Task TSK-'task_id' - DXCPPIterminated

ExplanationThe NetView Program-to-Program Interface (PPI)module DXCPPI is terminated. This is probably at therequest of the NetView operator, but it could be thatsome modification to the code has caused DXCPPI toterminate abnormally.

System actionDXCPPI terminates.

Operator responseIn the case of abnormal termination, check NetViewfor further information, and if necessary consult yoursystem programmer.

ModuleDXCPPI

DXC9002I Task TSK-'task_id' - DXCPPIinitialized

ExplanationThe NetView Program-to-Program Interface (PPI) toALCS is initialized.


ModuleDXCPPI

DXC9003E Task TSK-'task_id' - Requesttype RQT-'request_type' failed withreturn code RC-'return_code'

ExplanationThe NetView Program-to-Program Interface (PPI)request type request_type failed with returncode return_code. (See NetView Program-to-ProgramInterface for details.)


User responseCheck the PPI receiver-id is properly defined in theNetView fixed-format parameter list AM0TLIST.

ModuleDXCPPI

DXC9004E Task TSK-'task_id' - Genericalert was lost with return codeRC-'return_code'

ExplanationA NetView Program-to-Program Interface (PPI)Generic Alert received from ALCS was lost with returncode return_code.

ExplanationThe return_code is one of:

4The format of the buffer that was passed wasinvalid.


8The task identified by the operator-id is inactive oris not defined.

12A buffer could not be obtained.

16NetView is terminating.

20Service work block ( SWB ) address is invalid.

22The list specified with the LIST option containedno operator IDs. It contained only unassignedgroup IDs.

23Messages were routed to the first 255 operatorsand/or groups.

24An invalid value was specified for priority.


User responseCheck if the operator-id's are defined in the NetViewfixed-format parameter list, AM0TLIST, and that theyare active. In case of difficulty, consult your systemprogrammer.

ModuleDXCPPI

DXC9005E Task TSK-'task_id' - DXCPPIinternal logic error

ExplanationThere is an internal logic error in a NetView Program-to-Program Interface (PPI) DXCPPI routine.



ModuleDXCPPI

DXC9006E Task TSK-'task_id' - AM0TLISTomitted or invalid

ExplanationThe NetView Program-to-Program Interface (PPI)fixed-format parameter list supplied (AM0TLIST) wasomitted or invalid.


User responseCheck that the fields in the NetView AM0TLISTmember are defined in the correct fixed columnpositions (see "Automated Operations" in the ALCSInstallation and Customization). If they are, informyour system programmer.

ModuleDXCPPI

DXC9007E Task TSK-'task-id' - Message forTA-'ta' was lost with return codeRC-'return_code'

ExplanationA NetView Program-to-Program Interface (PPI)message received from ALCS for terminal ta was lostwith return code return_code.

ExplanationThe return_code is one of:

4The format of the buffer that was passed wasinvalid.

8The task identified by the operator-id is inactive oris not defined.

12A buffer could not be obtained.

16NetView is terminating.

20Service work block ( SWB ) address is invalid.

22The list specified with the LIST option containedno operator IDs. It contained only unassignedgroup IDs.

23Messages were routed to the first 255 operatorsand/or groups.

24An invalid value was specified for priority.



User responseCheck if the operator-id's are defined in the NetViewfixed-format parameter list, AM0TLIST, and that they

are active. In case of difficulty, consult your systemprogrammer.

ModuleDXCPPI

Chapter 11. NetView interface program messages: DXC9000-DXC9099 293

Chapter 12. Error Messages for COMTC ADD/REPLACE: DXC9100-DXC9199

The COMTC ADD and COMTC REPLACE macros require communication resource data to be provided in theCommunication Resource Definition DSECT (CT1TM). When ALCS validates that communicationresource data, if one or more errors are detected, appropriate error messages are placed in a storageblock and passed back to the program which issued the COMTC ADD or COMTC REPLACE macro. A returncode in register 15 should be tested to determine if any errors were found. An error message will reside inthe storage block for each error condition found. Each error message is a maximum of 80 bytes, thereforethe storage block is formatted into 80-byte items. A 4-byte header resides at the beginning of the blockcontaining a count of the error messages that have been placed in the block. Immediately following theheader is the first 80-byte error message item. The error message text is in EBCDIC and the messagecontains a prefix DXCnnnnE, where the message number nnnn is in the range 9100 to 9199.

This section describes all the DXC91nnE error messages and provides guidance on how each error can becorrected. The CEUS may wish to just pass these error messages back to the end user, or it may wish toinform the user in some other way.

DXC9101E Parameter not allowed for thisresource type

ExplanationThe communication resource definition contains datathat is not relevant for this resource type.

System actionALCS does not perform this change request.

User responseCheck the description of each field in theCommunication Resource Definition DSECT (CT1TM)to determine which fields are relevant for thecommunication resource type that this resourcebelongs to. Identify the fields in CT1TM that aremarked as not relevant for this communicationresource type and ensure that those fields containhexadecimal zero.

ModuleDXCOCTM

DXC9102E Application name not specified(for routing messages fromterminal)

ExplanationThe name of the ALCS application to which ALCS isto route messages for this new terminal has not beenspecified.


User responseProvide the ALCS application name in field CT1APLin the Communication Resource Definition DSECT(CT1TM).

ModuleDXCOCTM

DXC9103E Name of owning MQ/WAS resourcenot specified

ExplanationThe name of the ALCS MQ queue resource(LDTYPE=MQ) that owns this MQ terminal or the nameof the ALCS WAS resource (LDTYPE=WAS) that ownsthis WAS terminal has not been specified.

System actionALCS takes no action on this change request.

User responseProvide the name of the owning MQ queue resourcein field CT1MQL or provide the name of the owningWAS resource in field CT1WSL in the CommunicationResource Definition DSECT (CT1TM).

ModuleDXCOCTM


DXC9104E Other system communicationidentifier not specified

ExplanationThe system communication ID of the other system thatowns this OSYS Other System terminal has not beenspecified.


User responseProvide the system communication ID of the othersystem in field CT1COM in the CommunicationResource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9105E Cross system identifier notspecified

ExplanationThe cross system identifier for this OSYS Other Systemterminal has not been specified (the cross systemidentifier is the address of this terminal on the othersystem).


User responseProvide the cross system identifier in field CT1CSIin the Communication Resource Definition DSECT(CT1TM).

ModuleDXCOCTM

DXC9106E Terminal device type not specified

ExplanationThe device type has not been specified for thisterminal.


User responseSet the appropriate terminal type symbol in fieldCT1TRM in the Communication Resource DefinitionDSECT (CT1TM).

ModuleDXCOCTM

DXC9107E LEID address not specified

ExplanationThe Logical End-point IDentifier (LEID) address bywhich this terminal is known by ALCI has not beenspecified.


User responseProvide the LEID address for this VTAM/ALCI ALCterminal in field CT1LEI in the CommunicationResource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9108E Terminal address values notcomplete

ExplanationThe addressing information for the X.25 or TCP/IPMATIP terminal is incomplete.


User responseEnsure that all the required addressing information isprovided in the Communication Resource DefinitionDSECT (CT1TM). An X.25 ALC terminal requires aterminal address in field CT1CTA and an interchangeaddress in field CT1CIA. A TCP/IP MATIP terminalrequires a terminal address in field CT1CTA, an A1address value in field CT1TCI, and an A2 address valuein field CT1CIA.

ModuleDXCOCTM

Chapter 12. Error Messages for COMTC ADD/REPLACE: DXC9100-DXC9199 295

DXC9109E Name of owning X.25 PVC notspecified

ExplanationThe name of the ALCS X.25 PVC resource(LDTYPE=X25PVC) that owns this X.25 ALC terminalhas not been specified.


User responseProvide the name of the owning X.25 PVC resourcein field CT1PVC in the Communication ResourceDefinition DSECT (CT1TM).

ModuleDXCOCTM

DXC9110E Invalid application name (forrouting messages from terminal)

ExplanationThe name of the ALCS application to which ALCS is toroute messages for this terminal is invalid.


User responseCorrect the ALCS application name in field CT1APLin the Communication Resource Definition DSECT(CT1TM).

ModuleDXCOCTM

DXC9111E Invalid associated resource name

ExplanationThe name of the ALCS communication resource that isto be associated with this terminal is invalid.


User responseCorrect the name of the associated resource in fieldCT1ASD in the Communication Resource DefinitionDSECT (CT1TM).

ModuleDXCOCTM

DXC9112E Invalid initial status for terminal

ExplanationThe initial status of this ALCS communication resourcehas been incorrectly defined. For example, the initialstatus of an ALC terminal can not be defined as shared.


User responseSet the appropriate initial status symbol in fieldCT1IST in the Communication Resource DefinitionDSECT (CT1TM).

ModuleDXCOCTM

DXC9113E Invalid terminal device type

ExplanationThe device type that has been specified forthis terminal is invalid. For example, when thecommunications resource type is a VTAM 3270, theterminal type can not be defined as an ALC 4505display.


User responseSet the correct terminal type symbol in field CT1TRMin the Communication Resource Definition DSECT(CT1TM).

ModuleDXCOCTM

DXC9114E CRAS status incorrectly defined


ExplanationThe alternate CRAS status for this terminal isincorrectly defined.


User responseSet the correct alternate CRAS type symbol in fieldCT1CRS and the correct alternate CRAS numberin field CT1ALT in the Communication ResourceDefinition DSECT (CT1TM).

ModuleDXCOCTM

DXC9115E Invalid X.25 PVC type (must betype 1, 6 or 7)

ExplanationThe PVC type for this X.25 PVC has been incorrectlydefined.


User responseSet the correct PVC type symbol in field CT1PRT in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9116E Invalid interchange (A2) address

ExplanationThe interchange address provided for an X.25 ALCterminal, or the A2 address value provided for aTCP/IP MATIP terminal, is invalid.


User responseProvide a valid interchange address (or A2 addressvalue) in field CT1CIA in the Communication ResourceDefinition DSECT (CT1TM).

ModuleDXCOCTM

DXC9117E Invalid terminal address

ExplanationThe terminal address provided for an X.25 ALCterminal or a TCP/IP MATIP terminal is invalid.


User responseProvide a valid terminal address in field CT1CTA in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9118E Invalid gateway TCP/IP address

ExplanationThe address of the remote TCP/IP gateway to whichthis TCP/IP ALC terminal is attached is invalid.


User responseSet the correct gateway TCP/IP address in fieldCT1RHT in the Communication Resource DefinitionDSECT (CT1TM).

ModuleDXCOCTM

DXC9119E Output message translationincorrectly defined

ExplanationThe output message translation option has beenincorrectly specified for this X.25 or TCP/IP ALCterminal.



User responseSet the correct symbol for the message translationoption in field CT1CDE in the Communication ResourceDefinition DSECT (CT1TM).

ModuleDXCOCTM

DXC9120E Logon option and test option cannot both be defined

ExplanationThe logon option (for SAF authorization checking) andthe test option (for the ALCS STV facility) have bothbeen requested for this communication resource. Onlyone of these options is permitted, not both.


User responseSet either the logon symbol or the test symbol forthis communication resource in field CT1FLA in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9121E Other system communicationidentifier is invalid

ExplanationThe system communication ID of the other system thatowns this OSYS Other System terminal is invalid.


User responseProvide a system communication ID that is analphabetic character A through Z in field CT1COMin the Communication Resource Definition DSECT(CT1TM).

ModuleDXCOCTM

DXC9122E Invalid default user-ID

ExplanationThe default user ID (used for SAF authorizationchecking) provided for this communications resourceis invalid


User responseProvide a valid default user ID in field CT1UID in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9123E Invalid printer buffer size

ExplanationThe printer buffer size provided for this ALC printer isinvalid. Alternatively, a buffer size has been defined fora display terminal.


User responseDefine a printer buffer size between 0 and 4000in field CT1BUF in the Communication ResourceDefinition DSECT (CT1TM). Alternatively, if thiscommunication resource is a display terminal, theprinter buffer size must be defined as hexadecimalzero in field CT1BUF in CT1TM.

ModuleDXCOCTM

DXC9124E Invalid communications resourcetype

ExplanationThe name of the communications resource type forthis communication resource is invalid.



User responseSelect one of the 8 valid communication resourcetypes and define its name in field CT1TYP in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9125E Owning ALCI LU is invalid

ExplanationThe name of the ALCI Logical Unit (LDTYPE=VTAMALC)through which ALCS accesses this ALC terminal isunknown to ALCS.


User responseEnsure that the ALCI LU has been defined in the ALCScommunications generation and correct the name ofthe ALCI LU in field CT1NEF in the CommunicationResource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9126E Owning X.25 PVC is invalid

ExplanationThe name of the X.25 PVC (LDTYPE=X25PVC) throughwhich ALCS accesses this X.25 ALC terminal isunknown to ALCS.


User responseEnsure that the X.25 PVC has been defined in theOCTM database and correct the name of the owningX.25 PVC in field CT1PVC in the CommunicationResource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9127E Owning MQ/WAS is invalid

ExplanationThe name of the MQ queue resource (LDTYPE=MQ)or WAS resource (LDTYPE=WAS) through which ALCSaccesses this MQ terminal or WAS terminal is unknownto ALCS.

System actionALCS does not take action on this change request.

User responseEnsure that the MQ queue resource or theWAS resource has been defined in the ALCScommunications generation and correct the nameof the owning MQ queue in field CT1MQL or thename of the owning WAS resource in CT1WSL in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9128E Owning TCP/IP connection isinvalid

ExplanationThe name of the TCP/IP server connection(LDTYPE=TCPIP) through which ALCS accesses thisTCP/IP terminal is unknown to ALCS.


User responseEnsure that the TCP/IP server connection has beendefined in the ALCS communications generation andcorrect the name of the TCP/IP connection in fieldCT1TCL in the Communication Resource DefinitionDSECT (CT1TM).

ModuleDXCOCTM

DXC9129E Screen size incorrectly defined forprinter

ExplanationA screen size has been defined for printer terminal.



User responseIf this communication resource has been correctlydefined as a printer terminal, then the screen sizemust be hexadecimal zero in field CT1SCR in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9130E Logon option and default user-IDcan not both be defined

ExplanationThe logon option (for SAF authorization checking)and a default user ID have both been defined forthis communication resource. Only one of these ispermitted, not both.


User responseSet either the logon symbol for this communicationresource in field CT1FLA or provide a default userID in field CT1UID in the Communication ResourceDefinition DSECT (CT1TM).

ModuleDXCOCTM

DXC9131E Owning TCP/IP connection is not aserver

ExplanationThe TCP/IP connection (LDTYPE=TCPIP) throughwhich ALCS accesses this TCP/IP terminal is not aTCP/IP server connection.


User responseIdentify the TCP/IP server connection that owns thisTCP/IP terminal and put the name of that serverconnection in field CT1TCL in the CommunicationResource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9133E CRN for X.25 terminal containsinvalid IA or TA

ExplanationThe communications resource name (CRN) for theX.25 ALC terminal is comprised of a base CRN plusup to two addresses (a terminal address and aninterchange address). One or both of those addressesare invalid.


User responseVerify that the Interchange address defined in fieldCM1CIA and the terminal address defined in fieldCT1CTA (in the Communication Resource DefinitionDSECT (CT1TM)) are the same as the interchange andterminal addresses in the CRN.

ModuleDXCOCTM

DXC9134E Invalid timeout value for printeranswerbacks

ExplanationThe printer answerback timeout value is too high.


User responseVerify that the timeout value for printer answerbacksfor this ALC printer has been defined at a valuebetween 0 and 300 in field CT1TMO in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9135E Invalid timeout value for testmessage transmission interval

ExplanationThe printer test message transmission interval is toohigh.



User responseVerify that the timeout value for the test messagetransmission interval for this ALC printer has beendefined at a value between 0 and 910 in field CT1TMOin the Communication Resource Definition DSECT(CT1TM).

ModuleDXCOCTM

DXC9136E Invalid timeout value for recoveryretry count

ExplanationThe printer recovery retry count is too high.


User responseVerify that the timeout value for the recovery retrycount for this ALC printer has been defined at a

value between 0 and 30 in field CT1TMO in theCommunication Resource Definition DSECT (CT1TM).

ModuleDXCOCTM

DXC9137E Inhibiting Scrolling is not allowed

ExplanationInhibiting scrolling is not allowed for this resourcetype.


User responseCorrect the CT1TM.

ModuleDXCOCTM


Chapter 13. System error codes: 000000-000FFF

000000 ZDUMP message

ExplanationA manual dump was requested by entering the ZDUMPcommand. The message is a copy of the data enteredwith the ZDUMP command.


ModuleDXCCOMP, DXCOMR, DXCCOMT

000001 PROGRAM EXCEPTION IN ONLINEMONITOR

ExplanationThere was a program exception while the ALCS onlinemonitor was executing.

System actionIf there is an active entry, then ALCS terminates it andcontinues. If there is no active entry, then ALCS endsabnormally.

Operator responseIf ALCS goes catastrophic then activate the alternateALCS if there is one, or restart ALCS. If this is anisolated instance, follow your normal procedure for anon-urgent problem. If it happens repeatedly, informyour system programmer.

System programmer responseIf an application program did not cause the systemerror then inform your IBM programming supportrepresentative.

Problem determinationALCS diagnostic file processor prints the type ofprogram interruption in the system error dump header.If there is an active entry then it is possible thatan application programming error caused the systemerror. The system error dump contains informationabout the active entry (for example, the ECB). Use

this information to check, for example, if an ECB-controlled program issued a monitor-request macrowith incorrect register contents.

ModuleAny ALCS online monitor module.

000003 PROGRAM EXCEPTION INAPPLICATION PGM program_name

ExplanationThere was a program exception while an ALCSapplication program was executing.


Problem determinationALCS diagnostic file processor prints the type ofprogram interruption in the system error dump header.

ModuleAny ECB-controlled program.

000004 NO BASE REGISTER FOR ERRORRETURN

ExplanationAn ALCS online monitor routine requested a systemerror dump. The system error routines could not returncontrol to the routine that requested the system errordump.


Operator responseActivate the alternate ALCS if there is one, or restartALCS. If this is an isolated instance, follow your normalprocedure for a non-urgent problem. If it happensrepeatedly, inform your system programmer.



ModuleDXCPCH

000005 INVALID MONITOR REQUESTCODE

ExplanationAn ECB-controlled program issued a monitor-requestmacro linkage instruction, BRANCH AND SAVE ANDSET MODE (BASSM), but the 2 bytes following theBASSM did not contain a valid monitor request code.


User responseCheck if the application program issued a monitor-request macro for a user-written monitor service. If so,check that the installation-wide exit routine correctlyimplements the service.

ModuleDXCNUC

000006 STORAGE LEVEL ALREADY IN USE

ExplanationAn ECB-controlled program issued a GETCC or impliedget storage monitor-request macro with a storageblock already attached at the ECB or DECB storagelevel.


Programmer responseCorrect the programming error.

ModuleDXCSTM, DXCHLD

000007 STORAGE LEVEL NOT IN USE

ExplanationAn ECB-controlled program issued a RELCC or impliedrelease storage monitor-request macro with no blockattached at the ECB or DECB storage level.



ModuleDXCSTM

000008 RECORD(S) HELD AT EXIT

ExplanationAn ECB-controlled program issued an EXITC monitor-request macro with one or more records held.

System actionALCS unholds the records before it terminates theentry.


ModuleDXCVFA

000009 RELEASE STORAGE ERROR - SUSTORAGE CONTROL CORRUPTED

ExplanationDuring release storage processing ALCS detectedcorruption of fields it uses to manage storage for theentry. This is most likely caused by the applicationworking through data and stepping outside a storageblock. General register 14 points to the area wherecorruption was observed.



Chapter 13. System error codes: 000000-000FFF 303

ModuleDXCSTM

00000A INVALID ECB I/O COUNT

ExplanationThe ALCS online monitor detected that the ECB I/Ocounter for an entry was invalid.




ModuleDXCNUC

00000B INVALID LEVEL REFERENCE

ExplanationAn ECB-controlled program issued a monitor-requestmacro that specified an ECB or DECB storage level ordata level, but the level reference was invalid. ValidECB level references are D0 (value 0), D1 (value 8),and so on up to DF (value decimal 120).



ModuleDXCSTM, DXCVFM

00000C CORRUPTED ECB ADDRESS

ExplanationAn ECB-controlled program issued a monitor-requestmacro, but the ECB base register, general register 9(REB), did not contain the ECB address.



ModuleDXCNUC

00000D INVALID RELEASE STORAGEBLOCK variable

ExplanationAn ECB-controlled program issued a RELCC or impliedrelease storage monitor-request macro, but the blockaddress or type was invalid. Variable is eitherADDRESS or TYPE.



ModuleDXCSTM

00000E FLIPC - INVALID LEVELREFERENCE

ExplanationAn ECB-controlled program issued a FLIPC monitor-request macro. One or both of the level referenceswas invalid. Valid level references are D0 (value 0), D1(value 8), and so on up to DF (value decimal 120).



ModuleDXCSTG

00000F ENTRY LIFE LIMIT EXCEEDED


ExplanationThe entry exceeded its maximum entry life. The ALCSgeneration specifies two entry life limits; the entry canuse the SLIMC monitor-request macro to reset one,but the other is fixed. This error occurs if the entryexceeds either limit.


Programmer responseIf the entry exceeded the limit that SLIMC can reset,and if the entry genuinely needs to execute for avery long time, then include a SLIMC monitor-requestmacro in the application to increase the entry life limitfor this type of entry.

ModuleDXCTIR

000010 APPLICATION LOOP TIMEOUT

ExplanationAn application program executed too manyinstructions without releasing control. ALCS detectsthis when an application program executes for morethan a certain amount of time without releasingcontrol. The amount of time depends on the processor.


Programmer responseIf the application program genuinely needs to executea very large number of instructions, include DEFRCor DLAYC monitor-request macros to ensure that theentry loses control.

ModuleDXCTIR

000011 ABEND OTHER THAN PROGRAMEXCEPTION FROM MVS

ExplanationMVS ABEND that is not a program exception.



System programmer responseCheck the ALCS job log for any other messagesassociated with this error. If associated with HLLprograms check that sufficient secondary storage isdefined in the SCTGEN and that DXCHLIB specifies thecorrect LE runtime library.

If the problem is associated with HLL programs andthe problem can be recreated then use conversationaltrace to trace the macros called by the HLL programand determine where the error occurs. Tracing isdescribed in ALCS Operation and Maintenance.

Problem determinationALCS diagnostic file processor prints either the systemcompletion code or the user completion code, as wellas the hexadecimal reason code in the system errordump header.

MVS System Codes lists MVS system completioncodes and reason codes. User completion codes andreason codes appear in documents for the component,subsystem, or product that issues the codes.

The system error dump also includes the systemdiagnostic work area (SDWA). The SDWA containsinformation that can help problem determination; MVSDiagnosis: Data Areas describes the SDWA.

If the ALCS diagnostic file processor does not printa completion code and message then the abend is aUser Abend and the System Code is 000000.

If the program being executed is a HighLevel Language (HLL) program refer to LanguageEnvironment® Debugging and Run-Time MessagesGuide for the meaning of the user completion code. ACTL-000011 can occur if you attempt to execute a HLLprogram and no secondary storage units are availableor if the LE runtime library is not specified in the ALCSJCL deck (or ISPF panel) as ddname DXCHLIB.


ModuleAny ALCS online monitor module or any ECB-controlled program.

000012 EXCEPTION DUMP TABLE -SYSTEM ERROR

ExplanationAn internal ALCS error occurred during processing of aZASER or ZDSER command.



ModuleCVCH

000013 ENTRY SERRC LIMIT EXCEEDED

ExplanationAn ECB-controlled program issued a SERRC, SYSRA,or CPDMP monitor-request macro that exceeded theentry system error limit. The ALCS generation specifiestwo entry system error limits; the entry can use theSLIMC monitor-request macro to reset one, but theother is fixed. This error occurs if the entry exceedseither limit.


Programmer responseIf the entry exceeded the limit that SLIMC canreset, and if the entry genuinely needs to generate alarge number of system errors, then include a SLIMCmonitor-request macro in the application to increasethe entry system error limit for this type of entry.

ModuleDXCPCH

000014 PURGC - NOT FROM ZASYS ECB

ExplanationAn ECB-controlled program issued a PURGC monitor-request macro, but the entry was not authorized to

issue PURGC. Only state change entries are authorizedto issue PURGC.




ModuleDXCPHM

000015 PURGC - INVALID PARAMETERS

ExplanationAn ECB-controlled program issued a PURGC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.




ModuleDXCPHM

000016 ENTRY ACTIVE DURING STATECHANGE

ExplanationThe entry was active when a state change to IDLE wasinitiated.



ModuleDXCNUC

000017 ENTRY PURGED BY REQUEST

ExplanationThe operator entered ZPURG to terminate the entry.

System actionALCS terminates the entry, and continues.

Operator responseInform the application owner that you purged theentry (and why).

ModuleDXCPHM

000018 TRACE ENTRY ACTIVE DURINGSTATE CHANGE

ExplanationThe entry was active when a state change to IDLE wasinitiated.


ModuleDXCGTF

000019 TRACE ENTRY PURGED BYREQUEST

ExplanationThe operator entered ZPURG to terminate the entry.

System actionALCS terminates the entry and continues.


ModuleDXCGTF

00001A CAN NOT LOG RECORD

ExplanationALCS was unable to write a record to the log.



ModuleDXCLOG

00001B ENTRY PURGED BY FORCEREQUEST

ExplanationThe operator entered ZPURG Force to terminate theentry.

System actionALCS terminates the entry, and continues. ALCS marksthe storage unit containing the ECB for the entry,together with any storage units that are chained fromit, as quarantined. This ensures that the storage unit(s)will not be dispensed again until ALCS is restarted.


ModuleDXCPHM

00001C CAN NOT LOG RECORD IN HALTSTATE

ExplanationALCS was unable to write a record to the ALCS updatelog file during termination.


System actionALCS continues with termination.

Note: This system error does not generate a systemerror dump.

ModuleDXCLOG

00001D INVALID ESTAE(S) REMOVED

ExplanationDuring EXITC processing, ALCS detected one or moreinvalid ESTAEs (z/OS Extended Specify Task AbnormalExit). Those ESTAEs were removed by ALCS. Generalregister 3 (RGB) contains the address of the invalidESTAE. This system error is generated when the eventoccurs for the first time; it is not generated when theevent recurs, until the next ALCS restart.

System actionALCS continues with EXITC processing.

Note: This system error does not generate a systemerror dump.


ModuleDXCPGM

00001F Input list shut for too long

ExplanationThe Input list has been shut for too long. The ALCSdispatcher threshold has been reached.


System programmer responseInvestigate the reason why the input list has been shutfor too long.

ModuleDXCTIR

000020 macro - INVALID ACTION CODE

ExplanationAn ECB-controlled program issued a macro monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid. macro is one of:

RAISC - the macro issued is RAISA, GDSNC, orGDSRCRIDICRONIC


User responseCheck if the application program issued a monitor-request macro for a user-written monitor service.If so, check that the installation-wide exit routinecorrectly implements the service. If an IBM-suppliedmacro generated the incorrect monitor-request macrolinkage then ask your system programmer to informyour IBM programming support representative.

ModuleDXCFAR

000021 RIDIC - INVALID AREA CODE

ExplanationAn ECB-controlled program issued a RIDIC monitor-request macro with an invalid area code.


User responseCheck if the application program issued a monitor-request macro for a user-written monitor service.If so, check that the installation-wide exit routinecorrectly implements the service. If an IBM-suppliedmacro generated the incorrect monitor-request macrolinkage then ask your system programmer to informyour IBM programming support representative.

ModuleDXCFAR

000022 FIND - BLOCK ALREADYATTACHED


ExplanationAn ECB-controlled program issued a find-typemonitor-request macro with a storage block alreadyattached at the storage level.



ModuleDXCVFM

000023 FILE - NO BLOCK ATTACHED

ExplanationAn ECB-controlled program issued a file-type monitor-request macro with no storage block attached at thestorage level.



ModuleDXCVFM

000024 macro - FILE ADDRESS NOT HELD

ExplanationAn ECB-controlled program issued a FILUC (unholdfile address) or an UNFRC (request unhold file address)monitor-request macro, but the file address was notheld.



ModuleDXCVFM

000025 FIND - DATA LEVEL CORRUPTEDAT COMPLETION

ExplanationThe storage level was corrupted between the time thatan ECB-controlled program issued a find-type monitor-request macro and the time that the I/O completed.



ModuleDXCVFP

000026 VFA - NO BUFFER AVAILABLE

ExplanationALCS cannot obtain a VFA buffer.



Problem determinationCheck the system error dump to see why the VFAbuffers are in use. The shortage of buffers can indicate,for example:

• The ALCS generation did not specify enough buffers.• The ALCS generation specified entry write limits that

are too high. This can allow entries to request I/Ofaster that the DASDs can respond.

• A DASD is not working correctly, or requires toomany error recovery retries.

• An exceptional amount or type of work requires extrabuffers.

ModuleDXCVFB

000027 VFA LOGIC ERROR - reason


ExplanationThere is an internal logic error in an ALCS routine. Theerror is in the online monitor VFA routines. Reason isone of:

BAD F.A. IN VFAGETB ( F.A. = "file address")IOCB REQUEST INVALID ( IOCB = "I/O controlblock")LOCKS HELD ON RETURNNO OVERFLOW RLT ITEM AVAILABLE ( RLT ="record locator table")BAD RLT UNLOCKBAD AGE LIST UNLOCKSTAGING BUFFER ERRORTABLES CORRUPTED




ModuleDXCVFA, DXCVFB, DXCVFP

000028 FILE - RECORD HELD BY ANOTHERENTRY

ExplanationAn ECB-controlled program issued a file-type monitor-request macro, but another entry was holding thefile address. Application programs use record holdto ensure consistent updates when several entriescan update the same record at the same time. Thiserror occurs because two (or more) entries are usingrecord hold inconsistently; one entry holds the recordto prevent parallel updates but the other entry updates(files) the record without holding it.



Problem determinationThe system error dump includes two system errordump areas. Area 1 contains the VFA buffer headerfor the record held. Area 2 contains information aboutthe entry that was holding the record (block descriptor,ECB descriptor, ECB prefix, and ECB).

ModuleDXCVFM

000029 ECB LEVEL ERROR - I/O INPROGRESS

ExplanationAn ECB-controlled program issued a monitor-requestmacro which attempted to use a level on which I/O isin progress.



ModuleDXCGTC, DXCSTG, DXCSTM, DXCVFM

00002A ID CHANGE NOT ALLOWED BYEXIT

ExplanationAn ECB-controlled program issued a file-type monitor-request macro, for a long-term pool record. The recordID and the record code check is different from thepreviously filed copy of the record. The USRPIDCinstallation-wide exit has been invoked, and the IDchange is not allowed.




ModuleDXCGFE

00002B FLNPC -- RESTORE NOTAUTHORIZED

ExplanationAn ECB-controlled program issued an FLNPCTYPE=RESTORE monitor-request macro, but eitherRestore is not running or the originating entry was notthe Prime CRAS.



Programmer responseThis monitor-request macro is not intended to becalled by user-written programs. If you have calledit, replace the call; otherwise inform your systemprogrammer.

ModuleDXCVFA

00002C FIND -- ECB HOLD COUNT LIMITEXCEEDED

ExplanationAn ECB-controlled program issued a find and holdmonitor-request macro, but the record hold count forthe entry was already at the maximum allowed. TheALCS generation specifies two entry record hold countlimits; the entry can use the SLIMC monitor-requestmacro to reset one, but the other is fixed. The erroroccurs if the entry exceeds either limit.


Programmer responseIf the entry exceeded the limit that SLIMC can reset,and if the entry genuinely needs to hold a largenumber of records, then include a SLIMC monitor-request macro in the application to increase the recordhold count limit for this type of entry.

ModuleDXCVFM

00002D FILE - INVALID FILE ADDRESS -CLASS ERROR

ExplanationAn ECB-controlled program issued a file-type monitor-request macro, but the file address was invalid.



ModuleDXCVFM, DXCVFP

00002E FILE - RECORD ID ERROR

ExplanationAn ECB-controlled program issued a file-type monitor-request macro, but the record identifier (ID) in the datalevel was not the same as the record ID in the storageblock.



ModuleDXCVFM

00002F FILE - RCC ERROR

ExplanationAn ECB-controlled program issued a file-type monitor-request macro, but the record code check (RCC) in thedata level was not the same as the RCC in the storageblock.




ModuleDXCVFM

000031 DATABASE UNUSABLE - TOOMANY I/O ERRORS

ExplanationToo many consecutive I/O errors have occurred on theonly copy of an ALCS data set.



Problem determinationCheck the RO CRAS message, the EREP listing, and theMVS SYSLOG for more information about the error.

ModuleDXCDAI

000032 FILE - WRONG BLOCK SIZE

ExplanationAn ECB-controlled program issued a file-type monitor-request macro, but the size of the storage block wasnot the same as the size of the DASD record.



ModuleDXCVFM

000033 UNABLE TO BUILD SYSTEM ERRORDUMP AREA

ExplanationALCS was unable to build the system error dump areathat was intended to be included in a system errordump.

System actionThe system error dump area is omitted from thesystem error dump. ALCS continues processingnormally.


ModuleDXCVFM

00003D NO STAGING BUFFERS

ExplanationALCS does not have enough resources to write to thetest data set.


System programmer responseThis condition should not occur. If it does, inform yourIBM programming support representative.

ModuleDXCTDB

00003E TEST DATABASE PUT FAILURE

ExplanationAn error occurred when ALCS was writing to the testdata set.

System actionALCS issues message DXC179T and ends abnormally.Note that the user completion code associated withthis system error is 0003 indicating a double nestederror. This is because ALCS attempts to write to thetest data set during termination.

Problem determinationRefer to message DXC179T.


ModuleDXCTDB

00003F TEST DATABASE OPEN FAILURE

ExplanationAn error occurred when ALCS was opening the testdata set.

System actionALCS issues message DXC180T and ends abnormally.

Problem determinationRefer to message DXC180T ( “DXC180T” on page 25).

ModuleDXCTDB

000040 SEQUENTIAL FILE NOT DEFINED

ExplanationAn ECB-controlled program issued a sequential filemonitor-request macro, but the sequential file was notdefined in the ALCS sequential file generation.



ModuleDXCSEQM

000041 SEQUENTIAL FILE NOT GENERAL

ExplanationAn ECB-controlled program issued a generalsequential file monitor-request macro, but thesequential file was defined in the ALCS sequential filegeneration as a real-time or system sequential file.



ModuleDXCSEQM

000042 SEQUENTIAL FILE NOT REAL-TIME

ExplanationAn ECB-controlled program issued a real-timesequential file monitor-request macro, but thesequential file was defined in the ALCS sequential filegeneration as a general or system sequential file.



ModuleDXCSEQM

000043 SEQUENTIAL FILE NOT ASSIGNEDTO ENTRY

ExplanationAn ECB-controlled program issued a generalsequential file monitor-request macro, but thesequential file was not assigned to the entry.



ModuleDXCSEQM

000044 TASNC - SEQ FILE ALREADYASSIGNED TO ENTRY

ExplanationAn ECB-controlled program issued a TASNC monitor-request macro, but the sequential file was alreadyassigned to the entry.




ModuleDXCSEQM

000045 TASNC - SEQUENTIAL FILE NOTOPEN

ExplanationAn ECB-controlled program issued a TASNC monitor-request macro, but the sequential file was not open.



ModuleDXCSEQM

000046 TOPNC - SEQUENTIAL FILEALREADY OPEN

ExplanationAn ECB-controlled program issued a TOPNC monitor-request macro, but the sequential file was alreadyopen.



ModuleDXCSEQM

000047 SEQUENTIAL FILE OUTPUT ONLY

ExplanationAn application program attempted to open asequential file for input or to read from a sequentialfile, but the sequential file was defined in the ALCSsequential file generation as an output sequential file.



ModuleDXCSEQM

000048 SEQUENTIAL FILE INPUT ONLY

ExplanationAn application program attempted to open asequential file for output or to write to a sequentialfile, but the sequential file was defined in the ALCSsequential file generation as an input sequential file.



ModuleDXCSEQM

000049 TSQCC - ENTRY NOT AUTHORIZED

ExplanationAn ECB-controlled program issued a TSQCC monitor-request macro, but the entry was not authorized toissue TSQCC. Only entries that originate from PrimeCRAS input messages are authorized to issue TSQCC.





ModuleDXCSEQM

00004A TCLSC - ENTRIES WAITING TOASSIGN FILE

ExplanationAn ECB-controlled program issued a TCLSC monitor-request macro, but other entries were waiting toassign the sequential file.

System actionALCS terminates the entries that are waiting to assignthe sequential file.


ModuleDXCSEQM

00004B INVALID DATA LEVEL

ExplanationAn ECB-controlled program issued a sequential filemonitor-request macro that specified an invalid ECBlevel. Valid level references are D0 (value 0), D1 (value8), and so on up to DF (value decimal 120).



ModuleDXCSEQM

00004C TDTAC - INVALID OPERATIONCODE

ExplanationAn ECB-controlled program issued a TDTAC monitor-request macro, but the data level contained a channelcommand word ( CCW ) with an unsupported operationcode. ALCS TDTAC only supports operation codeshexadecimal 01 (write) and 02 (read).



ModuleDXCSEQM

00004D INVALID DATA ADDRESS ORLENGTH

ExplanationAn ECB-controlled program issued a sequential filemonitor-request macro. The storage address andlength for the data specified a storage area that theapplication program does not have write (store) accessto.



ModuleDXCSEQM

00004E TWRTC - UNRECOVERABLE WRITEERROR

ExplanationAn ECB-controlled program issued a TWRTC monitor-request macro. An unrecoverable I/O error occurredduring the write.


Problem determinationCheck the EREP listing for more information about theI/O error, and if necessary get the unit serviced.

ModuleDXCSEQT

00004F SEQUENTIAL FILE ASSIGNED ATEXIT


ExplanationAn ECB-controlled program issued an EXITC monitor-request macro with one or more sequential files stillassigned to the entry.

System actionALCS closes the sequential files.


ModuleDXCSEQR

000050 TOPNC - ERROR DURING OPEN

ExplanationAn ECB-controlled program issued a TOPNC monitor-request macro, but ALCS could not allocate or openthe data set. This error can occur if the definition of thesequential file is wrong; for example, if the specifieddata set name is not on the specified volume.


Problem determinationGeneral register 15 (RDB) contains a type code in byte1 and a return code in bytes 2 and 3. The meaning ofthe return code depends on the type code as follows:

TypeMeaning of Return Code

01Error return from MVS SVC 99 Function (DYNALLOCmacro). The return code is the SVC 99 error reasoncode.

MVS Authorized Assembler Services Guidedescribes these error reason codes. For someerror reason codes there is also an informationreason code. General register 14 (RDA) containsthis information reason code.

02Error return from MVS GETMAIN macro. ALCS wasunable to obtain storage for I/O buffers for thedata set. The return code is the contents of generalregister 15 on return from GETMAIN.


03Error return from MVS PGSER macro. ALCS wasunable to page fix the I/O buffers for the data set.The return code is the contents of general register15 on return from PGSER.


04Error return from MVS OPEN macro. ALCS wasunable to open the data set. The return code iszero (there is no return code from OPEN).

05System ABEND. The ALCS subtask that allocatesand opens the data sets ended abnormally. Thereturn code is the system completion code.

MVS System Codes describes system completioncodes.

06User ABEND. The ALCS subtask that allocates andopens the data sets ended abnormally. The returncode is the user completion code. This conditionshould not occur. If it does, ask your systemprogrammer to inform your IBM programmingsupport representative.

ModuleDXCSEQP

000051 SEQUENTIAL FILE SUBTASKABEND - SEQ FILE NAME-seq

ExplanationOne of the subtasks that ALCS attaches to processsequential files ended abnormally.

System actionIf the sequential file is a system or a real-timesequential file then ALCS switches the sequential fileto a new data set. If it is a general sequential file, thenALCS closes the sequential file; ALCS then terminatesany entry that attempts to use the sequential file (withsystem error number 000052).

Problem determinationAt the time of the system error dump, general register1 (RG1) contains the address of an ALCS I/O controlblock (IOCB). The IOCB contains information that canhelp to identify the error; in particular, fields tagged asfollows:

TagContents of Field


NMESymbolic name of sequential file (3 characters).

VSNVolume serial number of the volume that containsthe data set (6 characters).

DSNData set name (44 characters).

ABCCAbend completion code (4 bytes). This is thecontents of the MVS system diagnostic work area(SDWA) field SDWAABCC.

EC1Extended control program status word (PSW) atthe time of the abend (8 bytes). This is thecontents of the SDWA field SDWAEC1.

EC2Extended control PSW of the request block ( RB )that created the ESTAE exit at the time it lastincurred an interrupt (8 bytes). This is the contentsof the SDWA field SDWAEC2.

GRAC-GRDBGeneral registers corresponding to the PSW in EC1(4 bytes each). These are the contents of theSDWA fields SDWGR00-SDWAGR15.

SRAC-SRDBGeneral registers corresponding to the PSW in EC2(4 bytes each). These are the contents of theSDWA fields SDWSR00-SDWASR15.

MVS Diagnosis: Data Areas describes the contents ofSDWA fields in more detail.

ModuleDXCSEQP

000052 SEQUENTIAL FILE I/O ABEND

ExplanationA subtask that ALCS attached to process sequentialfiles for this entry ended abnormally (with system errornumber 000051).


Problem determinationSee the associated 000051 system error dump.

ModuleDXCSEQP

000053 NOT ENOUGH SPACE - SEQ FILESUBTASK ABEND

ExplanationOne of the subtasks that ALCS attaches to processsequential files ended abnormally. This is because alldata set secondary allocations have been used for asystem or real-time sequential file, but ALCS is stillunable to allocate a standby data set.

System actionIf the sequential file is a real-time sequential file thenALCS terminates the entry. If it is a system sequentialfile then ALCS ends abnormally.

ModuleDXCSEQM, DXCSEQS

000054 TOURC - NO BLOCK ATTACHED

ExplanationAn ECB-controlled program issued a TOURC with noblock attached at the level.



ModuleDXCSEQM

00005E BACKC - LOCAL SAVE STACKCORRUPTED

ExplanationThere is an internal logic error in an ALCS routineidentified while processing the BACKC macro. Thelocal save stack is corrupted.




User responseIf this is an isolated instance, follow your normalprocedure for a non-urgent problem. If it happensrepeatedly, inform your system programmer.

ModuleDXCPGM

00005F ENTRC - PROGRAM NEST LEVELCORRUPTED

ExplanationAn ECB-controlled program issued an enter/backmonitor-request macro, but the program enter nestlevel is invalid.


Programmer responseCheck if the application has corrupted this field. If not,then ask your system programmer to inform your IBMprogramming support representative.

Problem determinationThe program enter nest level is in the ECB prefix. Inthe system error dump, it is in the 4-byte field with thetag PNL.

ModuleDXCPGM

000060 ENTRC - PROGRAM NEST LEVELTOO HIGH

ExplanationAn ECB-controlled program issued an ENTRC monitor-request macro that exceeded the program enter nestlevel limit.


Programmer responseCheck if the application uses unnecessary ENTRCmonitor-request macros. ENTRC is unnecessary if thecalled program does not return control.

If the application uses unnecessary ENTRCs, replacethem with ENTNC or ENTDC monitor-request macros.

If only one program calls the called program, considermaking it a subroutine of the calling program.

ModuleDXCPGM

000061 PROGRAM program_name NOTFOUND

ExplanationAn ECB-controlled program issued an enter-typemonitor-request macro that specified a 4-characterprogram or transfer vector name that is not known ornot valid. Program_name is the 4-character program ortransfer vector name.


Operator responseIf this is an isolated instance, follow your normalprocedure for a non-urgent problem. If it happensrepeatedly, inform your system programmer.

System programmer responseCheck that the 4-character name is correct. If it is,then identify the application program load module thatcontains the program or transfer vector, and do one orboth of the following:

• Tell the operator the name of the load module. Theoperator can load it using the ZPCTL command.

• Update the program load list to include the module.ALCS loads these modules automatically at restart.

Programmer responseCorrect the program error.

ModuleDXCPGM

000062 FIPWC - PROGRAM TOO LONG

ExplanationAn ECB controlled program has issued a FIPWC macrocalling for a program to be moved to a block attachedto the ECB and the program size is too big to fit in thelargest block defined to the system.




System programmer responseIf it is not convenient to define a block size largeenough to contain the program to be moved, removethe FIPWC from the refer-from program or divide therefer-to program into smaller segments.

Programmer responseAlternatively, the application programmer can changethe program to use FINPC, which does not restrictprogram size.

Problem determinationThe system error dump contains the name of theprogram issuing the FIPWC and the name of theprogram being moved. General register 3 contains thesize of the program. General register 15 contains thesize of the largest block.

ModuleDXCPGM

000063 WASCC - ASYNC(1), SEC(1),TRANS(1) NOT SUPPORTED

ExplanationAn ECB-controlled program invoked an optimizedlocal adapter (OLA) callable service with an incorrectASYNC, SEC, or TRANS parameter value which ALCSdoes not support.



ModuleDXCWAS

000065 WAS SUBTASK ABEND

ExplanationOne of the subtasks that ALCS attaches to process anOLA callable service request ended abnormally.


Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. MVSSystem Codes lists abend codes. General register 1(RG1) points to a storage area containing the PSWand general registers at the time of the error. ThePSW is in an 8-byte field at displacement X'28' intothis storage area. The general registers, starting withgeneral register 0, are in 16 consecutive fullwords atdisplacement X'30' into this storage area.

ModuleDXCWAS

000066 WAS SUB TASK ABEND - ECBTERMINATED

ExplanationAn ECB-controlled program invoked an optimized localadapter (OLA) callable service but the subtask thatit was using ended abnormally. ALCS automaticallyreattaches the subtask.

One or more CTL-000066 system errors can resultfrom a ZCWAS DISC,F command because ALCSforcibly terminates the entries.



Problem determinationCheck that general register 1 (RG1) in the ECB'sregister save area points to a correct OLA parameterlist. Refer to system error 000065 for additionalinformation.

ModuleDXCWAS

000067 WASCC - INVALID PARAMETERLIST


ExplanationAn ECB-controlled program invoked an optimizedlocal adapter (OLA) callable service with an incorrectparameter list



Problem determinationCheck that general register 1 (RG1) in the ECB savearea points to the parameter list.

ModuleDXCWAS

000068 WASCC - TERMINATIONREQUESTED BY INST EXIT

ExplanationInstallation-wide monitor exit USRWAS1 determinedthat processing of this entry must be terminated.


User responseCheck that you are authorized to invoke OLA callableservices.

ModuleDXCWAS

000069 WASCC - INVALID REQUEST

ExplanationAn ECB-controlled program invoked an invalidoptimized local adapter (OLA) callable service.


System programmer responseThis error should not occur. If it does, inform your IBMprogramming support representative.

ModuleDXCWAS

00006A WAS DISCONNECT FAILURE

ExplanationDisconnecting ALCS from WAS failed.



ModuleDXCWAS

00006B WAS BRIDGE SUBTASK ABEND

ExplanationOne of the subtasks that ALCS attaches to process aWAS Bridge request ended abnormally.

System actionALCS inactivates the WAS resource.


Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. MVSSystem Codes lists abend codes. General register 1(RG1) points to a storage area containing the PSWand general registers at the time of the error. ThePSW is in an 8-byte field at displacement X'28' intothis storage area. The general registers, starting withgeneral register 0, are in 16 consecutive fullwords atdisplacement X'30' into this storage area.

ModuleDXCWAS

00006C WAS BRIDGE SUBTASK ABEND -ECB TERMINATED


ExplanationAn ECB-controlled program issued a ROUTC or SEND-type monitor-request macro to send a message toa WAS resource, but the subtask that it was usingabended abnormally. ALCS automatically reattachesthe subtask.



ModuleDXCWAS

000070 CREATE MACRO - INVALID DATA

ExplanationAn ECB-controlled program issued a create-typemonitor-request macro, but the parameter bytesfollowing the monitor-request macro linkageinstructions were not valid.


User responseIf an IBM-supplied macro generated the incorrectmonitor-request macro linkage then ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleDXCPGM

000071 CREATE MACRO - PROGRAMprogram_name NOT FOUND

ExplanationAn ECB-controlled program issued a create-typemonitor-request macro that specified an unknown orinvlaid 4-character program or transfer vector name.



System programmer responseCheck that the 4-character name is correct. If it is,then identify the application program load module thatcontains the program or transfer vector, and do one orboth of the following:

• Tell the operator the name of the load module. Theoperator can load it using the ZPCTL command.

• Update the program load list to include the module.ALCS loads these modules automatically at restart.

Programmer responseCorrect the program error.

ModuleDXCPGM

000073 CRET TABLE FULL

ExplanationAn ECB-controlled program issued a CRETC monitor-request macro, or the monitor CRET list service routinewas executing. The ALCS CRET table is full (all theentries are in use).

System actionIn the case of an ECB-controlled program issuing aCRETC macro ALCS terminates the entry, otherwisethe CRET list service routine does not add a new itemto the CRET list.

Problem determinationCheck the system error dump to see why the CRETtable entries are in use. The shortage of entries canindicate, for example:

• The ALCS generation did not specify enough CRETtable entries.

• An application programming error caused theapplication to issue excessive CRETCs.

• An exceptional amount or type of work requires extraCRET table entries.

ModuleDXCTIM, DXCTIR


000075 TIMEC - message

ExplanationAn ECB-controlled program issued a TIMEC monitor-request macro, but depending on message:

ENTRY NOT AUTHORIZED FOR ADD/SETThe entry was not authorized to change the ALCStime. Only entries that originate from Prime CRASinput messages are authorized to change the time.This option of the TIMEC macro is not intended foruser-written programs.

INVALID ACTION CODEThe parameter bytes following the monitor-request macro linkage instructions were not valid.

INVALID VALUE CODEThe parameter bytes following the monitor-request macro linkage instructions were not valid.



ModuleDXCTIM

000076 APPC - NO SRB AVAILABLE

ExplanationNo MVS service request block ( SRB ) was available toAdvanced Program-to-Program Communications/MVS(APPC/MVS).



ModuleDXCCOLF

000077 APPC - NO IOCB AVAILABLE

ExplanationAn ECB-controlled program issued a call toAdvanced Program-to-Program Communications/MVS(APPC/MVS), but no I/O control block (IOCB) wasavailable.


System programmer responseCheck the system error dump to see why the IOCBsare in use. The shortage of IOCBs can indicate, forexample:

• The ALCS generation specified entry write limits thatare too high. This can allow entries to request I/Ofaster that the I/O devices can respond.

• An I/O device is not working correctly, or requirestoo many error recovery retries.

• An exceptional amount or type of work requires extraIOCBs.

• The ALCS generation did not specify enough IOCBs.

ModuleDXCCOLF

000078 APPC - LOGIC ERROR

ExplanationThere is an internal logic error in an ALCSroutine. (This involves Advanced Program-to-ProgramCommunications/MVS (APPC/MVS).)




ModuleDXCCOLF


000079 COMMUNICATION TABLECORRUPTED

ExplanationThe ALCS communication routines detected acorruption of one of the communication tables.


System programmer responseCheck that the error is not caused by user-writtencode being executed in installation-wide exits or inuser modifications. If the error is in ALCS, inform yourIBM programming support representative.

Problem determinationRegister R14 contains the CRI of the invalidcommunication table (DXCREI) entry. Register R15contains either 4 (corruption detected by ALCS logonroutine) or 8 (corruption detected by ALCS simlogonroutine).

ModuleDXCCOME

00007A APPC - INVALID PARAMETERS

ExplanationAn SAA Common Programming Interface -Communications (CPI-C) or Advanced Program-to-Program Communications/MVS (APPC/MVS) callparameter is invalid.

System actionALCS terminates the entry. General register 1 is savedin the ECB register save area.

User responseCorrect your application program. Either one of theparameters in the parameter list is invalid, or noconversation existed for this CPI-C or APPC/MVS call,with the result that all parameters are invalid.

Problem determinationCheck the CPI-C or APPC/MVS parameters used in thiscall. (General register 1 in the ECB save area points tothe parameter list.)

ModuleDXCCOLF

00007B APPC/MVS NOT SUPPORTED

ExplanationAdvanced Program-to-Program Communications/MVS(APPC/MVS) support is not available for one of thefollowing reasons:

• This ALCS does not support APPC/MVS.• The z/OS release does not support APPC/MVS.• Either error DXC090E ( “DXC090E” on page 12),

DXC091E ( “DXC091E” on page 13), or DXC092E( “DXC092E” on page 13) occurred.

• APPCPMxx parmlib member is incorrect, resulting inmessage DXC093W ( “DXC093W” on page 13),


User response• Refer to ALCS Installation and Customization on how

to specify APPC/MVS support.• Check that the installed level of z/OS supports APPC/

MVS.• Check the MVS console for error messages.• Check and correct your APPCPMxx member, if

necessary.

Check the MVS console for error messages. Check thatthe installed level of MVS supports APPC/MVS. Checkand correct your APPCPMxx member, if necessary.

ModuleDXCCOLF

00007D APPC - TERMINATIONREQUESTED BY INST EXIT

ExplanationThe ALCS Advanced Program-to-ProgramCommunications/MVS (APPC/MVS) installation-wideexit determined that processing of this entry must beterminated.



User responseCheck authorization of the user.

ModuleDXCCOLF

00007E APPC - CPI-C OR APPC CALLABEND

ExplanationThe ALCS routine executing the SAA CommonProgramming Interface - Communications (CPI-C) orAdvanced Program-to-Program Communications/MVS(APPC/MVS) call ended abnormally.

System actionALCS terminates the entry. General register 1 issaved in the ECB register save area. General register14 (RDA) contains the MVS service request block( SRB ) abend code in the form 00xxxyyy, where xxxis the System completion code and yyy is the Usercompletion code. (Also ALCS writes the completeSDWA to SYS1.LOGREC).

User responseCheck the parameters, and correct your applicationprogram.

Problem determinationCheck the CPI-C or APPC/MVS parameters used in thiscall. (General register 1 in the ECB register save areapoints to the parameter list.)

ModuleDXCCOLF

00007F APPC - SUBTASK ABEND

ExplanationThere is an internal logic error in the ALCSAdvanced Program-to-Program Communications/MVS(APPC/MVS) subtask inhibiting any further APPC/MVSprocessing.

System actionALCS terminates the subtask. General register 14(RDA) contains the abend code in the form 00xxxyyy.Where xxx is the System completion code and yyy isthe User completion code.



ModuleDXCCOLF

000080 macro - NO BLOCK ATTACHED

ExplanationAn ECB-controlled program issued a ROUTC or send-type monitor-request macro, but either the storagelevel is invalid or there is no block attached on thestorage level. Macro is ROUTC or SEND.



ModuleDXCCOMQ, DXCSND, CPQS

000081 macro - MESSAGE TOO SHORT

ExplanationAn ECB-controlled program issued a ROUTC or send-type monitor-request macro, but the message is tooshort. That is, the character count in the messageblock is too small to contain any message data. macrois ROUTC or SEND.

System actionIf the message is to a WTTY link, then ALCS continuesprocessing normally. Otherwise ALCS terminates theentry.



ModuleDXCCOMQ, DXCSND, DXCCOLI

000082 macro - MESSAGE TOO LONG

ExplanationAn ECB-controlled program issued a ROUTC or send-type monitor-request macro, but the message is toolong. That is, the character count in the message blockis too large for the block to contain. Macro is SENDC orSEND.

System actionIf the message is to a WTTY resource thenALCS continues processing normally. Otherwise ALCSterminates the entry.


ModuleDXCCOMQ, DXCSND

000083 SEND - INVALID LINE NUMBER

ExplanationAn ECB-controlled program issued a WTTY monitor-request macro or a SENDC K monitor-request macro,but the line number does not exist.


User responseCheck that the resource is correctly specified in thecommunication generation.

ModuleDXCSND

000084 SEND - INVALID LINE TYPE

ExplanationAn ECB-controlled program issued a send-typemonitor-request macro, but one of the following errorshas occurred:

• For this send-type monitor-request macro thedestination must be a WTTY resource, but it was nota WTTY resource.

• For this send-type monitor-request macro thedestination must be an SLC link, but it was not anSLC link.

• The monitor-request macro was SENDC M, but thedestination was a printer.

• The monitor-request macro was SPOCC, but thedestination was a display.

• The monitor-request macro was POLLC, but thedestination was a WTTY resource that was not half-duplex.

• The monitor-request macro was SCDCC, STXTC, orSEOMC, but the destination was a simplex-in WTTYresource.



ModuleDXCSND

000085 SEND - INVALID TERMINALADDRESS

ExplanationAn ECB-controlled program issued a send-typemonitor-request macro, but one of the following istrue:

• The destination was not defined to ALCS.• The monitor-request macro was SENDC A or SENDCM, but the CRI was 000000 or 010000 through0100FF.



ModuleDXCSND

000086 SEND - NO EOM CHARACTER


ExplanationAn ECB-controlled program issued a send-typemonitor-request macro, but the message was notterminated by a valid end-of-message character.



ModuleDXCSND

000087 SEND - LINE TOO LONG FOR device

ExplanationThe destination was a 3270 device (DISPLAY orPRINTER), but the message contained a line longerthan the screen width.



ModuleDXCCOM3

000088 SEND - resource NOT AVAILABLE

ExplanationAn ECB-controlled program issued a send-type(resource = LU or TCP/IP CONNECTION) or SENDCK (resource = SLC LINK) monitor-request macro, butthe destination resource was not available.

System actionALCS detaches the message block from the ECB andreturns control to the entry.

User responseCheck the resource is correctly defined in thecommunication generation. Also check that allrequired communication resources are correctlystarted.

ModuleDXCSND, DXCCOMS

000089 macro - INVALID REFERENCEADDRESS

ExplanationAn ECB-controlled program issued either a REQSC oran SCDCC monitor-request macro but, depending onthe value of macro:

REQSCThe address of the program reference is invalid.

SCDCCThe address of the program reference is in storagethat the ECB-controlled program cannot accessread/write.




ModuleDXCSND

00008A SEND - LINE IN RECEIVE STATE

ExplanationAn ECB-controlled program issued an STXTC or SEOMCmonitor-request macro, but the destination resource(a WTTY link) was in receive state and not busy.





ModuleDXCSND

00008B SEND A/C/X - SEND TO PRINTERNOT SUPPORTED

ExplanationAn ECB-controlled program issued a SENDC A, orSENDC C, or SENDC X monitor-request macro, but thedestination resource was not a display.


User responseCheck that the resource is correctly defined in thecommunication generation.

ModuleDXCSND

00008C SENDC D - SEND TO device NOTSUPPORTED

ExplanationAn ECB-controlled program issued a SENDC Dmonitor-request macro to send a message to anunsupported device. Where device is:

PRC/ROCALCS does not allow SENDC D to send a messageto a device that has Prime or RO CRAS status.

ALC DEVICEALCS supports SENDC D (send direct) only for3270 devices. Use SENDC C instead of SENDC Dfor an ALC device.

OSYS DEVICEALCS does not allow SENDC D to send a messageto a communication device owned by anothersystem.



ModuleDXCSND

00008D SANSC - MACRO NOT SUPPORTED

ExplanationAn ECB-controlled program issued a SANSC monitor-request macro. ALCS does not support SANSC.



ModuleDXCSND

00008E EOM NOT LAST CHARACTER INMESSAGE BLOCK

ExplanationALCS detected an end-of-message characterimbedded in the text of a message received.


User responseIf this error occurs, ask your system programmerto inform your high-level-network supportrepresentative.

ModuleDXCCOMT

00008F ALCS PROGRAM ERROR OR NPSIGENERATION ERROR

ExplanationALCS received an invalid VTAM sense code on an X.25permanent virtual circuit (PVC).




ModuleDXCCOMX

000090 VTAM HALT OR ABEND - RESTARTVTAM

ExplanationVTAM operator has issued the HALT NET,QUICKcommand or VTAM has abended. This can also occur ifthe VTAM ACB has been inactivated.


Operator responseRestart VTAM, or activate the VTAM ACB . Thenactivate the alternate ALCS if there is one, or restartALCS.

ModuleDXCCOME

000091 COMMUNICATION LOGIC ERROR -routine

ExplanationThere is an internal logic error in an ALCS routine.Routine is the routine that contains the error, one of:

DELTERMRoutine that deletes communication resourcesfrom the ALCS communication tables.

ADDTERMRoutine that adds communication resources to theALCS communication tables.




ModuleDXCCOMV

000092 SEND - TOO MANY LINES

ExplanationThe destination was a 3270 display, but themessage contained data to display on unavailable ornonexistent lines (rows).



ModuleDXCCOM3

000093 CHAINED RU ERROR - TIMEOUT

ExplanationALCS is receiving a message from a VTAM resourcein two or more chained SNA request units (RUs). Theresource is a 3270-type terminal, an ALCI LU, or anX.25 permanent virtual circuit (PVC). After receiving achained RU, ALCS waits for another, using the intervalspecified on the COMGEN generation macro TIMEOUTparameter (first subparameter). ALCS did not receivethe next part of the message before the time intervalexpired.

System actionALCS discards the part of the message that has beenreceived.

User responseThis system error can occur if ALCS receives an RUchain containing too many RUs (see also system errornumber 000095); ALCS discards the first part of theRU chain and handles any remaining RUs as partof a new message. Otherwise, try to recreate theconditions that caused the system error and run aVTAM buffer trace to see the input message RUs.


ModuleDXCCOME

000094 CHAINED RU ERROR - ECB NOTFOUND

ExplanationALCS is receiving a message from a VTAM resourcein two or more chained SNA request units (RUs).The resource is a 3270-type terminal, an ALCI LU,or an X.25 permanent virtual circuit (PVC). For eachchained RU, ALCS uses an ECB to accumulate themessage data. The ECB address that was saved in thecommunication table entry for the VTAM resource wasunexpectedly zero.



ModuleDXCCOMR

000095 CHAINED RU ERROR - message

ExplanationALCS is receiving a message from a VTAM resourcein two or more chained SNA request units (RUs). Theresource is a 3270-type terminal, an ALCI LU, or anX.25 permanent virtual circuit (PVC). Message is oneof:

MORE THAN 16 RUSALCS accepts a maximum of 16 RUs in an input RUchain. in an input RU chain.

FIC ALREADY RECEIVEDALCS received two first-in-chain RUs apparently inthe same RU chain.

LIC ALREADY RECEIVEDALCS received two last-in-chain RUs apparently inthe same RU chain.

TOO MANY RUSThe SNA sequence numbers in the RU chainindicate that the chain is longer than 16 RUs.


User responseTry to recreate the conditions that caused the systemerror and run a VTAM buffer trace to see the inputmessage RUs.

ModuleDXCCOMR

000096 NO STORAGE - CRN-crn CRI-cri -action

ExplanationALCS is unable to obtain storage for a buffer.Depending on the value of action (SND or RCV), thebuffer is needed to send or receive data to or froma communication resource that has an LDTYPE ofALCSLINK.

System actionALCS takes a diagnostic system dump and continuesprocessing normally. No data is transmitted on theparallel session crn.

User responseRun ALCS in a region that has sufficient storageavailable.

ModuleDXCCOLB

000097 READ ERROR - CRN-crn CRI-cri

ExplanationALCS is unable to read a record from pool file.

System actionALCS takes a diagnostic system dump and continuesprocessing normally. No data is sent on the parallelsession crn.

User responseCheck if one of the following caused the error:

• User corruption of the message chain• Hardware error.


If not, then ask your system programmer to informyour IBM programming support representative.

ModuleDXCCOLB

000098 RECEIVE ERROR error_code - CRN-crn

ExplanationThe ALCS monitor has detected an error that preventsthe correct reception of data from a communicationresource that has an LDTYPE of ALCSLINK. Error_codespecifies the error:

0701ALCS is unable to obtain an L1 or L3 short-termpool record, because L1 or L3 records are notdefined to the system.

0702ALCS is unable to obtain an L1 or L3 short-termpool record, because there are no L1 or L3 short-term pool records available.

0703ALCS internal error.

0704ALCS internal error.

System actionALCS takes a diagnostic system dump and continuesprocessing normally.

User responseEnsure that sufficient L1 and L3 short-term poolrecords are generated and that sufficient L1 and L3VFA buffers are available.

In case of internal error, ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleDXCCOLB

000099 UNSUPPORTED RPL REQUESTRECEIVED

ExplanationLU 6.1 has received an unsupported VTAM requestparameter list ( RPL ) request unit control code.

System actionALCS takes a dump, ignores this RPL , and continuesprocessing.

User responseCheck what program sent the unsupported request. Ifit was an IBM program ( CICS® , ALCS, or IMS , forexample), then ask your system programmer to informyour IBM programming support representative.

ModuleDXCCOLB

00009A SPOCC - NO BLOCK ATTACHED

ExplanationAn ECB-controlled program issued a monitor-requestmacro to cause data to be transmitted on a link, butthere is no block attached on the storage level.




ModuleDXCCOLB

00009B SPOCC - INVALID LEVELREFERENCE

ExplanationAn ECB-controlled program issued a monitor-requestmacro to cause data to be transmitted on a link, butthe storage level is invalid.





ModuleDXCCOLB

00009C SPOCC - LINK NOT AVAILABLE

ExplanationAn ECB-controlled program issued a monitor-requestmacro to cause data to be transmitted, but theresource is not available.




ModuleDXCCOLB

00009D SPOCC - INVALID LINK CRI

ExplanationAn ECB-controlled program issued a monitor-requestmacro to cause data to be transmitted, but eitherthe CRI does not exist in this system or it doesnot specify a communication resource defined byLDTYPE=ALCSLINK.




ModuleDXCCOLB

00009E TPPCC - INVALID PARAMETERS

ExplanationTPPCC monitor-request macro parameter is invalid.



ModuleCLU6

00009F TPPCC - LEVEL DF IS NOT A TPPCCBLOCK

ExplanationAn ECB-controlled program issued a TPPCC monitor-request macro, but the storage block attached on levelDF was invalid.


User responseTPPCC monitor-request macro requires that level DFis not used by the application. Check and correct yourapplication program.

ModuleCLU6

0000A0 DASCC - ENTRY NOT AUTHORIZED


ExplanationAn ECB-controlled program issued a DASCC monitor-request macro, but the entry is not authorized toissue DASCC. Only entries that originate from PrimeCRAS input messages are authorized to issue DASCC(except that any entry is authorized to issue DASCCwith DISPLAY option).




ModuleDXCDAI

0000A1 DASCC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a DASCC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.




ModuleDXCDAI

0000B0 macro - POOL INACTIVE ORUNDEFINED

ExplanationAn ECB-controlled program issued a macro (GETFC orRELFC) monitor-request macro that specified a poolrecord type that was inactive or that did not exist. Poolrecord types are inactive during some ALCS systemfunctions, including restart.


Programmer responseCheck if the application program was executing whilethe pool record type was inactive. Check the ALCSDASD generation for a list of valid pool record types.

ModuleDXCGFS

0000B1 macro - INVALID LEVELREFERENCE

ExplanationAn ECB-controlled program issued a macro (GETFC orRELFC) monitor-request macro that specified storagelevel or data level. The level reference was invalid.Valid level references are D0 (value 0), D1 (value 8),and so on up to DF (value decimal 120).



ModuleDXCGFS

0000B2 GETFC - CAN NOT DETERMINERECORD SIZE

ExplanationAn ECB-controlled program issued a GETFC monitor-request macro that did not uniquely specify the recordsize. For example, the GETFC specified a recordidentifier (ID) that was defined for more than onerecord size.




ModuleDXCGFS

0000B3 RELFC - RELEASE CHAIN ITEMNOT ACCESSIBLE

ExplanationAn ECB-controlled program issued a RELFC with theCHNITEM parameter, but the address is in storage thatthe application program did not have read/write (store)access to.


Programmer responseThis parameter of the macro is not intended tobe called by user-written programs. If you havecalled it, replace the call; otherwise ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleDXCGFS

0000B4 RELFC - INVALID FILE ADDRESS

ExplanationAn ECB-controlled program issued a RELFC monitor-request macro, but the file address was invalid or wasnot a pool file address.

System actionALCS returns control to the program.

ModuleDXCGFS

0000B5 GETFC - type ENTRY LIMITEXCEEDED

ExplanationAn ECB-controlled program issued a GETFC monitor-request macro that exceeded the entry pool filedispense limit. type is one of

STThe short-term pool file dispense limit wasexceeded.

LTThe long-term pool file dispense limit wasexceeded.

The ALCS generation specifies two pool file dispenselimits, a maximum system limit and a default limit. Theentry can use the SLIMC monitor-request macro toreset one, but the other is fixed. This error occurs if theentry exceeds either limit.


Programmer responseIf the entry exceeded the limit that SLIMC can reset,and if the entry genuinely needs a large number ofpool file records, include a SLIMC monitor-requestmacro in the application to increase the pool filedispense limit for this type of entry.

ModuleDXCGFS

0000B6 LOGIC ERROR -- INVALID RETURNFROM MONFIND

ExplanationThere is an internal logic error in an ALCS poolmanagement routine.


Operator responseActivate the alternate ALCS if there is one, or restartALCS. If this is an isolated instance, follow your normalprocedure for a non-urgent problem. It happensrepeatedly, inform your system programmer.


ModuleDXCGFST

0000B7 PDU SUBTASK ABEND


ExplanationThe subtask that ALCS attaches to manage theemergency pool recovery (PDU) facility endedabnormally.

System actionALCS attaches the subtask again at the next request towrite to or read from the MVS log-stream.

Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code (4bytes). This is the contents of the MVS systemdiagnostic work area (SDWA) field SDWAABCC. MVSSystem Codes lists abend completion codes. At thetime of the system error dump, general register 15(RDB) contains the address of a field containing thecontents of the PSW (8 bytes) and general registers 0- 15 (64 bytes) at the time of the abend. These arethe contents of the MVS SDWA fields SDWAEC1 andSDWAGRSV.

ModuleDXCPDU

0000B8 POOL LOGIC ERROR - reason

ExplanationThere is an internal logic error in an ALCS poolmanagement routine. Reason is one of:

GFCINVALID F.A. IN GFEINVALID F.A. IN GFSINVALID PFDR F.A.ZPOOL

The reasons are only intended as pointers to help IBMidentify the cause of the problem.




ModuleDXCGFC, DXCGFE, DXCGFS, DXCGFD, DXCGFLT,DXCGFR, DXCGFST, DXCINTG

0000B9 LONG-TERM POOL EXHAUSTED -RUN RECOUP

ExplanationAn ECB-controlled program issued a GETFC monitor-request macro to obtain the address of a long-termpool record, but there are no records available for therequested pool type.


Operator responseRun Recoup.

System programmer responseCheck the ALCS DASD generation to ensure that theallocation for this pool type is adequate. If it is not,then run a new ALCS DASD generation to increase theallocation.

ModuleDXCGFD

0000BA GFSCC RECOUP,WRITEDIAG -error

ExplanationAn ECB-controlled program issued a GFSCC monitor-request macro with parameters RECOUP,WRITEDIAG,but there was an error, one of:

INVALID DATAStorage block did not contain a valid Recoup erroritem.

NO BLOCK ATTACHEDNo storage block attached at the specified level.





ModuleDXCGFC

0000BB GFSCC - reason

ExplanationAn ECB-controlled program issued a GFSCC monitor-request macro that caused an error. The reason wasone of:

INVALID LEVEL REFERENCEINVALID POOL IDINVALID REQUEST CODEINVALID WORK AREA ADDRESSNOT AUTHORIZED




ModuleDXCGFC

0000BC RLCHA - INVALID PARAMETERLIST

ExplanationAn ECB-controlled program issued a RLCHA monitor-request macro that specified a parameter list area instorage that the application program did not have read(fetch) access to.


ModuleDXCPGM

0000BD RLCHA - CONTROL RECORDACCESS ERROR

ExplanationALCS detected an error in the monitor find routinewhile processing a RLCHA monitor-request macro.



ModuleDXCPGM

0000BE CPDUC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a CPDUC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.




ModuleDXCPDU

0000BF CPDUC - INVALID POOL SIZE


ExplanationAn ECB-controlled program issued a CPDUC monitor-request macro with parameter SIZE that specified anundefined long-term pool size.




ModuleDXCPDU

0000C0 COMMUNICATION LOGIC ERROR

ExplanationThere is as internal logic error in an ALCS routine,during processing of a new input message.




ModuleDXCOPZ, DXCSAF

0000C1 COMCC -- UNABLE TO FORMATSCREEN

ExplanationAn ECB-controlled program issued a COMCCFORMAT=TOP macro to format a 3270 display screen,

but ALCS could not format the screen for one of thefollowing reasons:

no installation wide exit suppliedmore than 500 bytes of user text suppliedtoo many carriage returns in user textline length too long in user text



ModuleDXCCOM3

0000C3 HEAP STORAGE NOT AVAILABLE

ExplanationALCS could not obtain assembler heap storage duringinput message processing.


System programmer responseCheck that you have allocated enough type 3storage units using the SCTGEN NBRSU and SUSIZEparameters in your system configuration. Specify atype 3 storage unit size which is greater than or equalto the value of any COMDEF IPMGSZ values in yourcommunication generation plus 21 bytes (to allow fora message header). The number required will dependon factors such as the rate of large messages sent andreceived by your applications, and the existence timeof entries.

ModuleDXCOPZ, DXCCOMT, DXCSOCO

0000D3 KCTLC - SUBTASK TERMINATING -TRY AGAIN

ExplanationWhile processing a ZACOM command, ALCS found thatthe subtask that ALCS attaches to open and close SLCchannels is about to end.



Operator responseRetry the ZACOM OPEN or ZACOM CLOSE command.

ModuleDXCSLCCI

0000D4 SLC SUBTASK ABEND

ExplanationThe subtask that ALCS attaches to open and close SLCchannels ended abnormally.

System actionALCS terminates any entries that have outstandingopen or close requests for SLC channels. ALCSattaches the subtask again at the next request to openor close an SLC channel.

Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code (4bytes). This is the contents of the MVS systemdiagnostic work area (SDWA) field SDWAABCC.

ModuleDXCSLCCI

0000D5 macro - PROGRAM NOTAUTHORIZED

ExplanationAn unauthorized program issued a macro (KCTLC orPLONC) monitor-request macro.




ModuleDXCSLCCI

0000D6 macro - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a macro (KCTLCor PLONC) monitor-request macro, but the parameterbytes following the monitor-request macro linkageinstructions were not valid.




ModuleDXCSLCCI, DXCSLCOU

0000D7 KCTLC - CALLER REPLY AREA NOTACCESSIBLE

ExplanationAn ECB-controlled program issued a KCTLC monitor-request macro with parameter TEST that specified adata area in storage that the program did not haveread (fetch) access to.





ModuleDXCSLCCI

0000D8 macro - INVALID LINK NUMBER

ExplanationAn ECB-controlled program issued a macro (KCTLC orPLONC) monitor-request macro with an invalid SLC linknumber.



Programmer responseThese macros are not intended to be called by user-written programs. If you have called one, replace thecall; otherwise inform your system programmer.


0000D9 macro - INVALID LINK CHANNELNUMBER

ExplanationAn ECB-controlled program issued a macro (KCTLC orPLONC) monitor-request macro with an invalid SLC linkchannel number.



Programmer responseThese macros are not intended to be called by user-written programs. If you have called one, replace thecall; otherwise inform your system programmer.


0000DB PLONC MSG - NO MESSAGE FILEADDR PROVIDED

ExplanationAn ECB-controlled program issued a PLONC monitor-request macro with parameter MSG, but there was nofile address for the message in general register 15(RDB).




ModuleDXCSLCOU

0000DC SLC LINK QUEUE ERROR - type

ExplanationWhere type is one of:

BAD FILE ADDRESSFIND ERRORRELEASE ERROR

ALCS detected an error in the monitor find, file, orrelease routine while processing an item on queue foran SLC link.

System actionALCS ignores this item on the queue.


ModuleDXCSLCOU

0000DD KCTLC - NO SLC NETWORK


ExplanationAn ECB-controlled program issued a KCTLC monitor-request macro, but there are no SLC links.


System programmer responseCheck the ALCS communication generation.

ModuleDXCSLCCI

0000E0 TOD CLOCK ERROR

ExplanationThe processor time-of-day ( TOD ) clock is in not-set,error, stopped, or not-operational state.


Operator responseEnsure that the TOD clock is operational and set. Thenactivate the alternate ALCS if there is one, or restartALCS.

ModuleDXCTIR

0000E1 INVALID ENTRY TO PROGRAMprogram_name

ExplanationA program entered the ALCS ECB-controlled programprogram_name, which is not allowed.



Programmer responseThis program is not intended to be called. If youhave called it, remove the call; otherwise inform yoursystem programmer.

ModuleCDSN, COMH, CVEM

0000E2 CINFC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a CINFC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.



ModuleDXCINF

0000E3 KEYCC - INVALID KEY CHANGEREQUEST

ExplanationAn ECB-controlled program issued a KEYCC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.



ModuleDXCNUC


0000E4 DETAC - DETACHED BLOCKCONTROL TABLE CORRUPTED

ExplanationAn ECB-controlled program issued a DETAC monitor-request macro but ALCS detected corruption of thedetached block control table for the entry. This is mostlikely caused by the application working through dataand stepping outside a storage block.



ModuleDXCSTG

0000E5 ATTAC - DETACHED BLOCKCONTROL TABLE CORRUPTED

ExplanationAn ECB-controlled program issued an ATTAC monitor-request macro but ALCS detected corruption of thedetached block control table for the entry. This is mostlikely caused by the application working through dataand stepping outside a storage block.



ModuleDXCSTG

0000E6 FLIPC - DETACHED BLOCKCONTROL TABLE CORRUPTED

ExplanationAn ECB-controlled program issued a FLIPC monitor-request macro but ALCS detected corruption of thedetached block control table for the entry. This is mostlikely caused by the application working through dataand stepping outside a storage block.



ModuleDXCSTG

0000FA STATE CHANGE OR PENDINGINDICATOR CORRUPTED

ExplanationThe ZDSYS or ZASYS command processor detectedinvalid system state indicators.

System actionThe system state is unpredictable.

Operator responseUse the ZASYS command with the RESET option toset the correct system state. If this is an isolatedinstance, follow your normal procedure for a non-urgent problem. If it happens repeatedly, inform yoursystem programmer..


ModuleCVSN

0000FB SYSTEM STATE INDICATORCORRUPTED

ExplanationThe ZDSYS or ZASYS command processor detectedinvalid system state indicators.

System actionThe system state is unpredictable.

Operator responseUse the ZASYS command with the RESET option toset the correct system state. If this is an isolatedinstance, follow your normal procedure for a non-


urgent problem. If it happens repeatedly, inform yoursystem programmer..


ModuleCVSN

0000FC LODIC - ALTER ACV FROMUNAUTHORIZED ENTRY

ExplanationAn ECB-controlled program issued a LODIC monitor-request macro with parameter AACV, but the entrywas not authorized to issue LODIC AACV. Only entriesthat originate from Prime CRAS input messages areauthorized to issue LODIC AACV (except that anyentry is authorized to issue LODIC with other options).


User responseThis option of the LODIC macro is not intendedfor user-written programs. If the error is in an IBM-supplied program then ask your system programmer toinform your IBM programming support representative.(User-written programs can issue LODIC with optionsother than AACV.)

ModuleDXCINF

0000FD LODIC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a LODIC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.


User responseIf an IBM-supplied macro generated the incorrectmonitor-request macro linkage then ask your system

programmer to inform your IBM programming supportrepresentative.

ModuleDXCINF

0000FE LODIC - ALTER ACV REJECTED

ExplanationThe ZAACV command processor was unable to updatethe activity control variables.

System actionThe status of the activity control variables isunpredictable.

Operator responseUse the ZDACV command to check the activity controlvariables. If this is an isolated instance, follow yournormal procedure for a non-urgent problem. If ithappens repeatedly, inform your system programmer..


ModuleCVMS

0000FF LODIC - RESET FROMUNAUTHORISED ENTRY

ExplanationAn ECB-controlled program issued a LODIC monitor-request macro with parameter RESET but the entrywas not authorized to issue LODIC RESET. Onlyentries that originate from CRAS input messages areauthorized to issue LODIC RESET.

ModuleDXCINF

000100 GTFCC - reason

ExplanationAn ECB-controlled program issued a GTFCC monitor-request macro but, depending on reason:


INVALID typeThe parameter bytes following the monitor-request macro linkage instructions were not valid.Type is one of:

ACTION CODECONTROL TYPE CODETRACE TYPE CODE

NO WRITE ACCESS TO DISPLAY AREAThe entry did not have read/write access to thedisplay area storage at the address specified bythe DISPLAY parameter.

VARY ACT/INACT NOT FROM PRIME CRASOnly entries that originate from Prime CRAS inputmessages are authorized to issue GTFCC.




ModuleDXCGTC

000101 DMPCC - INVALID PARAMETERS

ExplanationAn ECB-controlled program issued a DMPCC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.




ModuleDXCDMPC

000102 DCRCC - reason

ExplanationAn ECB-controlled program issued a DCRCC monitor-request macro but, depending on the value of reason:

ENTRY NOT AUTHORIZEDThe entry was not authorized to issue DCRCC.Only entries that originate from Prime CRAS inputmessages are authorized to issue DCRCC.

INVALID MACRO PARAMETERSThe parameter bytes following the monitor-request macro linkage instructions were not valid.

INVALID START OPTIONSThe parameter bytes following the monitor-request macro linkage instructions were not valid.




ModuleDXCDCR

000103 ADRIC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued an ADRIC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.


User responseIf an IBM-supplied macro generated the incorrectmonitor-request macro linkage then ask your system



ModuleDXCINF

000104 SYSCC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a SYSCC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.



ModuleDXCINF

000105 EXITC - ISSUED BY STATECHANGE ENTRY

ExplanationA state change entry has ended (exited) beforecompleting the state change.

System actionThe state change entry ends, but the contents of thesystem state indicators are unpredictable.

Operator responseUse the ZASYS command with the RESET option toset the correct system state and inform your systemprogrammer.

System programmer response• If the state change entry ended abnormally (a

system error) then check and correct that systemerror.

• If the state change entry ended normally (EXITCmacro) then check which program issued the EXITC.

– If it is an IBM-supplied program the inform yourIBM programming support representative.

– If it is an installation-wide exit program thencorrect the program to avoid issuing EXITC.Installation-wide state change exit programs mustnot issue EXITC.

ModuleDXCINF

000106 STICC - reason

ExplanationAn ECB-controlled program issued a STICC monitor-request macro but, depending on the value of reason:

INVALID REQUEST CODEThe parameter bytes following the monitor-request macro linkage instructions were not valid.

INVALID PARAMETERThe parameter bytes following the monitor-request macro linkage instructions were not valid.

ENTRY NOT AUTHORIZEDThe entry was not authorized to issue STICC.Only entries that originate from Prime CRAS inputmessages are authorized to issue STICC (exceptthat any entry is authorized to issue STICC withDISPLAY or TEST option).



ModuleDXCINF

000107 GTFCC - ORIGINATOR CHANGENOT ALLOWED

ExplanationAn ECB-controlled program issued a GTFCCCONV,MODIFY to change the originator CRI for theentry. The requested change is not allowed because:

• The change-to CRI is not valid,

or:• The change-from CRI is not a communication link,


or:• The change-to CRI is not owned by the system that

the change-from CRI (communication link) connects.


Programmer responseIf this is an error in your application program,correct the error. Otherwise check that the ALCScommunication generation defines the change-to CRIas an OSYS terminal with the correct communicationID.

000108 CORUC - INVALID PARAMETERS

ExplanationAn ECB-controlled program issued a CORUC, EVNWC,POSTC, or DEQC monitor-request macro, but theparameter bytes following the monitor-request macrolinkage instructions were not valid. Note that CORUC,EVNWC, POSTC, and DEQC macros all generate a CORUCmonitor-request macro.



ModuleDXCHLD

000109 CORHC - DUPLICATE RESOURCEHOLD

ExplanationAn ECB-controlled program issued a CORHC, EVNTC,or ENQC monitor-request macro, but the entry wasalready holding the resource. Note that CORHC, EVNTC,and ENQC macros all generate a CORHC monitor-request macro.



ModuleDXCHLD

000110 CORUC - RESOURCE NOT HELD

ExplanationAn ECB-controlled program issued a CORUC or DEQCmonitor-request macro, but either:

• The entry was not holding the resource,

or:• The entry did not use a compatible monitor-request

macro to hold the resource; CORUC can only unhold aresource that CORHC held, and DEQC can only unholda resource that ENQC held.

Note that CORUC and DEQC macros both generate aCORUC monitor-request macro.



ModuleDXCHLD

000111 ALASC - BLOCK ALREADYATTACHED

ExplanationAn ECB-controlled program issued an ALASC monitor-request macro, but there is already an automaticstorage block attached for this application program.



ModuleDXCSTG

000112 macro - INVALID PARAMETERS


ExplanationAn ECB-controlled program issued a macro monitor-request macro (one of ALASC, DETAC, ATTAC), butthe parameter bytes following the monitor-requestmacro linkage instructions were not valid.



ModuleDXCSTG

000113 macro - INVALID PARAMETERS

ExplanationAn ECB-controlled program issued a SYNCC (macro= SYNCC) or a CORHC, EVNTC, or ENQC (macro =CORHC) monitor-request macro, but the parameterbytes following the monitor-request macro linkageinstructions were not valid. Note that CORHC, EVNTC,and ENQC macros all generate a CORHC monitor-request macro.



ModuleDXCHLD, DXCSNC

000114 ATTAC - BLOCK ALREADYATTACHED

ExplanationAn ECB-controlled program issued an ATTAC monitor-request macro with a storage block already attachedat the storage level.



ModuleDXCSTG

000115 ATTAC - NO DETACHED BLOCK

ExplanationAn ECB-controlled program issued an ATTAC monitor-request macro, but there was no detached blockavailable.



ModuleDXCSTG

000116 BLKIC - INVALID REQUEST CODE

ExplanationAn ECB-controlled program issued a BLKIC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.



ModuleDXCINF

000117 SLIMC - INVALID PARAMETER


ExplanationAn ECB-controlled program issued a SLIMC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.



ModuleDXCINF

000118 LOGIC ERROR - RESOURCE HOLDTABLE CORRUPTED

ExplanationThere is an internal logic error in an ALCS routine. TheALCS resource hold table is corrupted.




ModuleDXCHLD

000119 CORHC - RESOURCE TABLE FULL

ExplanationAn ECB-controlled program issued a CORHC, EVNTC, orENQC monitor-request macro, but the ALCS resourcehold table was full. Note that CORHC, EVNTC, and ENQCmacros all generate a CORHC monitor-request macro.


User responseCheck the contents of the ALCS resource hold table.In particular, check if the table is full because there isa real need for all the resource names, or because ofapplication program errors. If there is a real need forall the resource names that are in use, then run a newALCS generation to increase the size of the resourcehold table. To optimize performance, allocate at leasttwice as many resource hold table entries as are in useat any one time.

Problem determinationThe system error dump includes a dump of the ALCSresource hold table.

ModuleDXCHLD

00011A RESOURCE(S) HELD AT EXIT -UNHELD

ExplanationAn ECB-controlled program issued an EXITC monitor-request macro with one or more resources held. Thatis, the entry issued one or more of the following beforeit issued EXITC:

CORHC without a corresponding CORUCENQC without a corresponding DEQCEVNTC without a corresponding EVNWC.

System actionALCS unholds the resources before it terminates theentry.


ModuleDXCHLD

00011B ENQC - RESOURCE HOLD TIMEOUT

ExplanationAn ECB-controlled program issued an ENQC monitor-request macro that specified or defaulted a timeout.Another entry issued ENQC for the same resource and


waited for longer than the timeout time that this entryspecified.

System actionALCS terminates this entry. The entry that is waiting forthe resource can then proceed.

ModuleDXCHLD

00011C macro - CAUSES DEADLOCK

ExplanationThe entry issued a macro (CORHC, POSTC, TASNC,FINHC, or FIWHC.) monitor-request macro that causeda deadlock. Note that CORHC, EVNTC, and ENQC macrostatements all generate a CORHC monitor-requestmacro.

Deadlocks arise when more than one entry "holds"more than one resource; that is, the entries use:

Resource hold (for example CORHC monitor-requestmacro)Record hold (for example FINHC monitor-requestmacro)Sequential file assign (TASNC monitor-requestmacro).

System actionALCS terminates the entry. This relieves the deadlock.

User responseCheck the way that this entry uses these facilities.In particular, check that this entry holds resources inthe same order that other entries hold the resources.If possible, modify the program or programs thatprocessed this entry so that they hold only oneresource at a time. If that is not possible, then modifythe programs that hold the resources so that they allhold the resources in the same order.

ModuleDXCHLD, DXCSEQR, DXCVFM

00011D HASHC - PARAMETER TYPE NOTH, C, OR D

ExplanationAn ECB-controlled program issued a HASHC monitor-request macro with invalid parameters.



ModuleDXCWTO

00011E HASHC - INVALID DATA ADDRESS

ExplanationAn ECB-controlled program issued a HASHC monitor-request macro, but the data address passed to themonitor points to a protected storage area.



ModuleDXCWTO

00011F CORHC - INCOMPATIBLE MACROTYPES

ExplanationAn ECB-controlled program issued a CORHC, EVNTC,or ENQC monitor-request macro that conflicted withanother use of the same resource name; for example,another entry issued EVNTC TYPE=CNT and thisentry issued ENQC or EVNTC TYPE=MSK for the sameresource name. Note that CORHC, EVNTC, and ENQCmacros all generate a CORHC monitor-request macro.



ModuleDXCHLD


000120 LOGIC ERROR - INVALID PGMCCRETURN CODE

ExplanationThe ZPCTL command processor detected an internallogic error in an ALCS routine.



ModuleCPC0, CPCV

000121 LOGIC ERROR - PROGRAM HASHTABLE CORRUPTED

ExplanationThere is an internal logic error in an ALCS routine. TheALCS program hash table is corrupted.




ModuleDXCPGL

000122 PGMCC - INVALID ACTION CODE

ExplanationAn ECB-controlled program issued a PGMCC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.




ModuleDXCPGC

000123 PGMCC - USER AREA TOO SMALL

ExplanationAn ECB-controlled program issued a PGMCC monitor-request macro, but the user area length (PG0LEN) isnot big enough.




ModuleDXCPGC

000125 EVINC -- NOT COUNTER TYPEEVENT

ExplanationAn ECB-controlled program issued an EVINC monitor-request macro, but it specified an event which is not acounter type event.




ModuleDXCHLD

000126 EVINC -- EVNWC ALREADYISSUED FOR EVENT

ExplanationAn ECB-controlled program issued an EVINC monitor-request macro, but it specified an event for whichan EVNWC monitor-request macro had already beenissued.



ModuleDXCHLD

000127 EVINC -- COUNT ALREADY ATMAXIMUM

ExplanationAn ECB-controlled program issued an EVINC monitor-request macro, but it specified an event which alreadyhas the maximum count.



ModuleDXCHLD

000128 HLLCC - UNSUPPORTEDLANGUAGE

ExplanationAn ECB-controlled program issued an HLLCC monitor-request macro, but it specified a language that ALCSdoes not support.



ModuleDXCPGH

000129 HLLCC - INVALID SERVICE CODE

ExplanationAn ECB-controlled program issued an HLLCC monitor-request macro, but it contained a service code that isnot valid.



ModuleDXCPGH

00012A HLLCC - OUTSIDE HLLENVIRONMENT

ExplanationAn ECB-controlled program issued an HLLCC monitor-request macro outside a high-level language ( HLL )environment.


User responseThis macro is not intended for use in user-writtenprograms. If the error is in an IBM-suppliedprogram then inform your IBM programming supportrepresentative.


ModuleDXCPGH

000130 HELP PROGRAM ERROR

ExplanationThe ALCS command help facility found an error in ahelp text program.

System actionALCS substitutes a response message: "Help notavailable -- try: ZHELP INDEX"

Programmer responseIf the error is in a user-written help text programthen correct the programming error (see ALCSInstallation and Customization installation-wide helptext exit programs AHLx). Otherwise, inform your IBMprogramming support representative.

ModuleCHLP

000131 HELPC - INVALID CRI

ExplanationAn ECB-controlled program issued a HELPC monitor-request macro, but the originating terminal address inthe ECB descriptor is not a valid CRI.



ModuleDXCWTO

000132 HELPC - INVALID CHARACTER INTOPIC PARAMETER

ExplanationAn ECB-controlled program issued a HELPC monitor-request macro, but the primary or secondary helpcontext contains invalid characters.


ModuleDXCWTO

000133 HELPC - INVALID DEVICE TYPEFOR EXTRACT_CONTEXT

ExplanationAn ECB-controlled program issued a HELPC monitor-request macro specifying the EXTRACT_CONTEXTparameter, but the originating terminal is not a displaydevice.



Programmer responseInform your system programmer.

ModuleDXCWTO

00013F DXCPGC - VFA ERROR

ExplanationA VFA read/write error occurred while ALCS was usinga program configuration data set.



System programmer responseContact your IBM programming supportrepresentative.

ModuleCPCT


000140 LOGIC ERROR - XCF MEMBERTABLE FULL

ExplanationThere is an internal logic error in an ALCS routine.




ModuleDXCXCF

000144 DXCXCF - NO STORAGEAVAILABLE

ExplanationALCS is unable to obtain storage for a parallel sysplexcontrol table.



System programmer responseEnsure that enough storage is available to the ALCSregion.

ModuleDXCXCF

000149 LOGIC ERROR - XCF RINGADDRESS TABLE FULL





ModuleDXCXCF

000150 SAF LOGIC ERROR - UNABLE TODELETE ACEE

ExplanationThere is an internal logic error in an ALCS routine. ALCSwas unable to release the storage used to hold anaccesser environment element (ACEE).

System actionThe ACEE virtual storage is lost - it cannot be reuseduntil ALCS is restarted.

User responseIf this error occurs, inform your IBM programmingsupport representative.

ModuleDXCSAF

000151 AUTHC - INVALID MACROPARAMETER

ExplanationThere are two reasons for this dump.

1. An invalid value has been found in the first byte ofthe parameter list. The value must be between 0and 6 inclusive.

2. An invalid value has specified on a CRASC check.The value must be between 1 and 3 inclusive.



System programmer responseIf the error is in an IBM-supplied program, inform yourIBM programming representative.

Module:DXCSAF

000152 AUTHC - ENTITY NAME TOO LONG

ExplanationAn AUTHC macro call has generated an ENTITY namewhich is more than 255 characters long.


Programmer responseCheck the ENTITY name specified on the AUTHCmacro.

Problem determinationAt the time of the dump, general register 1 containsthe length of the generated ENTITY name and generalregister 5 points to the generated ENTITY name.

Module:DXCSAF

000153 SAF - INVALID CRAS LEVELSUPPLIED

ExplanationAn invalid CRAS check value has been specified.


Programmer responseCheck the CRAS check value on the AUTHC macro call.The value must be between 0 and 2 inclusive.

Module:DXCSAF

000154 GSAFC - INVALID MACROPARAMETER

ExplanationAn invalid parameter has been specified on a GSAFCmacro call.


Programmer responseCheck the parameters specified on the GSAFC macro.

Problem determinationAt the time of the dump, general register 14 point tothe invalid parameter.

Module:DXCSAF

000155 GSAFC - ABNORMAL ERROR FROMIRRSEQ00

ExplanationA call to the ESM callable services routine (IRRSEQ00)has returned an unexpected error code.

System actionALCS continues processing and returns to theapplication.

Programmer responseCheck the ESM documentation for explanation of errorcodes.

Problem determinationAt the time of the dump, general register 14 containsthe SAF return code and general register 5 containsthe ESM return code.

Module:DXCSAF

000156 GSAFC - CALLABLE SERVICES EPNOT LOADED

ExplanationA GSAFC macro call has been made but the callableservices routine IRRSEQ0 is not available.



Programmer responseCheck the R0 for the MVS abend and reason codesassociated with a DXC138E message which indicatesthe failure to load the IRRSEQ00 entry point duringsystem restart.

Module:DXCSAF

000160 PLEXC - INVALID TYPEPARAMETER

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro with an invalid TYPE parameter.




ModuleDXCPLEX

000161 PLEXC - INVALID ACTIONPARAMETER

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro with an invalid ACTION parameter.




ModuleDXCPLEX

000162 PLEXC - NO IOCB AVAILABLE

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro but no ALCS IOCB is available.




ModuleDXCPLX2

000163 NO IOCB AVAILABLE TO STARTNETWORK

ExplanationNo ALCS IOCB is available during start networkprocessing as a result of a PLEXC monitor-requestmacro.


System programmer responseInform your IBM programming representative.

ModuleDXCPLX2

000164 PLEXC - NO STORAGE FORAPPLICATION TABLE

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro but no storage for the application tableis available.





ModuleDXCPLX2

000165 PLEXC - BAD APPLICATIONTOKEN

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro with an invalid application TOKEN.




ModuleDXCPLX2

000166 PLEXC - BAD PROGRAM NAME

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro with an invalid PROGRAM name.




ModuleDXCPLEX

000167 LOGIC ERROR - APPLICATIONCONTROL TABLE ENTRY NOTFOUND AT PI

ExplanationThere is an internal logic error in ALCS.




ModuleDXCPLEX

000168 PLEXC - UNABLE TO NOTIFYOTHER INSTANCE(S)

ExplanationAn ECB-controlled program issued a PLEXC monitor-request macro, but other instance(s) of the ALCSplexcould not be notified.





ModuleDXCPLEX

000171 INVALID cause FOR MAPPINGINDEX RECORD

ExplanationWhen cause:

RECORD TYPEFixed file record type #KPTRI is not defined.(The hash (#) character is represented differentlyby some equipment and it is the EBCDIC X''7B''character.)

FILE ADDRFixed file record type #KPTRI ordinal 6 is notallocated.



ModuleCSM1, CSMI, CSMO

000172 ERROR READING MAPPINGINDEX RECORD or ERRORREADING MAPPING INDEXRECORD - RECORD RE-INITIALIZED

ExplanationThe system record header has been corrupted or therecord has not yet been initialized properly.

System actionALCS either terminates the entry or re-initializes therecord and continues with the entry.

System programmer responseFor an entry termination, ensure that the record type#KPTRI (system keypoint record) ordinal number 6

has not been illegally modified by a user applicationprogram. (The hash (#) character is representeddifferently by some equipment and it is the EBCDICX''7B'' character.) If it has not, then inform your IBMprogramming support representative. If the recordis re-initialized then any screen maps that werepreviously loaded on the ALCS database will have tobe reloaded. For further information see the ZCMSPcommand in ALCS Operation and Maintenance.


000173 ERROR READING SEQUENTIALFILE FOR MAP LOAD

ExplanationAn I/O error occurred.


System programmer responseEnsure that the sequential file containing the 3270map description is valid. Check the record length.If they are correct, inform your IBM programmingsupport representative.

ModuleCSM1

000174 INVALID WRITE COMMANDFOUND DURING MAP LOAD

ExplanationAn invalid value for the 3270 write command has beendetected while loading the 3270 map description ontoALCS.


System programmer responseEnsure that the sequential file containing the 3270map description is valid; and that it is not modifiedbefore being processed by ALCS.

If this does not solve the problem, inform your IBMprogramming support representative.


ModuleCSM1

000175 INVALID SEQUENTIAL FILERECORD SEQUENCE

ExplanationAn invalid sequence of records on the sequentialfile has been detected while loading the 3270 mapdescription onto ALCS.


System programmer responseEnsure that the sequential file containing the 3270map description is valid; and that it is not modifiedbefore being processed by ALCS.

If this does not solve the problem, inform your IBMprogramming support representative.

ModuleCSM1

000176 CAN NOT READ POOL MAPDESCRIPTION

ExplanationALCS detected an error when trying to read a 3270map description record. This may be caused by eitheran invalid record ID or an invalid file address.


System programmer responseEnsure that the record, and the index recordcontaining the file address of the record, have notbeen illegally modified by an application program. Ifthey have not, then inform your IBM programmingsupport representative.


000177 INVALID MAPNAME SPECIFIEDFOR 3270 MAPPING

ExplanationThe mapname specified by the calling program doesnot exist.


System programmer responseEnsure that the 3270 map does exist on the ALCSsystem, or correct the calling program.


000178 WTOPC - UNEXPECTED SEQUENCENUMBER

ExplanationA program issued WTOPC CHAIN=YES macros to senda message, but CSC6 was unable to build the completemessage because the message blocks were out ofsequence.



ModuleCSC6

000179 WTOPC - MESSAGE BLOCK NOTATTACHED ON LEVEL PROGRAMNAME PN-'name' DISPLACEMENTDSP-'nnnn'

ExplanationAn ECB-controlled program issued a WTOPC monitor-request macro with the LEVEL parameter, but there isno storage block attached on the specified level.


Programmer responseCorrect the program to provide a valid storage level.


ModuleCWTO

00017A DISPC - ERROR IN OUTPUT FILE

ExplanationThe ALCS output file for scrolling contains unreadabledata.


User responseCreating a new output file solves the problem. But ifthe problem occurs regularly it might indicate seriousshort-term pool problems.

ModuleCSC4, CSC5

00017B DISPC - CAN NOT PROCESS

ExplanationAn error occurred while building an ALCS output file forscrolling.



ModuleCSC4

00017C DISPC - CAN NOT RESET OUTPUTFILE INDICATOR

ExplanationAn error occurred while building an ALCS output file forscrolling.



ModuleCSC4

00017D DISPC - CAN NOT RETRIEVEOUTPUT MSG RECORD

ExplanationA find error occurred on the retrieval of an ALCS outputmessage record while building an ALCS output file forscrolling.


System programmer responseExamine the system error dump and determine thecause of the error.

• If it is due to a record ID error, check whether thedatabase is corrupted (for example, because of poolproblems).

• If it is due to an invalid file address, check whetherthe resource control record (RCR) is corrupted.

• If it is due to a hardware error, get the unit serviced.

ModuleCSC4

00017E DISPC - ERROR COPYING DATA

ExplanationA program issued a DISPC SEND macro, but CSC2 wasunable to copy the data into the ALCS output file forscrolling.


User responseIf this error occurs, ask your system programmerto investigate if scrolling is inhibited. If scrollingis inhibited, the type 3 storage unit size must begreater than or equal the largest response plus 50bytes. If scrolling is not inhibited, inform your IBMprogramming support representative.


ModuleCSC2

00017F DISPC - INVALID COUNT

ExplanationA program issued a DISPC ADD macro, and specified anegative value for the LENGTH parameter.



ModuleCSC1

000180 DISPC - INVALID ECB LEVELPARAMETER

ExplanationA program issued a DISPC ADD macro, specifying theLEVEL parameter incorrectly.



ModuleCSC1

000181 DISPC - INVALID ECB LEVELSPECIFIED

ExplanationA program issued a DISPC SEND macro, but the datalevel in the LEVEL parameter is invalid.



ModuleCSC2, CSC7

000182 DISPC - INVALID RECORD ID

ExplanationA program issued a DISPC SEND macro, but thestorage block allocated at the specified ECB level doesnot contain a record belonging to the ALCS output filefor scrolling.



ModuleCSC2

000183 DISPC - reason

ExplanationA program issued a DISPC SEND macro which couldnot be processed because of reason, where reason isone of the following:

INVALID RESOURCE IN EBROUTThe value in EBROUT, which is the CRI for theoriginating terminal, is invalid.

DESTINATION INACTIVEThe destination specified on either the PRINTER orthe DEST parameter of DISPC SEND is inactive.

CAN NOT DETERMINE THE SCREEN SIZEInformation about the size of the screen is notavailable from the communications table.

INVALID DESTINATION SPECIFIEDThe CRI or CRN provided for the PRINTER or theDEST parameter on DISPC SEND is not valid.



ModuleCSC2


000184 DISPC - NO LINES IN OUTPUTFILE

ExplanationA program issued a DISPC SEND macro, but no DISPCADD calls were performed to add one or more textlines to the ALCS output file for scrolling.



ModuleCSC2

000185 DISPC - SPECIFIED LEVEL NOTAVAILABLE

ExplanationA program issued a DISPC ADD macro, and the levelspecified in the LEVEL parameter is in use, but not byan AC06 record.



ModuleCSC1, CSC7

000186 DISPC - STORAGE LEVEL NOT INUSE

ExplanationA program issued a DISPC SEND macro, but the levelspecified in the LEVEL parameter is not in use.



ModuleCSC2

000187 DISPC - TOO MANY OUTPUT LINESCREATED

ExplanationA program issued a DISPC ADD macro, causing theALCS output file to exceed the maximum size. Anoutput file can be up to a maximum of 150 L3 records.



ModuleCSC1

000188 DISPC - CAN NOT SET OUTPUTFILE INDICATOR

ExplanationA program issued a DISPC SEND macro, but ALCSreturned an error condition on the COMCC to set theoutput file indicator.



ModuleCSC2

000189 SCROLL LOG -- ERROR IN LOGFILE

ExplanationAn error occurred while ALCS was processing the scrolllog for a terminal.




ModuleCSC9

00018A DISPC - TOO MANY LINES FORSORT

ExplanationYou have exceeded the maximum of 100 000 lines in aDISPC SORT routine.


Programmer responseReduce the size of the display message or find analternative method to sort it.

ModuleCSCS

00018B DISPC - TRUNCATED

ExplanationThe display message can not fit in the largest availablestorage block.

System actionALCS truncates the response and continues.

System programmer responseEither reduce the screensize for this terminal or definestorage blocks with a larger block size.

ModuleCSC4

00018C CXE0 - INVALID ENTRYCONDITIONS

ExplanationA program entered the ALCS ECB-controlled programCXE0 with one of the following incorrect entryconditions:

The communication error code is invalid

The ALCI record type code is not recognized.




ModuleCXE0

00018D ERROR RETURN FROM PRINTERQUEUE SWING

ExplanationA ZACOM command requested a message queuetransfer to another printer, but was unable to makethis transfer. This could be because the file copy of themessages was corrupted or ALCS could not retrievethe resource control record (RCR).

System actionALCS bypasses the request. Processing continues.


ModuleCOMB

00018E NO SLC LINKS DEFINED

ExplanationA program entered the ALCS ECB-controlled programCSQC or CSQS with incorrect entry conditions.





ModuleCSQC, CSQS

00018F ORIGINATING RESOURCE NOTKNOWN TO ALCS

ExplanationThe ZROUT command processor was called withincorrect entry conditions. The originating terminal CRI(in ECB field EBROUT) was invalid.




ModuleCOML

000190 COMMS LOGIC ERROR - BAD RCFROM COMCC




ModuleCOML, COMB, CPL1, CWAS

000191 INVALID CRI IN EBROUT

ExplanationA program entered the ALCS ECB-controlled programCFMT with an invalid CRI in EBROUT.


System programmer responseIf the error is in an IBM-supplied program then informyour IBM programming support representative.

ModuleCFMT

000192 ZRETR ERROR - reason

ExplanationThere was an internal error processing the ZRETRcommand. The reason is one of:

CAN NOT RETRIEVE MESSAGE RECORDCAN NOT SET/RESET RETRIEVE INDICATOR

User responseThis error should not occur. If it does, contact yourIBM programming service representative.

ModuleCRT1

000193 PLEXC - UNEXPECTED RETURNCODE

ExplanationInvalid return code from PLEXC monitor-requestmacro.




ModuleCPL1, CPL2

000194 CACU - UNEXPECTED RETURNCODE

ExplanationInvalid return code from ECB-controlled programCACU.



ModuleCPL1

000195 UNABLE TO RETRIEVE ANCHOR

ExplanationECB-controlled program CACU is not able to read theapplication and communication utility anchor record.



ModuleCACU

000196 UNABLE TO READ FIRST QUEUERECORD

ExplanationECB-controlled program CACU is not able to read thefirst queue record chained from the application andcommunication utility anchor record.



ModuleCACU

000197 UNABLE TO READ OVERFLOWQUEUE RECORD

ExplanationECB-controlled program CACU is not able to read theoverflow queue record chained from the applicationand communication utility anchor record.



ModuleCACU

000198 UNABLE TO OBTAIN A QUEUERECORD

ExplanationECB-controlled program CACU is not able to obtain aqueue record.


System programmer responseInvestigate if there is any abnormal condition (suchas GFS inactive, no pool records left) and takeappropriate action, otherwise collect all relevantinformation and inform your IBM programmingrepresentative.

ModuleCACU

000199 CACU LOGIC ERROR

ExplanationLogic error in ECB-controlled program CACU.




ModuleCACU

00019A NO FREE ENTRIES IN ANCHOR

ExplanationECB-controlled program CACU was called. No freeentries are left in the application and communicationutility anchor record.



ModuleCACU

00019B INVALID REQUEST CODE

ExplanationECB-controlled program CACU was called with aninvalid request code.



ModuleCACU

00019C INVALID ADD TO QUEUE

ExplanationECB-controlled program CACU was called with invalidentry conditions.



ModuleCACU

00019D DISPC - INVALID RESOURCE

ExplanationScrolling is inhibited for this communication resource.Only the DISPC ADD and DISPC SEND macros may beused. DISPC SEND DEST is not allowed.



ModuleCSCS, CSC2, CSC7, CSC8

0001A0 ZCTCB LOGIC ERROR

ExplanationALCS detected a logic error while processing a ZCTCBcommand.



System programmer responseInform your IBM programming support representative.

0001A1 INVALID CLCCC MACROPARAMETERS

ExplanationALCS detected a logic error while processing a ZCTCBcommand.





ModuleDXCPERF

0001A2 LEVEL DF IS NOT FREE

ExplanationALCS detected a logic error (level DF is not free) whileprocessing a ZCTCB command.




ModuleDXCPERF

0001A3 INVALID PRFCC MACROPARAMETERS

ExplanationALCS detected a logic error while processing a ZPERFcommand.




ModuleDXCPERF

0001A4 PERFORMANCE MONITOR - LOGICERROR

ExplanationALCS detected a logic error while processing a ZPERFcommand.




ModuleCPM3, CPM7

0001A5 PERFORMANCE MONITOR -INTERNAL ERROR

ExplanationALCS detected an internal error while processing aZPERF command.





0001A6 PERFORMANCE MONITOR -INTERNAL ERROR

ExplanationALCS detected an internal error while processinghistory performance data.





ModuleCPM5

0001A7 TERMINATION REQUESTED BYUSRWAIT INSTALLATION-WIDEEXIT

ExplanationALCS installation-wide monitor exit USRWAITdetermined that processing of this entry must beterminated.


Programmer responseIf the entry exceeded the limit that SLIMC can reset,and if the entry genuinely needs to do a large numberof reads, then include a SLIMC monitor-request macroin the application to increase the read threshold forthis entry. Otherwise correct the programming erroror inform your system programmer to investigate theUSRWAIT installation-wide monitor exit.

ModuleDXCNUC

0001A8 HALTC - ENTRY NOT AUTHORIZED

ExplanationAn ECB-controlled program issued a HALTC monitor-request macro, but the entry is not authorized to issueHALTC. Only entries with Prime CRAS authority areauthorized to issue HALTC.



ModuleDXCPHM

0001A9 NO BATAP IMA SLOTS

ExplanationNo BATAP input message acknowledgment ( IMA )transmit slots are available.

System actionALCS terminates the entry. BATAP is unusable.

User responseAfter solving the problem, terminate the session andre-establish it by means of an ALCS command.

If this error occurs, ask your system programmer toinform your IBM programming support representative.

ModuleCBQX

0001AB INVALID BATAP TRAILER

ExplanationAn incorrect BATAP trailer, appended to an inputmessage, was received.

System actionALCS terminates the entry and ignores the inputmessage, forcing re-transmission of the message.


ModuleCBQZ

0001AC INVALID BATAP IMA

ExplanationAn invalid BATAP input message acknowledgment( IMA ), appended to an input message, was received.

System actionALCS terminates the entry and ignores the inputmessage, forcing re-transmission of the message.



ModuleCBQZ

0001AD COMMS LOGIC ERROR - BAD RCFROM COMCC




ModuleCKY1, CKY2

0001AE COMMS LOGIC ERROR - INVALIDCRI




ModuleCKY1

0001AF PF KEY RECORD type ERROR

ExplanationAn error occurred while:

type READreading

type FIND/FILEreading or filing

a PF key record.

System actionIf type is READ, ALCS continues processing normallyusing default PF keys. If type is FIND/FILE, ALCSterminates the entry.

User responseCheck if the error was caused by:

• User corruption of the PF key record.• Hardware problem.

If not then ask your system programmer to inform yourIBM programming support representative.

ModuleCKY1, CKY2

0001B3 RECYCLE ATTENTION MSGREQUESTED FOR LT POOL

ExplanationA program entered the ALCS ECB-controlled programCVEA with incorrect entry conditions.




ModuleCVEA

0001C1 DECBC - INVALID DECBREFERENCE

ExplanationAn ECB-controlled program issued a monitor-requestmacro that specified a DECB address. The DECBaddress did not reference a valid DECB or referencedone that had been released.




ModuleDXCSTG

0001C2 DECBC - I/O IN PROGRESS

ExplanationAn ECB-controlled program issued a DECBC monitor-request macro macro that specified a DECB for whichI/O was in progress.



ModuleDXCSTG

0001C3 DECBC - BLOCK ATTACHED

ExplanationAn ECB-controlled program issued a DECBCFUNC=RELEASE monitor-request macro that specifieda DECB with a storage block attached.



ModuleDXCSTG

0001C4 DECBC - DECB NAME NOT KNOWN

ExplanationAn ECB-controlled program issued a DECBCFUNC=RELEASE monitor-request macro and specifiedthe NAME parameter. However the DECB namespecified did not reference a known DECB.



ModuleDXCSTG

0001C5 DECBC - INVALID FUNCTIONCODE

ExplanationAn ECB-controlled program issued a DECBC monitor-request macro macro but the function type was notvalid.


System programmer responseThis should not occur. If it does, contact your IBMprogramming service representative.

ModuleDXCSTG

0001C6 DECBC - INVALID LEVELREFERENCE

ExplanationAn ECB-controlled program issued a DECBCFUNC=SWAPBLK monitor-request macro that specifieda data level that was invalid. Valid ECB level referencesare D0 (value 0), D1 (value 8), and so on up to DF(value decimal 120).



ModuleDXCSTG

0001D1 TRACE - INVALID ENTRYCONDITIONS


ExplanationA program entered the ALCS ECB-controlled programCGTD with incorrect entry conditions.




ModuleCGTD

0001D2 TRACE LOGIC ERROR

ExplanationThere is an internal logic error in an ALCS routine.Either there is no buffer for trace, or the buffer is toosmall.




ModuleDXCGTF

0001D3 ERROR STOPPING CONV TRACE

ExplanationThe ALCS trace facility was unable to stop aconversational trace.




ModuleCGTD

0001D4 ERROR RELEASING CONV TRACECONTROL AREA

ExplanationThe ALCS trace facility was unable to release aconversational trace control area.




ModuleCGTD

0001D5 LOGIC ERROR -- INVALID GTFCCRETURN CODE

ExplanationThe ZTRAC command processor detected an internallogic error in an ALCS routine.




ModuleCGTZ

0001D8 ALCS THROTTLE -- INTERNALERROR

ExplanationALCS detected an internal error while processing aZCTHR command or THRTC monitor-request macro.



System programmer responseThis problem should not occur. If it does, contact yourIBM programming support representative.

ModuleCTH1, CTH2, CTH3

0001D9 INTERNAL ERROR

ExplanationALCS detected an internal error.



System programmer responseThis problem can not occur. Inform your IBMprogramming support representative.

ModuleCTH3, CTH4

0001E0 SYNCC - ADDRESS SUPPLIED NOTWITHIN GLOBAL AREA

ExplanationAn ECB-controlled program issued a SYNCC monitor-request macro, but the address of the global fieldpassed to the monitor is not within the global areaaddress range.



ModuleDXCSNC

0001E1 GLOBAL TOO LARGE TO FIT IN XCFBUFFER

ExplanationALCS is trying to derive the size of buffer requiredto read/write a global record/field from/to a couplingfacility cache structure. The maximum size of thebuffer is 64K and the global record/field size is greaterthan that.


Operator responseIf ALCS goes catastrophic, then activate the alternateALCS if there is one, or restart ALCS. If this is anisolated instance, follow your normal procedure for anon-urgent problem. If it happens repeatedly, informyour system programmer.

System programmer responseThe size of the global record/field is derived fromthe global load control programs. Check that theseprograms assembled without error; if any errors werereported, correct them and reassemble the programs.Check that the specified size of any global record is notgreater than 64K. If it is, reduce the size of the globalrecord. If the error is in an IBM-supplied program,inform your IBM programming support representative.

ModuleDXCKPM, DXCKPT, DXCSNC


0001E2 SYNCC - GLOBAL TOO LARGE FORCACHE ENTRY

ExplanationAn ECB-controlled program issued a SYNCC monitor-request macro, but ALCS has found that the globalrecord/field is too large for the maximum size of a dataentry as currently defined in the coupling facility cachestructure.


System programmer responseThe size of the global record/field is derived fromthe global load control programs. Check that theseprograms assembled without error; if any errorswere reported, correct them and reassemble theprograms. If not, inform your IBM programmingsupport representative.

Programmer responseInform your System Programmer.

ModuleDXCSNC

0001E3 UNEXPECTED RETURN CODEFROM XES REQUEST

ExplanationALCS received an unexpected return code from arequest for an XES service.


Operator responseIf ALCS goes catastrophic, then activate the alternateALCS if there is one, or restart ALCS. If this is anisolated instance, follow your normal procedure for anon-urgent problem. If it happens repeatedly, informyour System Programmer.


ModuleDXCKPM, DXCKPT, DXCSNC

0001F0 CRYPC - ICSF NOT SUPPORTED

ExplanationAn ECB-controlled program issued a CRYPC macro,but this ALCS system does not support communicatingwith ICSF.


Operator responseActivate an ALCS system that supports communicationwith ICSF.

User responseIf you intend to run programs that use the CRYPCmacro, you must activate ICSF on the same z/OSimage and generate ALCS with ICSF support.

ModuleDXCICSF

0001F1 CRYPC - PARAMETER LIST NOTACCESSIBLE

ExplanationAn ECB-controlled program issued a CRYPC macro,but the parameter list that was specified is notin accessible storage or the parameters that areaddressed by the parameter list are not accessible.The output parameter must have write access.



ModuleDXCICSF

0001F2 CRYPC - INVALID LENGTH

ExplanationThe length of the data to be encrypted or decrypted isnot valid. The length must be 1 - 4096 characters.


System actionALCS returns a return code of 8 to the application.


ModuleDXCICSF

0001F3 CRYPC - INVALID PARAMETERS

ExplanationOne of the parameters that was passed to theDXCICSF monitor routine is not valid.


System programmer responseThis error should not occur because the assemblershould flag any invalid parameters on the CRYPCmacro call. The parameter is either the function orthe key type. Inform your IBM programming supportrepresentative.

ModuleDXCICSF

0001F4 CRYPC - NO IOCB AVAILABLE

ExplanationAn ECB-controlled program issued a CRYPC macro butALCS needs an IOCB to process the request. All exceptone of the IOCBs are in use. (ALCS cannot dispensethe last IOCB.)


System programmer responseCheck the system error dump to see why the IOCBsare in use. The shortage of IOCBs can indicate, forexample, one of the following conditions:

• An exceptional amount and type of work requiredextra IOCBs.


ModuleDXCICSF

0001F5 ICSF SUBTASK ABEND

ExplanationThe subtask that ALCS attaches in order to processCRYPC macro requests ended abnormally.

System actionALCS terminates any entry that was using the subtask.

Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. Generalregister 15 (RDB) contains the address of a 72-bytearea of storage that contains the PSW and generalregisters 0 - 15.

ModuleDXCICSF

000200 HTTPC -- HTTP CLIENT SERVICESNOT SUPPORTED

ExplanationAn ECB-controlled program issued a HTTP CLIENTcall but this ALCS system does not support the HTTPclient.


Operator responseActivate an ALCS system that supports the HTTPClient.

User responseIf you intend to run programs which use the HTTPclient, you must generate ALCS with HTTP Clientsupport.

ModuleDXCJSON

000201 HTTPC -- PARAMETER LIST NOTACCESSIBLE


ExplanationAn ECB-controlled program issued a HTTP Client callbut the parameter list specified is not in accessiblestorage or the parameters addressed by the parameterlist are not accessible.



ModuleDXCHTTP

000202 HTTPC -- INVALID PARAMETER

ExplanationAn ECB-controlled program issued a HTTP Client callbut the parameter specified is invalid.



ModuleDXCHTTP

000204 HTTPC – EXIT SUBTASK ABEND

ExplanationThe subtask that ALCS uses to do HTTP handle clean-up has abended.

System actionThe EXIT subtask is terminated by RTM and ALCS willcreate a new Exit subtask.


Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. General

register 1 (RG1) points to a storage area containing thePSW and general registers at the time of the error.The PSW is in an 8-byte field at displacement X'28'into this storage area.The general registers, starting with general register 0are in 16 consecutive fullwords at displacement X'30'into this storage area.

ModuleDXCHTTP

000205 HTTPC -- CONNECTION SUBTASKABEND

ExplanationA subtask that ALCS uses to perform application HTTPClient calls has abended.

System actionALCS terminates the Entry. The Connection subtaskis terminated by RTM and ALCS will create a newConnection subtask.


Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. Generalregister 1 (RG1) points to a storage area containing thePSW and general registers at the time of the error.The PSW is in an 8-byte field at displacement X'28'into this storage area.The general registers, starting with general register 0are in 16 consecutive fullwords at displacement X'30'into this storage area.

ModuleDXCHTTP

000206 HTTPC -- SUBTASK TABLE FULL

ExplanationThe subtask table has no available slots.

System actionALCS terminates the Entry.


System programmer responseIncrease the number of HTTP subtasks on the SCTGENHTTP= parameter, rebuild the System Table andrestart ALCS with the new System Table.

ModuleDXCHTTP

000207 HTTPC -- REQUEST HANDLETABLE FULL

ExplanationThe request handle table has no available slots.


System programmer responseIncrease the number of HTTP request handles on theSCTGEN HTTP= parameter, rebuild the System tableand restart ALCS with the new System table.

ModuleDXCHTTP

000208 HTTPC -- CONNECTION SUBTASKABEND - ECB TERMINATED

ExplanationA subtask that ALCS uses to perform application HTTPClient calls has abended.

System actionALCS terminates the Entry. The Connection subtaskis terminated by RTM and ALCS will create a newConnection subtask.

ModuleDXCHTTP

000210 JSONC -- JSON PARSER SERVICESNOT SUPPORTED

ExplanationAn ECB-controlled program issued a JSON Parser call,but this ALCS system does not support JSON Parserservices.


Operator responseActivate an ALCS system that supports JSON Parserservices.

User responseIf you intend to run programs which use JSON Parserservices, you must generate ALCS with JSON ParserServices support.

ModuleDXCJSON

000211 JSONC -- PARAMETER LIST NOTACCESSIBLE

ExplanationAn ECB-controlled program issued a JSON Parser callbut the parameter list specified is not in accessiblestorage or the parameters addressed by the parameterlist are not accessible.



ModuleDXCJSON

000212 JSONC -- INVALID PARAMETER

ExplanationAn ECB-controlled program issued a JSON Parser callbut the parameter specified is invalid.



Module:DXCJSON

000213 JSONC -- NO IOCB AVAILABLE


ExplanationAn ECB-controlled program issued a JSON Parser callbut ALCS needs an IOCB to process the request. Allexcept one of the IOCBS are in use (ALCS cannotdispense the last IOCB).


System programmer responseCheck the system error dump to see why the IOCBsare in use. The shortage of IOCBs can indicate forexample:

• An exceptional amount and type of work requiredextra IOCBs. The ALCS generation did not specifyenough IOCBs.


ModuleDXCJSON

000214 JSONC -- JSON SUBTASK ABEND

ExplanationA subtask that ALCS uses to perform JSON Parser callshas abended.

System actionALCS terminates the entry. RTM will terminate theSubtask and ALCS will create a new JSON subtask.


Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. Generalregister 1 (RG1) points to a storage area containing thePSW and general registers at the time of the error.The PSW is in an 8-byte field at displacement X'28'into this storage area.The general registers, starting with general register 0are in 16 consecutive fullwords at displacement X'30'into this storage area.

ModuleDXCJSON

000215 JSONC -– HANDLE TABLE FULL

ExplanationThe Parser Instance Handle table has no availableslots.


System programmer responseIncrease the number of JSON Handles on the JSON=parameter in SCTGEN.Rebuild the System table and restart ALCS with thenew System table.

ModuleDXCJSON

000216 JSONC -- THE HWTJDELCALLABLE SERVICE IS NOTAVAILABLE ON THIS LEVEL OFZ/OS

ExplanationThe HWTJDEL callable service is only available on z/OS2.3 or later.


Programmer responseEither remove the HWTJDEL call or have the z/OSversion upgraded to 2.3 or later.

ModuleDXCJSON

000217 JSONC -- JSON SUBTASK ABEND -ECB TERMINATED

ExplanationALCS terminates the Entry. A subtask that ALCS usesto perform application JSON Parser calls has abended.

System actionThe JSON subtask is terminated by RTM and ALCS willcreate a new JSON subtask.


ModuleDXCJSON

000218 218 JSONC -- HTTP CONNECTIONSUBTASK ABEND

ExplanationA subtask that ALCS uses to perform application JSONParser calls has abended.

System actionALCS terminates the Entry. The Connection subtask isterminated by RTM and ALCS will create a new HTTPConnection subtask.


Problem determinationGeneral register 1 points to a storage area containingthe PSW and general registers at the time of the error.The PSW is in an 8-byte field at displacement X'28'into this storage area.The general registers, starting with general register 0,are in 16 consecutive fullwords at displacement X'30'into this storage area.

ModuleDXCHTTP

000219 JSONC -- HTTP CONNECTIONSUBTASK ABEND - ECBTERMINATED

ExplanationALCS terminates the Entry. A subtask that ALCS usesto perform application JSON calls has abended.

System actionALCS terminates the entry. The HTTP Connectionsubtask is terminated by RTM and ALCS will create anew HTTP Connection subtask.

ModuleDXCHTTP

000301 SEND - MONITOR action ERROR

ExplanationALCS detected an error in a monitor routine whileprocessing a SENDC K or ROUTC monitor-requestmacro for an SLC message. Where action is one of:

FINDGET FILERELEASE FILE

System actionALCS discards the message and terminates the entry.


ModuleDXCSLCSN

000302 INPUT LCB - MONITOR RELEASEFILE ERROR

ExplanationALCS detected an error in a monitor release file routinewhile processing an input SLC link control block (LCB).



ModuleDXCSLCIN

000305 SEND - MAXIMUM MESSAGE TEXTEXCEEDED

ExplanationAn ECB-controlled program issued a SENDC Kmonitor-request macro and the message lengthexceeded the maximum message length allowed.




ModuleDXCSLCSN

000306 SEND - NCB NOT ALLOWED

ExplanationAn ECB-controlled program issued a SENDCK,NCB=YES monitor-request macro and did notspecify a Type 3 SLC link.


User responseCheck the ALCS communication generation. Ensurethat this type of macro is only issued for a Type 3 SLClink. Correct the programming error.

ModuleDXCSLCSN

000307 SEND - NOT ALLOWED TO SLC STVRESOURCE

ExplanationAn ECB-controlled program issued a send-typemonitor-request macro, but the destination was asystem test vehicle ( STV ) terminal on an SLC link.


User responseCheck the ALCS communication generation. Ensurethat SLC resources are not specified as STV resources.Correct the programming error.

ModuleDXCSLCSN

00030A CMD - TEST MESSAGE TEXT ISTOO LONG

ExplanationThere is an internal logic error in an ALCS routine.ALCS could not generate a test message requested bya ZLTST command.

System actionALCS bypasses the test message and continues toprocess the command.


ModuleCMDC, CMDD

00030B RESUME/STOP RCVD FORNONEXISTENT CHANNEL

ExplanationALCS received a resume or stop link control block(LCB) on an SLC link and the LCB referred to a linkchannel number that was out of range of valid channelnumbers for the link.


User responseThis is an SLC protocol error. Check that the ALCScommunication generation correctly defines the SLClink. If the problem persists, use (for example) theALCS SLC link trace facility to discover the exactsequence of blocks transmitted on the link.

ModuleDXCSLCIN

00030C SUBSEQUENT ENQ - NOT IN ENQPROCEDURE

ExplanationThere is an internal logic error in an ALCS routine.ALCS detected an error in the internal SLC procedure(subsequent ENQ requested, channel not in ENQprocedure).

System actionALCS ignores the error.



ModuleCMC4, DXCSLCIN

000313 ERROR ON FILING PSEUDO LINKBLOCK

ExplanationALCS detected an error when filing a pool record. Theerror occurred while ALCS was preparing to retransmita multiblock message.

System actionALCS does not retransmit the message.


ModuleCMCY, CMC1

000314 SLC PROTOCOL ERROR - ACK FORUNUSED LABEL

ExplanationALCS received a positive acknowledgment link controlblock (LCB) that completely acknowledged an SLCmultiblock message, but the associated message labelwas not in use.

System actionALCS ignores the LCB.

User responseThis is an SLC protocol error. If the problem persists,use (for example) the ALCS SLC link trace facility todiscover the exact sequence of blocks transmitted onthe link.

ModuleDXCSLCIN

000315 SLC OUTPUT MESSAGE FINDERROR

ExplanationALCS detected an error when reading a pool filerecord. The error occurred while ALCS was preparingto retransmit an SLC multiblock message as a possibleduplicate message.



ModuleCMC1

000316 SLC OUTPUT MESSAGE FILEERROR

ExplanationALCS detected an error when filing a pool file record.The error occurred while ALCS was preparing toretransmit an SLC multiblock message as a possibleduplicate message.



ModuleCMC1

000317 SLC LOGIC ERROR - INVALIDINPUT CRI





ModuleDXCSLCIP

000318 SLC LINK ENVELOPE FORMATERROR

ExplanationALCS detected an error in the contents of the linkenvelope for a message received on an SLC link.


User responseThis is an SLC protocol error. Check that the ALCScommunication generation correctly defines the SLClink. If the problem persists, use (for example) theALCS SLC link trace facility to discover which SLC linkenvelope flags were in error.

ModuleDXCSLCIP

00031E DXCCOMT - INVALID INPUTMESSAGE DISCARDED

ExplanationALCS detected an invalid character (x'00') in an ALCformat input message.


User responseEnsure that ALC format messages do not containinvalid characters.

Problem determinationAt the time of the system error dump, general register1 points to the invalid character and general register 5points to the base of the input message block.

ModuleDXCCOMT

00031F module - INVALID APPLICATIONNAME

ExplanationALCS detected an invalid destination application namefor a message received on an SLC link.


User responseCheck that the remote ALC terminal or SLC link isrouted to a valid ALCS application.

ModuleDXCSLCIP, DXCCOMT

000320 CSMS CALLED WITH NO MESSAGE

ExplanationAn ECB-controlled program called the ALCS SMTPmessage sender program, CSMS, with no outputmessage block attached on storage level 0 (D0).


Programmer responseCorrect the program that called CSMS.

ModuleCSMS

000321 EMAIL LOGIC ERROR - BADRETURN FROM CSO1

ExplanationWhile processing an outbound e-mail SMTP message,ALCS detected a logic error in the e-mail support.

System actionALCS discards the e-mail message.


ModuleCSMS


000322 ERROR FINDING SMTP MESSAGEBLOCK

ExplanationALCS detected an error when trying to read a database record which contains part or all of an e-mailSMTP message. This may be caused by either aninvalid record-id or an invalid file address.

System actionALCS terminates the entry. The SMTP message is lost.

System programmer responseEnsure that the record has not been illegally modifiedby an application program. If it has not, inform yourIBM programming support representative.

ModuleCSI1

000323 SMTP HEADER LINE TOO LONG

ExplanationWhile analyzing an inbound e-mail SMTP message,ALCS detected that the message contained a headerline which was longer than the maximum (1024characters) which ALCS supports.


ModuleCSI1

000324 SMTP HEADER FIELD TOO LONG

ExplanationWhile analyzing an inbound e-mail SMTP message,ALCS detected that the message contained a headerfield which was longer than the maximum (1024characters) which ALCS supports.


ModuleCSI1

000325 INVALID MIME HEADER

ExplanationWhile analyzing an inbound e-mail SMTP message,ALCS detected that the message contained a headerthat was not in the correct format (RFC 822).


ModuleCSI1

000326 EMAIL CONVERSION TO BASE64FAILED

ExplanationAn ECB-controlled program called the ALCS SMTPmessage sender program, CSMS, and the body of themessage was not in EBCDIC. ALCS could not convertthe message body into base64 code because it is toolarge.

System actionALCS discards the e-mail message.


ModuleCSMS

000327 E-MAIL ERROR RETRIEVINGMESSAGE RECORD

ExplanationALCS was unable to process the outbound e-mailmessage queue because it was unable to retrieve amessage record.

System actionIf the condition occurs during ZMAIL QUEUE,PURGEcommand processing, ALCS sends an error response,otherwise ALCS terminates the entry. ALCS discardsany messages on the outbound e-mail messagequeue.

System programmer responseEnsure that the record type #KPTRI (system keypointrecord) ordinal number 13 has not been illegallymodified by a user application program. (The hash


(#) character is represented differently by someequipment; it is the EBCDIC X'7B' character.) If ithas not, then inform your IBM programming supportrepresentative.

ModuleCSMB, CSMM

000328 E-MAIL ERROR RETRIEVINGKEYPOINT RECORD

ExplanationALCS was unable to access the outbound e-mailmessage queue because it was unable to retrieve thekeypoint record.

System actionIf the condition occurs during ZMAIL QUEUEcommand processing, ALCS sends an error response.Otherwise ALCS terminates the entry and if processingan outbound e-mail SMTP message (in transfer vectorCSMA), the e-mail message is lost.

System programmer responseEnsure that the record type #KPTRI (system keypointrecord) ordinal number 13 has not been illegallymodified by a user application program. (The hash(#) character is represented differently by someequipment; it is the EBCDIC X'7B' character.) If ithas not, then inform your IBM programming supportrepresentative.

ModuleCSMB, CSMM

000329 E-MAIL KEYPOINT RECORDINITIALIZED

ExplanationWhile processing the outbound e-mail message queue,ALCS was unable to access the queue due to anID (record identifier) or RCC (record code check)mismatch when retrieving the keypoint record.

System actionALCS initializes the keypoint record. Any outbound e-mail messages on the queue are discarded. The statusof the outbound e-mail message queue is started.

System programmer responseIf this is the first time the outbound e-mail messagequeue is used, this message is normal. At any othertime, ensure that the record type #KPTRI (systemkeypoint record) ordinal number 13 has not beenillegally modified by a user application program. (Thehash (#) character is represented differently by someequipment; it is the EBCDIC X'7B' character.) If ithas not, then inform your IBM programming supportrepresentative.

ModuleCSMB, CSMM

00032A CSMS CALLED WITH INVALIDSTORAGE BLOCK SIZE

ExplanationAn ECB-controlled program called the ALCS SMTPmessage sender program, CSMS, with an outputmessage block attached on storage level 0 (D0). Thisblock is not large enough to contain the message in theformat defined by the DXCSMTM macro.



ModuleCSMS

00032B E-MAIL ERROR RETRIEVINGOPERATING VALUES

ExplanationALCS was unable to process the outbound e-mailmessage queue because it was unable to retrievethe e-mail operating values using the SOCKC monitor-request macro.

System actionALCS terminates the entry and stops processing theoutbound e-mail message queue.



ModuleCSMB

000330 E-MAIL OUTBOUND MESSAGEQUEUE CORRUPTED

ExplanationALCS detected corruption of the fields it uses tomanage the outbound e-mail message queue.

System actionALCS initializes the control fields in the keypointrecord. Any outbound e-mail messages on the queueare discarded.

System programmer responseEnsure that the record type #KPTRI (system keypointrecord) ordinal number 13 has not been illegallymodified by a user application program. (The hash(#) character is represented differently by someequipment; it is the EBCDIC X'7B' character.) If ithas not, then inform your IBM programming supportrepresentative.

ModuleCSMB, CSMM

000333 COMIC -- UNEXPECTEDCONDITION

ExplanationWhile retrieving data from the communication tables,ALCS detected that they are corrupted.



ModuleDXCCOMM

000334 COMMUNICATION LOGIC ERROR -type

ExplanationWhile updating the communication tables, ALCSdetected that they are corrupted.



System programmer responseDepends on type:

COMCCIf this error occurs inform your IBM programmingsupport representative.

TABLE UPDATECheck that all stages of the communicationgeneration have been carried out correctly andwithout error. If there are no errors in thecommunication generation, then inform your IBMprogramming support representative.

ModuleDXCCOMM

000335 UNKNOWN LDTYPE IN COMMSCONFIG LOAD MODULE

ExplanationDuring the online loading of a communication loadmodule, the ALCS monitor routines detected anunknown LDTYPE. The LDTYPE is specified onthe COMDEF macro in the communication stage 1generation.


System programmer responseCheck that all stages of the communication generationhave been carried out correctly and without error.If there are no errors in the communicationgeneration then inform your IBM programming supportrepresentative.


ModuleDXCCOMM

000341 CAN NOT COPY DATA

ExplanationDuring the resource control record (RCR)housekeeping processing, program CQS2 could notcopy data from a message block to an output block.



ModuleCQS2

000343 CAN NOT UPDATE indicator

ExplanationALCS detected an error while updating thecommunication table entry for a terminal, during ahousekeeping activity. The indicator is one of:

PFKEY INDICATORSCROLL INDICATORRCR CHECKED INDICATORREQUEST PRINTER INDICATORSCROLL LOG INDICATORRETRIEVE ACTIVE INDICATORREDIRECTION INDICATORSHADOWING INDICATOR

System actionALCS ignores the error and continues.


ModuleCQS6

000344 CAN NOT UPDATE SCROLLINDICATOR

ExplanationDuring the resource control record (RCR)housekeeping processing, program CQS2 was unableto set the COMMS table indicator which indicates one ormore scrollable output files exist for a terminal.



ModuleCQS2

000345 CAN NOT UPDATE TRANSACTIONACTIVE INDICATOR

ExplanationResetting the transaction active bit in the COMMS tablefailed.

System actionALCS exits the ECB and continues.


ModuleCUM2

000346 INVALID CRI SPECIFIED

ExplanationAn application program issued a ROUTC with theUMSG indicator set, but the CRI in the routing controlparameter list is not valid.

System actionALCS exits the ECB and continues.

User responseCheck the calling program. Make sure the applicationsets up a correct RCPL before issuing the ROUTC.


ModuleCUM5

000347 CAN NOT PROCESS

ExplanationAn application program issued a ROUTC with theUMSG indicator set, but an internal error occurred. Thecreation of a ZSNDU command line failed.

System actionALCS exits the ECB and continues processing.


ModuleCUM5

000348 INVALID ZSNDU PARAMETERS

ExplanationProgram CUM1 issued a ROUTC with the UMSG indicatorset, but there was an error in the ZSNDU parameters- probably a wrong time-out value in the installation-wide exit AUM3.

System actionALCS exits the ECB and continues processing.

User responseIf the installation-wide exit caused the error, correctit. Otherwise, ask your system programmer to informyour IBM programming support representative.

ModuleCUM5

000351 RESOURCE IS NOT APPC

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to an APPCresource, but ALCS found that the resource type wasnot valid.


Programmer responseThis error should not occur. If it does, ask yoursystem programmer to inform your IBM programmingrepresentative.

ModuleDXCCOLI

000352 APPC RESOURCE IS INACTIVE

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to an APPCresource, but the destination resource was not active.


Programmer responseUse the COMIC monitor-request macro to determine ifthe destination APPC resource is active before callingROUTC.

ModuleDXCCOLI

000353 APPC SEND CONVERSATION NOTALLOCATED

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to an APPCresource, but there was no conversation allocated forsending the data.



ModuleDXCCOLI

000354 SEND TO TYPE3 APPC RESOURCENOT SUPPORTED


ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to an APPCresource, but the destination resource is definedas COMDEF PRTCOL=TYPE3 in the communicationgeneration.


User responseCheck that the resource is correctly defined in thecommunication generation.

ModuleDXCCOLI

000360 CWW1 - UNKNOWN ORIGINATOR

ExplanationThe ALCS Web server received input with an unknownoriginator CRI.

User responseThis error should not occur. If it does, contact yourIBM programming representative.

000361 CWW1 - ORIGINATOR NOT TCP/IP

ExplanationThe ALCS Web server received input with an originatorCRI that is not defined as a TCP/IP resource.

User responseThis error should not occur. If it does, contact yourIBM programming representative.

000362 CWW1 - HFS UNUSABLE

ExplanationThe ALCS Web server was not able to access the ALCShierarchical file system (HFS).

Operator responseNotify your system programmer. The ALCS Web serveris unusable.

System programmer responseYou may be able to recover the ALCS HFS by restoringthe record #KPTRI ordinal 9 from the ALCS databaseupdate log.

Alternatively, you can reinitialize the ALCS HFS byresetting the record ID of #KPTRI(9) to binary zeros,using the ZAFIL command. This deletes the entirecontents of the ALCS HFS - you must reload all yourfiles from your PC copies.

Alternatively, restore the ALCS real-time database.

000363 CWW3 - UNABLE TO READ HFSOBJECT

ExplanationThe ALCS Web server was not able to access an objectin the ALCS hierarchical file system (HFS).

Operator responseNotify your system programmer.

System programmer responseReload the object from your PC copy.

000364 CWW5 - INVALID ECB LEVELSPECIFIED

ExplanationA program entered module CWW5, but the data levelspecified in general register 14 is invalid.

System actionThe ALCS web server sends an error response.


000365 CWW5 - STORAGE LEVEL NOT INUSE

ExplanationA program entered module CWW5, but the levelspecified in general register 14 is not in use.

System actionThe ALCS web server sends an error response.



000366 CWW5 - INVALID RECORD ID

ExplanationA Web program entered program CWW5, but thestorage block attached at the specified ECB level doesnot contain a record belonging to the ALCS output file(created by DISPC ADD macro).

System actionThe ALCS Web server sends an error response.


000367 CWW5 - NO LINES IN OUTPUTFILE

ExplanationA Web program entered module CWW5, but no DISPCADD calls were issued to add one or more HTML textlines to the ALCS output file.



000368 CWW5 - CANNOT RETRIEVEOUTPUT MSG RECORD

ExplanationA find error occurred on the retrieval of an ALCS outputmessage record while building a Web server Senderdata record.


System programmer responseExamine the system error dump and determine thecause of the error.

If it is due to a record ID error, check whether thedatabase is corrupted (for example, because of poolproblems).

If it is due to a hardware error, get the unit serviced.

000369 CWW1 - INCORRECT RETURNCONDITIONS FROM WEBPROGRAM

ExplanationA Web program returned to program CWW1 usingBACKC in order to select a Web page, but the returnconditions were incorrect.


Programmer responseCorrect the Web program to ensure the correctconditions are set up before you return to CWW1 usingBACKC.

00036A CWW1 - LOOP DETECTED INDYNAMIC PAGE SELECTION

ExplanationA Web program returned to program CWW1 usingBACKC in order to select a Web page, but themaximum number of nested Web programs selectedhas been reached. ALCS assumes an unrecoverableloop has occurred.


System programmer responseYou may only dynamically select up to a maximum offive nested Web programs. Check your Web programsto ensure that no more than five nested Web programsare selected. Check also that your Web program is notselecting itself.

00036B CWW6 - UNABLE TO READ HFSOBJECT

ExplanationThe ALCS Web server was not able to access an objectin the ALCS hierarchical file system (HFS).

Operator responseNotify your system programmer.

System programmer responseReload the object from your PC copy.


00036C CWW6 - HFS UNUSABLE

ExplanationThe ALCS Web server was not able to access the ALCShierarchical file system (HFS).

Operator responseNotify your system programmer. The ALCS Web serveris unusable.

System programmer responseYou may be able to recover the ALCS HFS by restoringthe record #KPTRI ordinal 9 from the ALCS databaseupdate log.

Alternatively, you can reinitialize the ALCS HFS byresetting the record ID of #KPTRI(9) to binary zeros,using the ZAFIL command. This deletes the entirecontents of the ALCS HFS - you must reload all yourfiles from your PC copies.

Alternatively, restore the ALCS real-time database.

00036D CWW6 - LOOP DETECTED IN SSIPROCESSING

ExplanationWeb pages may include the text of another file byusing the #include SSI directive. This file may alsoinclude the text of another file. This is known asnesting. ALCS has detected more than 5 levels ofnesting. ALCS assumes an unrecoverable loop hasoccurred.


System programmer responseCorrect your Web pages. Ensure that no more than5 levels of #include nesting is present in yourpages. Check also that your pages do not #includethemselves.

00036E UNABLE TO READ HFS STATECONTROL BLOCK

ExplanationALCS could not read the hierarchical file system (HFS)state control block for a resource.

System actionALCS allocates a new HFS state control record andcontinues.

00036F CWW2 - OUTPUT MESSAGE NOTATTACHED

ExplanationA Web program entered program CWW2, but there isno OMSG block attached at ECB storage level D0.

System actionALCS terminates the entry and closes the originatingWeb connection.


000370 UNABLE TO READ HFS DIRECTORY

ExplanationALCS was not able to access a directory in the ALCShierarchical file system (HFS).

000371 LOGIC ERROR - WILDC WORKAREA TOO SMALL

ExplanationAn internal error occurred in ALCS hierarchical filesystem (HFS) processing. The work area provided toWILDC was too small.


System programmer responseThis error should not occur. If it does, contact yourIBM programming representative.

000373 UNABLE TO OPEN HFS

ExplanationALCS was not able to open the ALCS hierarchical filesystem (HFS).



System programmer responseYou may be able to recover the ALCS HFS by restoringthe record #KPTRI ordinal 9 from the ALCS data baseupdate log. Alternatively, you can reinitialize the ALCSHFS by resetting the record ID of #KPTRI(9) to binaryzeros, using the ZAFIL command. This deletes theentire contents of the ALCS HFS - you must reload allyour files from your PC copies. Alternatively, restorethe ALCS real-time data base.

ModuleCHFC

000374 UNABLE TO READ HFS LONG-NAME

ExplanationALCS was not able to access the component of theALCS hierarchical file system (HFS) that contains thefull name of an object with a long name.



ModuleCHFC

00037A FILE TRANSFER - UNEXPECTEDINPUT

ExplanationThe terminal (PC) which initiated the file transfertransmitted data to ALCS which does not conform tothe IBM 3270-PC file transfer protocol.

System actionALCS terminates the file transfer.

User responseInform your PC administrator. If this PC is able totransfer files successfully to other IBM host systemssuch as VM/CMS or MVS/TSO, then ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleCHFP

00037B FILE TRANSFER - NOT DDNTERMINAL

ExplanationThe terminal (PC) which initiated the file transfer doesnot support the 3270 Distributed Data ManagementDDN protocol.

System actionALCS terminates the file transfer.

User responseInform your PC administrator. If this PC is able totransfer files successfully to other IBM host systemssuch as VM/CMS or MVS/TSO, then ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleCHFP

0003B0 ROUTC/SENDC/SPOCC - NOSUITABLE MATIP SESSION

ExplanationAn ECB-controlled program issued a ROUTC, SENDC, orSPOCC monitor-request macro to send a message toan ALC display or printer terminal connected throughthe TCP/IP network. The current TCP/IP connectionfor this terminal is defined as MATIP Type A, but theMATIP session is stopped or reconfiguring or it doesnot include this terminal.


ModuleDXCSOCA

0003B1 ROUTC/SENDC/SPOCC - NOTCP/IP CONNECTION

ExplanationAn ECB-controlled program issued a ROUTC, SENDC, orSPOCC monitor-request macro to send a message toan ALC display or printer terminal connected through


the TCP/IP network. There is no current TCP/IPconnection for this terminal.


ModuleDXCSOCA

0003B2 ROUTC/SENDC/SPOCC - TCP/IPCONNECTION IS INACTIVE

ExplanationAn ECB-controlled program issued a ROUTC, SENDC, orSPOCC monitor-request macro to send a message toan ALC display or printer terminal connected throughthe TCP/IP network. The current TCP/IP connection forthis terminal is inactive or being inactivated.


ModuleDXCSOCA

0003B6 ROUTC/SENDC/SPOCC - TCP/IPPROTOCOL NOT SUPPORTED

ExplanationAn ECB-controlled program issued a ROUTC, SENDC, orSPOCC monitor-request macro to send a message toan ALC display or printer terminal connected throughthe TCP/IP network. The current TCP/IP connection forthis terminal is not the correct type for terminal traffic.


ModuleDXCSOCA

0003B8 ROUTC/SENDC/SPOCC - NO ROOMFOR MATIP HEADER

ExplanationAn ECB-controlled program issued a ROUTC, SENDC, orSPOCC monitor-request macro to send a message toan ALC display or printer terminal connected throughthe TCP/IP network. ALCS can not obtain a storage

block that is large enough to contain the outputmessage text plus the MATIP packet header.


ModuleDXCSOCA

0003BC MATIP - TERMINAL NOT IN THISSESSION

ExplanationALCS received a message from an ALC displayor printer terminal connected through the TCP/IPnetwork, using a MATIP session. However the MATIPsession does not currently include this terminaladdress.


ModuleDXCSOCA

0003C0 MATIP - NO STORAGE AVAILABLEFOR ASCU LIST

ExplanationALCS received a MATIP Session Open or Open Confirmcommand. ALCS can not obtain space (MVS GETMAINmacro) in which to build the required list of ASCUaddresses.

System actionFor Session Open, ALCS rejects the MATIP session. ForOpen Confirm, ALCS closes the MATIP session.

ModuleDXCSOCA

0003C1 MATIP - NO CORRECT ASCUS

ExplanationALCS received a MATIP Session Open command thatcontains a list of ASCU addresses. None of theseaddresses is valid.


System actionALCS rejects the MATIP session.

ModuleDXCSOCA

0003C2 MATIP - NO CORRECT ASCUS

ExplanationALCS received a MATIP Open Confirm command thatcontains a list of ASCU addresses. None of theseaddresses is valid.

System actionALCS closes the MATIP session.

ModuleDXCSOCA

000400 ECB LOGIC ERROR

ExplanationThe ALCS online monitor detected an internal logicerror when handling an ECB.




Problem determinationAt the time of the system error dump, general register15 (RDB) identifies the error condition:

R15

Routine Condition

0 Release ECB Invalid ECB address

1 Release ECB Invalid block pointer

2 Release ECB Invalid block address

3 Release ECB Storage unit not in use

R15

Routine Condition

4 Release ECB Storage unit on queue

5 Release ECB ECB not in use

6 Release ECB ECB on queue

7 Release ECB Overflow SU Type 1 not inuse

8 Release ECB Overflow SU Type 1 onqueue

9 Release ECB Overflow SU Type 2/3 notin use

10 Release ECB Overflow SU Type 2/3 onqueue

11 Add to queue ECB on queue

12 Add to queue ECB quarantined

13 Locked dispatcher ECB not in use

14 Locked dispatcher ECB not on queue

15 Lockless dispatcher ECB not in use

16 Lockless dispatcher ECB not on queue

The system error dump includes two system errordump areas. Area 2 contains information about thefailing entry (block descriptor, ECB descriptor, ECBprefix, and ECB). Area 3 contains the nucleus savearea for each CPU loop.

The ECB descriptor contains additional informationwhich may be useful for problem determination. Thisincludes the value of the TOD clock at the time theerror was detected, and events during the entry's life.

ModuleDXCNUC, DXCSTM

000401 IOCB LOGIC ERROR

ExplanationThe ALCS online monitor detected an internal logicerror when handling an I/O control block (IOCB).





ModuleDXCNUC, DXCSTM, DXCDSP

000402 ENTRY ACTIVATED AFTER FORCEREQUEST

ExplanationAn entry resumed processing after it was purged by aZPURG Force command.

System actionALCS terminates the entry, and continues. ALCS marksthe storage unit containing the ECB for the entry,together with any storage units that are chained fromit, as quarantined. This ensures that the storage unit(s)will not be dispensed again until ALCS is restarted.

Operator responseInform the application owner.

ModuleDXCNUC

000403 ECB CONSISTENCY ERROR

ExplanationALCS detected corruption of an ECB. This is most likelycaused by the application working through data andstoring outside the ECB work areas.

System actionA system dump is taken and the entry continuesprocessing. If the error is occurring frequently, onlyone dump is taken each minute.


ModuleDXCSTM

000409 Error return from IFAUSAGEmacro -- ACTION=REGISTERREQUEST=functionbegin orREQUEST=functionend

ExplanationAn error occurred when ALCS executed the IFAUSAGEmacro to register for, to begin, or to end MeasuredUsage Licensing Charge recording.

This error can only occur at initialization or during aRecoup run. The return code is in register 15.




ModuleDXCMULC

000410 ENTRY STORAGE LIMIT EXCEEDED

ExplanationAn ECB-controlled program issued a GETCC or impliedget storage monitor-request macro that exceeded theentry storage limit. The ALCS generation specifies twoentry storage limits; the entry can use the SLIMCmonitor-request macro to reset one, but the other isfixed. This error occurs if the entry exceeds eitherlimit.


User responseIf the entry exceeded the limit that SLIMC can reset,and if the entry genuinely needs a large amount ofstorage, then include a SLIMC monitor-request macroin the application to increase the entry storage limit forthis type of entry.

ModuleDXCSTM

000411 GETCC - INVALID GET STORAGEBLOCK TYPE


ExplanationAn ECB-controlled program issued a GETCC monitor-request macro with an invalid storage block type code.Valid block type codes are L0 (value hexadecimal 11),L1 (value hexadecimal 21), and so on.



ModuleDXCSTG

000412 GETCC - INVALID GET STORAGERECORD ID

ExplanationAn ECB-controlled program issued a GETCC monitor-request macro with an unknown record identifier (ID).


User responseCheck the record ID that the application specifiesagainst the record IDs in the ALCS generation.


ModuleDXCSTG

000413 GETCC - INVALID GET STORAGERECORD SIZE

ExplanationAn ECB-controlled program issued a GETCC monitor-request macro, but there is no storage block with auser size large enough to contain the size requested.



ModuleDXCSTG

000414 INVALID GET STORAGE BLOCKTYPE

ExplanationAn ECB-controlled program issued an implied getstorage monitor-request macro with an invalid storageblock type code. Valid block type codes are L0 (valuehexadecimal 11), L1 (value hexadecimal 21), and soon.



ModuleDXCSTM

000415 NO AVAILABLE IOCBS

ExplanationALCS needs an I/O control block (IOCB). All except oneof the IOCBs are in use (ALCS cannot dispense the lastIOCB).









ModuleDXCSTM

000416 NO AVAILABLE STORAGE UNITS

ExplanationALCS needs to create a new entry or an existing entryrequires more storage. All except one of the storageunits are in use (ALCS cannot dispense the last storageunit).



System programmer responseCheck the system error dump to see why the storageunits are in use. The shortage of storage units canindicate, for example:

• The ALCS generation or command specifiedunsuitable activity control values. This can allowALCS to start processing too many entries for theavailable number of storage units.

• An exceptional amount or type of work requires extrastorage units.

• The ALCS generation did not specify enough storageunits.

ModuleDXCGTC, DXCSTM

000417 NO STORAGE FOR LIST SERVICE

ExplanationThere is a deadlock. ALCS cannot complete processingfor existing entries and it cannot start processing fornew entries.



System programmer responseExamine the dump to find the cause of the high levelof ECB activity. Unless it is caused by a programmingerror, consider allocating more storage.

ModuleDXCDSP

000418 GET STORAGE ERROR - SUSTORAGE CONTROL CORRUPTED

ExplanationDuring get storage processing ALCS detectedcorruption of fields it uses to manage storage for theentry. Most likely caused by the application workingthrough data and stepping outside a storage block.



ModuleDXCSTM

000419 SAVEC - INCORRECT USE OFMACRO

ExplanationAn ECB-controlled program issued a SAVEC monitor-request macro, but the program does not use a localprogram work area.



Programmer responseSpecify LPW=YES on the BEGIN macro or do not issueSAVEC in this program.

ModuleDXCSTG

000420 REHKA - BLOCK ALREADYATTACHED

ExplanationAn ECB-controlled program issued a REHKA monitor-request macro, but a storage block is already presenton the ECB level specified by the LEVEL parameter.



ModuleDXCSTG

000421 REHKA - FIXCEL DATA INVALID

ExplanationAn ECB-controlled program issued a REHKA monitor-request macro, but the data contained in the 8-bytefield specified by the FIXCEL parameter is invalid.



ModuleDXCSTG

000422 REHKA - HOOK DATA LEVELCORRUPTED

ExplanationAn ECB-controlled program issued a REHKA monitor-request macro, but ALCS has found that control data iscorrupted. This may be caused by one of the following:

• An application program illegally modifying ALCScontrol data.

• An ALCS internal logic error.


Programmer responseCorrect the programming error. If the error is notcaused by an application program, then ask yoursystem programmer to inform your IBM programmingsupport representative.

ModuleDXCSTG

000423 REHKA - HOOK ECB CHAININVALID

ExplanationAn ECB-controlled program issued a UNHKA monitor-request macro, but ALCS has found that control data iscorrupted.

This may be caused by:

• An application program illegally modifying ALCScontrol data, or



ModuleDXCSTG

000424 REHKA - HOOK LEVEL COUNTINVALID







ModuleDXCSTG

000425 REHKA - INVALID FIXCELADDRESS

ExplanationAn ECB-controlled program issued a REHKA monitor-request macro, but the address of an 8-byte fieldspecified by the FIXCEL parameter is invalid.



ModuleDXCSTG

000426 REHKA - INVALID LEVEL

ExplanationAn ECB-controlled program issued a REHKA monitor-request macro, but the storage level specified isinvalid.



ModuleDXCSTG

000427 REHKA - NO DATA AVAILABLE

ExplanationAn ECB-controlled program issued a REHKA monitor-request macro, but the storage block specified by theFIXCEL parameter has never been unhooked by theUNHKA monitor-request macro.



ModuleDXCSTG

000428 UNHKA - COUNT AND IN-USEINCONSISTENT






ModuleDXCSTG

000429 UNHKA - INVALID FIXCELADDRESS

ExplanationAn ECB-controlled program issued an UNHKA monitor-request macro, but the address of an 8-byte fieldspecified by the FIXCEL parameter is invalid.



ModuleDXCSTG

00042A UNHKA - INVALID LEVEL ORBLOCK


ExplanationAn ECB-controlled program issued an UNHKA monitor-request macro, but either the storage level specified isinvalid or the storage level contains invalid data.



ModuleDXCSTG

00042B UNHKA - NO BLOCK ATTACHED

ExplanationAn ECB-controlled program issued an UNHKA monitor-request macro, but there is no storage block on theECB level specified by the LEVEL parameter.



ModuleDXCSTG

00043E KEYUC - GLOBLOAD -SYNCHRONIZABLE GLOBALSOVERLAP

ExplanationA KEYUC GLOBLOAD macro has been issued and themain storage address of the synchronizable globalfield overlaps the main storage address range of anentry already in the synchronization table.

System actionALCS ignores this FIELD_SYNCH request so this globalfield is not synchronizable.

System programmer responseCheck that your global load definition programs do notcontain global field synchronization requests for fieldsthat overlap.

ModuleDXCKPM

00043F KEYUC - GLOBLOAD - SYNCHTABLE FULL

ExplanationA KEYUC GLOBLOAD macro has been issued and isattempting to place an additional item in a monitortable which is already full.



Programmer responseThis function of KEYUC is not intended for applicationprograms. If you have used it, replace the call;otherwise inform your system programmer.

ModuleDXCKPM

000440 KEYUC - GLOBLOAD -KEYPOINTING ENABLED

ExplanationALCS detected a serious error while loading the globalarea by means of KEYUC.



ModuleDXCKPM

000441 KEYUC - NOT AUTHORIZED FORGLOBLOAD


ExplanationA message originating from a terminal other thanprime CRAS has caused a KEYUC GLOBLOAD macro.



ModuleDXCKPM

000442 KEYUC - GLOBLOAD ADDRESS ORLENGTH INVALID

ExplanationA KEYUC GLOBLOAD macro has been asked to copyto the global area some data for which ALCS does nothave read/write access.

System programmer responseCheck that your global load control programsassembled without error; if any errors were reported,correct them and reassemble the programs.

If the error is in an IBM-supplied program, inform yourIBM programming support representative.


ModuleDXCKPM

000443 KEYUC - GLOBLOAD FILEADDRESS INVALID

ExplanationA KEYUC GLOBLOAD macro has been given an invalidfile address for a record to be loaded into the globalarea.




ModuleDXCKPM

000444 KEYUC - GLOBLOAD DIRECTORYNUMBER INVALID

ExplanationA KEYUC GLOBLOAD macro has been given an invalidglobal area directory number for a record to be loadedinto the global area.




ModuleDXCKPM

000445 KEYUC - GLOBLOAD - KEYPOINTTABLE FULL

ExplanationA KEYUC GLOBLOAD macro has been issued and isattempting to place an additional item in a monitortable which is already full.




ModuleDXCKPM

000446 KEYUC - GLOBLOAD HEADERSTRIP LEN INVALID

ExplanationA KEYUC GLOBLOAD macro has been issued and theparameter list contains an invalid header strip length.




ModuleDXCKPM

000447 KEYUC - GLOBLOAD FILEADDRESS ALREADY IN TABLE

ExplanationThe KEYUC macro has been issued and the file addressof the keypointable global is already in the monitortable.

System actionALCS loads the global but it is not keypointable.

System programmer responseCheck that your global load control programs donot contain any duplicate fixed file types/ordinals forkeypointable global records.

ModuleDXCKPT

000448 KEYPOINT FAILURE - CTKB FILEADDR INVALID

ExplanationALCS was unable to keypoint (write to DASD) the ALCSmonitor keypoint record, CTKB.




ModuleDXCKPT

000449 KEYPOINT FAILURE - FILEADDRESS INVALID

ExplanationALCS was unable to keypoint (write to DASD) akeypointable global record because the file address inthe global area directory was invalid.




ModuleDXCKPT

00044A KEYPOINT FAILURE - RECORD IDMISMATCH


ExplanationALCS was unable to keypoint (write to DASD) akeypointable global record because the record ID ofthe record in the global area did not match the recordID of the record at the time ALCS loaded it from DASD.

This error indicates that an application program hascorrupted the application global area.

System actionALCS will either end abnormally or produce a dump.Normally ALCS will terminate abnormally, however ifinstallation-wide-exit USRGIDC is installed then ALCSmay produce a dump. See ALCS Installation andCustomization for an explanation of installation-wide-exit USRGIDC.


Programmer responseIdentify the program which corrupted the global areaand correct it.

Problem determinationYou may be able to use the MVS SLIP command tohelp identify the offending program.

ALCS Installation and Customization discusses the useof SLIP with ALCS.

ModuleDXCKPT

00044B KEYPOINT FAILURE - EXITREJECTED KEYPOINT

ExplanationInstallation-wide-exit USRGUPD has detected that thecontents of a global record is corrupt.

System actionEither ALCS will terminate abnormally or will issuea dump. This depends on how the installation-wide-exit has been coded. See ALCS Installation andCustomization for an explanation of installation-wide-exit USRGUPD.

Programmer responseIdentify the program which corrupted the global areaand correct it.

ModuleDXCKPT

000450 CSQLC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued an SQL request thatspecified an invalid parameter.


Programmer responseCorrect the programming error. Or, if the erroris in an IBM-supplied program, ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleDXCSQL

000451 CSQLC - DB2 NOT SUPPORTED

ExplanationAn ECB-controlled program issued an SQL request,but this ALCS system does not support communicationwith DB2.


Operator responseActivate an ALCS system that supports communicationwith DB2.

User responseIf you intend to run programs which issue SQLrequests you must install DB2 on the same MVS imageand generate ALCS with DB2 support. Otherwise,either do not run these programs, or remove any SQLstatements from them.

ModuleDXCSQL


000454 CSQLC - TERMINATIONREQUESTED BY INST EXIT

ExplanationAn ECB-controlled program issued an SQL request, butthe ALCS SQL installation-wide exit has determinedthat the entry should be terminated.


System programmer responseIf the application and/or end user is allowed to issuethis SQL request then you must modify your ALCS SQLinstallation-wide exit routine accordingly.

User responseThis may be an accidental or deliberate securityviolation. We advise you to investigate and take actionto prevent any security violation.

ModuleDXCSQL

000455 CSQLC - SQL SUBTASK FOR THISENTRY ABENDED

ExplanationAn ECB-controlled program issued an SQL request,but the attached subtask that it was using hasended abnormally. ALCS automatically reattaches thesubtask.



ModuleDXCSQL

000456 CSQLC - PROGRAM NOT FOUND

ExplanationAn ECB-controlled program issued an SQL request, butALCS could not locate the active program name in theprogram control table.



ModuleDXCSQL

000457 CSQLC - PROGRAM NOT LOADED

ExplanationAn ECB-controlled program issued an SQL request, butALCS found that the active program is not loaded.



ModuleDXCSQL

000458 CSQLC - NOT STATE CHANGEENTRY

ExplanationAn ECB-controlled program issued a CSQLC RESTARTmonitor-request macro, but it was not the statechange entry.





ModuleDXCSQL

000459 CSQLC - ERROR RETURN FROMDB2

ExplanationAn ECB-controlled program issued an SQL requestwhich resulted in an error return from DB2.

System actionALCS issues message DXC2907E (see “DXC2907E” onpage 167) or DXC2909E (see “DXC2909E” on page167) and then terminates the entry. These messagescontain the return code and the reason code from DB2.

User responseRespond to the return code and reason code fromDB2.

ModuleDXCSQL

00045A SQL SUBTASK ABEND

ExplanationOne of the subtasks that ALCS attaches to process SQLrequests ended abnormally.

System actionALCS terminates any entry that was using the subtask.ALCS automatically reattaches the subtask.

Problem determinationAt the time of the system error dump, general register14 contains the abend completion code. MVS SystemCodes lists abend codes. General register 1 points to astorage area containing the PSW and general registersat the time of the error. The PSW is in an 8-byte field atdisplacement X'28' into this storage area. The generalregisters, starting with general register 0, are in 16consecutive fullwords at displacement X'30' into thisstorage area.

ModuleDXCSQL

00045B DB2 CONNECTION SUBTASKABEND

ExplanationThe subtask that ALCS attaches to process DB2connection and disconnection requests has endedabnormally.


Problem determinationAt the time of the system error dump, general register14 contains the abend completion code. MVS SystemCodes lists abend codes. General register 1 points to astorage area containing the PSW and general registersat the time of the error. The PSW is in an 8-byte field atdisplacement X'28' into this storage area. The generalregisters, starting with general register 0, are in 16consecutive fullwords at displacement X'30' into thisstorage area.

ModuleDXCSQL

00045C CSQLC - SQL PARAMETER LISTNOT ACCESSIBLE

ExplanationAn ECB-controlled program issued an SQL requestthat specified a parameter list in storage that theapplication program did not have write (store) accessto.



ModuleDXCSQL

00045E CSQLC - SQL SUBTASK FOR THISENTRY UNAVAILABLE

ExplanationAn ECB-controlled program was issuing SQL requests,but the subtask it was using cannot continue. Possiblereasons are:

• DB2 has stopped


• The ALCS operator issued ZCSQLDISCONNECT,FORCE.


User responseExamine the system log to determine why DB2stopped.

ModuleDXCSQL

000460 ROUTC - NO END OF MESSAGE

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the message is not correctlyterminated with an end-of-message character.



ModuleDXCCOMQ

000461 ROUTC - NO LINK AVAILABLE

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but there is no communication pathbetween this ALCS and the system that owns thedestination resource.


Operator responseCheck that the destination of the data is correct, andthat the communication generation correctly specifiesthe paths between this ALCS system and any remotesystems.

Start a communication link between the two systems.

ModuleDXCCOMQ

000462 ROUTC - INVALID DESTINATIONIN RCPL

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the destination specified in therouting control parameter list does not exist in thecommunication tables.


User responseCheck that the destination of the data is correct, andthat the communication generation correctly specifiesall the communication resources.


ModuleDXCCOMQ

000463 ROUTC - INVALID ORIGIN IN RCPL

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the origin specified in therouting control parameter list does not exist in thecommunication tables.


User responseCheck that the origin of the data is correct and that thecommunication generation correctly specifies all thecommunication resources.


ModuleDXCCOMQ


000464 ROUTC - INACTIVE DESTINATIONIN RCPL

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the destination specified in therouting control parameter list is marked as inactive inthe communication tables.


Operator responseIf the destination resource is owned by this system,start the resource. If the destination resource is ownedby another system, start the link to the system thatowns the resource.

Problem determinationCheck that the destination of the data is correct.

ModuleDXCCOMQ

000465 ROUTC - PATH LOOP DETECTED

ExplanationBoth the origin and destination are controlled by thisALCS, but the message has been received from a linkbetween two systems.


User responseCheck the routing definitions of all connected systemsand correct any circular definitions. Check that thepaths between all connected systems are correct.

ModuleDXCCOMQ

000466 ROUTC - COMMS LOGIC ERROR -DXCRIT CORRUPT

ExplanationAn error has occurred while trying to obtain the CRI ofa resource owned by another system.


User responseThe communication table DXCRIT is corrupted.Examine any installation-wide exits to ensure that theydo not corrupt the table. If it is not a user error,then ask your system programmer to inform your IBMprogramming support representative.

ModuleDXCCOMQ

000467 ROUTC - NO MATCH FOUND FOROTHER-SYSTEM ID

ExplanationA message has been received from another system,but the other-system identification (OSID) of the originresource is not defined in this system's communicationtables.


User responseCheck the communication generation in both systemsand ensure that they are compatible.

ModuleDXCCOMQ

000468 ROUTC - NO CSID SPECIFIED FORTERMINAL

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the destination resource does nothave an other-system terminal identifier defined for it.


User responseCheck the communication generation to ensure thatthe resource is correctly defined. The CSID parameterof the COMDEF generation macro defines the other-system terminal identifier. ALCS substitutes this value


for the CRI when it sends a message to anothersystem.

ModuleDXCCOMQ

000469 ROUTC - INVALID DESTINATIONRESOURCE TYPE

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the destination resource type wasinvalid. The destination resource must be an ALCSsupported non-WTTY terminal or an application. AROUTC issued to a user device must be processed by acommunication installation-wide exit.


User responseCheck the communication generation to ensure thatthe resource is correctly defined.


ModuleDXCCOMQ

00046A ROUTC - RCPL AREA NOTACCESSIBLE

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro, but the routing control parameter listwas in a storage area that the application program didnot have write (store) access to.



ModuleDXCCOMQ

00046B ROUTC - DESTINATION DOES NOTSUPPORT LARGE MESSAGES

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro with a routing control parameter listindicating that the message is extended format,but the destination is neither an ALC terminal thatconnects to ALCS through TCP/IP, nor a TCP/IPconnection.


ModuleDXCCOMQ

00046C ROUTC - INVALID TRANSLATECODE FOR PPMSG

ExplanationALCS received a message on a message router path.ALCS cannot convert the message from PPMSG formatbecause the translate code is invalid.


User responseCheck that the ALCS communication generationcorrectly defines the message router path, and thatthe path correctly connects the two host systems.General register 6 (RGE) points to the message block inPPMSG format, before any required translation.

ModuleDXCCOMQ

000470 MESSAGE TOO SHORT

ExplanationA program entered the ALCS ECB-controlled programCVIA to send a message, but the length specified forthe message is too small for the message to containany data that can be sent to the resource.



System programmer responseIf the error is in an IBM-supplied program, inform yourIBM programming support representative

Programmer responseIf you have called CVIA, correct the program;otherwise inform your system programmer.

ModuleCVIA

000471 INVALID CRI IN MESSAGE

ExplanationA program entered the ALCS ECB-controlled programCVIA to send a message, but the CRI in the message isnot known to the system.

This system error could occur when the CRI in themessage is the symbolic CRAS CRI for RO CRAS(000000) but there is no RO CRAS defined.


User responseCheck that the message is being sent to the correctresource, and that all resources are defined in thecommunication generation.

ModuleCVIA

000472 DESTINATION NOT ACTIVE

ExplanationA program entered the ALCS ECB-controlled programCVIA to send a message; the CRI specified in themessage is known to the system but it is not availablefor communication.


User responseCheck that:

• The message is being sent to the correct resource• All resources are defined with the correct status in

the communication generation

• All required communication resources are active.

ModuleCVIA

000473 DESTINATION NOT PRINTER ORDISPLAY

ExplanationA program entered the ALCS ECB-controlled programCVIA to send a message, but the destination resourceis not a printer or a display.


User responseCheck that the message is being sent to the correctresource, and that the resource is correctly defined inthe communication generation.

ModuleCVIA

000474 INVALID MESSAGE FORMAT

ExplanationA program entered the ALCS ECB-controlled programCVIA to send a message, but the last character in themessage is not #EOM.


System programmer responseIf the error is in an IBM supplied program inform yourIBM programming support representative

Programmer responseIf you have called CV1A correct the program otherwiseinform your IBM programming support representative

ModuleCVIA

00047F RCR FILE ERROR - CRN-crn


ExplanationALCS was unable to write (FILE error) a resourcecontrol record (RCR).

System actionALCS marks the resource as unusable in thecommunication table and terminates the entry, unlessthe calling program indicated that a return is alwaysneeded.


ModuleCQS1

000480 RCR FACE ERROR - CRN-crnoptional_extension

ExplanationALCS was unable to calculate the file address (FACEerror) while trying to read a resource control record(RCR).

Optional_extension: - ROC SWITCHED (if trying to readthe RCR for RO CRAS).

System actionALCS marks the resource as unusable in thecommunication table and terminates the entry, exceptif the calling program indicated that return is alwaysneeded.

User responseCheck that there are at least as many #CPRCRrecords defined in the DASD generation of ALCS asthere are items in the communication table. (Thehash (#) character is represented differently by someequipment and it is the EBCDIC X''7B'' character.)

ModuleCQS1

000481 RCR FIND ERROR - CRN-crnoptional_extension

ExplanationALCS was unable to read (FIND error) a resourcecontrol record (RCR).

Optional_extension: - ROC SWITCHED (if trying to readthe RCR for RO CRAS).

System actionALCS marks the resource as unusable in thecommunication table and terminates the entry, exceptif the calling program indicated that return is alwaysneeded.


ModuleCQS1

000482 RCR COMIC ERROR - CRI-cri

ExplanationThe CRI as passed by the calling program to retrievethe resource control record (RCR) cannot be found inthe ALCS communication table.

System actionALCS terminates the entry, except if the callingprogram indicated that return is always needed.


User responseCheck the source of the CRI. If the program calling theALCS function is user-written, correct it. If the error isin ALCS, inform your system programmer.

ModuleCPQI, CQS1

000483 RCR RONIC ERROR - CRN-crn

ExplanationThere are no #CPRCR records defined in the system.(The hash (#) character is represented differentlyby some equipment and it is the EBCDIC X''7B''character.)


System actionALCS terminates the entry, except if the callingprogram indicated that return is always needed.


ModuleCQS1

000484 RCR ID CHECK ERROR - CRN-crn

ExplanationWhen ALCS verified the status of the resource controlrecord (RCR) it just retrieved, it encountered the wrongID inside the record.

System actionALCS re-initializes the record according to the resourcedefinition in the ALCS communication generation.


• User corruption of the resource control record (RCR)• Hardware problem.


ModuleCQS1

000485 CAN NOT UPDATE SHADOWINGINDICATOR

ExplanationA ZACOM SHADOW command was issued, but theprogram CPQP was unable to set the communicationtable indicator, which indicates printer shadowing.



ModuleCPQP

000486 ERROR READING MESSAGE type [-CRN-crn]

ExplanationAn error occurred reading a message record from aresource control record (RCR) queue. Type indicateswhich type of record as follows:

FIQFirst (or only) block of the first message on thequeue being processed.

LIQFirst (or only) block of the last message on thequeue being processed.

NXBSecond or subsequent block of a message.

LMTA block of the last message transmitted.

The CRN is omitted if the dump header messageDXC2021 (see “DXC2021E” on page 126) has alreadyprovided it.

System actionALCS reconstructs the queue. One or more messages(or parts of messages) will be lost.


• User corruption of the resource control record (RCR)• User corruption of the message record• Hardware problem.


ModuleCBQC, CBQS, CBQX, CBQZ, CLQP, CLQQ, CLQS,CLQX, CPQP, CPQQ, CPQS, CPQX, CQS2, CSQC,CUM2

000487 INVALID DESTINATION IN RCPL

ExplanationA message to an LU 6.1 link is being returned tothe originating application, but either the applicationno longer exists, or the routing control parameter listcontains an invalid destination when the ROUTC macrois issued.



User responseIf the error was not caused by user programmingthen ask your system programmer to inform your IBMprogramming support representative.

ModuleCLQR, CLQS

000488 INVALID STATUS CODE VALUE

ExplanationA program entered the ALCS ECB-controlled programwith incorrect entry conditions.




ModuleCBQS, CLQC, CPQC, CPQS, CSQC, CQS7

000489 SEND - MESSAGE TOO SHORT

ExplanationThe message contains no data to be transmitted.

System actionALCS ignores the message.



ModuleCPQX

00048A ACK RECEIVED FOR UNUSED RCRQUEUE ITEM

ExplanationThe ALCS ECB-controlled program CSQC was calledwith incorrect entry conditions. The RCR queue itemnumber does not refer to a message on queue.




ModuleCSQC

00048B INVALID LINE NUMBER

ExplanationThe ALCS ECB-controlled program CSQC was calledwith incorrect entry conditions. The SLC line numbercontained in the ECB work area does not exist.





ModuleCSQC

00048C INVALID RCR QUEUE ITEMNUMBER

ExplanationThe ALCS ECB-controlled program CSQC was calledwith incorrect entry conditions. The resource controlrecord (RCR) queue item number is out of range.




ModuleCSQC

00048D APPLICATION NAME NOT FOUND -CRN-crn

ExplanationThe printer acknowledgment is routed to anapplication that no longer exists. If ALCS receives anyanswerbacks from the printer and if they are to beprocessed by a user application, then ALCS tries topass them to the application that is indicated in themessage.

System actionALCS discards the acknowledgment to the applicationand continues processing normally.

User responseCheck the communication generation tables. Ifthe application is still defined, ask your system


ModuleCPQX

00048E CAN NOT UPDATE REDIRECTIONINDICATOR

ExplanationA ZACOM REDIRECT command was issued, but theprogram CPQP was unable to set the communicationtable indicator, which indicates printer redirection.



ModuleCPQP

00048F NOT VIRTUAL SLC LINK

ExplanationAn ECB-controlled program invoked BATAP via ENTRC.The symbolic line number provided by the callingprogram does not represent a virtual SLC link.


User responseCheck the ALCS communication generation andcorrect the program which issued this monitor-requestmacro. If the symbolic line number is correct, or thecalling program is an ALCS program, ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleCBQS

000490 INVALID CRI IN MESSAGE - CRI-cri


ExplanationAn ECB-controlled program issued a CRASC, SENDCL, SLMTC, or SENDC K monitor-request macro tosend a message, or invoked BATAP via ENTRC. TheCRI contained in the message does not exist. Thesemonitor-request macros generate an ENTRC to anECB-controlled monitor program as follows:

CPQSMessage to a display or printer terminal that ALCSowns

CBQS/CBQXMessage to a BATAP link (Type 2 X.25 permanentvirtual circuit (PVC) or MATIP Type B TCP/IPresource).

System actionOne of:

CPQSALCS terminates the entry

CBQS/CBQXALCS terminates the entry, BATAP is unusable forthis session.

User responseCheck the ALCS communication generation andcorrect the program which issued this monitor-requestmacro. If the CRI is correct or the calling program is anALCS program, ask your system programmer to informyour IBM programming support representative.

CBQSAlso terminate and re-establish the session aftercorrecting the problem.

ModuleCBQS, CBQX, CPQS

000491 INVALID MESSAGE LENGTH - CRN-crn

ExplanationAn ECB-controlled program issued a CRASC, SENDCL, SLMTC, SENDC K, or ROUTC monitor-requestmacro to send a message, or invoked BATAP viaENTRC. The message length is not within the limitsas required by ALCS. These monitor-request macrosgenerate an ENTRC to an ECB-controlled monitorprogram as follows:


CBQSMessage to a BATAP link (Type 2 X.25 permanentvirtual circuit (PVC) or MATIP Type B TCP/IPresource).

CLQSMessage to an LU 6.1 link

System actionOne of:

CPQSALCS terminates the entry

CBQSALCS discards the message and returns to thecalling program

CLQSALCS terminates the entry

User responseCheck the message length with ALCS ApplicationProgramming Guide and correct. If the message lengthis correct or the calling program is an ALCS program,ask your system programmer to inform your IBMprogramming support representative.

ModuleCBQS, CLQS, CPQS

000492 NO EOM CHARACTER IN MESSAGE- CRN-crn

ExplanationAn ECB-controlled program issued a CRASC, SENDCL, or SLMTC monitor-request macro to send amessage to an ALCS printer or display terminal. Themessage did not have an end-of-message ( EOM )character in the correct place at the end of themessage. These monitor-request macros generate anENTRC to an ECB-controlled monitor program CPQS.


User responseCheck the message format for the correct position ofthe EOM character. If the message format is corrector the calling program is an ALCS program, ask yoursystem programmer to inform your IBM programmingsupport representative.


ModuleCPQS

000493 FORWARD CHAIN FIND ERROR -CRN-crn

ExplanationAn ECB-controlled program issued a SENDC L orROUTC monitor-request macro to send a message.The CRI contained in the message does not exist.These monitor-request macros generate an ENTRC toan ECB-controlled monitor program as follows:


CLQSMessage to an LU 6.1 link.


User responseCheck the message is properly chained with thecorrect record ID. If the message chain is corrector the calling program is an ALCS program, ask yoursystem programmer to inform your IBM programmingsupport representative.

ModuleCLQS, CPQS

000495 INVALID PRIORITY IN MESSAGE -CRN-crn

ExplanationAn ECB-controlled program issued a CRASC, SENDCL, or SLMTC monitor-request macro to send amessage to an ALCS printer or display terminal. Thesemonitor-request macros generate an ENTRC to anECB-controlled monitor program CPQS. The messagepriority is incorrect. It should be priority 0 (SLMTC) orpriority 1 - 16 (SENDC L, CRASC).


User responseCheck the message priority is correct. If the messagepriority is correct or the calling program is an ALCS

program, ask your system programmer to inform yourIBM programming support representative.

ModuleCPQS

000496 RESOURCE IS NOT A PRINTER -CRN-crn

ExplanationAn ECB-controlled program issued a SLMTC monitor-request macro to send a message to an ALCS printer.This monitor-request macro generates an ENTRC to anECB-controlled monitor program CPQS. However, theresource CRI that was passed in the message is notdefined in the ALCS communication generation as aprinter.


User responseCheck the ALCS communication generation andcorrect the program which issued this monitor-requestmacro. If the CRI is a printer or the calling programis an ALCS program, ask your system programmer toinform your IBM programming support representative.

ModuleCPQS

000497 APPLICATION NAME NOT FOUND -CRN-crn

ExplanationAn ECB-controlled program issued a SENDC Lmonitor-request macro to send a message to anALCS printer or display terminal with the ACK=applparameter. This monitor-request macro generates anENTRC to an ECB-controlled monitor program CPQS.The application in the ACK= parameter is not definedin the ALCS communication generation.


User responseCheck the ALCS communication generation andcorrect the program which issued this monitor-requestmacro. If the application does exist or the callingprogram is an ALCS program, ask your system



ModuleCPQS

000498 APPLICATION NOT ACTIVE - CRN-crn

ExplanationAn ECB-controlled program issued a SENDC Lmonitor-request macro to send a message to anALCS printer or display terminal with the ACK=applparameter. This monitor-request macro generates anENTRC to an ECB-controlled monitor program CPQS.The application in the ACK= parameter does existin the ALCS communication generation, but it is notactive.


User responseVerify why the application is not active and correct. Ifthe application is active or the calling program is anALCS program, ask your system programmer to informyour IBM programming support representative.

ModuleCPQS

000499 PREVIOUS SLMTC OUTSTANDING

ExplanationAn ECB-controlled program issued a SLMTC monitor-request macro to send a message to an ALCS printer.This monitor-request macro generates an ENTRC to anECB-controlled monitor program CPQS. However, theprevious SLMTC macro issued to this printer has notyet been completed or has timed out.

For ALC type printers, the next SLMTC macro cannotbe executed before the previous SLMTC transmittedmessage is completed or timed out. For non- ALC typeprinters there is no time-out.


User responseCorrect the program which issued this monitor-requestmacro. If the previous SLMTC message was alreadycompleted or should have been timed out, or if thecalling program is an ALCS program, ask your systemprogrammer to inform your IBM programming supportrepresentative.

Problem determinationFor further information, see ALCS Installation andCustomization.

00049A INVALID LINE NUMBER INMESSAGE

ExplanationAn ECB-controlled program issued a SENDC K,TYPE=QUEUE monitor-request macro to send a TypeB message on an SLC link. This monitor-request macrogenerates an ENTRC to the ECB-controlled programCSQS. The SLC link number contained in the messageblock does not exist.



ModuleCSQS

00049B SLC LINK NOT STARTED - CRN-crn

ExplanationAn ECB-controlled program issued a SENDC K,TYPE=QUEUE monitor-request macro to send a Type Bmessage on an SLC link. (This monitor-request macrogenerates an ENTRC to the ECB-controlled programCSQS). The SLC link number contained in the messageblock is known to the system, but it is not available forcommunication.


ModuleCSQS

00049C EXITn NOT DEFINED


ExplanationThe relevant resource control record (RCR) is notcorrectly initialized, where n is an integer between 1and 5.

System actionALCS terminates the entry. BATAP is unusable.

Operator responseTerminate the session, and try to re-establish it. If thiserror occurs, ask your system programmer to informyour IBM programming support representative.

ModuleCBQC, CBQS, CBQZ

00049D WTOPC --INVALID BUFFERADDRESS SPECIFIED PROGRAMNAME PN-'name' DISPLACEMENTDSP-'nnnn'

ExplanationAn ECB-controlled program issued a WTOPC monitor-request macro, but the address specified on theBUFFA parameter is not valid.


Programmer responseIf this error occurs in a user-written program thencorrect the program. Otherwise ask your systemprogrammer to inform your IBM programming supportrepresentative.

ModuleCWTO

00049E WTOPC -- INVALIDSUBSTITUTION ADDRESSSPECIFIED

ExplanationAn ALCS monitor routine called WTOPC macro serviceto send a message, but the address of the storage areacontaining substitution data could not be accessed.

System actionALCS continues to build the message, but does notperform any substitution of the message variables.


ModuleDXCWTO

00049F WTOPC - DESTINATION INVALIDOR OMITTED PROGRAMNAME PN-'name' DISPLACEMENTDSP-'nnnn'

ExplanationAn ECB-controlled program issued a WTOPC monitor-request macro that includes message text, but thedestination is not a valid CRI.


Programmer responseCorrect the program to provide a valid destination CRI.

ModuleCWTO

0004A0 CMQIC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued an MQI requestthat specified an invalid parameter.



ModuleDXCMQI


0004A1 CMQIC -- MQSERIES NOTSUPPORTED

ExplanationAn ECB-controlled program issued an MQI request,but this ALCS system does not support communicationwith MQSeries.


Operator responseActivate an ALCS system that supports communicationwith MQSeries.

User responseIf you intend to run programs which issue MQIrequests you must install MQSeries on the same MVSimage and generate ALCS with MQSeries support.Otherwise, do not run these programs, or remove anyMQI statements from them.

ModuleDXCMQI

0004A3 CMQIC -- TERMINATIONREQUESTED BY INST EXIT

ExplanationAn ECB-controlled program issued an MQI request,but the ALCS MQI installation-wide exit hasdetermined that the entry should be terminated.


System programmer responseIf the application or end user is allowed to issue thisMQI request then you must modify your ALCS MQIinstallation-wide exit routine accordingly.

User responseThis may be an accidental or deliberate securityviolation. We advise you to investigate and take actionto prevent any security violation.

ModuleDXCMQI

0004A4 CMQIC -- NOT STATE CHANGEENTRY

ExplanationAn ECB-controlled program issued a CMQIC RESTARTmonitor-request macro, but it was not the statechange entry.




ModuleDXCMQI

0004A5 CMQIC -- CALL PARAMETER LISTNOT ACCESSIBLE

ExplanationAn ECB-controlled program issued an MQI requestthat specified a parameter list in storage that theapplication program did not have write (store) accessto.



ModuleDXCMQI

0004A6 CMQIC -- NO IOCB AVAILABLE

ExplanationAn ECB-controlled program issued an MQI request,but ALCS needs an I/O control block (IOCB) to processthe request. All except one of the IOCBs are in use(ALCS cannot ispense the last IOCB).



Operator responseIf this is an isolated instance, follow your normalprocedure for a non-urgent problem. It it happensrepeatedly, inform your system programmer.







ModuleDXCMQI

0004A7 CMQIC -- MQM SUBTASK HASABENDED

ExplanationAn ECB-controlled program issued an MQI request,but the attached subtask that it was using has endedabnormally.

System actionALCS terminates the entry. ALCS attaches a newsubtask for MQI requests when it processes the nextMQI request or ZCMQI command.


ModuleDXCMQI

0004A8 MQM SUBTASK ABEND

ExplanationThe subtask that ALCS attaches in order to processMQI requests ended abnormally.

System actionALCS terminates any entry that was using the subtask,and disconnects from the MQSeries queue manager.ALCS attaches a new subtask for MQI requests when itprocesses the next MQI request or ZCMQI command.

Operator responseUse the ZCMQI command to connect ALCS to theMQSeries queue manager again.

Problem determinationAt the time of the system error dump, general register14 (RDA) contains the abend completion code. MVSSystem Codes lists abend completion codes. Generalregister 15 (RDB) contains the address of a 72-bytearea of storage containing the PSW and generalregisters 0 through 15 (RAC to RDB) for the time ofthe abend.

ModuleDXCMQI

0004A9 MQM -- INVALID APPLICATION INTRIGGER MESSAGE

ExplanationA trigger message arrived on the MQSeries queuemanager initiation queue, but the application name inthe trigger message application identifier field is notdefined in the ALCS communication generation.

System actionALCS discards the trigger message and waits foranother.

System programmer responseCheck that the initiation queue is defined correctlyin MQSeries, and that it is consistent with theALCS system generation and the ALCS communicationgeneration.

ModuleDXCMQI


0004B0 F.A. LOGIC ERROR -- NO F.A. FORINDEX



Operator responseActivate the alternate ALCS if there is one, or restartALCS. if this is an isolated incident, follow your normalprocedure for a non-urgent problem. If this happensrepeatedly, inform your system programmer.


ModuleDXCFFA

0004B1 NOT ENOUGH STORAGE FOR F.A.CONVERSION TABLE

ExplanationAn ECB-controlled program, or the ALCS monitor,attempted to use a file address for which ALCSneeds conversion tables. ALCS was unable to allocatememory for the tables.

System actionALCS treats the file address as invalid. The recordcannot be accessed. Note that this system error doesnot generate a system error dump.

System programmer responseCheck if your installation limits the maximum size ofa dataspace through the system management facility(SMF) installation-wide exit IEFUSI. If it does then thiserror indicates that the limit is too restrictive for yourALCS requirements. ALCS must be able to obtain adataspace of at least 4*n bytes, where n is the totalnumber of fixed-file and short-term pool file recordsin your ALCS database, plus an allowance for systemfixed file records and for expansion.

If it does not, then this problem should not occur -inform your IBM programming support representative.

ModuleDXCFFA

0004B2 F.A. LOGIC ERROR -- INVALID VFARETURN


System actionALCS ends abnormally



ModuleDXCFFA, DXCFFC

0004B3 F.A. TABLE CORRUPTION --INVALID table F.A.

ExplanationThere is an internal logic error in an ALCS routine. tableis DIRECTORY or INDEX.




ModuleDXCFFA, DXCFFB


0004B4 F.A. LOGIC ERROR -- INVALIDINDEX F.A.






0004B5 F.A. LOGIC ERROR -- INVALIDPOOL RECORD SIZE






0004B6 NOT ENOUGH POOL FOR F.A.CONVERSION

ExplanationAn ECB-controlled program, or the ALCS monitor,attempted to use a file address for which ALCS needsconversion tables. ALCS was unable to allocate poolrecords for the tables.

System actionALCS treats the file address as invalid. The recordcannot be accessed. This system error does notgenerate a system error dump.

Operator responseRun Recoup


ModuleDXCFFA, DXCFFB

0004B7 NOT ENOUGH POOL FOR RECORDALLOCATION

ExplanationAn ECB-controlled program, or the ALCS monitor,attempted to access a newly-created fixed-file, short-term pool file, or system fixed-file record for the firsttime. ALCS was unable to allocate a pool record for thispurpose.

System actionALCS treats the file address as invalid. The recordcannot be accessed. This system error does notgenerate a system error dump.

Operator responseRun Recoup


ModuleDXCFFA


0004B8 DXCFFB LOGIC ERROR - reason


System actionDepends on the reason:

RECORD DELETIONALCS ends abnormally.

TABLE BUILDThe build process terminates.

RELOCATEThe relocate process terminates.

System programmer responseThis error is an indication that the fixed file tablesare corrupted. If it occurs, please inform your IBMprogramming support representative.

ModuleDXCFFB

0004B9 F.A. TABLE CORRUPTION -INVALID IDENTIFIER

ExplanationThe memory copy of a File Address Table record iscorrupted.

System actionALCS marks the record as 'not loaded', and continues.If the record is subsequently addressed, it is reloadedfrom DASD.

Operator responseNo immediate action is required, but this problemshould not occur. Inform your IBM programmingrepresentative.

ModuleDXCFFA

0004C0 CONFIG DATA SET RETRIEVALERROR

ExplanationAn error has occurred in keypointing the statusfollowing a ZDASD COMMIT or a ZDASD BACKOUT.

System actionALCS continues processing but it is no longer possibleto perform a ZDASD LOAD.

System programmer responseRestore a configuration data set and retry thecommand. If the error occurs again contact your IBMsupport representative.

ModuleDXCINTT

0004C1 INVALID RETURN FROMCDFDELET

ExplanationAn error has occurred in deleting fixed file or shortterm pool records following a ZDASD COMMIT or aZDASD BACKOUT.


Operator responseActivate the alternate ALCS if there is one, or restartALCS. If this is an isolated incident, follow your normalprocedure for a non-urgent problem. If this happensrepeatedly, inform your system programmer.

ModuleDXCINTT

0004C2 ATTENTION - INVALID DASDUPDATE IGNORED

ExplanationAn invalid item was discovered in a DASD configurationload module and it was ignored.

System actionThe ZDASD LOAD completes but without the invaliditem.

Operator responseContact your system programmer.

ModuleDXCINTT


0004D6 MQ BRIDGE - NO MATCH FORTRIGGER MESSAGE

ExplanationThe ALCS MQ bridge facility has received a triggermessage, but the queue name in the trigger messagedoes not match the input queue defined for any MQcommunication resource.

System actionALCS discards the trigger message.

System programmer responseCheck that the MQ resources are correctly specifiedin the ALCS communication generation. The inputqueue name is defined on the INQNAME parameterfor COMDEF LDTYPE=MQ. Check that the queue andprocess objects are correctly specified in MQSeries.

ModuleDXCMQB

0004D9 MQ BRIDGE - INVALID CRI FORMESSAGE or WAS BRIDGE -INVALID CRI FOR MESSAGE

ExplanationThe MQ Bridge or WAS Bridge was invoked for anoutput message, but the destination is not a terminalconnected through MQ Bridge or WAS Bridge.



ModuleDXCMQB/DXCWSB

0004DA MQ BRIDGE - INACTIVE CRIFOR MESSAGE or WAS BRIDGE -INACTIVE CRI FOR MESSAGE

ExplanationThe MQ Bridge or WAS Bridge was invoked for anoutput message, but the destination terminal is notactive.



ModuleDXCMQB/DXCWSB

0004DB MQ BRIDGE - INVALID MQ QUEUERESOURCE or WAS BRIDGE -INVALID WAS RESOURCE

ExplanationThe MQ Bridge or WAS Bridge was invoked for anoutput message, but the destination terminal doesnot have any owning MQ resource or owning WASresource.



ModuleDXCMQB/DXCWSB

0004DC MQ BRIDGE - INACTIVE MQQUEUE RESOURCE or WASBRIDGE - INACTIVE WASRESOURCE

ExplanationThe MQ Bridge or WAS Bridge was invoked for anoutput message but the destination terminal has aninactive owning MQ or WAS resource.




ModuleDXCMQB/DXCWSB

0004DD MQ BRIDGE - NO IOCBSAVAILABLE FOR MQPUT1 or WASBRIDGE - NO IOCBS AVAILABLEFOR SEND

ExplanationAn ECB-controlled program issued a ROUTC or SEND-type monitor-request macro to send a message toan MQ or WAS destination, but ALCS does not haveenough resources to process the message.


System programmer responseIncrease the total number of I/O control blocks(IOCBs) in the ALCS system. (See the descriptionof the SCTGEN macro NBRIOB parameter in ALCSInstallation and Customization.)

ModuleDXCMQB/DXCWSB

0004DE WAS BRIDGE - WAS APPLICATIONINITIALIZATION FAILED

ExplanationDuring activation of a protocol type 2 WAS Bridge theECB-controlled exit AWA1 terminated abnormally.

System actionALCS does not activate the WAS Bridge.

System programmer responseInvestigate the AWA1 system error, Correct and reloadAWA1. Activate the WAS Bridge.

ModuleDXCWSB

0004E0 SOCKC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest that specified an invalid parameter.



ModuleDXCSOCK, DXCSOCL, DXCSOCM

0004E1 SOCKC - TCPIP NOT SUPPORTED

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest, but this ALCS system does not supportcommunication with TCP/IP.


Operator responseActivate an ALCS system that supports communicationwith TCP/IP.

User responseIf you intend to run programs that issue TCP/IPsockets requests , you must install TCP/IP on the sameMVS image and generate ALCS with TCP/IP support.Otherwise, either do not run these programs or removeany TCP/IP sockets statements from them.

ModuleDXCSOCM

0004E2 SOCKC - TCPIP NOT CONNECTED

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest, but this ALCS system is not currentlyconnected to TCP/IP.



User responseIf you intend to run programs that issue TCP/IPsockets requests, you must connect ALCS to TCP/IPfirst. Use the ALCS system generation parameters orthe ZCTCP command to do this.

ModuleDXCSOCM

0004E3 SOCKC - NOT AUTHORIZED BYINST EXIT

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest, but the ALCS TCP/IP installation-wide exit hasdetermined that the entry is not authorized.


System programmer responseIf the application and/or end user is allowed to issuethis TCP/IP sockets request, you must modify yourALCS TCP/IP installation-wide exit routine accordingly.

User responseThis may be an accidental or deliberate securityviolation. IBM recommends that you investigate andtake action to prevent any security violation.

ModuleDXCSOCM

0004E4 SOCKC - TERMINATIONREQUESTED BY INST EXIT

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest, but the ALCS TCP/IP installation-wide exit hasdetermined that the entry should be terminated.


System programmer responseIf the application and/or end user is allowed to issuethis TCP/IP sockets request, you must modify yourALCS TCP/IP installation-wide exit routine accordingly.

User responseThis may be an accidental or deliberate securityviolation. IBM recommends that you investigate andtake action to prevent any security violation.

ModuleDXCSOCM

0004E5 SOCKC - SOCKETS SUBTASK FORTHIS ENTRY ABENDED

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest, but the attached subtask that it was using hasended abnormally.

System actionALCS terminates the entry. ALCS automaticallyreattaches the subtask.


ModuleDXCSOCM

0004E6 SOCKC - SOCKETS PARAMETERLIST NOT ACCESSIBLE

ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest that specified a parameter list in storage thatthe application program did not have write (store)access to.



ModuleDXCSOCM

0004E7 SOCKC - SOCKETS CALL IS NOTALLOWED


ExplanationAn ECB-controlled program issued a TCP/IP socketsrequest, but ALCS does not allow user-writtenprograms to issue the following TCP/IP socketsrequests:

GIVESOCKETTAKESOCKET


Programmer responseThis TCP/IP sockets call is not appropriate for aclient or iterative server application. If you aredesigning a server application, you can use the ALCSTCP/IP concurrent server (ALCS Listener) to wait forconnection requests to arrive on a port.

ModuleDXCSOCM

0004E8 SOCKC - NOT STATE CHANGEENTRY

ExplanationAn ECB-controlled program issued a SOCKC RESTARTmonitor-request macro, but it was not the statechange entry.




ModuleDXCSOCM

0004E9 ASCIC - INVALID PARAMETER

ExplanationAn ECB-controlled program issued an ASCIC monitor-request macro with an invalid parameter.



ModuleDXCSOCM

0004EA SOCKETS SUBTASK ABEND

ExplanationOne of the subtasks that ALCS attaches to processTCP/IP sockets requests has ended abnormally.


Problem determinationAt the time of the system error dump, general register14 contains the abend completion code. MVS SystemCodes lists abend codes.

Problem determinationAt the time of the system error dump, general register14 contains the abend completion code. MVS SystemCodes lists abend codes. General register 1 points to astorage area containing the PSW and general registersat the time of the error. The PSW is in a 8-byte field atdisplacement X'28' into this storage area. The generalregisters, starting with general register 0, are in 16consecutive fullwords at displacement X'30' into thisstorage area.

ModuleDXCSOCK

0004EB LISTENER START/STOP SUBTASKABEND

ExplanationThe subtask that ALCS attaches to process TCP/IPconcurrent server start and stop requests has endedabnormally.


System actionALCS automatically reattaches the subtask.



ModuleDXCSOCK

0004EC CHILD SERVER SUBTASK ABEND

ExplanationOne of the subtasks that ALCS attaches to processTCP/IP child server sockets requests has endedabnormally.




ModuleDXCSOCK

0004ED TCPIP CONNECTION SUBTASKABEND

ExplanationThe subtask that ALCS attaches to process TCP/IPconnection and disconnection requests endedabnormally.

System actionALCS automatically reattaches the subtask.


ModuleDXCSOCK

0004F1 ROUTC - DESTINATION IS NOTTCPIP RESOURCE

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to a TCP/IPresource, but ALCS found that the resource type wasnot valid.



ModuleDXCSOCO

0004F2 ROUTC - NOT ALLOWED TO TCPIPBASE SERVER


ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to a TCP/IPresource, but the destination resource was neither aclient connection nor a dynamic server connection.


Programmer responseUse the COMIC monitor-request macro to determine ifthe destination TCP/IP resource is a client or dynamicserver connection.

ModuleDXCSOCO

0004F3 ROUTC - TCPIP NOT SUPPORTED

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to a TCP/IPresource, but this ALCS system does not supportTCP/IP communication.


User responseIf you intend to run programs which communicatewith TCP/IP resources, you must install z/OSCommunications Server IP on the same MVS imageand generate ALCS with TCP/IP support.

ModuleDXCSOCO

0004F4 ROUTC - TCPIP NOT CONNECTED

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to a TCP/IPresource, but there is no connection between ALCSand a TCP/IP address space.


Operator responseUse the ZCTCP command to establish a connectionbetween ALCS and a TCP/IP address space.

ModuleDXCSOCO

0004F5 ROUTC - NO IOCB AVAILABLE FORTCPIP

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to a TCP/IPresource, but ALCS does not have enough resourcesto process the message.


System programmer responseIncrease the total number of I/O control blocks(IOCBs) in the ALCS system. (See the descriptionof the SCTGEN macro NBRIOB parameter in ALCSInstallation and Customization.)

ModuleDXCSOCO

0004F6 ROUTC - TCPIP SOCKETS CALLERROR

ExplanationAn ECB-controlled program issued a ROUTC monitor-request macro to send a message to a TCP/IPresource, but an error occurred when ALCS issued aTCP/IP SEND sockets call.


Problem determinationAt the time of the system error dump, general registers14 and 15 (RDA and RDB) contain the TCP/IP returncode and error number. See Communications Server IPAPI Guide for an explanation of the return code anderror number.

ModuleDXCSOCO


0004F7 TCPIP COMMUNICATIONSUBTASK ABEND

ExplanationThe subtask that ALCS attaches in order to processTCP/IP communication resources ended abnormally.

System actionALCS terminates any entry that was using the subtask,and stops the TCP/IP communication resourceassociated with the subtask. ALCS attaches a newsubtask when the TCP/IP communication resource isstarted again.

Operator responseUse the ZACOM command to start the TCP/IPcommunication resource again.

Problem determinationAt the time of the system error dump, general register14 contains the abend completion code. MVS SystemCodes lists abend completion codes.

General register 1 points to a storage area containingthe PSW and general registers at the time of the error.The PSW is in a 8-byte field at displacement X'28' intothis storage area.

Bits 32-63 of each of the general registers, startingwith general register 0, are in 16 consecutive fullwordsat displacement X'30' into this storage area.Bits 0-31 of each of the general registers, starting withgeneral register 0, are in 16 consecutive fullwords atdisplacement X'70' into this storage area.

ModuleDXCSOCO

0004F8 UNABLE TO ADD DYNAMICSERVER

ExplanationA new client attempted to connect to a TCP/IP serverconnection but ALCS was unable to dynamically createa new communication table entry for this client.



ModuleDXCSOCO

0004F9 UNABLE TO DELETE DYNAMICSERVER

ExplanationALCS was unable to dynamically delete acommunication table entry.

System actionALCS continues normally.


ModuleDXCSOCO

000600 STVCC - INVALID ACTION VALUE

ExplanationAn ECB-controlled program issued an STVCC monitor-request macro, but the parameter bytes following themonitor-request macro linkage instructions were notvalid.




ModuleDXCSTV

000601 STVCC - INVALID INIT ACTIONVALUE






ModuleDXCSTV

000602 STVCC - INVALID WRITE ACTIONCODE





ModuleDXCSTV

000603 STVCC - INVALID LEVELSPECIFIED

ExplanationAn ECB-controlled program issued an STVCC monitor-request macro that specified a storage level or datalevel. The level reference was invalid. Valid levelreferences are D0 (value 0), D1 (value 8), and so onup to DF (value decimal 120).




ModuleDXCSTV

000604 STVCC - NO BLOCK ATTACHED

ExplanationAn ECB-controlled program issued an STVCC monitor-request macro with no block attached at the specifiedlevel.




ModuleDXCSTV

000605 I/O ERROR ON TUT FILE


ExplanationAn I/O error other than a short length record occurredon the TUT file.

System actionALCS cancels the test; it does not process any moremessages from the TUT.

User responseIf the input data set was a TUT and if STC did notreport any errors, then ask your system programmer toinform your IBM programming support representative.

Problem determinationCheck that the input data set was a TUT that STCcreated. Check and correct any errors that STCreported.

ModuleCSV1

000606 FIRST TUT FILE RECORD NOTRUNID

ExplanationThe first record read from a TUT file was not a RUNIDrecord.

System actionALCS cancels the test; it does not process anymessages from the TUT.

User responseIf the input data set was a TUT and if STC did notreport any errors, then ask your system programmer toinform your IBM programming support representative.

Problem determinationCheck that the input data set was a TUT that STCcreated. Check and correct any errors that STCreported.

ModuleCSV1

000607 LOGIC ERROR




ModuleCSV1

000CC0 EDCXSTRL NOT LINKED - MODULEUNUSABLE

ExplanationA load module containing programs written in the Clanguage has been linked incorrectly.


Programmer responseRelink the module and check that the required librarymodules have been included.

ModuleDXCBHLL

000CC1 OPEN FOR STDIN FAILED - text

ExplanationALCS was unable to open a memory file for the inputmessage. text is additional explanatory message text(if available) from the C runtime environment.


System programmer responseCheck that you have defined a sufficiently large defaultstorage limit and a suitable storage unit size.

Programmer responseCheck that a valid input message was passed to theprogram on ECB level 0.


ModuleDXCBSTDI

000CC2 FWRITE TO STDIN FAILED - text

ExplanationALCS was unable to write the input message into amemory file. text is additional explanatory messagetext (if available) from the C runtime environment.




ModuleDXCBSTDI

000CC3 FREOPEN FOR STDIN FAILED - text

ExplanationALCS was unable to reopen the memory file containingthe input message for input. text is additionalexplanatory message text (if available) from the Cruntime environment.




ModuleDXCBSTDI

000CC4 OPEN FOR STDOUT FAILED - text

ExplanationALCS was unable to open a memory file for outputmessage text. text is additional explanatory messagetext (if available) from the C runtime environment.



ModuleDXCBSTDO

000CC5 FSEEK FOR STDOUT FAILED - text

ExplanationALCS was unable to seek to the start of the outputmessage text file before outputting the message textusing the ALCS scrolling package. text is additionalexplanatory message text (if available) from the Cruntime environment.



ModuleDXCBSTDO

000CC6 reason

ExplanationA C language application called the IPRSE_parsefunction with one of the following errors (reason) inthe grammar:

AN UPPERCASE LETTER CANNOT FOLLOW ALOWER CASE LETTERGRAMMAR TOO LARGEILLEGAL CHARACTER FOLLOWING WILDCARDILLEGAL CHARACTER FOLLOWINGPARENTHESISILLEGAL KEYWORD DELIMITER IN THEGRAMMARILLEGAL USE OF TOKEN IN LIST PARAMETER


ILLEGAL WILDCARD CHARACTER IN LISTINVALID CHARACTER IN GRAMMARTOO MANY CHARACTERS IN MANDATORYPARAMETER LISTUNEVEN BALANCE OF LEFT BRACES IN THEGRAMMARUNEVEN BALANCE OF LEFT BRACKETS IN THEGRAMMARUNMATCHED PARENTHESIS IN GRAMMARA PLUS MUST BE FOLLOWED BY A PLUS OR ATOKEN DELIMETERA POSITIONAL PARAMETER WAS FOUND AFTERA KEYWORD PARAMETER

Or, there was an error on the IPRSE_parse call:

INVALID OPTION VALUE PASSED TO PARSEREOM CODED AND NO EOM IN STRING


Programmer responseCorrect the grammar or the call to IPRSE_parse.

ModuleDXCBPRSE

000CC7 HEAP STORAGE EXHAUSTED

ExplanationThe parser is unable to allocate sufficient heap storageto complete its processing.


System programmer responseDetermine why the ECB heap storage was depleted.

ModuleDXCBPRSE

000CC8 INVALID FUNCTION CODE - CODEIN R02

ExplanationWhile debugging an ECB-controlled C program, theALCS Debug Tool system services adapter received arequest from Debug Tool with an invalid function code.

System actionALCS ignores the request and continues normally.


ModuleDXC10OSM

000CC9 UNSUPPORTED FUNCTION - CODEIN R02

ExplanationWhile debugging an ECB-controlled C program, theALCS Debug Tool system services adapter received arequest from Debug Tool with a function code that theadapter does not support.

System actionALCS ignores the request and continues normally.


ModuleDXC10OSM

000CCC C RUNTIME ABEND/REASONCODES IN R03/R04

ExplanationAn abend condition occurred while running an ECB-controlled C program. This abend may be generated bythe C system programming environment, the LE libraryenvironment, or MVS. This error can occur if yourprogram requests an excessive amount of memoryduring initialization or if there is a shortage of memoryfor stack storage during execution.


System programmer responseCheck that a suitable storage unit size has beendefined. Also check that the LE runtime library isavailable to ALCS in the runtime JCL as STEPLIB orDXCHLIB.


Problem determinationDepending on the environment generating the abend,see:

1. C/C++ Programming Guide2. Language Environment Debugging Guide and Run-

Time Messages3. MVS System Codes

for a description of the abend code, and (1) or (2) forthe reason code.

Check also the MVS console.

ModuleDXCBHLL

000CD0 CEEPIPI COULD NOT BE LOADED

ExplanationALCS was unable to load the CEEPIPI module.


System programmer responseEnsure that the LE runtime library is specified inDXCHLIB or STEPLIB in the ALCS runtime JCL.

ModuleDXCBHLLE

000CD1 CEEPIPI TERMINATE FAILED

ExplanationALCS was unable to terminate the high level languageenvironment.



ModuleDXCBHLLE

000CD2 CEEPIPI CALLMAIN FAILED

ExplanationALCS was unable to execute the high level languageenvironment.



ModuleDXCBHLLE

000CD3 CEEEPIPI ADDENTRY FAILED

ExplanationALCS was unable to add DXCBHLLF to the PIPI table.



ModuleDXCBHLLE

000CD4 CEEPIPI INITMAIN FAILED

ExplanationALCS was unable to activate the PIPI environment.



ModuleDXCBHLLE

000CD5 CEEPIPI INITSUBDP FAILED


ExplanationALCS was unable to activate the PIPI environment.



ModuleDXCBHLLE

000CD6 CEEPIPI CALLSUB FAILED

ExplanationALCS was unable to execute the high level languageenvironment.



ModuleDXCBHLLE

000CE0 CBXF - INVALID ENTRYCONDITIONS

ExplanationA program entered the ALCS ECB-controlled programCBXF with incorrect entry conditions.

System actionCBXF builds and sends an error message to RO CRAS.Then ALCS continues processing normally.



ModuleCBXF

000CE1 CBXF - INVALID MESSAGE CODE

ExplanationA program entered the ALCS ECB-controlled programCBXF with an invalid message code.

System actionCBXF builds and sends an error message to RO CRAS.Then ALCS continues processing normally.



ModuleCBXF

000CE2 RELOCATE TABLE READ ERROR -LOAD ABANDONED

ExplanationThe ZRELO LOAD command processor was unable toread a record from one of the relocate tables.

System actionThe ZRELO LOAD is abandoned.


System programmer responseEither correct the table by manual intervention or clearthe relocate table by ZRELO CLEAR before running thejob again.


Problem determinationFirst check for corruption of the load dump keypoint. Ifthis is correct then format the dump on the diagnosticfile to detect which relocate table record is in error.

ModuleCBXQ

000CE3 RELOCATE TABLE READ ERROR -CLEAR CONTINUES

ExplanationThe ZRELO CLEAR command processor was unable toread a record from one of the relocate tables.

System actionThe ZRELO CLEAR continues.

Problem determinationFormat the dump on the diagnostic file to detect whichrelocate table record is in error.

ModuleCBXS

000CE4 RELOCATE TABLE READ ERROR -RELOC CONTINUES

ExplanationThe ZRELO RELOCATE command processor wasunable to read a record from one of the relocatetables.

System actionThe ZRELO RELOCATE continues, but one or moreimbedded addresses will not be relocated.


System programmer responseEither correct the table by manual intervention andrerun the job or clear the relocate table by ZRELOCLEAR before running both the ZRELO LOAD and theZRELO RELOCATE.

Problem determinationFirst check for corruption of the load dump keypoint. Ifthis is correct then format the dump on the diagnosticfile to detect which relocate table record is in error.

ModuleCRC5

000CE5 CBXM - INTERNAL LOGIC ERROR

ExplanationThe ZDATA DUMP utility calls the data base scanfunction to scan the data base for records to dump.The return code from the data base scan functionindicates that an error has occurred.

System actionALCS terminates the ZDATA DUMP utility.


ModuleCBXM

000CE6 CBXM - SEQUENTIAL FILE I/OERROR IN ZDATA DUMP

ExplanationAn I/O error occurred while attempting to write to thesequential file when running the ZDATA DUMP utility.

System actionALCS issues message DXC2650E and terminates theZDATA DUMP utility.

Problem determinationRefer to message DXC2650E.

ModuleCBXM

000CE7 LOGGING TIME STAMP SEQUENCEERROR

ExplanationThe ZRSTR command processor read a record from theinput data set, but the record is not in the correct time


sequence. The time stamp indicates that the recordwas logged (written to the log) before records thatprecede it on the log.

System actionThe ZRSTR command processor cancels the restorefunction.

User responseCheck that the input data set is an log. If it is, thencheck that the data set was correctly closed. If thedata set was not correctly closed then this error canoccur for records that follow the last valid record onthe data set; in this case the restore has completedand it is safe to ignore this error.

ModuleCBXN

000CE8 MAXIMUM BLOCK SIZE TOOSMALL FOR TPFDBR TAPE

ExplanationA TPF database reorg tape requires a minimum blocksize of 10944 bytes. The largest block size on thesystem is less than 10944 bytes.

System actionThe load of the TPFDBR tape is not performed.

User responsePerform a new ALCS generation with a larger maximumblock size.

ModuleCBXN

000CE9 CBXF - VALID ENTRY CONDITIONSFORCED

ExplanationA program entered the ALCS ECB-controlled programCBXF with incorrect entry conditions.

System actionCBXF forces valid entry conditions. Then ALCScontinues processing normally.



ModuleCBXF

000CF0 ZPDAR COMMAND - INTERNALERROR

ExplanationALCS detected an internal error while processing aZPDAR command.



System programmer responseThis problem should not occur. If it does, contact yourIBM programming support representative.

ModuleCPDR

000D13 ZAFIL - CAN NOT READ RECORD

ExplanationThe ZAFIL command processor detected anunrecoverable I/O error or other error that preventedreading the record that the ZAFIL command specified.

System actionThe ZAFIL command processor sends an errorresponse message.

ModuleCVAE

000D15 CVAG - INVALID ENTRYCONDITIONS


ExplanationA program entered the ALCS ECB-controlled programCVAG with incorrect entry conditions.

System actionCVAG builds and sends an error message to RO CRAS.Then ALCS continues processing normally.



ModuleCVAG

000D16 CVFG - INTERNAL LOGIC ERROR




ModuleCVFG

000DB0 SEND - END OF LINE OR MESSAGEIN DBCS TEXT

ExplanationThere is a new-line (#CHAR) character after a DBCSSO character and before any DBCS SI character. (Thehash (#) character is represented differently by someequipment and it is the EBCDIC X''7B'' character.)Alternatively, there may be a DBCS SI charactermatching a DBCS SO character before the end of themessage.

This is an application error. The output datastream isnot correctly created by the application. The DBCS SOand SI characters must occur in pairs. There must be

no new-line (#CHAR) character between the DBCS SOand SI characters.

System actionA dump is taken and the DBCS SO character isreplaced with the "?" character.


ModuleDXCCOM3

000DB1 SEND - INVALID DBCSCHARACTER

ExplanationAn invalid DBCS character has been detected after aDBCS SO character and before any DBCS SI character.

This is an application error. The output datastream isnot correctly created by the application. Ensure thatthe DBCS data, delimited by the DBCS SO and SIcharacters, contains only valid DBCS characters.



ModuleDXCCOM3

000DB2 SEND - INVALID DBCS CONTROLCHARACTER

ExplanationAn invalid DBCS control character has been detectedafter a DBCS SO character and before any DBCS SIcharacter.

This is an application error. The output datastream isnot correctly created by the application.




Problem determinationEnsure that the DBCS data, delimited by the DBCS SOand SI characters contains only valid DBCS characters.

ModuleDXCCOM3

000DB3 SEND - ODD NUMBER OF DBCSCHARACTERS

ExplanationThere is an odd (not a multiple of 2) number ofcharacters between the DBCS SO and SI characters.


System actionA dump is taken and the DBCS SO and SI charactersare replaced with the "?" character.


ModuleDXCCOM3

000DB4 SEND - #SI NOT PRECEDED BY#SO

Explanation(The hash (#) character is represented differentlyby some equipment and it is the EBCDIC X''7B''character.) A DBCS SI character has been detected,but there is no corresponding DBCS SO characterpreceding it in the data stream.


System actionA dump is taken and the DBCS SI character is replacedwith the "?" character.


Problem determinationThe DBCS SO and SI characters must occur in pairsand the DBCS SO character must come before theDBCS SI character.

ModuleDXCCOM3

000E02 STORAGE LEVEL FOR OUTPUTMESSAGE IN USE

ExplanationA program entered the ALCS ECB-controlled programCRC9 with incorrect entry conditions. The storage levelfor the Recoup message was in use.




ModuleCRC9

000E03 PROGRAM program NOT FOUND -RECOUP ABANDONED

ExplanationRecoup cannot proceed because the ECB-controlledprogram program is unknown to ALCS; program is oneof:

BZ00This program contains the names of the Recoupdescriptor programs.

CZ01This is the Recoup descriptor program for ALCSpool records.

System actionRecoup ends abnormally.


User responseEnsure the programs BZ00 and CZ01are both loadedand rerun Recoup.

ModuleCRC2

000E04 INVALID METHOD IN PRIMEGROUP - RECOUP ABEND

ExplanationRecoup cannot process a prime group because thedescriptor program contains an invalid code thatdescribes the method.

System actionRecoup ends abnormally.

Operator responseThese errors may reduce pool integrity. Inform yoursystem programmer.

System programmer responseEnsure rapid fixing of these errors and rerunning ofRecoup.

User responseCheck if there were any assembly errors or MNOTEsfrom the assembly of the Recoup descriptor. Correctthe coding of the Recoup descriptor program and rerunRecoup.

If the Recoup descriptor program is coded correctlyand there were no assembly errors or MNOTEs, thenask your system programmer to inform your IBMprogramming support representative.

ModuleCRC3

000E06 FACE ERROR IN PRIME GROUP -RECORD IGNORED

ExplanationRecoup could not calculate the file address of a recordin the application global area; there was a FACEerror calculating the file address. The Prime groupdescriptor specified METHOD=STOR. Either there areno records of type #GLOBL, or the ordinal number inan entry in one of the global load programs (GOA0,GOA1, and so on) was invalid. (The hash (#) character

is represented differently by some equipment and it isthe EBCDIC X''7B'' character.)

System actionRecoup ignores the entry in the global load programand proceeds with the next entry.





ModuleCRC3

000E07 INVALID FILE ADDRESS

ExplanationRecoup detected an invalid file address during fixedmode chain chase. Either the file address of the firstrecord in a group or the forward or backward chain fileaddress of a record was invalid.

System actionRecoup processes the invalid file address as the endof the group (the end of the chain of records) andproceeds with the next group.






ModuleCRC4

000E08 parameter INVALID IN INDEXDSECT

ExplanationThere is an error in an index in a Recoup descriptorprogram. The index contains an invalid parameter.Note that this error occurs because the index is invalid,not because the record (that the index describes)contains invalid data. The parameter in error isparameter, one of:

ITEM COUNTNumber of items in the record. Items are tableentries or logical records within the record. Eachitem can contain one reference to another group,or it can contain several references (in sub-items).

ITEM LENGTHSize (length in bytes) of items.

SUB-ITEM COUNTNumber of sub-items that an item contains.

SUB-ITEM LENGTHSize (length in bytes) of sub-items.

REFERENCE LENGTHSize (length in bytes) of a field that contains areference (for example a file address) to anothergroup.

All the parameters above can be invalid if, forexample, the index specifies that the item is in azero length field.

REFERENCE METHODReference method (type of reference). Thisparameter is invalid if the reference method is notone of:

File addressFixed record ordinal numberTerminal address (CRI)User-converted reference.

System actionRecoup ignores this index. If there are more indexesfor the same record then Recoup processes them.Otherwise Recoup proceeds with the next record in thegroup.





ModuleCRC5

000E09 INVALID FILE ADDRESS - RECOUPCONTINUES

ExplanationThere is a logic error in Recoup.

System actionRecoup ignores the invalid address and continues.


ModuleCRC7

000E0A INST EXIT INVALID ITEM -RECOUP CONTINUES

ExplanationInstallation-wide exit program ARC7 has returned aninvalid length for user data.


System actionRecoup uses the default length instead of the invalidlength.

System programmer responseCorrect your installation-wide exit program.

ModuleCRC7

000E0B CRCD - BAD ENTRY - STORAGELEVEL IN USE

ExplanationA program entered the ALCS ECB-controlled programCRCD with incorrect entry conditions. The storage levelfor the Recoup message was in use.




ModuleCRCD

000E0C DIRECTORY BUILD START ERRORLnLT POOL

ExplanationThe monitor is unable to create a new directory for along-term pool.

System actionRecoup continues. If the pool is an existing pool ALCScontinues using the existing directory. If the pool is anew pool ALCS is unable to use this pool.


Problem determinationAt the time of the system error dump, generalregister 15 (RDB) contains the return code from aGFSCC RECOUP,DIRBUILD,START,POOLID monitor-request macro; general register 14 (RDA) contains theaddress of the data set information from a DASCCDISPLAY,DATASET monitor-request macro, or zero ifthere are no data sets of this size.

ModuleCRC8

000E0D DIRECTORY BUILD END ERRORLnLT POOL

ExplanationThe monitor is unable to write out new long-term pooldirectories to the database following directory build.

System actionRecoup continues. If the pool is an existing pool ALCScontinues using the existing directory. If the pool is anew pool ALCS is unable to use this pool.


Problem determinationAt the time of the system error dump, generalregister 15 (RDB) contains the return code froma GFSCC RECOUP,DIRBUILD,END,POOLID monitor-request macro.

ModuleCRC8

000E0E GF-000 ERROR - QUICK RECOUPTERMINATED

ExplanationRecoup is unable to write out the file addresses ofthe in-use records to the Recoup general file, GF-000.This could be due to an I/O error, or the file is fullor offline. Because ZRECP QUICK does not timestampall the records, it is unsafe to build new directories,therefore the command terminates.

System actionRecoup is terminated.


System programmer responseDetermine why the Recoup general file is not availableand make it available. Retry the command.

ModuleCRC1, CRC7

000EE0 macro - LOGIC ERROR IN ALCSHEAP STORAGE SUPPORT

ExplanationAn ECB-controlled program issued an assemblerMALOC, FREEC, RALOC, or CALOC monitor-requestmacro, but there is an internal logic error in ALCS.



ModuleDXCSTH

000EE1 macro - SIZE IS NOT A VALIDPOSITIVE VALUE

ExplanationAn ECB-controlled program issued an assemblerMALOC, RALOC, or CALOC monitor-request macro, butthe the requested size is not a positive value.

System actionALCS continues processing normally, but the storagerequest fails.


ModuleDXCSTH

000EE2 macro - SIZE EXCEEDS TYPE 3STORAGE UNIT SIZE

ExplanationAn ECB-controlled program issued an assemblerMALOC, RALOC, or CALOC monitor-request macro, but

the requested size exceeds the type 3 storage unitsize. Register 14 contains the requested size (in bytes).


System programmer responseIf this is not an application error, then increase thetype 3 storage unit size in the ALCS generation.

Programmer responseInform your system programmer if the ECB-controlledprogram genuinely needs the storage. Otherwisecorrect the programming error.

ModuleDXCSTH

000EE3 macro - INVALID STORAGEADDRESS

ExplanationAn ECB-controlled program issued an assemblerFREEC or RALOC monitor-request macro, but theaddress is invalid.



ModuleDXCSTH

000EE4 macro - ENTRY STORAGE LIMITEXCEEDED

ExplanationAn ECB-controlled program issued an assemblerMALOC, RALOC, or CALOC monitor-request macro, butthe requested size exceeds the total entry storagelimit.



Programmer responseIf the entry genuinely requires a large amount ofstorage, include a SLIMC monitor-request macro in theapplication.

ModuleDXCSTH

000EE5 macro - NO AVAILABLE TYPE 3STORAGE UNITS

ExplanationAn ECB-controlled program issued an assemblerMALOC, RALOC, or CALOC monitor-request macro, butall the type 3 storage units are in use.


System programmer responseCheck to see why the storage units are in use. Theshortage of storage units can indicate for example:

• The ALCS generation did not specify enough type 3storage units.

• An exceptional amount or type of work requires extratype 3 storage units.

ModuleDXCSTH

000EE6 macro - NO TYPE 3 STORAGEUNITS DEFINED

ExplanationAn ECB-controlled program issued an assemblerMALOC, FREEC, RALOC, or CALOC monitor-requestmacro, but there are no type 3 storage units defined.


System programmer responseDefine type 3 storage units in the ALCS generation.

ModuleDXCSTH

000EE7 macro - INVALID HEAP STORAGE

ExplanationAn ECB-controlled program issued a ROUTC or SENDCX monitor-request macro, but either the level is invalid,or the data level points to an incorrect heap storagearea.



ModuleDXCCOMQ, DXCSND

000EE8 SENDCX - DEVICE DOES NOTSUPPORT LARGE MESSAGES

ExplanationAn ECB-controlled program issued a SENDC Xmonitor-request macro, but the destination of themessage is not an ALC terminal that connects to ALCSthrough TCP/IP.


ModuleDXCXND

000EEA COMTC - ERROR DURING LOAD ORBACKOUT PROCESSING

ExplanationALCS failed to build an on-line communicationtable entry during COMTC LOAD or COMTC BACKOUTprocessing.

System actionALCS returns control to the ECB-controlled programwhich issued the COMTC macro with a returncode of COMTC_R_ERROR and a reason code ofCOMTC_S_LOAD in register 15.



System programmer responseThe on-line communication table may contain anincomplete communications entry. Do not use COMTCCONFIRM to confirm this communication table update,but schedule an ALCS restart to rebuild the on-linecommunication table. After the restart, either removethe update by a COMTC CANCEL or load it again by aCOMTC LOAD. A COMTC LOAD or BACKOUT error canoccur when the number of available resource ordinalnumbers is running low. If additional ordinal numbersare required, increase the ordinal number range inthe ALCS communication generation COMGEN macroparameter, MAXORD. If the problem persists, informyour IBM programming support representative.

ModuleDXCOCTM

000EEB COMTC - ERROR OCCURREDDURING COMMUNICATIONSRESTART

ExplanationDuring ALCS restart, program COTA issues the COMTCSTART macro to initiate the building of communicationtable entries from the Online Communication TableMaintenance (OCTM) database. An error has occurredduring the building of the communications tableentries, therefore COTA has received a non-zero returncode from COMTC START.

System actionALCS terminates the state change entry. Anothersystem error (000EF1 or 000EF2) may also occurimmediately prior to this system error.


System programmer responseRestore the Online Communication Table Maintenance(OCTM) database using the online ZOCTM RESTOREfunction. If this does not correct the problem, informyour IBM programming support representative.

ModuleCOTA

000EEC OCTM - LOGIC ERROR WHILECHECKING L3LT POOL RECORDS

ExplanationALCS detected a logic error while checking the numberof available L3 long-term pool records.




ModuleDXCOCTM

000EED OCTM - UNABLE TO READ/WRITETO SEQUENTIAL FILE

ExplanationThe ALCS operator activated the OnlineCommunication Table Maintenance (OCTM) BACKUP orRESTORE functions, but ALCS was unable to performany I/O to the OCTM sequential file.



System programmer responseVerify that the OCTM sequential file is correctlydefined in the ALCS system (see the description ofthe SEQGEN generation macro in ALCS Installation andCustomization).

ModuleCOTA

000EEE OCTM - INVALID CHANGE RECORDON OCTM DATABASE


ExplanationDuring ALCS restart, while ALCS was loadingthe on-line communication table from the OnlineCommunication Table Maintenance (OCTM) database,it detected an invalid CHANGE record on the OCTMdatabase.

System actionALCS continues with the restart (an invalid CHANGErecord does not impact the integrity of the on-linecommunication table).



ModuleDXCOCTM

000EF0 COMTC - INVALID ACTIONPARAMETER

ExplanationAn ECB-controlled program issued a COMTC macro thatspecified an invalid action parameter.



System programmer responseReview the object code in the ECB-controlledprogram which issued the COMTC macro. An invalidaction parameter should be detected when anECB-controlled program is assembled, therefore theexpansion of the COMTC macro may be incorrect.Alternatively, contact your IBM programming supportrepresentative for assistance.

ModuleDXCOCTM

000EF1 OCTM - LOGIC ERROR DURINGCOMMUNICATIONS RESTART

ExplanationALCS detected a logic error while loadingcommunication resources from the OnlineCommunication Table Maintenance (OCTM) databaseduring system restart.

System actionALCS continues with the restart, however thecommunications restart will not finish normally.System error 000EEB may also occur.


System programmer responseRestore the OCTM database using the online ZOCTMRESTORE function. If this does not correct theproblem, inform your IBM programming supportrepresentative.

ModuleDXCOCTM

000EF2 OCTM - FIND ERROR ON OCTMDATABASE

ExplanationALCS is unable to read records on the OnlineCommunication Table Maintenance (OCTM) databaseduring communications restart.



System programmer responseRestore the OCTM database using the online ZOCTMRESTORE function. If this does not correct theproblem, inform your IBM programming supportrepresentative.


ModuleDXCOCTM

000EF3 OCTM - CANNOT OBTAIN EXTRAOCTM DATABASE RECORDS

ExplanationAn error occurred when ALCS attempted to expand thesize of the Online Communication Table Maintenance(OCTM) database.

System actionALCS disables access to the OCTM database.


System programmer responseAt the time of the system error, general register 15contains one of the following reason codes:

4There are insufficient spare ordinal numbers forcommunication resources.

Increase the range of ordinal numbers definedon the MAXORD parameter of the ALCScommunication generation COMGEN macro andrebuild the initial communication configurationload module.

8There are insufficient (less than 500) size L3 long-term pool records available.

Run Recoup. If not enough size L3 long-term poolrecords are returned by Recoup, then increase thenumber of available size L3 long-term pool recordsby expanding the database.

ModuleDXCOCTM

000EF4 COMTC - UNABLE TO OBTAINPOOL FILE ADDRESS

ExplanationThe COMTC macro has been issued with theACTION=GROUPS parameter, but ALCS was unable toobtain an L3ST pool file address for a CommunicationsGroups Information record.



System programmer responseCheck your database generation to verify that an L3STpool is defined. If it is, verify that the L3ST pool is stillactive.

ModuleDXCOCTM

000EF5 COMTC - LOGIC ERROR DURINGCOMTC MACRO PROCESSING

ExplanationAn ECB-controlled program issued a COMTC macro butan error occurred in DXCOCTM while the macro wasbeing processed.

System actionALCS returns control to the ECB-controlled programwhich issued the COMTC macro with a return code ofCOMTC_R_SYSERR in register 15.



ModuleDXCOCTM

000EF6 OCTM - LOAD ERROR DURINGALCS RESTART

ExplanationALCS failed to build an on-line communication tableentry during restart.




System programmer responseRestore the Online Communication Table Maintenance(OCTM) database using the online ZOCTM RESTOREfunction. If this does not correct the problem, informyour IBM programming support representative.

ModuleDXCOCTM

000EF7 COMTC - UNABLE TO RETRIEVECOMTC GROUPS RECORD

ExplanationALCS was processing the COMTC macro with theACTION=GROUPS parameter, but was unable toretrieve the Communications Groups Informationrecord (which is built by ALCS for the ECB-controlledprogram that issued the COMTC macro).




ModuleCOTC, COTG

000EF8 OCTM - NO IOCB AVAILABLE FORBUILD OR RESTORE FUNCTIONS

ExplanationThe ALCS operator activated the OnlineCommunication Table Maintenance (OCTM) BUILD orRESTORE function, but ALCS does not have enoughIOCB resources to process the request.



System programmer responseIncrease the total number of I/O control blocks(IOCBs) in the ALCS system (see the description of theNBRIOB parameter on the SCTGEN generation macroin ALCS Installation and Customization).

ModuleDXCOCTM

000EF9 OCTM - LOGIC ERROR WHILEBUILDING INITIAL OCTMDATABASE

ExplanationALCS detected a logic error while building the initialOnline Communication Table Maintenance (OCTM)database.




ModuleDXCOCTM

000EFA TPFDF - PROGRAM NOT AMODE 31

ExplanationA TPFDF program is not an AMODE 31 program.Register R03 points to the name of the program.




ModuleDXCDFS, DXCDFT

000EFB TPFDF - INVALID MACRO CALL

ExplanationAn ECB-controlled program issued an invalid TPFDFmacro call. Register R14 contains the incorrect valuein the TPFDF macro call.



ModuleDXCDFS

000EFC TPFDF - PROGRAM NOT LOADED

ExplanationA TPFDF program is not loaded. Register R03 points tothe name of the program.



ModuleDXCDFS, DXCDFT


Chapter 14. Abnormal termination completion codes

This section lists and describes the completion codes that ALCS issues when it uses the ABEND macroinstruction to end abnormally. These are user completion codes; they are decimal numbers. They applyonly when the system completion code is hexadecimal 000. Refer to MVS System Codes for informationabout other system completion codes.

0000

ExplanationThe ALCS Prime CRAS operator entered a ZASYSHALT command. This command terminates ALCS.

System actionALCS completes pending output operations. Then itends abnormally.

0001

ExplanationThe ALCS system error routine identified an error thatis normally catastrophic.

System actionThe system error routine generates a system errordump. Then it completes pending output operations.Then it ends abnormally.

Problem determinationMessage DXC250T accompanies this completion code.Refer to the explanation “DXC250T” on page 40 forinformation about the error condition.

If a system error dump is not available then an MVSSYSABEND or SYSUDUMP contains information thatcan help with problem determination. In particular,at entry to ABEND, general register 4 containsthe address of the MVS recovery and terminationmanagement ( RTM ) system diagnostic work area(SDWA). General register 7 contains the ABENDcompletion codes in the low order 3 bytes; the first12 bits are the system completion code, the second 12bits are the user completion code.

For some error conditions, the ALCS monitor programdeliberately provokes a specification exception torequest a system error dump. The applicationsystem error macros SYSRA and SERRC deliberatelyprovoke specification exceptions in the same way.In these cases, the system and user completioncodes in general register 7 are hexadecimal 0C6 andhexadecimal 000 respectively.

0002

ExplanationThe ALCS system error routine identified a nestederror. That is, a second (nested) error occurred whilethe system error routine was already processing asystem error.

System actionThe system error routine cancels the system errordump for the original error. Then it completes pendingoutput operations. Then it ends abnormally.

Problem determinationMessage DXC250T accompanies this completion code.Refer to the explanation “DXC250T” on page 40 forinformation about the original error condition.

An MVS SYSABEND or SYSUDUMP contains informationthat can help with problem determination. Inparticular, at entry to ABEND, general registers 4 and7 contain the system diagnostic work area (SDWA)address and abend completion codes for the originalerror, as for completion code 0001 ( “Explanation”on page 445). General registers 2 and 5 contain theSDWA address and abend completion codes for thesecond error.

0003

ExplanationThe ALCS system error routine identified a doublenested error. That is, a third (double nested) erroroccurred while the system error routine was alreadyprocessing a nested system error.

System actionThe system error routine ends abnormally, without anyattempt to complete pending output operations.


Problem determinationMessage DXC250T accompanies this completion code.Refer to the explanation “DXC250T” on page 40 forinformation about the original error condition.

An MVS SYSABEND or SYSUDUMP contains informationthat can help with problem determination. Inparticular, at entry to ABEND, general registers 4 and7 contain the system diagnostic work area (SDWA)address and abend completion codes for the originalerror, as for completion code 0001 ( “Explanation”on page 445). General registers 3 and 6 contain theSDWA address and abend completion codes for thesecond error. General registers 2 and 5 contain theSDWA address and abend completion codes for thethird error.

0011

ExplanationThe ALCS system error routine identified an error thatnormally terminates the active entry but there is noactive entry.


Problem determinationAs for completion code 0001 ( “Explanation” on page445).

0012

ExplanationThe ALCS system error routine identified an error thatnormally terminates the active entry but it cannotidentify the active entry.



0013

ExplanationThe ALCS system error routine identified an error in anonline monitor routine. The routine was executing withincorrect base register contents.



0020

ExplanationThe ALCS system error routine identified an error. Theuser-written installation-wide system error exit routinerequested a catastrophic.



0030

ExplanationThe ALCS system error routine identified an error in anonline monitor routine. The online monitor save areachain was corrupted.



0031


ExplanationThe ALCS system error routine identified an error in anonline monitor routine. An online monitor subroutine(called an emergency exit routine) returned a non-zeroreturn code.



0041

ExplanationThe operator replied CANCEL to ALCS messagenumber DXC110R.


0042

ExplanationThe ALCS initializer identified an error that preventssuccessful initialization.

System actionThe initializer may send one or more messages withseverity code "T" to the MVS operator console. Then itends abnormally. The messages describe the reasonfor the abend. Observe that ALCS does not sendmessages with severity code "T" when it cannotinitialize either the ALCS - WAS interface or the ALCSmessage trace. In these cases the MVS dump containsadditional information indicating the problem.

• When ALCS is not able to initialize the ALCS - WASinterface, general register four in the MVS dumpcontains either:WAS4

could not allocate storage, orWAS8

could not load one or more of the WAS OLA stubprograms.

• When ALCS is not able to initialize the onlinemessage trace facility, register four in the MVS dumpcontains either

MGT4could not allocate the online trace anchor or

MGT8could not allocate the trace buffer area. Notethat if your online message trace area isabove the bar, then you must specify a properMEMLIMIT.

Problem determinationRefer to the MVS console for messages that describethe reason for the abend or refer to the MVS abend.

0795

ExplanationThe ALCS communication routines identified an errorthat prevents normal operation. This can be caused by,for example:

• Corruption of one or more of the communicationtables

• Incorrect use of an internal communicationsubroutine from an installation-wide exit

• An internal error.

System actionThe ALCS communication report file generator endsabnormally. No message accompanies this completioncode.

System programmer responseCheck that the error is not caused by user-writtencode being executed in the installation-wide exits.If the error is in ALCS, then inform your IBMprogramming support representative.

0796





Chapter 14. Abnormal termination completion codes 447



0797







0798







0799







0997

ExplanationThe USRTSK1 exit used by third party software couldnot be initialized by ALCS.

System actionALCS ends abnormally. No message accompanies thiscompletion code.

System programmer responseContact the ALCS Support Group

1000

ExplanationThe ALCS communication report file generator hasended normally.

1001








1002

ExplanationAn ALCS initialization routine failed.

System actionThe ALCS communication report file generator endsabnormally.

1003

ExplanationThe ALCS communication report file generator wasunable to open the output report file.


System programmer responseNo message accompanies this completion code.Examine the system log for any message associatedwith the output report file. Correct the error andresubmit the job.

1004

ExplanationThe ALCS security routines identified an error.


System programmer responseExamine the system log for any ALCS message withsubcomponent code SAF.

1005

ExplanationThe ALCS communication routines identified an errorthat prevents normal operation.


System programmer responseExamine the system log for any ALCS message withsubcomponent code COM.

1006

ExplanationThe ALCS communication routines could not openthe Online Communication Table Maintenance (OCTM)sequential file (created by the online ZOCTM BACKUPcommand).


System programmer responseExamine the system log for messages that areassociated with the OCTM backup sequential file orthe PARM parameter on the JCL. Correct the JCL (andthe PARM parameter if required) and resubmit the job.

Chapter 14. Abnormal termination completion codes 449

Chapter 15. Sense codes

ALCS can send the following SNA sense codes over an LU 6.1 link. For any other sense codes refer to theappropriate SNA or VTAM manual.

081C

ExplanationRequest Not Executable: The requested function cannot be executed because of a permanent error condition inthe receiver.

The following list shows ALCS unique codes that are set as part of sense code 081C.

Sense DataMeaning

081C0701ALCS is unable to obtain an L1 or L3 short-term pool record because L1 or L3 records are not defined to thesystem.

081C0702ALCS is unable to obtain an L1 or L3 short-term pool record because there are no L1 or L3 short-term poolrecords available.

081C0703ALCS is unable to obtain an L1 or L3 VFA buffer.

081C0704ALCS is unable to read a pool record that was previously written.

081C0705The input data is too long to fit in an L3 pool record.


Appendix A. Messages intended for automatedoperations

The following messages are intended as part of the ALCS General-Use Programming Interface.

The wording of messages is not a part of the General-Use Programming Interface.

However, if you wish to use ALCS messages as input to an automated operator, you can do so by makinguse of:

• The message number, and• The tokenized variables (if any).

For further information see “Automated operations” on page viii.

DXC030ETPFDF initialization failed - Not enough storage for DB table

DXC031WTPFDF initialization failed - Not enough storage for DF statistics

DXC040TTimer initialization failed - TOD clock error

DXC051TSequential file initialization failed - Not enough sequential files available

DXC052TCan not read seq file configuration table TN-'name'Abend code AC-X'system_completion_code' Reason code RSC-X'reason_code'

DXC054ISeq file SEQN-'name' Dsname DSN-'data_set_name' Volume VS-'volume_serial' allocated

DXC055ISeq file SEQN-'name' Dsname DSN-'data_set_name' Volume VS-'volume_serial' deallocated

DXC056ESequential file SEQN-'name' allocate/open failed - Return code RC-X'return_code'

DXC070EHiperspace initialization failed - Return code RC-X'return_code' Reason code RSC-X'reason_code'

DXC071EHiperspace initialization failed - Not enough storage for control block

DXC080EDB2 initialization failed - Not enough storage

DXC081EDB2 CAF entry point load failed - Abend code AC-X'abend_code' Reason code RSC-X'reason_code'

DXC090EAPPC/MVS initialization failed - Not enough storage

DXC091EAPPC/MVS initialization failed - Not enough CSA storage

DXC092EAPPC/MVS join failed - Return codesRC1-X'join_return_code' RC2-X'XCF_return_code' RC3-X'XCF_reason_code'

DXC093WAPPC/MVS identify failed - Return code RC-X'return_code'

DXC104TInitialization failed - Available storage NR-'valueK', minimum required NR2-'valueK'


DXC106TInitialization failed - Return code RC-'return_code' from user initialization routine

DXC107TCan not read system configuration table TN-'table_name' -Abend code AC-X'abend_code' Reason code RSC-X'reason_code'

DXC108TInitialization failed - Parameter format invalid

DXC109TInitialization failed - TCB count parameter not in range 1-32

DXC110RStandby state - Reply with required system state (IDLE, CRAS, MESW, or NORM) or CANCEL

DXC111ICancel request accepted

DXC112RCan not obtain exclusive control for database - Reply U to proceed

DXC113EReply invalid - Ignored

DXC114IInitialization complete

DXC162TDASD initialization failed - Not enough storage

DXC163TCan not read DASD configuration table TN-'name' -Abend code AC-X'system_completion_code' Reason code RSC-X'reason_code'

DXC164TCan not continue - Not enough data sets available for database

DXC165WDYNALLOC (A) Return code 0 Error code EC-X'error_code' DSN-'data_set_name'

DXC166EFN-'function' Return code RC-X'return_code' EC-X'error_code' DSN-'data_set_name'

DXC167IData set DSN-'data_set_name' allocated

DXC168IData set DSN-'data_set_name' copy complete

DXC169EData set DSN-'data_set_name' copy failed

DXC170TCan not read either copy of control record

DXC172EGETMAIN error - Can not obtain work block for DASD termination

DXC175WDYNALLOC (U) Return code 0 Error code EC-X'error_code' DSN-'data_set_name'

DXC176EFN-'function' Return code RC-'return_code' EC-X'error_code' DSN-'data_set_name'

DXC177IData set DSN-'data_set_name' deallocated

DXC180TInitialization failed - Test data set FN-'function' Return code RC-'return_code' Reason code RSC-X'reason_code'


DXC181ETest data set FN-'function' Return code RC-'return_code' Reason code RSC-X'reason_code'

DXC182WTest data set FN-'function' Return code RC-'return_code' Reason code RSC-X'reason_code'

DXC200ROpen VTAM ACB LUN-'acbname' failed, Return code RC-X'return_code' - Reply U to retry, or C tocancel

DXC201WCRAS CT-'cras_type' CRI-'cri' CRN-'crn' not available -Return code RC-X'rr' FB2-X'ff' SC-X'ssmmuuuu'

DXC202WCRAS CT-'cras_type' CRI-'cri' CRN-'crn' not acquired - Device type not supported

DXC203TInitialization failed - No VTAM network available - Return code RC-X'rr' FDBK2 FB2-X'ff'

DXC204AVTAM operator has issued halt - Halt ALCS with 'ZASYS HALT' command

DXC206TInitialization failed - No fallback available for CRAS CT-'cras_type'

DXC207ICRAS CT-'cras_type' is CRI-'cri' CRN-'crn'

DXC208ICRAS CT-'cras_type' CRI-'cri' CRN-'crn' acquired

DXC209EResource CRN-'crn' not defined - Can not be deleted or replaced

DXC210EResource CRN-'crn' already defined - Can not be added

DXC212EResource CRN-'crn' is a different device type from replace entry - Entry cannot be replaced

DXC213EResource CRN-'crn' has duplicate other-system identification specified - Entry cannot be processed

DXC214EResource CRN-'crn' - No room in DXCRIT table to add other-system identification

DXC215EResource CRN-'crn' has duplicate HEX/TCID/IA/TA specified - Entry cannot be processed

DXC216EResource CRN-'crn' - No room in DXCSLCTB table to add HEX/TCID/IA/TA

DXC217EResource CRN-'crn' has duplicate name specified - Entry cannot be added

DXC218EResource CRN-'crn' - No room in table DXCNHT to add entry

DXC219EResource CRN-'crn' specifies an unknown terminal type

DXC220ESLC link CRN-'crn' not replaced/deleted - At least one terminal still accessed through it

DXC221ELU 6.1 link CRN-'crn' not found

DXC222EResource CRN-'crn' has no DXCREI table defined for its LDI type

DXC224TInvalid communication load module MODN-'name'

Appendix A. Messages intended for automated operations 453

DXC225TToo many resources specified

DXC226TToo many SLCLINK and WTTY resources specified

DXC227TUnknown LDTYPE specified

DXC228ESLC link CRN-'crn' not found

DXC229EALCI LU CRN-'crn' not found

DXC230TCan not read communication load module MODN-'name' -Abend code AC-X'system_completion_code' Reason code RSC-X'reason_code'

DXC231WAssociated resource ACRN-'crn1' not found for resource CRN-'crn2'

DXC232ELogical unit presentation services profile NR-X'profile_number' not supported for resource CRN-'crn'

DXC233ISLC line allocation - Unit address AD-'address' Ddname DDN-'name'

DXC234ISLC line deallocation - Ddname DDN-'name'

DXC235WSLC line allocation failure -Unit address AD-'address' Error code EC-X'error_code' Reason code RSC-X'reason_code'

DXC236WSLC line deallocation failure -Ddname DDN-'name' Error code EC-X'error_code' Reason code RSC-X'reason_code'

DXC237WDevice is not suitable for SLC - Ddname DDN-'name' UCBTYP UCBT-X'ucbtype_code'

DXC238WSLC line DCB open failure - Ddname DDN-'name'

DXC239EResource CRN-'crn' has duplicate LEID specified - Entry cannot be processed

DXC240EResource CRN-'crn' - No room in DXCLEID table to add LEID

DXC241ELU 6.1 CRN-'crn' not replaced/deleted - At least one parallel session still defined

DXC242EResource CRN-'crn' - No room in table DXCREI to add entry

DXC243EX.25 PVC XCRN-'crn' not found

DXC244EX.25 PVC XCRN-'crn' not replaced/deleted - At least one terminal still accessed through it

DXC245EType 2/3 X.25 PVC XCRN-'X.25_crn' not found for SLC link CRN-'crn'

DXC246ICRAS CRI-'cri' NetView CRN-'crn' acquired

DXC247RReply invalid - Reply U to retry or C to cancel


DXC248TCan not continue - Not enough storage available for communication table

DXC249TLoad of communication load module MODN-'name' failed - Resource CRN-'crn' in use

DXC250TALCS system failure - SERRC-error_description

DXC251WGlobal area corruption - Not all global area dumped

DXC260WLoad of module MODN-'name' failed - Unrecognizable application CSECT at offset OFS-X'offset'

DXC261WLoad of module MODN-'name' failed - reason_message

DXC262WMODN-'name' failed - Error during module load, Abend code AC-X'system_completion_code' Reasoncode RSC-X'reason_code'

DXC263TLoad of program config table TN-'name' failed -Abend code AC-X'system_completion_code' Reason code RSC-X'reason_code'

DXC264TCan not load/build internal table TN-'name' -Abend code AC-X'system_completion_code' Reason code RSC-X'reason_code'

DXC266TCan not load all ALCS entry controlled monitor programs

DXC270TCan not read CTKB

DXC280TGETMAIN for DCB failed -Abend code AC-X'system_completion_code' Reason code RSC-X'reason_code'

DXC281TCan not open DCB DDN-'ddname' - Return code RC-X'return_code'

DXC2000ELogic error - Invalid message number or prefix EC-'cccnnn'

DXC2001ELogic error - Invalid message parameters

DXC2003IALCS state change from SS1-'state1' to SS2-'state2' starting

DXC2004IALCS in SS-'state' state

DXC2005EInvalid global load message index NR-'number'

DXC2006IGlobal record load complete

DXC2007EInvalid global record type/ordinal - Slot SN-'slot_number' Directory DN-'directory_number'

DXC2008ECan not read global record - Fixed file type FT-'filetype' Ordinal ORD-'ordinal'Slot SN-'slot_number' Directory DN-'directory_number'

DXC2009ECan not find global load program PN-'name'


DXC2010IGlobal record load starting

DXC2011EInvalid directory slot number - Slot SN-'slot_number' Directory DN-'0'

DXC2012ENot enough space in global area AN-'area_number' -Slot SN-'slot_number' Directory DN-'directory_number'

DXC2014EInvalid header strip request for keypointable record -Slot SN-'slot_number' Directory DN-'directory_number'

DXC2015EGlobal load only allowed in idle state

DXC2016ENo ALCS globals defined - Check CGAF

DXC2020ECheck entry and retry - If problem persists call supervisorProblem reference information followsSE-number {CTL|OPR}-code PROG-name OFFSET-listing_address CRN-crnVOLUME volume_serial DSNAME data_set_nameMSG-message

DXC2021ESE-number CTL-code PROG-name OFFSET-listing_address CRN-crnVOLUME volume_serial DSNAME data_set_nameMSG-message

DXC2022ESE-number OPR-code PROG-name OFFSET-listing_address CRN-crnVOLUME volume_serial DSNAME data_set_nameMSG-message

DXC2401WApplication name does not exist

DXC2402WApplication name not active

DXC2403WNot routed to an application

DXC2404WRequest not processed - System restricted

DXC2405WLogon rejected from LU CRN-'crn' - Unknown LU name

DXC2406WLogon rejected from LU CRN-'crn' - Unsupported PS profile

DXC2407WLogon rejected from LU CRN-'crn' - Display width not 80 columns

DXC2408WLogon rejected from LU CRN-'crn' - Requested by installation exit

DXC2409WLogon rejected from LU CRN-'crn' - Incompatible PS profile

DXC2410WLogon rejected from LU CRN-'crn' - No session available

DXC2411WLogon rejected from LU CRN-'crn' - Response bind unacceptable


DXC2412WX25PVC XCRN-'crn' unknown terminal address TA-'ta'

DXC2413WSLC link CRN-'crn' unknown HEX-'hex' TCID-'tcid' IA-'ia' TA-'ta'

DXC2414WALCI LU CRN-'crn' unknown LEID-'leid'

DXC2415WAPPC/MVS re-identify failure

DXC2416IAPPC/MVS APPC-LU LUN-'luname' deactivated

DXC2417IAPPC/MVS APPC-LU LUN-'luname' activated

DXC2418EAPPC/MVS define TP-ID failure

DXC2419EVTAM request to release LU LUN-'luname' rejected - LU not VTAM 3270 printer

DXC2420EVTAM request to release LU LUN-'luname' rejected - Unknown LU name

DXC2421ELU LUN-'luname' logged off - Timeout expired

DXC2422WNetView unknown CRN-'crn'

DXC2490ICT-'cras_type' CRAS is now on CRN-'crn' CRI-'cri'CRAS status was CT2-'old_cras_type' - Changed by ALCS

DXC2501ENo fallback available for Prime CRAS CRN-'crn'

DXC2502WCRI-'cri' CRN-'crn' RC-'rr' FB2-'ff' SC-'ssmmuuuu' - Negative response received

DXC2503WCRI-cri CRN-crn RC-'rr' FB2-'ff' SC-'ssmmuuuu' - Non-zero RTNCD/FDBK2 received

DXC2504WCRI-'cri' CRN-'crn' RC-'rr' FB2-'ff' SC-'ssmmuuuu' - Non-zero RTNCD/FDBK2 received




DXC2511WCRI-'cri' CRN-'crn' SC-'ssmmuuuu' LEID-'leid' - ALCI - Sense data received


DXC2513WCRI-'cri' BATAP retry limit exceeded

DXC2514ECRI-'cri' BATAP lockout

DXC2515ICRI-'cri' BATAP connected


DXC2516WCRI-'cri' BATAP disconnected

DXC2517ICRN-'crn' KCN-'kcn' line out of service

DXC2518ICRN-'crn' link in control state - Data suspended

DXC2519WCRN-'crn' lost AML for message label LBL-'mm' type MT-'t'

DXC2520WCRN-'crn' KCN-'kcn' LCB received with illogical or reset ATSI

DXC2521ICRN-'crn' KCN-'kcn' line in service

DXC2522ICRN-'crn' data transmission restarted

DXC2523ICRN-'crn' stop all received

DXC2524ICRN-'crn' KCN-'kcn' stop received

DXC2525ICRN-'crn' link down

DXC2528ICRN-'crn' resume all received

DXC2529WCRN-'crn' block found after block with last block set - Type MT-'t'

DXC2530WCRN-'crn' incomplete type MT-'t' message received

DXC2531WCRN-'crn' type MT-'t' output MBI exhaustion

DXC2532WCRN-'crn' KCN-'kcn' invalid LCB received - LSI-'lsi'

DXC2533WCRN-'crn' KCN-'kcn' lost ETB

DXC2534WCRN-'crn' KCN-'kcn' lost DLE

DXC2535WCRN-'crn' message received with invalid MBI - MBI-'mbi'

DXC2536WCRN-'crn' KCN-'kcn' line in loop

DXC2537ICRN-'crn' all channels non-functioning - Cycled down

DXC2538WCRN-'crn' KCN-'kcn' EIB-'eib' received on LCB

DXC2539WCRN-'crn' KCN-'kcn' short block received - X'hex_data'

DXC2540WCRN-'crn' KCN-'kcn' AML received for unused MBI-'mm'

DXC2543WCRN-'crn' KCN-'kcn' block received not LCB or LDB - X'hex_data'

DXC2544WCRN-'crn' KCN-'kcn' repeated NAK received and discarded - X'hex_data'


DXC2545ICRN-'crn' no messages received during previous 15 mins

DXC2546ICRN-'crn' no messages sent during previous 15 mins

DXC2547ISLC send side error - Recovered - KCN-'kcn' LINK CRN-'crn' OP-'oo' SC-'ss' CC-'cc' CSW-'csw'

DXC2548WSLC send side error - Line closed - KCN-'kcn' LINK CRN-'crn' OP-'oo' SC-'ss' CC-'cc' CSW-'csw'

DXC2549ISLC receive side error - Recovered - KCN-'kcn' LINK CRN-'crn' OP-'oo' SC-'ss' CC-'cc' CSW-'csw'

DXC2550WSLC receive side error - Line closed - KCN-'kcn' LINK CRN-'crn' OP-'oo' SC-'ss' CC-'cc' CSW-'csw'

DXC2551EInvalid action code ACT-'x' in emergency exit

DXC2552ENo response from link CRN-'crn'

DXC2553ENo response from printer CRN-'crn'

DXC2554AVTAM operator has issued halt - Halt ALCS with 'ZASYS HALT' command

DXC2555ITest message - Please ignore

DXC2650ESequential file seq I/O errordev,ty,ddname,operation,error,address,BSAMDSN-'data_set_name'VS-'volume_serial'

DXC2750WAttempted access to unavailable general file NR-'gf_number' - Program PN-'name'

DXC2751IDASD data set allocated,Volume VS-'volume_serial',DSN-'data_set_name'

DXC2752IDASD data set copy complete,Volume VS-'volume_serial',DSN-'data_set_name'

DXC2753EDASD data set copy failed - Data set offline,Volume VS-'volume_serial',DSN-'data_set_name'

DXC2754EDASD data set copy failed - I/O error,Volume VS-'volume_serial',DSN-'data_set_name'

DXC2755EDASD data set deallocated - Too many I/O errors,Volume VS-'volume_serial',DSN-'data_set_name'

DXC2756IDASD data set deallocated - ZDASD VARY request,Volume VS-'volume_serial',


DSN-'data_set_name'DXC2757E

DASD operation error, FA-file_address, ID-record_id,RRN-relative_record_number,RBA-relative_byte_address,CCHHR-cylinder/head/record,Volume VS'-volume_serial',DSN-'data_set_name'

DXC2758WPT-'pool_type' pool dispense rate is NR-'number_of_records' per second

DXC2759WPT-'pool_type' pool recycled HH-'hhh' hours MM-'mm' minutes before recycle due

DXC2760WPT-'pool_type' pool will be depleted within HH-'hh' hours

DXC2875WCTKB replaced - reason

DXC2900IALCS connected to DB2 subsystem SBS-'ssnm'

DXC2901IALCS disconnected from DB2 subsystem SBS-'ssnm'

DXC2902IMVS operator has started DB2 subsystem

DXC2903IMVS operator has stopped DB2 subsystem

DXC2904EDB2 subsystem has terminated abnormally

DXC2905EDB2 connection failure -Subsystem SBS-'ssnm' Return code RC-X'return_code' Reason code RSC-X'reason_code'

DXC2906EDB2 disconnection failure -Subsystem SBS-'ssnm' Return code RC-X'return-code' Reason code RSC-X'reason-code'

DXC2907EDB2 open failure -Application plan PLN'plan' Return code RC-X'return-code' Reason code RSC-X'reason-code'

DXC2908EDB2 close failure -Application plan PLN-'plan' Return code RC-X'return-code' Reason code RSC-X'reason-code'

DXC2909EDB2 SQL call failure - Return code RC-X'return_code' Reason code RSC-X'reason_code'

DXC9000ITask TSK-'task_id' - DXCPPI active

DXC9001WTask TSK-'task_id' - DXCPPI terminated

DXC9002ITask TSK-'task_id' - DXCPPI initialized

DXC9003ETask TSK-'task_id' - Request type RQT-'request_type' failed with return code RC-'return_code'

DXC9004ETask TSK-'task_id' - Generic alert was lost with return code RC-'return_code'


DXC9005ETask TSK-'task_id' - DXCPPI internal logic error

DXC9006ETask TSK-'task_id' - AM0TLIST omitted or invalid

DXC9007ETask TSK-'task-id' - Message for TA-'ta' was lost with return code RC-'return_code'


Acronyms and abbreviations

The following acronyms and abbreviations are used in books of the ALCS Version 2 library. Not all arenecessarily present in this book.

AAAagent assembly area

ACBVTAM access method control block

ACFAdvanced Communications Function

ACF/NCPAdvanced Communications Function for the Network Control Program, usually referred to simply as"NCP"

ACF/VTAMAdvanced Communications Function for the Virtual Telecommunication Access Method, usuallyreferred to simply as "VTAM"

ACKpositive acknowledgment (SLC LCB)

ACPAirline Control Program

AIDIBM 3270 attention identifier

AIX®Advanced Interactive eXecutive

ALCairlines line control

ALCIAirlines Line Control Interconnection

ALCS/MVS/XAAirline Control System/MVS/XA

ALCS/VSEAirline Control System/Virtual Storage Extended

ALCS V2Airline Control System Version 2

AMLacknowledge message label (SLC LCB)

AMSaccess method services

AMSGAMSG application message format

APARauthorized program analysis report

APFauthorized program facility

APIapplication program interface

APPCadvanced program-to-program communications


ARINCAeronautical Radio Incorporated

ASCUagent set control unit (SITA), a synonym for "terminal control unit"

AT&TAmerican Telephone and Telegraph Co.

ATAAir Transport Association of America

ATSNacknowledge transmission sequence number (SLC)

BATAPType B application-to-application program

BSCbinary synchronous communication

CC programming language

CAFCall Attach Facility

CCWchannel command word

CDPIclearly differentiated programming interface

CECcentral electronic complex

CEUScommunication end-user system

CIVSAM control interval

CICSCustomer Information Control System

CLISTcommand list

CMCcommunication management configuration

CMLclear message label (synonym for AML)

COBOLCOmmon Business Oriented Language

CPI-CCommon Programming Interface - Communications

CPUcentral processing unit

CRAScomputer room agent set

CRIcommunication resource identifier

CRNcommunication resource name

CSAcommon service area

Acronyms and abbreviations 463

CSECTcontrol section

CSIDcross system identifier

CSWchannel status word

CTKBKeypoint record B

CTLcontrol system error

CUACommon User Access

DASDdirect access storage device

DBCSdouble-byte character set

DBRMDB2 database request module

DB2IBM DB2 for z/OS (refers to DB2)

DCBdata set control block

DECBALCS data event control block

DFdelayed file record

DFDSSData Facility Data Set Services

DFHSMData Facility Hierarchical Storage Manager

DFPData Facility Product

DFSMSData Facility Storage Management Subsystem

DFTdistributed function terminal

DIXdelete item index

DRILdata record information library

DSIdirect subsystem interface

DSECTdummy control section

DTPALCS diagnostic file processor

EBCDICextended binary-coded decimal interchange code

ECBALCS entry control block


EIBerror index byte

EIDevent identifier

EJBEnterprise Java Bean

ENQenquiry (SLC LCB)

EOFend of file

EOMend of message

EOIend of message incomplete

EOPend of message pushbutton

EOUend of message unsolicited

EPEmulation Program

EP/VSEmulation Program/VS

ETXend of text

EvCBMVS event control block

EXCPExecute Channel Program

FACEfile address compute

FIFOfirst-in-first-out

FIfile immediate record

FMfunction management

FMHfunction management header

GBgigabyte (1 073 741 824 bytes)

GDSgeneral data set

GFSget file storage (called pool file storage in ALCS)

GMTGreenwich Mean Time

GTFgeneralized trace facility (MVS)

GUPIgeneral-use programming interface


HENhigh-level network entry address

HEXhigh-level network exit address

HFSHierarchical File System

HLASMHigh Level Assembler

HLLhigh-level language

HLNhigh-level network

HLShigh-level system (for example, SITA)

HTTPHypertext Transfer Protocol

IAinterchange address

IASCInternational Air Transport Solution Centre

IATAInternational Air Transport Association

IATA5ATA/IATA transmission code 5

IATA7ATA/IATA transmission code 7

ICFintegrated catalog facility

ICSFIntegrated Cryptographic Service Facility

IDidentifier

ILBidle (SLC LCB)

IMABATAP acknowledgement

IMSInformation Management System

IMSGIMSG input message format

I/Oinput/output

IOCBI/O control block

IPInternet Protocol

IPARSInternational Programmed Airlines Reservation System

IPCSInteractive Problem Control System


IPLinitial program load

ISAinitial storage allocation

ISCintersystem communication

ISO/ANSIInternational Standards Organization/American National Standards Institute

ISPFInteractive System Productivity Facility

ISPF/PDFInteractive System Productivity Facility/Program Development Facility

ITA2International Telegraph Alphabet number 2

JCLjob control language

JESjob entry subsystem

JNDIJava Naming and Directory Interface

JSONJavaScript Object Notation

KBkilobyte (1024 bytes)

KCNlink channel number (SLC)

KSDSVSAM key-sequenced data set

LANlocal area network

LCBlink control block (SLC)

LDBlink data block (SLC)

LDIlocal DXCREI index

LEIDlogical end-point identifier

LELanguage Environment

LICRALink Control - Airline

LMTlong message transmitter

LNline number (ALCS/VSE and TPF terminology)

LN/ARIDline number and adjusted resource identifier (ALCS/VSE terminology)

LSETLoad set


LSIlink status identifier (SLC)

LUlogical unit

LU 6.2Logical Unit 6.2

MATIPMapping of airline traffic over IP

MBmegabyte (1 048 576 bytes)

MBImessage block indicator (SLC)

MCHRmodule/cylinder/head/record

MESWmessage switching

MNOTEmessage note

MQIMessage Queueing Interface

MQMMessage Queue Manager

MSNFMultisystem Networking Facility

MVSMultiple Virtual Storage (refers to MVS) (refers to both MVS/XA and MVS/ESA, and also to OS/390 andz/OS)

MVS/DFPMultiple Virtual Storage/Data Facility Product

MVS/ESAMultiple Virtual Storage/Enterprise System Architecture

MVS/XAMultiple Virtual Storage/Extended Architecture

NABnext available byte

NAKnegative acknowledgment (SLC LCB)

NCBnetwork control block (SLC)

NCPNetwork Control Program (refers to ACF/NCP)

NCP/VSNetwork Control Program/Virtual Storage.

NEFNetwork Extension Facility

NEF2Network Extension Facility 2

NPDANetwork Problem Determination Application


NPSINetwork Control Program packet switching interface

NTONetwork Terminal Option

OCRone component report

OCTMonline communication table maintenance

OLAoptimized local adapters

OMSGOMSG output message format

OPRoperational system error

OSIDother-system identification

OS/2IBM Operating System/2®

PARSProgrammed Airlines Reservation System

PDFparallel data field (refers to NCP)

PDMpossible duplicate message

PDSpartitioned data set

PDSEpartitioned data set extended

PDUpool directory update

PERprogram event recording

PFDRpool file directory record

PL/Iprogramming language one

PLMpurge long message (name of ALCS/VSE and TPF general tape)

PLUprimary logical unit

PNLpassenger name list

PNRpassenger name record

PPIBM program product

PPIprogram-to-program interface

PPMSGprogram-to-program message format


PPTprogram properties table

PRpermanently resident record

PRCprime computer room agent set

PRDTphysical record (block) descriptor table

PRPQprogramming request for price quotation

PR/SMProcessor Resource/Systems Manager

PSVTAM presentation services

PSPIproduct sensitive programming interface

PSWprogram status word

PTFprogram temporary fix

PTTPost Telephone and Telegraph Administration

PUphysical unit

PVCpermanent virtual circuit

QSAMqueued sequential access method

RACFresource access control facility

RBrequest block

RBArelative byte address

RCCrecord code check

RCPLrouting control parameter list

RCRresource control record

RCSregional control center

RDBRelational Database

RDBMRelational Database Manager

REIresource entry index

RLTrecord locator table


RMFResource Measurement Facility

RO CRASreceive-only computer room agent set

RONrecord ordinal number

RPLVTAM request parameter list

RPQrequest for price quotation

RSMresume (SLC LCB)

RTMrecovery and termination management

RUrequest unit

SAASystems Application Architecture®

SALsystem allocator list (TPF terminology)

SAMsequential access method

SDLCSynchronous Data Link Control

SDMFstandard data and message file

SDSFSystem Display and Search Facility

SDWAsystem diagnostic work area

SIDBCS shift in

SITASociété Internationale de Télécommunications Aéronautiques

SLCATA/IATA synchronous link control

SLIPserviceability level indication processing

SLNsymbolic line number

SLRService Level Reporter

SLUsecondary logical unit

SMP/ESystem Modification Program Extended

SNASystems Network Architecture

SODBCS shift out


SONsystem ordinal number

SQAsystem queue area

SQLStructured Query Language

SQLCASQL Communication Area

SQLDASQL Descriptor Area

SRBservice request block

SRGstatistical report generator

SRMSystem Resource Manager

STCsystem test compiler

STPstop (SLC LCB)

STVsystem test vehicle

SWBservice work block

SYNcharacter synchronization character

TAterminal address

TAStime available supervisor

TCBtask control block

TCIDterminal circuit identity

TCP/IPTransmission Control Protocol / Internet Protocol

TItime-initiated record

TODtime of day

TPFTransaction Processing Facility

TPF/APPCTransaction Processing Facility/Advanced Program to Program Communications

TPF/DBRTransaction Processing Facility/Data Base Reorganization

TPFDFTPF Database Facility

TPF/MVSTransaction Processing Facility/MVS (alternative name for ALCS V2)


TP_IDtransaction program identifier

TSItransmission status indicator

TSNtransmission sequence number

TSOtime-sharing option

TSO/ETime Sharing Option Extensions

TUTtest unit tape (sequential file)

UCBunit control block

UCTFUniversal Communications Test Facility

VFAvirtual file access

VIPAvirtual IP address

VMvirtual machine

VM/CMSvirtual machine/conversational monitor system

VSvirtual storage

VSAMvirtual storage access method

VSEVirtual Storage Extended

VSE/AFVirtual Storage Extended/Advanced Function

VSE/VSAMVirtual Storage Extended/Virtual Storage Access Method

VTAMVirtual Telecommunications Access Method (refers to

VTOCvolume table of contents

WASWebSphere Application Server (refers to WebSphere)

WSFWrite Structured Field

WTTYWorld Trade Teletypewriter

XMSGXMSG message switching message format

XREFALCS cross referencing facility


Glossary

Notes:

1. Acronyms and abbreviations are listed separately from this Glossary. See “Acronyms andabbreviations” on page 462.

2. For an explanation of any term not defined here, see the IBM Dictionary of Computing.

AAAA hold

See terminal hold.abnormal end of task (abend)

Termination of a task before its completion because of an error condition that cannot be resolved byrecovery facilities while the task is executing.

access method services (AMS)A utility program that defines VSAM data sets (or files) and allocates space for them, converts indexedsequential data sets to key-sequenced data sets with indexes, modifies data set attributes in thecatalog, facilitates data set portability between operating systems, creates backup copies of data setsand indexes, helps make inaccessible data sets accessible, and lists data set records and catalogentries.

activity control variableA parameter that ALCS uses to control its workload. The system programmer defines activity controlvariables in the ALCS system configuration table generation.

Advanced Communications Function for the Network Control Program (ACF/NCP)An IBM licensed program that provides communication controller support for single-domain,multiple-domain, and interconnected network capability.

Advanced Program-to-Program Communications (APPC)A set of inter-program communication services that support cooperative transaction processing in anSNA network. APPC is the implementation, on a given system, of SNA's logical unit type 6.2 (LU 6.2).See APPC component and APPC transaction scheduler.

Aeronautical Radio Incorporated (ARINC)An organization which provides communication facilities for use within the airline industry.

agent assembly area (AAA)A fixed-file record used by IPARS applications. One AAA record is associated with each terminal andholds data that needs to be kept beyond the life of an entry. For example, to collect information frommore than one message.

agent setSynonym for communication terminal.

agent set control unit (ASCU)Synonym for terminal interchange.

Airline Control Program (ACP)An earlier version of the IBM licensed program Transaction Processing Facility (TPF).

Airline Control System (ALCS)A transaction processing platform providing high performance, capacity, and availability, that runsspecialized (typically airline) transaction processing applications.

Airline Control System/Multiple Virtual Storage/Extended Architecture (ALCS/MVS/XA)An ALCS release designed to run under an MVS/XA operating system.

Airline Control System Version 2 (ALCS V2)An ALCS release designed to run under a z/OS operating system.


Airline Control System/Virtual Storage Extended (ALCS/VSE)An ALCS release designed to run under a VSE/AF operating system.

airlines line control (ALC)A communication protocol particularly used by airlines.

Airlines Line Control Interconnection (ALCI)A feature of Network Control Program (NCP) that allows it to manage ALC networks in conjunctionwith a request for price quotation (RPQ) scanner for the IBM 3745 communication controller.

Airline X.25 (AX.25)A discipline conforming to the ATA/IATA AX.25 specification in the ATA/IATA publication ATA/IATAInterline Communications Manual, ATA/IATA document DOC.GEN 1840. AX.25 is based on X.25 and isintended for connecting airline computer systems to SITA or ARINC networks.

ALCS commandA command addressed to the ALCS system. All ALCS commands start with the letter Z (they are alsocalled "Z messages") and are 5 characters long.

These commands allow the operator to monitor and control ALCS. Many of them can only be enteredfrom CRAS terminals. ALCS commands are called "functional messages" in TPF.

ALCS data collection fileA series of sequential data sets to which ALCS writes performance-related data for subsequentprocessing by the statistical report generator or other utility program. See also data collection andstatistical report generator.

ALCS diagnostic fileA series of sequential data sets to which the ALCS monitor writes all types of diagnostic data forsubsequent processing by the diagnostic file processor.

ALCS diagnostic file processorAn offline utility, often called the "post processor", that reads the ALCS diagnostic file and formats andprints the dump, trace, and system test vehicle (STV) data that it contains.

ALCS entry dispatcherThe ALCS online monitor's main work scheduler. Often called the "CPU loop".

ALCS offline programAn ALCS program that runs as a separate MVS job (not under the control of the ALCS online monitor).

ALCS online monitorThe part of ALCS that performs the services for the ECB-controlled programs and controls theiractions.

ALCS trace facilityAn online facility that monitors the execution of application programs. When it meets a selectedmonitor-request macro, it interrupts processing and sends selected data to an ALCS display terminal,to the ALCS diagnostic file, or to the system macro trace block. See also instruction step.

The ALCS trace facility also controls tracing to the MVS generalized trace facility (GTF), for selectedVTAM communication activity, and controls tracing of input and output messages to a (wrap around)online trace area for selected communication resources.

ALCS update log fileA series of sequential data sets in which the ALCS monitor records changes to the real-time database.

ALCS user fileA series of sequential data sets to which you may write all types of diagnostic data for subsequentprocessing by an offline processor. You write the data from an installation-wide monitor exit using thecallable service UWSEQ.

allocatable poolThe ALCS record class that includes all records on the real-time database. Within this class, there isone record type for each DASD record size.

Glossary 475

The allocatable pool class is special in that ALCS itself can dispense allocatable pool records anduse them for other real-time database record classes. For example, all fixed-file records are alsoallocatable pool records (they have a special status of "in use for fixed file").

When ALCS is using type 2 long-term pool dispense, ALCS satisfies requests for long-term pool bydispensing available allocatable pool records.

See DASD record, real-time database, record class, and record type.

alternate CRASA computer room agent set (CRAS) that is not Prime CRAS or receive only CRAS. See computer roomagent set, Prime CRAS, and receive only CRAS.

alternate CRAS printerA CRAS printer that is not receive only CRAS. See CRAS printer and receive only CRAS.

answerbackA positive acknowledgement (ACK) from an ALC printer.

APPC componentThe component of MVS that is responsible for extending LU 6.2 and SAA CPI Communicationsservices to applications running in any MVS address space. Includes APPC conversations andscheduling services.

APPC transaction schedulerA program such as ALCS that is responsible for scheduling incoming work requests from cooperativetransaction programs.

application planSee DB2 application plan.

applicationA group of associated application programs that carry out a specific function.

application global areaAn area of storage in the ALCS address space containing application data that any entry can access.

The application global area is subdivided into keypointable and nonkeypointable records.Keypointable records are written to the database after an update; nonkeypointable records eithernever change, or are reinitialized when ALCS restarts.

C programs refer to global records and global fields within the application global area.

application programA program that runs under the control of ALCS. See also ECB-controlled program.

application program load moduleIn ALCS, a load module that contains one or more application programs.

application queueIn message queuing with ALCS, any queue on which application programs put and get messages usingMQI calls.

assignAllocate a general sequential file to an entry. The TOPNC monitor-request macro (or equivalentC function) opens and allocates a general sequential file. The TASNC monitor-request macro (orequivalent C function) allocates a general sequential file that is already open but not assigned to anentry (it is reserved).

associated resourceSome ALCS commands generate output to a printer (for example, ZDCOM prints information abouta communication resource). For this type of command the printed output goes to the associatedresource; that is, to a printer associated with the originating display. There is also a response to theoriginating display that includes information identifying the associated resource.

asynchronous traceOne mode of operation of the ALCS trace facility. Asynchronous trace is a conversational trace facilityto interactively trace entries that do not originate from a specific terminal.


automatic storage blockA storage block that is attached to an entry, but is not attached at a storage level. An assemblerprogram can use the ALASC monitor-request macro to obtain an automatic storage block and BACKCmonitor-request macro to release it. C programs cannot obtain automatic storage blocks.

Bbackward chain

The fourth fullword of a record stored on the ALCS database, part of the record header. See chaining ofrecords.

When standard backward chaining is used, this field contains the file address of the previous record inthe chain, except that the first record contains the file address of the last record in the chain. (If thereis only one record, the backward chain field contains zeros.)

balanced pathA path where no single component (channel, DASD director or control unit, head of string, and internalpath to the DASD device) is utilized beyond the limits appropriate to the required performance.

barIn the MVS 64-bit address space, a virtual line called the bar marks the 2-gigabyte address. Thebar separates storage below the 2-gigabyte address, called below the bar, from storage above the2-gigabyte address, called above the bar.

BATAPType B application-to-application program

Binary Synchronous Communication (BSC)A form of telecommunication line control that uses a standard set of transmission control charactersand control character sequences, for binary synchronous transmission of binary-coded data betweenstations.

bindSee DB2 bind

BINDIn SNA, a request to activate a session between two logical units (LUs). The BIND request is sentfrom a primary LU to a secondary LU. The secondary LU uses the BIND parameters to help determinewhether it will respond positively or negatively to the BIND request.

binderThe program that replaces the linkage editor and batch loader programs that were provided withearlier versions of MVS.

BIND imageIn SNA, the set of fields in a BIND request that contain the session parameters.

blockSee storage block.

Ccatastrophic

A type of system error that results in the termination of ALCS.chain-chase

See Recoup.chaining of records

One record can contain the file address of another (usually a pool-file record). The addressed record issaid to be chained from the previous record. Chains of records can contain many pool-file records. Seeforward chain and backward chain.

classSee record class.

Glossary 477

clearly differentiated programming interfaces (CDPI)A set of guidelines for developing and documenting product interfaces so that there is cleardifferentiation between interfaces intended for general programming use (GUPIs) and those intendedfor other specialized tasks.

closeClose a sequential file data set (MVS CLOSE macro) and deallocate it from ALCS. For generalsequential files this is a function of the TCLSC monitor-request macro (or equivalent C function).ALCS automatically closes other sequential files at end-of-job.

commandSee ALCS command.

command list (CLIST)A sequential list of commands, control statements, or both, that is assigned a name. When the nameis invoked the commands in the list are executed.

commitAn operation that terminates a unit of recovery. Data that was changed is now consistent.

common entry point (CEP)A function in the Transaction Processing Facility Database Facility (TPFDF) product that providescommon processing for all TPFDF macro calls issued by ALCS application programs. It also providestrace facilities for TPFDF macro calls.

Common Programming Interface - Communications (CPI-C)The communication element of IBM Systems Application Architecture (SAA). CPI-C provides aprogramming interface that allows program-to-program communication using the IBM SNA logicalunit 6.2.

Common User AccessGuidelines for the dialog between a user and a workstation or terminal.

communication management configuration (CMC)A technique for configuring a network that allows for the consolidation of many network managementfunctions for the entire network in a single host processor.

communication resourceA communication network component that has been defined to ALCS. These include each terminalon the network and other network components that ALCS controls directly (for example, SLC links).Resources can include, for example:

SNA LUs (including LU 6.1 links)ALC terminalsSLC and WTTY linksApplications.

communication resource identifier (CRI)A 3-byte field that uniquely identifies an ALCS communication resource. It is equivalent to theLN/IA/TA in TPF and the LN/ARID in ALCS/VSE. ALCS generates a CRI for each resource.

communication resource name (CRN)A 1- to 8-character name that uniquely identifies an ALCS communication resource. For SNA LUs, it isthe LU name. The system programmer defines the CRN for each resource in the ALCS communicationgeneration.

communication resource ordinalA unique number that ALCS associates with each communication resource. An installation can usethe communication resource ordinal as a record ordinal for a particular fixed-file record type. Thisuniquely associates each communication resource with a single record.

For example, IPARS defines a fixed-file record type (#WAARI) for AAA records. Each communicationresource has its own AAA record - the #WAARI record ordinal is the communication resource ordinal.See also record ordinal and agent assembly area.


compilerA program that translates instructions written in a high level programming language into machinelanguage.

computer room agent set (CRAS)An ALCS terminal that is authorized for the entry of restricted ALCS commands.

Prime CRAS is the primary terminal that controls the ALCS system. Receive Only CRAS (RO CRAS) isa designated printer or NetView operator identifier to which certain messages about system functionand progress are sent.

configuration data set(1) A data set that contains configuration data for ALCS. See also configuration-dependent table .

(2) The ALCS record class that includes all records on the configuration data set. There is only onerecord type for this class. See record class and record type.

configuration-dependent tableA table, constructed by the ALCS generation process, which contains configuration-dependent data.Configuration-dependent tables are constructed as conventional MVS load modules. In ALCS V2,there are separate configuration-dependent tables for:

System dataDASD dataSequential file dataCommunication dataApplication program data.

See also configuration data set.

control byteThe fourth byte of a record stored on the ALCS database, part of the record header. ALCS ignores thisbyte; some applications, however, make use of it.

control interval (CI)A fixed-length area of direct access storage in which VSAM stores records. The control interval is theunit of information that VSAM transmits to or from direct access storage.

control transferThe process that the ALCS online monitor uses to create a new entry and to transfer control to anECB-controlled program.

conversation_ID:An 8-byte identifier, used in Get_Conversation calls, that uniquely identifies a conversation.APPC/MVS returns a conversation_ID on the CMINIT, ATBALLOC, and ATBGETC calls; aconversation_ID is required as input on subsequent APPC/MVS calls.

CPU loopSee ALCS entry dispatcher.

CRAS printerA computer room agent set (CRAS) that is a printer terminal. See computer room agent set.

CRAS displayA computer room agent set (CRAS) that is a display terminal. See computer room agent set.

CRAS fallbackThe automatic process that occurs when the Prime CRAS or receive only CRAS becomes unusable bywhich an alternate CRAS becomes Prime CRAS or receive only CRAS. See also Prime CRAS, receiveonly CRAS, and alternate CRAS.

create serviceAn ALCS service that enables an ALCS application program to create new entries for asynchronousprocessing. The new ECBs compete for system resources and, once created, are not dependent orconnected in any way with the creating ECB.

Glossary 479

cycling the systemThe ALCS system can be run in one of four different system states. Altering the system state is calledcycling the system. See SLC link for another use of the term "cycling".

DDASD record

A record stored on a direct access storage device (DASD). ALCS allows the same range of sizes forDASD records as it allows for storage blocks, except no size L0 DASD records exist.

data collectionAn online function that collects data about selected activity in the system and sends it to the ALCSdata collection file, if there is one, or to the ALCS diagnostic file. See also statistical report generator.

database request module (DBRM)A data set member created by the DB2 precompiler that contains information about SQL statements.DBRMs are used in the DB2 bind process. See DB2 bind.

data-collection areaAn ECB area used by the ALCS online monitor for accumulating statistics about an entry.

data event control block (DECB)An ALCS control block, that may be acquired dynamically by an entry to provide a storage level anddata level in addition to the 16 ECB levels. It is part of entry storage.

The ALCS DECB is independent of the MVS control block with the same name.

Data Facility Storage Management Subsystem (DFSMS)An MVS operating environment that helps automate and centralize the management of storage. Itprovides the storage administrator with control over data class, management class, storage group,and automatic class selection routine definitions.

Data Facility Sort (DFSORT)An MVS utility that manages sorting and merging of data.

data fileA sequential data set, created by the system test compiler (STC) or by the ZDATA DUMP command,that contains data to be loaded on to the real-time database. (An ALCS command ZDATA LOAD can beused to load data from a data file to the real-time database.) A data file created by STC is also called a"pilot" or "pilot tape".

data levelAn area in the ECB or a DECB used to hold the file address, and other information about a record. SeeECB level and DECB level.

data record information library (DRIL)A data set used by the system test compiler (STC) to record the formats of data records on thereal-time system. DRIL is used when creating data files.

DB2 application planThe control structure produced during the bind process and used by DB2 to process SQL statementsencountered during program execution. See DB2 bind.

DB2 bindThe process by which the output from the DB2 precompiler is converted to a usable control structurecalled a package or an application plan. During the process, access paths to the data are selected andsome authorization checking is performed.

DB2 Call Attach Facility (CAF)An interface between DB2 and batch address spaces. CAF allows ALCS to access DB2.

DB2 for z/OSAn IBM licensed program that provides relational database services.

DB2 host variableIn an application program, an application variable referenced by embedded SQL statements.


DB2 packageAlso called application package. An object containing a set of SQL statements that have been boundstatically and that are available for processing. See DB2 bind.

DB2 package listAn ordered list of package names that may be used to extend an application plan.

DECB levelWhen an application program, running under ALCS, reads a record from a file, it must "own" a storageblock in which to put the record. The address of the storage block may be held in an area of a DECBcalled a storage level.

Similarly, there is an area in a DECB used for holding the 8-byte file address, record ID, and recordcode check (RCC) of a record being used by an entry. This is a data level.

The storage level and data level in a DECB, used together, are called a DECB level.

See also ECB level.

diagnostic fileSee ALCS diagnostic file.

dispatching priorityA number assigned to tasks, used to determine the order in which they use the processing unit in amultitasking situation.

dispense (a pool-file record)To allocate a long-term or short-term pool-file record to a particular entry. ALCS performs this actionwhen requested by an application program. See release a pool-file record.

double-byte character setA set of characters in which each character is represented by 2 bytes. Languages such as Japanese,Chinese, and Korean, which contain more symbols than can be represented by 256 code points,require double-byte character sets.

Because each character requires 2 bytes, entering, displaying, and printing DBCS characters requireshardware and supporting software that are DBCS-capable.

duplexA communication link on which data can be sent and received at the same time. Synonymous with fullduplex. Communication in only one direction at a time is called "half-duplex". Contrast with simplextransmission.

duplex databaseSynonym for duplicated database.

duplicated databaseA database where each data set is a mirrored pair. In ALCS, you can achieve this using either ALCSfacilities or DASD controller facilities (such as the IBM 3990 dual copy facility). See mirrored pair.

dynamic program linkageProgram linkage where the connection between the calling and called program is established duringthe execution of the calling program. In ALCS dynamic program linkage, the connection is establishedby the ALCS ENTER/BACK services. Contrast with static program linkage.

dynamic SQLSQL statements that are prepared and executed within an application program while the programis executing. In dynamic SQL, the SQL source is contained in host language variables rather thanbeing coded into the application program. The SQL statement can change several times during theapplication program's execution. Contrast with embedded SQL.

EECB-controlled program

A program that runs under the control of an entry control block (ECB). These programs can beapplication programs or programs that are part of ALCS, for example the ALCS programs that processoperator commands (Z messages). ECB-controlled programs are known as E-type programs in TPF.

Glossary 481

ECB levelWhen an application program, running under ALCS, reads a record from file, it must "own" a storageblock in which to put the record. The address of the storage block may be held in an area of the ECBcalled a storage level.

There are 16 storage levels in the ECB. A storage block with its address in slot zero in the ECB is saidto be attached on level zero.

Similarly, there are 16 areas in the ECB that may be used for holding the 4-byte file addresses, recordID, and record code check (RCC) of records being used by an entry. These are the 16 data levels.

Storage levels and data levels, used together, are called ECB levels.

See also DECB level.

embedded SQLAlso called static SQL. SQL statements that are embedded within an application program and areprepared during the program preparation process before the program is executed. After it is prepared,the statement itself does not change (although values of host variables specified within the statementcan change). Contrast with dynamic SQL.

Emulation Program/Virtual Storage (EP/VS)A component of NCP/VS that ALCS V2 uses to access SLC networks.

ENTER/BACKThe general term for the application program linkage mechanism provided by ALCS.

entryThe basic work scheduling unit of ALCS. An entry is represented by its associated entry control block(ECB). It exists either until a program that is processing that entry issues an EXITC monitor-requestmacro (or equivalent C function), or until it is purged from the system. An entry is created foreach input message, as well as for certain purposes unrelated to transactions. One transaction cantherefore generate several entries.

entry control block (ECB)A control block that represents a single entry during its life in the system.

entry dispatcherSee ALCS entry dispatcher.

entry macro trace blockThere is a macro trace block for each entry. Each time an entry executes a monitor-request macro (ora corresponding C function), ALCS records information in the macro trace block for the entry.

This information includes the macro request code, the name of the program that issued the macro,and the displacement in the program. The ALCS diagnostic file processor formats and prints thesemacro trace blocks in ALCS system error dumps.

See also system macro trace block.

entry storageThe storage associated with an entry. It includes the ECB for the entry, storage blocks that areattached to the ECB or DECBs, storage blocks that are detached from the ECB or DECBs, automaticstorage blocks, and DECBs. It also includes heap storage (for high-level language or assemblerlanguage programs) and stack storage (for high-level language programs).

equateInformal term for an assignment instruction in assembler languages.

error index byte (EIB)See SLC error index byte.

extended bufferA storage area above 2 GB used for large messages.

extended message formatFor input and output messages, a message format which includes a 4-byte field for the messagelength.


Execute Channel Program (EXCP)An MVS macro used by ALCS V2 to interface to I/O subsystems for SLC support.

Ffetch access

Access which only involves reading (not writing). Compare with store access.file address

4-byte (8 hexadecimal digits) value or 8-byte value in 4x4 format (low order 4-bytes contain a 4-bytefile address, high order 4 bytes contain hexadecimal zeros) that uniquely identifies an ALCS record onDASD. FIND/FILE services use the file address when reading or writing DASD records. See fixed fileand pool file.

file address compute routine (FACE)An ALCS routine, called by a monitor-request macro (or equivalent C function) that calculates the fileaddress of a fixed-file record. The application program provides the FACE routine with the fixed-filerecord type and the record ordinal number. FACE returns the 4-byte file address.

There is also an FAC8C monitor-request macro (or equivalent C function), that will return an 8-bytefile address in 4x4 format.

FIND/FILEThe general term for the DASD I/O services that ALCS provides.

fixed fileAn ALCS record class - one of the classes that reside on the real-time database. All fixed-file recordsare also allocatable pool records (they have a special status of "in use for fixed file").

Within this class there are two record types reserved for use by ALCS itself (#KPTRI and #CPRCR).There can also be installation-defined fixed-file record types.

Each fixed-file record type is analogous to a relative file. Applications access fixed-file records byspecifying the fixed-file record type and the record ordinal number. Note however that fixed-filerecords are not physically organized as relative files (logically adjacent records are not necessarilyphysically adjacent).

See real-time database, record class, and record type. See also system fixed file. Contrast with poolfile.

fixed-file recordOne of the two major types of record in the real-time database (the other is a pool-file record). Whenthe number of records of a particular kind will not vary, the system programmer can define a fixed filerecord type for these records. ALCS application programs accessing fixed-file records use the ENTRCmonitor-request macro to invoke the 4-byte file address compute routine (FACE or FACS) or use theFAC8C monitor-request macro to compute an 8-byte file address. The equivalent C functions are faceor facs or tpf_fac8c.

fixed-file record type(Known in TPF as FACE ID.) The symbol, by convention starting with a hash sign (#) 1 which identifiesa particular group of fixed-file records. It is called the fixed-file record type symbol. The equated valueof this symbol (called the fixed-file record type value) also identifies the fixed-file record type.

forward chainThe third fullword of a record stored on the ALCS database (part of the record header). When standardforward chaining is used, this field contains the file address of the next record in the chain, except thatthe last (or only) record contains binary zeros.

full-duplexDeprecated term for duplex.

1 This character might appear differently on your equipment. It is the character represented by hexadecimal7B.

Glossary 483

functional messageSee ALCS command.

Ggeneral data set (GDS)

The same as a general file, but accessed by different macros or C functions in ALCS programs.general file

(1) A DASD data set (VSAM cluster) that is used to communicate data between offline utility programsand the online system. General files are not part of the real-time database.

(2) The ALCS record class that includes all records on the general files and general data sets. Eachgeneral file and general data set is a separate record type within this class. See record class andrecord type.

general file recordA record on a general file.

generalized trace facility (GTF)An MVS trace facility. See also ALCS trace facility.

general sequential fileA class of sequential data set that is for input or output. ALCS application programs must haveexclusive access to a general sequential file before they can read or write to it. See also real-timesequential file.

general tapeTPF term for a general sequential file.

general-use programming interface (GUPI)An interface intended for general use in customer-written applications.

get file storage (GFS)The general term for the pool file dispense mechanisms that ALCS provides.

global areaSee application global area.

global resource serializationThe process of controlling access of entries to a global resource so as to protect the integrity of theresource.

Hhalf-duplex

A communication link that allows transmission in one direction at a time. Contrast with duplex.halt

(1) The ALCS state when it is terminated.

(2) The action of terminating ALCS.

heapAn area of storage that a compiler uses to satisfy requests for storage from a high-level language (forexample, calloc or malloc C functions). ALCS provides separate heaps for each entry (if needed).The heap is part of entry storage. Assembler language programs may also obtain or release heapstorage using the CALOC, MALOC, RALOC, and FREEC monitor-request macros.

High Level Assembler (HLASM)A functional replacement for Assembler H Version 2. HLASM contains new facilities forimproving programmer productivity and simplifying assembler language program development andmaintenance.

high-level language (HLL)A programming language such as C or COBOL.


high-level language (HLL) storage unitAlternative name for a type 2 storage unit. See storage unit.

high-level network (HLN)A network that provides transmission services between transaction processing systems (for example,ALCS) and terminals. Strictly, the term "high-level network" applies to a network that connects totransaction processing systems using SLC. But in ALCS publications, this term is also used for anetwork that connects by using AX.25 or MATIP.

high-level network designator (HLD)The entry or exit point of a block in a high-level network. For SLC networks, it is the SLC address of aswitching center that is part of a high-level network. It comprises two bytes in the 7-bit transmissioncode used by SLC.

HLN entry address (HEN)The high-level designator of the switching center where a block enters a high-level network.

HLN exit address (HEX)The high-level designator of the switching center where a block leaves a high-level network.

holdA facility that allows multiple entries to share data, and to serialize access to the data. The data canbe a database record, or any named data resource. This facility can be used to serialize conflictingprocesses. See also record hold and resource hold.

host variableSee DB2 host variable

HTTP enablerPart of the z/OS Client Web Enablement Toolkit which provides RESTful services enabling a z/OSapplication HTTP client to access Web services.

Iinformation block

See SLC link data block.initial storage allocation (ISA)

An area of storage acquired at initial entry to a high-level language program. ALCS provides a separateISA for each entry (if required). The ISA is part of entry storage.

initiation queueIn message queuing, a local queue on which the queue manager puts trigger messages. You candefine an initiation queue to ALCS, in order to start an ALCS application automatically when a triggermessage is put on the queue. See trigger message.

input/output control block (IOCB)A control block that represents an ALCS internal "task". For example, ALCS uses an IOCB to process aDASD I/O request.

input queueIn message queuing with ALCS, you can define a local queue to ALCS in order to start an ALCSapplication automatically when a message is put on that queue. ALCS expects messages on the inputqueue to be in PPMSG message format. See PPMSG.

installation-wide exitThe means specifically described in an IBM software product's documentation by which an IBMsoftware product may be modified by a customer's system programmers to change or extend thefunctions of the IBM software product. Such modifications consist of exit routines written to replacean existing module of an IBM software product, or to add one or more modules or subroutines toan IBM software product for the purpose of modifying (including extending) the functions of the IBMsoftware product. Contrast with user exit.

instruction stepOne mode of operation of the ALCS trace facility. Instruction step is a conversational trace facility thatstops the traced application program before the execution of each processor instruction.

Glossary 485

Integrated Cryptographic Service Facility (ICSF)A facility on z/OS that provides data encryption and decryption services.

Interactive System Productivity Facility (ISPF)An IBM licensed program that serves as a full-screen editor and dialog manager. ISPF providesa means of generating standard screen panels and interactive dialog between the applicationprogrammer and terminal user.

interchange address (IA)In ALC, the 1-byte address of a terminal interchange. Different terminal interchanges connected tothe same ALC link have different interchange addresses. Different terminal interchanges connected todifferent ALC links can have the same interchange address. See also terminal interchange

International Programmed Airlines Reservation System (IPARS)A set of applications for airline use. The principal functions are reservations and message switching.

IPARS for ALCSThe ALCS shipment includes IPARS as a sample application, and installation verification aid for ALCS.

JJSON Parser

Part of the z/OS Client Web Enablement Toolkit which provides a generic, native z/OS JavaScriptObject Notation (JSON) parser for z/OS applications

KKCN

Abbreviation for an SLC channel number. See SLC channel.keypointable

See application global area.keypoint B (CTKB)

A record that contains dynamic system information that ALCS writes to DASD when it is updated sothat ALCS can restart from its latest status.

LLanguage Environment

A common run-time environment and common run-time services for z/OS high level languagecompilers.

levelSee ECB level.

line number (LN)(1) In ALC, the 1-byte address of an ALC link. Different links connected to the same communicationcontroller have different line numbers. Different links connected to different communicationcontrollers can have the same line number.

(2) Synonym for symbolic line number.

Link Control -- Airline (LICRA)The name of a programming request for price quotation (PRPQ) to the IBM 3705 Emulation Program(EP/VS). This modifies EP/VS to support SLC networks.

link control block (LCB)See SLC link control block.

link data block (LDB)See SLC link data block.

link traceSee SLC link trace.


local DXCREI index (LDI)The first byte of a communication resource indicator (CRI).

local queueIn message queuing, a queue that belongs to the local queue manager. A local queue can contain a listof messages waiting to be processed. Contrast with remote queue.

lockA serialization mechanism whereby a resource is restricted for use by the holder of the lock. See alsohold.

logSee ALCS update log.

loggingThe process of writing copies of altered database records to a sequential file. This is the method usedto provide an up-to-date copy of the database should the system fail and the database have to berestored. The database records are logged to the ALCS update log file.

logical end-point identifier (LEID)In NEF2 and ALCI environments, a 3-byte identifier assigned to an ALC terminal.

logical unit type 6.2 (LU 6.2)The SNA logical unit type that supports general communication between programs in a distributedprocessing environment; the SNA logical unit type on which Common Programming Interface -Communications (CPI-C) is built.

log inTPF term for establishing routing between a terminal and an application.

log onEstablish a session between an SNA terminal and an application such as ALCS. See also routing.

logon modeIn VTAM, a set of predefined session parameters that can be sent in a BIND request. When a set isdefined, a logon mode name is associated with the set.

logon mode tableIn VTAM, a table containing several predefined session parameter sets, each with its own logon modename.

long message transmitter (LMT)A part of the IPARS application that is responsible for blocking and queuing printer messages foroutput. Also called XLMT.

long-term poolAn ALCS record class - one of the classes that reside on the real-time database. Within thisclass, there is one record type for each DASD record size. All long-term pool-file records are alsoallocatable pool records. ALCS application programs can use long-term pool records for long-lived orhigh-integrity data. See pool file, real-time database, record class, and record type.

L0, L1, L2, L3, ..., L8Assembler symbols (and defined values in C) for the storage block sizes and record sizes that ALCSsupports. See DASD record and storage block size.

Mmacro trace block

See entry macro trace block and system macro trace block.Mapping of Airline Traffic over IP (MATIP)

A protocol for transporting traditional airline messages over an IP (Internet Protocol) network.Internet RFC (Request for Comments) number 2351 describes the MATIP protocol.

MBI exhaustionThe condition of an SLC link when a sender cannot transmit another message because all 7 SLCmessage labels are already "in use"; that is, the sender must wait for acknowledgement of a message

Glossary 487

so that it can reuse the corresponding message label. See also SLC link, SLC message label, and SLCmessage block indicator.

messageFor terminals with an Enter key, an input message is the data that is sent to the host when the Enterkey is hit. A response message is the data that is returned to the terminal. WTTY messages havespecial "start/end of message" character sequences. One or more input and output message pairsmake up a transaction.

message block indicatorSee SLC message block indicator.

message labelSee SLC message label.

Message Queue Interface (MQI)The programming interface provided by the IBM WebSphere MQ message queue managers. Thisprogramming interface allows application programs to access message queuing services.

message queue managerSee queue manager.

message queuingA programming technique in which each program within an application communicates with theother programs by putting messages on queues. This enables asynchronous communication betweenprocesses that may not be simultaneously active, or for which no data link is active. The messagequeuing service can assure subsequent delivery to the target application.

message switchingAn application that routes messages by receiving, storing, and forwarding complete messages. IPARSfor ALCS includes a message switching application for messages that conform to ATA/IATA industrystandards for interline communication ATA/IATA Interline Communications Manual, DOC.GEN/1840.

mirrored pairTwo units that contain the same data and are referred to by the system as one entity.

monitor-request macroAssembler language macro provided with ALCS, corresponding to TPF "SVC-type" or "controlprogram" macros. Application programs use these macros to request services from the onlinemonitor.

MQ BridgeThe ALCS MQ Bridge allows application programs to send and receive messages using WebSphereMQ for z/OS queues, without the need to code MQ calls in those programs. The MQ Bridge installation-wide monitor exits USRMQB0, USRMQB1, USRMQB2, and USRMQB3 allow you to customize thebehaviour of the MQ Bridge to suit your applications.

MQSeriesA previous name for WebSphere MQ.

multibyte characterA mixture of single-byte characters from a single-byte character set and double-byte characters froma double-byte character set.

multiblock messageIn SLC, a message that is transmitted in more than one link data block. See link data block.

Multiple Virtual Storage/Data Facility Product (MVS/DFP)An MVS licensed program that isolates applications from storage devices, storage management, andstorage device hierarchy management.

Multisystem Networking Facility (MSNF)An optional feature of VTAM that permits these access methods, together with NCP, to control amultiple-domain network.


Nnamelist

In message queuing, a namelist is an object that contains a list of other objects.native file address

For migration purposes ALCS allows two or more file addresses to refer to the same database orgeneral file record. The file address that ALCS uses internally is called the native file address.

NCP Packet Switching Interface (NPSI)An IBM licensed program that allows communication with X.25 lines.

NetViewA family of IBM licensed programs for the control of communication networks.

NetView operator identifier (NetView operator ID)A 1- to 8-character name that identifies a NetView operator.

NetView programAn IBM licensed program used to monitor a network, manage it, and diagnose network problems.

NetView resourceA NetView operator ID which identifies one of the following:

• A NetView operator logged on to a terminal.• A NetView operator ID automation task. One of these tasks is used by ALCS to route RO CRAS

messages to the NetView Status Monitor Log (STATMON).

network control block (NCB)A special type of message, used for communication between a transaction processing system anda high-level network (HLN). For example, an HLN can use an NCB to transmit information about thenetwork to a transaction processing system.

For a network that connects using SLC, an NCB is an SLC link data block (LDB). Indicators in the LDBdifferentiate NCBs from other messages.

For a network that connects using AX.25, NCBs are transmitted across a dedicated permanent virtualcircuit (PVC).

Network Control Program (NCP)An IBM licensed program resident in an IBM 37xx Communication Controller that controls attachedlines and terminals, performs error recovery, and routes data through the network.

Network Control Program Packet Switching Interface (NPSI)An IBM licensed program that provides a bridge between X.25 and SNA.

Network Control Program/Virtual Storage (NCP/VS)An IBM licensed program. ALCS V2 uses the EP/VS component of NCP/VS to access SLC networks.

Network Extension Facility (NEF)The name of a programming request for price quotation (PRPQ P09021) that allows management ofALC networks by NCP; now largely superseded by ALCI.

Network Terminal Option (NTO)An IBM licensed program that converts start-stop terminal device communication protocols andcommands into SNA and VTAM communication protocols and commands. ALCS uses NTO to supportWorld Trade Teletypewriter (WTTY).

Oobject

In message queuing, objects define the attributes of queue managers, queues, process definitions,and namelists.

offlineA function or process that runs independently of the ALCS online monitor. For example, the ALCSdiagnostic file processor is an offline function. See also ALCS offline program.

Glossary 489

onlineA function or process that is part of the ALCS online monitor, or runs under its control. For example, allALCS commands are online functions. See also ALCS online monitor.

openAllocate a sequential file data set to ALCS and open it (MVS OPEN macro). For general sequential filesthis is a function of the TOPNC monitor-request macro (or equivalent C function). ALCS automaticallyopens other sequential files during restart.

optimized local adapters (OLA) for WebSphere Application Server for z/OS (WAS)Built-in, high-speed, bi-directional adapters for calls between WebSphere Application Server forz/OS and ALCS in another address space on the same z/OS image. OLA allows ALCS customers tosupport an efficient integration of newer Java-based applications with ALCS-based applications. Aset of callable services can be used by ALCS assembler or C/C++ programs for exchanging datawith applications running in WebSphere Application Server for z/OS. For more information on thecallable services (with names of the form BBOA1xxx) see the IBM Information Center for WebSphereApplication Server - Network Deployment (z/OS) and search for BBOA1. You can use the USRWAS1installation-wide monitor to verify the caller's authority and to identify input and output messages.

operator commandSee ALCS command. Can also refer to non-ALCS commands, for example, MVS or VTAM commands.

ordinalSee communication resource ordinal and record ordinal.

Ppackage

See DB2 packagepackage list

See DB2 package listpadded ALC

A transmission code that adds one or more bits to the 6-bit airline line control (ALC) transmissioncode so that each ALC character occupies one character position in a protocol that uses 7- or 8-bittransmission codes. See also airlines line control.

padded SABRESynonym for padded ALC.

passenger name record (PNR)A type of record commonly used in reservation systems. It contains all the recorded information aboutan individual passenger.

pathThe set of components providing a connection between a processor complex and an I/O device. Forexample, the path for an IBM 3390 DASD volume might include the channel, ESCON Director, 3990Storage Path, 3390 Device Adapter, and 3390 internal connection. The specific components used in aparticular path are dynamic and may change from one I/O request to the next. See balanced path.

pathlengthThe number of machine instructions needed to process a message from the time it is received untilthe reponse is sent to the communication facilities.

performance monitorAn online function that collects performance data and stores it in records on the ALCS real-timedatabase. It can produce online performance reports based on current data and historical data.

pilotSee data file.

pool directory update (PDU)A facility of TPF that recovers long-term pool file addresses without running Recoup . PDU identifiesand makes available all long-term pool-file records that have been released.


pool fileShort-term pool, long-term pool, and allocatable pool. Within each pool file class, there is one recordtype for each record size; for example, short-term pool includes the record type L1STPOOL (size L1short-term pool records).

Each pool-file record type contains some records that are in-use and some that are available. There isa dispense function that selects an available record, changes its status to in-use, and returns the fileaddress. Also, there is a release function that takes the file address of an in-use pool-file record andchanges the record status to available.

To use a pool-file record, a program must:

1. Request the dispense function. This returns the file address of a record. Note that the recordcontents are, at this stage, unpredictable.

2. Write the initial record contents, using the file address returned by step “1” on page 491.3. Save the file address returned by step “1” on page 491.4. Read and write the record to access and update the information as required. These reads and

writes use the file address saved in step “3” on page 491.

When the information in the record is no longer required, a program must:5. Delete (clear to zeros) the saved copy of the file address (see step “3” on page 491).6. Request the release function.

See also record class. Contrast with fixed file.

pool file directory record (PFDR)The ALCS pool file management routine keeps a directory for each size (L1, L2, ...L8) of short-termpool file records and long-term pool-file records. It keeps these directories in pool file directoryrecords.

pool-file recordALCS application programs access pool-file records with file addresses similar to those for fixed-filerecords. To obtain a pool-file record, an application program uses a monitor-request macro (orequivalent C function) that specifies a 2-byte record ID or a pool-file record type.

When the data in a pool-file record is no longer required, the application uses a monitor-requestmacro (or equivalent C function) to release the record for reuse. See pool file.

pool-file record identifier (record ID)The record ID of a pool-file record. On get file requests (using the GETFC monitor-request macroor equivalent C function) the program specifies the pool-file record ID. This identifies whether thepool-file record is a short-term or long-term pool-file record and also determines the record size (L1,L2, ...L8). (Coding the 2-byte record IDs, and the corresponding pool-file record sizes and types, ispart of the ALCS generation procedure.) See also record ID qualifier.

pool-file record typeEach collection of short-term and long-term pool-file records of a particular record size (identified bythe symbols L1, L2, ..., L8) is a different record type. Each pool-file record type has a different name.For short-term pool-file records, this is LnSTPOOL, where Ln is the record size symbol. For long-termpool-file records the name is LnLTPOOL.

post processorSee ALCS diagnostic file processor.

PPMSGALCS program-to-program message format, used by the ALCS message router to send and receivemessages on a message routing path to another system. In PPMSG message format, the routingcontrol parameter list (RCPL) precedes the message text.

primary action codeThe first character of any input message. The primary action code Z is reserved for ALCS commands.See secondary action code.

Glossary 491

Prime CRASThe primary display terminal, or NetView ID, that controls the ALCS system. See also computer roomagent set (CRAS).

process definition objectIn message queuing, an object that contains the definition of a message queuing application. Forexample, a queue manager uses the definition when it works with trigger messages.

product sensitive programming interface (PSPI)An interface intended for use in customer-written programs for specialized purpose only, such asdiagnosing, modifying, monitoring, repairing, tailoring or tuning of ALCS. Programs using this interfacemay need to be changed in order to run with new product releases or versions, or as a result ofservice.

program linkageMechanism for passing control between separate portions of the application program. See dynamicprogram linkage and static program linkage.

program nesting levelOne of 32 ECB areas used by the ENTER/BACK mechanism for saving return control data.

program-to-program interfaceIn NetView, a facility that allows user programs to send data to, or receive data from, other userprograms. It also allows system and application programs to send alerts to the NetView hardwaremonitor.

P.1024A SITA implementation of SLC. See SLC.

P.1124A SITA implementation of SLC. See SLC.

P.1024AThe SITA implementation of airline line control (ALC).

Qqueue manager

A system program that provides queuing services to applications. It provides an applicationprogramming interface so that programs can access messages on the queues that the queue managerowns. WebSphere MQ for z/OS is an example of a queue manager.

Rreal-time database

The database to which ALCS must have permanent read and write access. As an ALCS generationoption, the real-time database can be duplicated in order to minimize the effects of a DASD failure.

real-time sequential fileA sequential data set used only for output. ALCS application programs can write to any real-timesequential file without requiring exclusive access to the data set. See also general sequential file.

real-time tapeTPF term for a real-time sequential file.

receive only (RO)The function of a communication terminal that can receive but not send data. An example is a printerthat does not have a keyboard.

receive only CRASA printer terminal (or NetView operator ID) that ALCS uses to direct status messages. Commonlyknown as RO CRAS.

recordA set of data treated as a unit.


record classThe first (highest) level categorization of ALCS DASD records. ALCS defines the following recordclasses:

Allocatable poolApplication fixed fileConfiguration data setGeneral fileLong-term poolShort-term poolSystem fixed file.

See also record type and record ordinal.

record code check (RCC)The third byte of any record stored in the ALCS database. It is part of the record header.

The RCC field is intended to help detect the incorrect chaining of records which have the same recordID. This is particularly useful for passenger name records (PNRs), of which there are often hundredsof thousands. A mismatch in RCC values shows that the chain is broken, probably as a result of anapplication program releasing a record too soon. (A false match cannot be excluded, but the RCCshould give early warning of a chaining problem.)

record headerA standard format for the first 16 bytes of a record stored on the ALCS database. It contains thefollowing fields:

Record IDRecord code checkControl byteApplication program nameForward chainBackward chain.

Not all records contain forward chains and backward chains. Some applications extend the recordheader by including extra fields. TPFDF uses an extended record header.

record holdA type of hold that applies to DASD records. Applications that update records can use record hold toprevent simultaneous updates. See also resource hold.

record identifier (record ID)The first two bytes of a record stored on the ALCS database, part of the record header.

The record ID should always be used to indicate the nature of the data in the record. For example,airlines reservations applications conventionally store passenger name records (PNRs) as long-termpool-file records with a record ID of 'PR'.

When application programs read such records, they can (optionally) request ALCS to check that therecord ID matches that which the application program expects.

When application programs request ALCS to dispense pool file records, ALCS uses the record IDto select an appropriate long-term or short-term pool-file record of the requested record size (L1,L2,...,L8). See also record ID qualifier.

record ID qualifierA number 0 through 9 that differentiates between record types that have the same record ID.

For compatibility with previous implementations of the record ID qualifier, ALCS also accepts thecharacter qualifiers P and O. P (primary) is equivalent to 0, and O (overflow) is equivalent to 1.

record ordinalThe relative record number within a record type. See record class and record type.

Glossary 493

record sizeSee DASD record.

record typeThe second level categorization of ALCS DASD records. Within any one record class, the records arecategorized into one or more record types. See also record type number, record type symbol, recordclass and record ordinal.

record type numberA number that identifies a record type.

record type symbolThe character string that identifies a fixed-file record type (#xxxxx), a long-term pool-file record type(LsLTPOOL), a short-term pool-file record type (LsSTPOOL), or a general file (GF-nnn). The value of therecord type symbol is the record type number.

RecoupA real-time database validation routine which runs online in the ALCS system. (Note that, while theRecoup routines of TPF consist of a number of phases, some online and some offline, the ALCSRecoup is a single online phase that runs, without operator intervention, in any system state.)

Recoup reads selected fixed-file records in the database, and then follows up all chains of pool-filerecords in the database, noting that these records are in use and giving a warning of any that havebeen corrupted or released. It then updates the pool file directory records (PFDRs) to show the statusof all records.

The ALCS pool file dispense procedure identifies records not in a chain (and so apparently availablefor reuse) that have not been released.

recoup descriptorsThese describe the structure of the entire real-time database.

reentrantThe attribute of a program or routine that allows the same copy of the program or routine to be usedconcurrently by two or more tasks. All ALCS application programs must be reentrant.

relational databaseA database that is in accordance with the relational model of data. The database is perceived as a setof tables, relationships are represented by values in tables, and data is retrieved by specifying a resulttable that can be derived from one or more base tables.

release (a pool-file record)To make available a long-term or short-term pool-file record so that it can be subsequently dispensed.An application program requests the release action. See dispense a pool-file record.

release file storage (RFS)The general term for the pool-file release mechanisms that ALCS provides.

remote queueIn message queuing, a queue that belongs to a remote queue manager. Programs can put messageson remote queues, but they cannot get messages from remote queues. Contrast with local queue.

remote terminal traceOne mode of operation of the ALCS trace facility. Remote terminal trace is a conversational tracefacility to interactively trace entries from a terminal other than your own.

REpresentational State Transfer (REST)An architecture which defines how data is represented to a client in a format (using pis) that isconvenient for that client to access Web services.Common message protocols used for this purpose are HTTP, JSON and XML. Applications using theREST pis are said to be RESTful applications.

reservationsAn online application which is used to keep track of seat inventories, flight schedules, and otherrelated information. The reservation system is designed to maintain up-to-date data and to respondwithin seconds or less to inquiries from ticket agents at locations remote from the computing system.

IPARS for ALCS includes a sample reservations application for airlines.


reserveUnassign a general sequential file from an entry but leave the file open, so that another (or the same)entry can assign it. Application programs can use the TRSVC monitor-request macro (or equivalent Cfunction) to perform this action.

resourceAny facility of a computing system or operating system required by a job or task, and including mainstorage, input/output devices, processing unit, data sets, and control or processing programs. Seealso communication resource.

resource entry index (REI)The second and third bytes of a communication resource identifier (CRI).

resource holdA type of hold that can apply to any type of resource. Applications can define resources according totheir requirements, and identify them to ALCS using a unique name. See also record hold.

RO CRASSee receive only CRAS.

rollbackAn operation that reverses all the changes made during the current unit of recovery. After theoperation is complete, a new unit of recovery begins.

routingThe connection between a communication resource connected to ALCS (typically a terminal onan SNA or non-SNA network) and an application (running under ALCS or another system). Alsosometimes called "logging in", but this must be distinguished from logging on, which establishes theSNA connection (session) between the terminal and ALCS.

routing control parameter list (RCPL)A set of information about the origin, destination, and characteristics of a message. With each inputmessage, ALCS provides an RCPL in the ECB. An output message that is sent using the ROUTC (routc)service also has an RCPL associated with it.

Sscroll

To move a display image vertically or horizontally to view data that otherwise cannot be observedwithin the boundaries of the display screen.

secondary action codeThe second character of an ALCS command. (ALCS commands are made up of 5 characters: Zfollowed by a secondary action code.) See primary action code.

sequential fileA file in which records are processed in the order in which they are entered and stored in the file. Seegeneral sequential file and real-time sequential file.

serializationA service that prevents parallel or interleaved execution of two or more processes by forcing theprocesses to execute serially.

For example, two programs can read the same data item, apply different updates, and then writethe data item. Serialization ensures that the first program to start the process (read the item)completes the process (writes the updated item) before the second program can start the process- the second program applies its update to the data item which already contains the first update.Without serialization, both programs can start the process (read the item) before either completes theprocess (writes the updated item) - the second write destroys the first update. See also assign, lock,and hold.

Serviceability Level Indicator Processing (SLIP)An MVS operator command which acts as a problem determination aid.

Glossary 495

short-term poolAn ALCS record class - one of the classes that resides on the real-time database. Within thisclass, there is one record type for each DASD record size. All short-term pool-file records are alsoallocatable pool records (they have a special status of "in use for short-term pool"). ALCS applicationprograms can use short-term pool records for short-lived low-integrity data. See pool file, real-timedatabase, record class, and record type.

simplex transmissionData transmission in one direction only. See also duplex and half-duplex.

sine in/outThose applications that provide different functions to different end users of the same applicationcan require the user to sine in 2 to the specific functions they require. The sine-in message can, forexample, include an authorization code.

single-block messageIn SLC, a message that is transmitted in one link data block. See link data block.

single-phase commitA method in which a program can commit updates to a message queue or relational database withoutcoordinating those updates with updates the program has made to resources controlled by anotherresource manager. Contrast with two-phase commit.

SLCSee synchronous link control.

SLC channelA duplex telecommunication line using ATA/IATA SLC protocol. There can be from 1 to 7 channels onan SLC link.

SLC error index byte (EIB)A 1-byte field generated by Line Control - Airline (LICRA) and transferred to ALCS with each incominglink control block and link data block. Certain errors cause LICRA to set on certain bits of the EIB. Seealso Link Control -- Airline (LICRA).

SLC information blockSynonym for SLC link data block.

SLC linkA processor-to-processor or processor-to-HLN connection. ALCS supports up to 255 SLC links in anSLC network.

An SLC link that is in the process of an open, close, start, or stop function is said to be "cycling".

SLC link control block (LCB)A 4-byte data item transmitted across an SLC link to control communications over the link. LCBs areused, for example, to confirm that a link data block (LDB) has arrived, to request retransmission of anLDB, and so on.

SLC link data block (LDB)A data item, transmitted across an SLC link, that contains a message or part of a message. One LDBcan contain a maximum of 240 message characters, messages longer than this must be split andtransmitted in multiple LDBs. Synonymous with SLC information block.

SLC link traceA function that provides a record of SLC communication activity. It can either display the informationin real time or write it to a diagnostic file for offline processing, or both. Its purpose is like that of anNCP line trace, but for the SLC protocol.

SLC message block indicator (MBI)A 1-byte field in the SLC link data block that contains the SLC message label and the block number. Amultiblock message is transmitted in a sequence of up to 16 link data blocks with block numbers 1, 2,3, ... 16. See also multiblock message, SLC link data block, and SLC message label.

2 This spelling is established in the airline industry.


SLC message labelA number in the range 0 through 7, excluding 1. In P.1024, consecutive multiblock messages areassigned SLC message labels in the sequence: 0, 2, 3, ... 6, 7, 0, 2, and so on. In P.1124, single-blockmessages are (optionally) also included in the sequence. See also P.1024, P.1124 and SLC messageblock indicator.

SLC transmission status indicator (TSI)A 1-byte field in the SLC link data block that contains the SLC transmission sequence number. Seealso SLC transmission sequence number.

SLC transmission sequence number (TSN)A number in the range 1 through 31. Consecutive SLC link data blocks transmitted in one direction onone SLC channel are assigned TSNs in the sequence: 1, 2, 3, ... 30, 31, 1, 2, and so on. See also SLClink data block, SLC channel, and SLC transmission status indicator.

SLC Type A trafficSee Type A traffic.

SLC Type B trafficSee Type B traffic.

Société Internationale de Télécommunications Aéronautiques (SITA)An international organization which provides communication facilities for use within the airlineindustry.

SQL Communication Area (SQLCA)A structure used to provide an application program with information about the execution of its SQLstatements.

SQL Descriptor Area (SQLDA)A structure that describes input variables, output variables, or the columns of a result table used inthe execution of manipulative SQL statements.

stackAn area of storage that a compiler uses to allocate variables defined in a high-level language. ALCSprovides separate stacks for each entry (if needed). The stack is part of entry storage.

standard message formatFor input and output messages, a message format which includes a 2-byte field for the messagelength.

standbyThe state of ALCS after it has been initialized but before it has been started. Standby is not consideredone of the system states.

static program linkageProgram linkage where the connection between the calling and called program is established beforethe execution of the program. The connection is established by the assembler, compiler, prelinker,or linkage editor. Static program linkage does not invoke ALCS monitor services. See also dynamicprogram linkage.

static SQLSee embedded SQL.

statistical report generator (SRG)An offline ALCS utility that is a performance monitoring tool. It takes the data written to the ALCS datacollection or diagnostic file processor by the data collection function and produces a variety of reportsand bar charts. The SRG is the equivalent of TPF "data reduction".

STATMONSee NetView resource.

storage blockAn area of storage that ALCS allocates to an entry. It is part of entry storage. See storage block sizes.

Glossary 497

storage block sizeALCS allows storage blocks of up to 9 different sizes. These are identified in programs by theassembler symbols (or defined C values) L0, L1, L2, ..., L8. Installations need not define all theseblock sizes but usually define at least the following:

Size L0 contains 127 bytes of user dataSize L1 contains 381 bytes of user dataSize L2 contains 1055 bytes of user dataSize L3 contains 4000 bytes of user dataSize L4 contains 4095 bytes of user data.

The system programmer can alter the size in bytes of L1 through L4, and can specify the remainingblock sizes.

storage levelAn area in the ECB or a DECB used to hold the address and size of a storage block. See ECB level andDECB level.

storage unitThe ALCS storage manager allocates storage in units called storage units. Entry storage issuballocated within storage units; for example, one storage unit can contain an ECB and severalstorage blocks attached to that ECB.

ALCS uses three types of storage units:

• Prime and overflow storage units for entry storage and heap storage (if an entry storage block canbe used). Also called type 1 storage units.

• High-level language storage units for stack storage Also called type 2 storage units.• Storage units for heap storage (if an entry storage block can not be used) for programs. Also called

type 3 storage units.

The size of a storage unit, and the number of each type of storage unit, is defined in the ALCSgeneration. See entry storage.

store accessAccess which only involves writing (not reading). Compare with fetch access.

stripingA file organization in which logically adjacent records are stored on different physical devices. Thisorganization helps to spread accesses across a set of physical devices.

Structured Query Language (SQL)a standardized language for defining and manipulating data in a relational database.

symbolic line number (SLN)In TPF, a 1-byte address of an ALC link, derived from the line number but adjusted so that all ALC linksconnected to the TPF system have a different symbolic line number. See also line number.

Synchronous Data Link Control (SDLC)A discipline conforming to subsets of the Advanced Data Communication Control Procedures (ADCCP)of the American National Standards Institute (ANSI) and High-level Data Link Control (HDLC) of theInternational Organization for Standardization, for managing synchronous, code-transparent, serial-by-bit information transfer over a link connection.

Transmission exchanges can be duplex or half-duplex over switched or nonswitched links. Theconfiguration of the link connection can be point-to-point, multipoint, or loop.

Synchronous Link Control (SLC)A discipline conforming to the ATA/IATA Synchronous Link Control, as described in the ATA/IATApublication ATA/IATA Interline Communications Manual, ATA/IATA document DOC.GEN 1840.

syncpointAn intermediate or end point during processing of a transaction at which the transaction's protectedresources are consistent. At a syncpoint, changes to the resources can safely be committed, or theycan be backed out to the previous syncpoint.


system errorError that the ALCS monitor detects. Typically, ALCS takes a dump, called a system error dump, to theALCS diagnostic file. See also ALCS diagnostic file and ALCS diagnostic file processor. See also systemerror dump, system error message.

system error dump(1) A storage dump that ALCS writes to the ALCS diagnostic file when a system error occurs. See alsoALCS diagnostic file and system error.

(2) The formatted listing of a storage dump produced by the ALCS diagnostic file processor. See alsoALCS diagnostic file processor.

system error messageA message that ALCS sends to receive only CRAS when a system error occurs. See also receive onlyCRAS and system error.

system error optionA parameter that controls what action ALCS takes when it detects a system error. See also systemerror.

system fixed fileAn ALCS record class - one of the classes that reside on the real-time database. All system fixed-filerecords are also allocatable pool records (they have a special status of "in use for system fixed file").

System fixed-file records are reserved for use by ALCS iteslf. See real-time database, record class, andrecord type.

system macro trace blockThere is one system macro trace block. Each time an entry issues a monitor-request macro (orequivalent C function), ALCS records information in the system macro trace block.

This information includes the ECB address, the macro request code, the name of the program thatissued the macro, and the displacement in the program. The ALCS diagnostic file processor formatsand prints the system macro trace block in ALCS system error dumps. See also entry macro traceblock.

System Modification Program/Extended (SMP/E)An IBM licensed program used to install software and software changes on MVS systems. In additionto providing the services of SMP, SMP/E consolidates installation data, allows flexibility in selectingchanges to be installed, provides a dialog interface, and supports dynamic allocation of data sets.

Systems Application Architecture (SAA)A set of software interfaces, conventions, and protocols that provide a framework for designing anddeveloping applications with cross-system consistency.

Systems Network Architecture (SNA)The description of the logical structure, formats, protocols, and operational sequences fortransmitting information units through, and controlling the configuration and operation of networks.

system sequential fileA class of sequential data sets used by ALCS itself. Includes the ALCS diagnostic file, the ALCS datacollection file, and the ALCS update log file or files.

system stateThe ALCS system can run in any of the following system states: IDLE, CRAS, message switching(MESW), and normal (NORM).

Each state represents a different level of availability of application functions. Altering the system stateis called "cycling the system". See also standby.

system test compiler (STC)An offline ALCS utility that compiles data onto data files for loading on to the real-time database. STCalso builds test unit tapes (TUTs) for use by the system test vehicle (STV).

Glossary 499

system test vehicle (STV)An online ALCS function that reads input messages from a general sequential file test unit tape (TUT)and simulates terminal input. STV intercepts responses to simulated terminals and writes them to theALCS diagnostic file.

Tterminal

A device capable of sending or receiving information, or both. In ALCS this can be a display terminal, aprinter terminal, or a NetView operator identifier.

terminal address (TA)In ALC, the 1-byte address of an ALC terminal. Different terminals connected to the same terminalinterchange have different terminal addresses. Different terminals connected to different terminalinterchanges can have the same terminal address. See also terminal interchange.

terminal circuit identity (TCID)Synonym for line number.

terminal holdWhen an ALCS application receives an input message, it can set terminal hold on for the inputterminal. Terminal hold remains on until the application sets it off. The application can reject inputfrom a terminal that has terminal hold set on. Also referred to as AAA hold.

terminal interchange (TI)In ALC, synonym for terminal control unit.

terminate(1) To stop the operation of a system or device.

(2) To stop execution of a program.

test unit tape (TUT)A general sequential file that contains messages for input to the system test vehicle (STV). TUTs arecreated by the system test compiler (STC).

time available supervisor (TAS)An ALCS or TPF function that creates and dispatches low priority entries.

time-initiated functionA function initiated after a specific time interval, or at a specific time. In ALCS this is accomplished byusing the CRETC monitor-request macro or equivalent C function. See create service.

TP profileThe information required to establish the environment for, and attach, an APPC/MVS transactionprogram on MVS, in response to an inbound allocate request for the transaction program.

trace facilitySee ALCS trace facility, generalized trace facility, and SLC link trace.

transactionThe entirety of a basic activity in an application. A simple transaction can require a single input andoutput message pair. A more complex transaction (such as making a passenger reservation) requires aseries of input and output messages.

Transaction Processing Facility (TPF)An IBM licensed program with many similarities to ALCS. It runs native on IBM System/370 machines,without any intervening software (such as MVS). TPF supports only applications that conform to theTPF interface. In this book, TPF means Airline Control Program (ACP), as well as all versions of TPF.

Transaction Processing Facility Database Facility (TPFDF)An IBM licensed program that provides database management facilities for programs that run in anALCS or TPF environment.

Transaction Processing Facility/Advanced Program to Program Communications (TPF/APPC)This enables LU 6.2 for TPF.


Transaction Processing Facility/Data Base Reorganization (TPF/DBR)A program which reorganizes the TPF real-time database.

Transaction Processing Facility/MVS (TPF/MVS)Alternative name for ALCS V2 .

Transaction program identifier (TP_ID)A unique 8-character token that APPC/MVS assigns to each instance of a transaction program.When multiple instances of a transaction program are running sumultaneously, they have the sametransaction program name, but each has a unique TP_ID.

transaction scheduler nameThe name of an APPC/MVS scheduler program. The ALCS transaction scheduler name is ALCSx000,where x is the ALCS system identifier as defined during ALCS generation.

transfer vectorAn ALCS application program written in assembler, SabreTalk, or C, can have multiple entry points fordynamic program linkage. These entry points are called transfer vectors. Each transfer vector has aseparate program name.

transmission status indicatorSee SLC transmission status indicator.

transmission sequence numberSee SLC transmission sequence number.

trigger eventIn message queuing, an event (such as a message arriving on a queue) that causes a queue managerto create a trigger message on an initiation queue.

trigger messageIn message queuing, a message that contains information about the program that a trigger monitor isto start.

trigger monitorIn message queuing, a continuously-running application that serves one or more initiation queues.When a trigger message arrives on an initiation queue, the trigger monitor retrieves the message.When ALCS acts as a trigger monitor, it uses the information in the trigger message to start an ALCSapplication that serves the queue on which a trigger event occurred.

triggeringIn message queuing, a facility that allows a queue manager to start an application automatically whenpredetermined conditions are met.

TSI exhaustionThe condition of an SLC channel when a sender cannot transmit another SLC link data block (LDB)because the maximum number of unacknowledged LDBs has been reached. The sender must wait foracknowledgement of at least one LDB so that it can transmit further LDBs. See also SLC channel, SLClink data block, SLC transmission sequence number, and SLC transmission status indicator.

two-phase commitA protocol for the coordination of changes to recoverable resources when more than one resourcemanager is used by a single transaction. Contrast with single-phase commit.

typeSee record type.

Type A trafficATA/IATA conversational traffic - that is, high-priority low-integrity traffic transmitted across an SLC orAX.25 link.

Type B application-to-application program (BATAP)In any system (such as ALCS) that communicates with SITA using AX.25 or MATIP, this is the programwhich receives and transmits type B messages.

Type B trafficATA/IATA conventional traffic - that is, high-integrity, low-priority traffic transmitted across an SLC orAX.25 link or a MATIP TCP/IP connection.

Glossary 501

type 1 pool file dispense mechanismThe mechanism used in ALCS prior to V2 Release 1.3 (and still available in subsequent releases) todispense both short-term and long-term pool-file records.

type 1 storage unitPrime or overflow storage unit for entry storage and small heap storage. See storage unit.

type 2 pool file dispense mechanismsThe mechanisms available since ALCS V2 Release 1.3 to dispense pool-file records (the mechanismsare different for short-term and long-term pool-file records).

IBM recommends users to migrate to type 2 dispense mechanisms as part of their migration process.

type 2 storage unitHigh-level language storage unit for stack storage. See storage unit.

type 3 storage unitStorage unit for heap storage that is used when an entry storage block cannot satisfy a request. Seestorage unit.

Uunit of recovery

A recoverable sequence of operations within a single resource manager (such as WebSphere MQ forz/OS or DB2 for z/OS). Compare with unit of work.

unit of workA recoverable sequence of operations performed by an application between two points ofconsistency. Compare with unit of recovery.

Universal Communications Test Facility (UCTF)An application used by SITA for SLC protocol acceptance testing.

update logSee ALCS update log.

user data-collection areaAn optional extension to the data-collection area in the ECB. Application programs can use the DCLACmacro to update or read the user data-collection area.

user exitA point in an IBM-supplied program at which a user exit routine can be given control.

user exit routineA user-written routine that receives control at predefined user exit points. User exit routines can bewritten in assembler or a high-level language.

Vversion number

In ALCS and TPF, two characters (not necessarily numeric), optionally used to distinguish betweendifferent versions of a program. Sometimes also used with other application components such asmacro definitions.

virtual file access (VFA)An ALCS caching facility for reducing DASD I/O. Records are read into a buffer, and subsequent readsof the same record are satisfied from the buffer. Output records are written to the buffer, either to bewritten to DASD - immediately or at a later time - or to be discarded when they are no longer useful.

virtual SLC linkUsed to address an X.25 PVC or TCP/IP resource for transmitting and receiving Type B traffic. Someapplications (such as IPARS MESW) address communication resources using a symbolic line number(SLN) instead of a CRI. These applications can address X.25 PVC and TCP/IP resources by convertingthe unique SLN of a virtual SLC link to the CRI of its associated X.25 PVC or TCP/IP resource.


WWAS Bridge

The ALCS WAS Bridge allows ALCS application programs to send and receive messages usingoptimized local adapters (OLA) for WebSphere Application Server for z/OS without the need to codethose callable services in ALCS programs. The ALCS WAS Bridge installation-wide monitor exitsUSRWAS3, USRWAS4, USRWAS5, and USRWAS6 allow you to customize the behaviour of the WASBridge to suit your applications.

WebSphere MQ for z/OSAn IBM product that provides message queuing services to systems such as CICS, IMS, ALCS or TSO.Applications request queuing services through MQI.

wide characterA character whose range of values can represent distinct codes for all members of the largestextended character set specified among the supporting locales. For the z/OS XL C/C++ compiler,the character set is DBCS, and the value is 2 bytes.

workstation traceOne mode of operation of the ALCS trace facility. Workstation trace controls the remote debuggerfacility. The remote debugger is a source level debugger for C/C++ application programs.

World Trade Teletypewriter (WTTY)Start-stop telegraph terminals that ALCS supports through Network Terminal Option (NTO).

ZZ message

See ALCS command.

Glossary 503

Bibliography

Note that unless otherwise specified, the publications listed are those for the z/OS platform.

Airline Control System Version 2 Release 4.1• Application Programming Guide, SH19-6948• Application Programming Reference - Assembler Language, SH19-6949• Application Programming Reference - C Language, SH19-6950• Concepts and Facilities, SH19-6953• General Information Manual, GH19-6738• Installation and Customization, SH19-6954• Licensed Program Specifications, GC34-6327• Messages and Codes, SH19-6742• Operation and Maintenance, SH19-6955• Program Directory, GI10-2577• ALCS World Wide Web Server User Guide• OCTM User Guide

MVS• Data Areas, Volumes 1 through 5, GA22-7581 through GA22-7585• Diagnosis Reference, GA22-7588• Diagnosis Tools and Service Aids, GA22-7589• Initialization and Tuning Guide, SA22-7591• Initialization and Tuning Reference, SA22-7592• Installation Exits, SA22-7593• IPCS Commands, SA22-7594• IPCS User's Guide, SA22-7596• JCL Reference, SA22-7597• JCL User's Guide, SA22-7598• JES2 Initialization and Tuning Guide, SA22-7532• JES2 Initialization and Tuning Reference, SA22-7533• Program Management: User's Guide and Reference, SA22-7643• System Codes, SA22-7626• System Commands, SA22-7627• System Messages, Volumes 1 through 10, SA22-7631 through SA22-7640

APPC/MVS• MVS Planning: APPC/MVS Management, SA22-7599• MVS Programming: Writing Transaction Programs for APPC/MVS, SA22-7621

DFSMS• Access Method Services for Catalogs, SC26-7394


• DFSMSdfp Storage Administration Reference, SC26-7402• DFSMSdss Storage Administration Guide, SC35-0423• DFSMSdss Storage Administration Reference, SC35-0424• DFSMShsm Storage Administration Guide, SC35-0421• DFSMShsm Storage Administration Reference, SC35-0422• Introduction, SC26-7397

RMF• RMF Report Analysis, SC33-7991• RMF User's Guide, SC33-7990

Data Facility Sort (DFSORT)• Application Programming Guide, SC33-4035• Messages, Codes and Diagnostic Guide, SC26-7050

Language Environment• Language Environment Concepts Guide, SA22-7567• Language Environment Customization, SA22-7564• Language Environment Debugging Guide, GA22-7560• Language Environment Programming Guide, SA22-7561• Language Environment Programming Reference, SA22-7562• Language Environment Run-Time Messages, SA22-7566

z/OS XL C/C++• Standard C++ Library Reference, SC09-4949• z/OS XL C/C++ Compiler and Run-Time Migration Guide, GC09-4913• z/OS XL C/C++ Language Reference, SC09-4815• z/OS XL C/C++ Messages, GC09-4819• z/OS XL C/C++ Programming Guide, SC09-4765• z/OS XL C/C++ Run-Time Library Reference, SA22-7821• z/OS XL C/C++ User's Guide, SC09-4767

COBOL• Enterprise COBOL for z/OS and OS/390 Language Reference, SC27-1408• Enterprise COBOL for z/OS and OS/390 Programming Guide, SC27-1412• VisualAge COBOL for OS/390 and VM Language Reference, SC26-9046• VisualAge COBOL for OS/390 and VM Programming Guide, SC26-9049

PL/I• Enterprise PL/I for z/OS and OS/390 Language Reference, SC27-1460• Enterprise PL/I for z/OS and OS/390 Messages and Codes, SC27-1461• Enterprise PL/I for z/OS and OS/390 Programming Guide, SC27-1457• VisualAge PL/I for OS/390 Compile-Time Messages and Codes, SC26-9478

Bibliography 505

• VisualAge PL/I for OS/390 Language Reference, SC26-9476• VisualAge PL/I for OS/390 Programming Guide, SC26-9473

High Level Assembler• Language Reference, SC26-4940• Programmer's Guide, SC26-4941

CPI-C• SAA CPI-C Reference, SC09-1308

DB2 for z/OS• Administration Guide, SC18-9840• Application Programming and SQL Guide, SC18-9841• Codes, GC18-9843• Command Reference, SC18-9844• Installation Guide, GC18-9846• Messages, GC18-9849• SQL Reference, SC18-9854• Utility Guide and Reference, SC18-9855• DB2 for z/OS What's New?, GC18-9856

ISPF• ISPF Dialog Developer's Guide, SC34-4821• ISPF Dialog Tag Language, SC34-4824• ISPF Planning and Customizing, GC34-4814

WebSphere MQ for z/OS• An Introduction to Messaging and Queuing, GC33-0805• Application Programming Guide, SC34-6595• Application Programming Reference, SC34-6596• Command Reference, SC34-6597• Concepts and Planning Guide, GC34-6582• Intercommunication, SC34-6587• Messages and Codes, GC34-6602• MQI Technical Reference, SC33-0850• Problem Determination Guide, GC34-6600• System Administration Guide, SC34-6585

WebSphere Application Server for z/OS• IBM Information Center for WebSphere Application Server• IBM Information Center for WebSphere Application Server - Network Deployment z/OS• WebSphere on z/OS - Optimized Local Adapters (Redpaper), REDP-4550


Tivoli Netview• Administration Reference, SC31-8854• Automation Guide, SC31-8853• Installation, Getting Started, SC31-8872• User's Guide, GC31-8849• Security Reference, SC31-8870

SMP/E• Reference, SA22-7772• User's Guide, SA22-7773

Communications Server IP (TCP/IP)• API Guide, SC31-8788• Configuration Guide, SC31-8775• Configuration Reference, SC31-8776• Diagnosis Guide, SC31-8782• Implementation Volume 3: High Availability, Scalability, and Performance, SG24-7534• IP and SNA Codes, SC31-8791• Messages Volume 1, SC31-8783• Messages Volume 2, SC31-8784• Messages Volume 3, SC31-8785• Messages Volume 4, SC31-8786• Migration Guide, SC31-8773

Web Enablement Toolkit• MVS Programming: Callable Services for High-Level Languages, SA23-1377

TPF• Application Programming, SH31-0132• Concepts and Structures, GH31-0139• C/C++ Language Support Users Guide, SH31-0121• General Macros, SH31-0152• Library Guide, GH31-0146• System Macros, SH31-0151

TPF Database Facility (TPFDF)• Database Administration, SH31-0175• General Information Manual, GH31-0177• Installation and Customization, GH31-0178• Programming Concepts and Reference, SH31-0179• Structured Programming Macros, SH31-0183• Utilities, SH31-0185

Bibliography 507

TSO/E• Administration, SA22-7780• Customization, SA22-7783• System Programming Command Reference, SA22-7793• User's Guide, SA22-7794

Communications Server SNA (VTAM)• IP and SNA Codes, SC31-8791• Messages, SC31-8790• Network Implementation , SC31-8777• Operations, SC31-8779• Programming, SC31-8829• Programmers' LU6.2 Guide, SC31-8811• Programmers' LU6.2 Reference, SC31-8810• Resource Definition Reference, SC31-8778

Security Server (RACF)• RACF General User's Guide, SA22-7685• RACF Messages and Codes, SA22-7686• RACF Security Administrator's Guide, SA22-7683• RACF Callable Services, SA23-2293• z/OS Security Server RACF Data Areas, GA32-0885

Integrated Cryptographic Service Facility (ICSF)• ICSF Administrator's Guide, SA22-7521• ICSF Application Programmer's Guide, SA22-7522• ICSF Messages, SA22-7523• ICSF Overview, SA22-7519• ICSF System Programmer's Guide, SA22-7520

Other IBM publications• IBM 3270 Information Display System: Data Stream Programmer's Reference, GA23-0059• Input/Output Configuration Program User's Guide and Reference, SB0F-3741• NTO Planning, Migration and Resource Definition, SC30-3347• Planning for NetView, NCP, and VTAM, SC31-7122• SNA Formats, GA27-3136• X.25 NPSI Planning and Installation, SC30-3470• z/Architecture Principles of Operation, SA22-7832

ALCS product kit• ALCS PDF Product Kit, SK3T-6944


SITA publications• ACS protocol acceptance tool, SITA document 032-1/LP-SD-001• Communications control procedure for connecting IPARS agent set control unit equipment to a SITA SP,

SITA document P.1024B (PZ.7130.1)• P.1X24 automatic testing (with UCTF on DIS), SITA document 032-1/LP-SDV-001• P.1024 Test Guide, SITA Document PZ.1885.3• Status Control Service Step 2: Automatic Protected Report to ACS, SITA document 085-2/LP-SD-001• Synchronous Link Control Procedure, SITA Document P.1124

SITA produces a series of books which describe the SITA high level network and its protocols. These maybe obtained from:

Documentation Section SITA 112 Avenue Charles de Gaulle 92522 Neuilly sur Seine France

Other non-IBM publicationsSystems and Communications Reference Manual (Vols 1-7). This publication is available from theInternational Air Transport Association (IATA). You can obtain ordering information from the IATA website <http://www.iata.org/> or contact them directly by telephone at +1(514) 390-6726 or by e-mail [email protected].

Bibliography 509

IBM®

Product Number: 5695-068

SH19-6742-24

airline control system version 2: messages and codes

Documents