AionDS Messages and Codes Guide
Share Embed Flag
Download ePaper

AionDS Messages and Codes Guide

AionDS Messages and Codes Guide AionDS Messages and Codes Guide

arti.vub.ac.be
from arti.vub.ac.be More from this publisher
29.06.2013 Views

CICS/VS exception conditions .........................................................................................................................................................................................................˝.......................................... 1307 3-12 AionDS Messages and Codes Transaction unauthorized. The DL/I request was rejected when CICS/VS determined that the transaction had not been properly authorized to use that function. .........................................................................................................................................................................................................˝.......................................... 1308 PSB already scheduled. Due to an internal error, the transaction driver attempted to schedule a PSB a second time. .........................................................................................................................................................................................................˝.......................................... 1309 Language conflict. CICS/VS rejected a DL/I request because of a conflict between the language being used and what was specified in the PSB. .........................................................................................................................................................................................................˝.......................................... 1310 PSB initialization failed. The transaction driver attempted to schedule the PSB but the request failed when CICS/VS could not initialize the PSB. See the CICS/VS console log to determine the specific error CICS/VS encountered. .........................................................................................................................................................................................................˝.......................................... 1311 PSB not authorized. CICS/VS rejected a DL/I request because the program was not authorized to issue that specific request. For example, if the transaction driver issued an ISRT request yet the PSB only authorized the program to retrieve segments, error 1311 would be reported. .........................................................................................................................................................................................................˝.......................................... 1312 Unscheduled termination. A DL/I request was rejected due to an unscheduled termination. .........................................................................................................................................................................................................˝.......................................... 1313 Function unscheduled. A DL/I request was rejected and the function unscheduled.

CICS/VS exception conditions .........................................................................................................................................................................................................˝.......................................... 1314 DL/I not active. CICS/VS rejected a DL/I request because DL/I was not active. .........................................................................................................................................................................................................˝.......................................... 1315 Unrecognized DL/I status code. CICS/VS returned a DL/I status condition that the transaction driver could not interpret. This condition normally represents a program error. The code was returned in UIBFCTR. .........................................................................................................................................................................................................˝.......................................... 1316 Unrecognized DL/I status code. CICS/VS returned a DL/I status condition that the transaction driver could not interpret. This condition normally represents a program error. The code was returned in UIBDLTR. .........................................................................................................................................................................................................˝.......................................... 1317 Search for data segment. The transaction driver sets this internal status condition when it needs the data segment in the message to satisfy the user request. It will not appear as a message or an error condition. .........................................................................................................................................................................................................˝.......................................... 1318 Data segment not provided. To satisfy an ISRT, DLET, or REPL DL/I request, the SAES program or the user-written external routine must pass or return the segment in question. The transaction driver could not find the segment in the message requesting the insert, delete, or replace. CICS/VS Exception Conditions 3-13

CICS/VS exception conditions<br />

.........................................................................................................................................................................................................˝..........................................<br />

1314<br />

DL/I not active.<br />

CICS/VS rejected a DL/I request because DL/I was not active.<br />

.........................................................................................................................................................................................................˝..........................................<br />

1315<br />

Unrecognized DL/I status code.<br />

CICS/VS returned a DL/I status condition that the transaction driver could<br />

not interpret. This condition normally represents a program error. The code<br />

was returned in UIBFCTR.<br />

.........................................................................................................................................................................................................˝..........................................<br />

1316<br />

Unrecognized DL/I status code.<br />

CICS/VS returned a DL/I status condition that the transaction driver could<br />

not interpret. This condition normally represents a program error. The code<br />

was returned in UIBDLTR.<br />

.........................................................................................................................................................................................................˝..........................................<br />

1317<br />

Search for data segment.<br />

The transaction driver sets this internal status condition when it needs the<br />

data segment in the message to satisfy the user request. It will not appear as a<br />

message or an error condition.<br />

.........................................................................................................................................................................................................˝..........................................<br />

1318<br />

Data segment not provided.<br />

To satisfy an ISRT, DLET, or REPL DL/I request, the SAES program or the<br />

user-written external routine must pass or return the segment in question.<br />

The transaction driver could not find the segment in the message requesting<br />

the insert, delete, or replace.<br />

CICS/VS Exception Conditions 3-13

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!