This appendix contains a list of status codes that Mainframe Access servers may return to a client program; this list supplements but does not supersede the list of status codes documented in the Error Messages manual.
It also documents, in the section File Status Comparisons, the anomalies in file status settings based upon the environment in which the I/O statements are executed.
Table B-1: Status Codes Returned by the CICS Server
| Status Code | Description |
|---|---|
| 0/0 | The CICS server returns a status of 0/0 when writing a record to an indexed file which results in two or more records with identical keys. Both IBM VS COBOL II batch processing and Micro Focus COBOL return a status of 0/2 when such a condition arises. |
| 0/5 | A file status of 0/5 indicates that an open operation was successful, but the file is empty. A file status of 0/5 is returned in some cases where IBM VS COBOL II returns a status of 0/0 and in other cases where IBM VS COBOL II returns a status of 3/5. See the appendix File Status Comparisons for some examples of the conditions under which this status code is returned during open processing. |
| 4/3 | A status code of 4/3 is returned if an attempt is made to delete a VSAM record via an alternate index, if another record in that file contains the same key as the record being deleted. |
| 4/6 | If an I/O operation is attempted which requires a previous I/O operation to have set the current record pointer, and the previous I/O operation failed, a file status of 4/6 is returned. It is also issued if the CICS server loses track of the current record position, probably due to an invalid sequence of I/O statements. |
| 9/039 | A file status of 9/039 is returned if the CICS server receives an I/O request for a line sequential file. |
| 9/100 | A file status of 9/100 is returned if the CICS server receives an operation code that it does not support. This status is also returned when the server attempts to execute a CICS command at a time when that command is invalid. In this case, the operation code received by the server was valid, but the I/O operation was invalid given the type of operation requested and the nature of the previous I/O operations executed for the file. |
| 9/125 | A status code of 9/125 will be returned
when the maximum number of concurrent Users has been exceeded. The CICS server was unable to process the operation code requested. This may indicate that the server has reached a resource limit that prevents the request from being processed at this time. In some cases, you may be able to retry the request at another time when the CICS server is less busy. |
| 9/051 9/243 |
A VSAM file cannot be opened or is currently unavailable to the CICS server. The 9/243 file status corresponds to the EBCDIC characters '93'. If the requesting program was not compiled with the CHARSET"EBCDIC" directive, the ASCII characters '93' (or 9/051) are returned. This status code was adopted from the IBM VS COBOL II run-time status codes. |
| 9/241 | The CICS server is NOT STARTED. See the chapter Administration for details on starting the CICS server using the FSADMN CICS transaction (FADM). |
| 9/242 | The requested function or component has not been licensed. |
Table B-2: File Status Codes Returned by the MVS Server
| Status Code | Description |
|---|---|
| 0/0 | The MVS server returns a status of 0/0 when writing a record to an indexed file which results in two or more records with identical keys. Both IBM VS COBOL II batch processing and Micro Focus COBOL return a status of 0/2 when such a condition arises. |
| 0/5 | A file status 0/5 indicates an open operation was successful, but the file is empty. A file status of 0/5 is returned in some cases where IBM VS COBOL II returns a status of 0/0 and in other cases where IBM VS COBOL II returns a status of 3/5. See the appendix File Status Comparisons for some examples of the conditions under which this status code is returned during open processing. |
| 4/3 | A status code of 4/3 is returned if an attempt is made to delete a VSAM record via an alternate index, if another record in that file contains the same key as the record being deleted. |
| 4/6 | If an I/O operation is attempted which requires a previous I/O operation to have set the current record pointer, and the previous I/O operation failed, a file status of 4/6 is returned. It is also issued if the MVS server loses track of the current record position, probably due to an invalid sequence of I/O statements. |
| 9/100 | A file status of 9/100 is returned if the MVS server receives an operation code that it does not support. This status is also returned when the server attempts to execute a command at a time when that command is invalid. In this case, the operation code received by the server was valid, but the I/O operation was invalid given the type of operation requested and the nature of the previous I/O operations executed for the file. |
| 9/125 | A status code of 9/125 will be returned when the maximum number of concurrent Users has been exceeded. |
| 9/242 | The requested function or component has not been licensed. |
Table B-3: Error Messages Displayed by the MVS Server
| Error Message | Description |
|---|---|
| MFA100 E ESTAE ENTERED - ABEND CODE UXXX/SXXX |
The MFA abend handler has been entered. These are usually file open errors. All dumps are suppressed unless the abend code is 0Cx. The client program is notified of the error and processing continues. See the MVS console log for additional error information. |
| MFA101 E LIMIT OF 256 PROCESSES EXCEEDED |
The MFA client process count has reached it's maximum design limits. Notify our Product Support. |
| MFA102 E INPUT DATA FLOW EXCEEDS MAX ALLOWED |
Internal MFA TCP/IP error. Notify our Product Support. |
| MFA110 I VTAM PROCESSOR ACTIVE USING VTAMAPPL XXXXXXXX |
The VTAM logon processor has successfully initialized using the indicated VTAM application id. |
| MFA111 W VTAM ACB CLOSE FAILURE |
An attempt to close the VTAM acb has failed. This may be a VTAM environmental problem. See the MVS console log for additional information. |
| MFA112 I VTAM PROCESSOR HAS TERMINATED |
The VTAM logon processor has terminated. |
| MFA113 E USING VTAMAPPL XXXXXXXX, ERROR_TEXT |
A VTAM APPC error has occurred. The error_text contains diagnostic information. See the VTAM messages and codes manual for a description of the error. |
| MFA114 E APPC SINGLE SESSION REJECTION |
An APPC single session logon attempt has failed. See the VTAM messages and codes manual for a description of the primary and seconday return codes. |
| MFA115 E MFA DOES NOT SUPPORT 3270/LU2 DATASTREAMS |
An MFA logon attempt has been made via a non APPC connection. |
| MFA120 E SUB-NAME,I/O_ERROR_DATA |
An open edition error has occurred. Sub-name is the name of the MFA process. The i/o_error_data contains the verb being executed, the internet address of the client and the return and reason codes. See the open edition messages and codes manual under return codes for the meaning of the error. The MFA process id is terminated. |
| MFA121 I HALTING DUE TO JOB TERMINATION |
An MFA TCP/IP listener has terminated due a purge jobname operator command being issued. |
| MFA122 E ERR_IDNT,ERR_DATA |
A TCP/IP error has occurred. The err_idnt contains the verb being executed, the MFA process id, the internet address of the client and the return code. See the TCP/IP messages and codes manual under return codes for the meaning of the error. The MFA process id is terminated. |
| MFA130 E ERROR OPENING INTERLINK A.P.I |
An MFA listener has failed to initialize the Intrlink API. This may be due a subsystem name other than "acss" being used or the Intrlink subsystem not being active. The subsystem name may be changed in the registration macro i.e. MFAREG00 LOCAL=@intxxxx where xxxx is the subsystem name from the Intrlink startup jcl. See msg 131I and 132E. |
| MFA131 I TEMPORARY - WILL RETRY IN 30 SECONDS |
Intrlink has posted a temporary error during API initialization. The operation will be retried. See msg 130E. |
| MFA132 E PERMANENT - PROCESS ABORTING |
Intrlink has posted a permanent error during API initialization. The operation will not be retried. Issue the F jobname,START(DAEMON/DIRECT) command after the problem has been corrected. See msg 130E. |
| MFA133 I HAS SEVERED ALL INTERLINK CONNECTIONS |
An MFA listener has terminated it's connection to Intrlink. |
| MFA134 E INTRLINK ENV ERR CAUSES TERMINATION |
Intrlink has posted an environment error during verb processing. The current process is terminated. Check the MVS console log to determine the cause of the problem. |
| MFA135 W SHUTDOWN ERROR ON ACLOSE PROCESSING |
Intrlink has posted an error during API close. This may be due to Intrlink being purged while MFA is running. |
| MFA200 W DDNAME FSMSG? - FILE OPEN FAILURE, NO XXXX LOGGING |
A file open error has occurred. the //FSMSG? is not present in the startup JCL. Processing continues with no logging. Xxxx may be VSAM, SVC99, or VTAM. |
| MFA201 W ERROR OPENING DDNAME //VSAMCTL |
A file open error has occurred. Check the DDNAME in the startup JCL for //VSAMCTL. Check the MVS console log for the specific error encountered. |
| MFA202 I ERROR READING VSAMCTL FOR ???? MEMBER |
An I/O error has been encountered for member ????. The dataset or member may be corrupted. |
| MFA300 E MAXIMUM NUMBER OF SERVERS EXCEEDED |
The max number of MFA servers are currently executing. Additional licenses may need to be purchased. Contact our Product Support. |
| MFA301 E JCL PARM INVALID OR OMITTED |
The parm passed on the // EXEC PGM=MFARSC00,PARM='...' is invalid. Correct the parm and resubmit the job. |
| MFA302 I ATTACHING XXXXXXXX YYYYYYYYYYYYY |
An MFA communication driver is being activated at startup or via an operator start command. Xxxx represents the program name and yyyy contains a brief description. |
| MFA303 I VERSION MESSAGE |
Identifies the MFA version number and a copyright statement. |
| MFA310 E CANT UNDERSTAND REQUEST - RETRY |
An invalid operator command has been entered. |
| MFA311 W PROCESS IS ALREADY RUNNING |
An attempt has been made to start a process via an operator command. The process is already active. |
| MFA312 I TRACE FACILITY DISABLED |
The trace facility has been stopped by an operator command. |
| MFA313 W TRACE FACILITY FAILED TO STOP |
A dynamic allocation error occurred trying to stop the trace. |
| MFA314 I TRACE FACILITY ENABLED |
The trace facility has been started by an operator command. |
| MFA315 E TRACE FACILITY FAILED TO START |
A dynamic allocation error occurred trying to start the trace. |
| MFA316 E TCP/IP DAEMON SUPPORT NOT ACTIVATED |
An F jobname,PING operator command has been issued. This MFA region is not running a daemon process. |
| MFA317 I HAS BEEN TERMINATED |
The MFA job has been successfully terminated. |
| MFA318 E ABORT - MFASCK00 NOT IN LOAD LIBRARY |
TCP/IP has been requested but the registration table could not be loaded successfully. |
| MFA319 E ABORT - MFASCK00 IS BACK LEVEL |
Software module error. The registration table should be recompiled with the correct version for the MFA release being used. This is located in the INSTLIB dataset member $MVSTCP. |
| MFA320 E MFATAB00 VER/REL MISMATCH - RECOMPILE WITH LATEST VER |
Software module error. The FSTAB should be recompiled with the correct version for the MFA release being used. This is located in the INSTLIB dataset member $MVSFTAB. |
| MFA400 I USING HARD CODED LISTENER ADDRESS |
A bind is being issued for a specific internet addr as specified by the registration table. |
| MFA401 W WAITING FOR RELEASE OF PORT XXXXX |
A listener is not begin granted access to a port by TCP/IP. The port may be in use by another process. |
| MFA402 I REGISTERING AS XXXXXXXXXXX |
A TCP/IP daemon registration is being broadcast. xxxx represents the MFA server name. This matches the entry in the FHREDIR.CFG on the workstation. |
| MFA403 I RETURN CODE |
A TCP/IP daemon process has returned a code indicating
one of the below conditions. REGISTERED OK OK REGISTERED AGAIN RE-REGISTERED REGISTERED OVERRIDE RE-REGISTERED WITH CHANGES FAILED DAEMON OUT OF SPACE UNKNOWN CODE XXXX |
| MFA404 I LISTENING ON PORT XXXXX |
TCP/IP information. A listener has been successfully initalized on the indicated port. |
| MFA405 E TERMINATING DUE TO EXCP COND ON SOCKET |
TCP/IP error information. An exception condition has been posted on a connection. This may be due to a NETSTAT DROP command. |
| MFA406 E ERR_DATA |
TCP/IP error information. See the return code section of the TCP/IP messages and codes manual for the meaning. |
| MFA407 E NOT AUTHORIZED TO USE OE SERVICES |
The MFA jobname is not authorized to issue TCP/IP verbs. Contact your security administrator. |
| MFA408 W DE-REGISTERED BAD |
A TCP/IP daemon process has been terminated unsucessfully. The workstation daemon process or network may be down. Local processing continues. |
| MFA409 I DE-REGISTERED OK |
A TCP/IP daemon process has been terminated sucessfully. |
| MFA410 I HAS SEVERED ALL TCP/IP CONNECTIONS |
A TCP/IP listener has terminated it's connection. |
| MFA411 I FAILING TO CONNECT TO TCP/IP |
A listener is not connecting to TCP/IP. The attempt will be retried. Msg 412E may follow. |
| MFA412 E TCP/IP IS NOT AVAILABLE |
A listener didn't initialize because TCP/IP is not available. |
| MFA450 I USING IUCV INTERACE TO TCP/IP |
IUCV interace to TCP/IP is being used. |
| MFA452 W ATTEMPTING TO REGISTER AGAIN |
A registration attempt is being sent to the CCITCP2 daemon. |
| MFA453 I TCP/IP TERMINATION DETECTED |
An MFA listener has terminated due to TCP/IP being stopped. |
| MFA900 I | Security access logging is displaying an access message. |
| MFA901 W YOUR MICRO FOCUS MFA EVAL LICENSE HAS EXPIRED |
Your 45 days of evaluation are up. You will need to contact your account representative. |
| MFA902 E ABEND xxx DETECTED - ESTAE PROCESSED |
MFA has detected a mainframe ABEND. This information has been sent back to the workstation. Processing will continue, however this logical function was terminated. |
Table B-4: Abend Codes Returned by the MVS Server
| Abend Code | Description |
|---|---|
| User code 20 | More than 256 files were requested to be opened per application. |
| User code 26 | The maximum number of servers has been exceeded. Shut one down. |
| User code 44 | A back level TCP/IP registration table was used, or the registration table was not found. You need to run the $MFATCP installation jobstream. |
| User code 99 | The VTAM applid was inuse or not defined, or the TCP/IP registration table was not valid. |
Table B-5: Error Messages Returned by Drag and Drop
| Error Message | Description |
|---|---|
| MFDAS01: Mainframe access problem. |
A communication problem has been detected. Refer to the MFAERROR.LOG file for more information. |
| MFDAS02: Cannot import multiple files to a single file. |
An illogical request has been made, in that the user is attempting to import more than one file into a single file. |
| MFDAS03: Cannot export multiple files to a single file. |
An illogical request has been made, in that the user is attempting to export more than one file into a single file. |
| MFDAS04: Module 'MFLSC' is missing or inaccessible. |
The required module MFLSC cannot be found. This is most likely an installation problem. |
| MFDAS05: File had no length, or does not exist. |
The file had either a zero length, or had been deleted but the display was not refreshed. |
| MFDAS06: Call to module 'DFCONV' failed. Unable to convert the VSAM/QSAM file. |
A bad return code was given by the converter program. Run the dfconvwg program on its own to determine the error. |
| MFDAS07: Value is not a valid number. |
A non-numeric value was given when a numeric value was expected. |
| MFDAS08: For VSAM/QSAM files, extensions of PRO, DAT, or IDX are reserved. |
You cannot use a restricted extension for a file transfer. |
| MFDAS09: Rename to file failed. |
An error was returned when trying to rename a file. |
| MFDAS10: The allocation of failed with message number. |
An error message has been returned from MVS Workbench or Mainframe Express. Refer to those product's documentation for a description of the message. |
| MFDAS11: The allocation of differs from the mainframe. |
The DCB information for the MVS Workbench or Mainframe Express dataset differs from that of the mainframe. |
| MFDAS12: One or more of the fields have not been properly entered. |
Insufficient or incorrect information has been provided in the panel. |
| MFDAS13: The PC file name cannot have more than 4 subdirectory levels. |
MVS Workbench is unable to support more than 4 subdirectory levels. |
| MFDAS14: Mismatch between new and repeat passwords. |
The new and repeat passwords given do not match. |
| MFDAS15: Unable to make the directory. |
An error was returned when trying to create a directory. |
| MFDAS16: Unable to remove directory. |
An error was returned when trying to remove a directory. |
| MFDAS17: Call to module 'PCIMS' failed. Unable to convert the IMS database. |
A bad return code was given by the PCIMS program. Run the PCIMS program on its own to determine the error. |
| MFDAS18: A catalog search criteria must be entered. |
You must enter one or more mainframe catalog search criteria. If specifying more than one, then separate them by commas. This catalog search criteria is similar to that when using ISPF 3.4. |
| MFDAS19: A real workstation drive must be used. |
The drive selected for the MVS Workbench or Mainframe Express dataset does not exist on this workstation. |
| MFDAS21: A CCC/LCM system and configuration must be entered. |
You must provide both the LCM system and configuration name. |
| MFDAS22: Call to module 'SQL-Wizard' failed. Unable to convert the XDB table. |
A bad return code was given by the SQL wizard program. Run the SQL wizard program on its own to determine the error. |
| MFDAS23: Cannot establish connection to the mainframe server. |
Unable to connect to the mainframe server. |
| MFDAS24: Network communication problems with blocks of size. |
The user's network is unable to transport a data block of the size specified. This is most likely a router configuration problem. To temporarily circumvent the problem, you can specify the MFAMAXSENDLENGTH environment variable, with the value set to a size below the size in error. |
| MFDAS25: CCI module was not found. |
The CCI communications file is not found. |
| MFDAS26: Module is not a CCI module. |
The module specified is not a CCI communications file. |
| MFDAS27: Unable to delete file. |
An error was returned when trying to delete a file. |
| MFDAS28: Either recall this dataset or assign a type. |
This dataset is migrated. Either use the right-mouse context to recall it, or assign a specific type. |
| MFDAS29: Assign a type to this dataset. |
Unknown DSORG for this dataset. You need to use the right-mouse context to assign a specific type. |
| MFDAS30: The workstation dataset is connected to the mainframe |
This workstation dataset you are tying to access is redirection to a mainframe dataset. |
| MFDAS31: Copy of file failed. |
Unable to copy from the Windows clipboard. |
| MFDAS32: Paste of file failed. |
Unable to paste the file to the Windows clipboard. |
| MFDAS33: PCIMS is not available. Unable to convert the IMS database. |
The PCIMS.LBR routines could not be found, or if running under Mainframe Express, a project was not open. |
Table B-6: CIG Error Messages for E Option
| Error Message | Description |
|---|---|
| MSG01 | Now starting the MF/Endevor server |
| MSG02 | MF/Endevor server is now waiting |
| MSG03 | Unable to start MF/Endevor server |
| MSG04 | BSTIPT01 not allocated |
| MSG05 | Endevor actions not allowed |
| MSG06 | Syntax error in BSTIPT01 file |
| MSG07 | ESSI option not allowed in C1DEFLTS table |
| MSG08 | RACFUID= not allowed in C1DEFLTS table |
CICS
This section documents the anomalies in file status settings based
upon the environment in which the I/O statements are executed. Expected
results, including expected anomalies (for example, the order of records
returned when reading an alternate index in reverse order), are not included in
this list unless they help clarify the conditions under which the anomalies
were detected.
These results were compiled from a set of test programs that we executed in three environments: MVS-batch using IBM VS COBOL II accessing VSAM datasets, OS/2 using Micro Focus COBOL accessing sequential, relative and indexed files, and the CICS Mainframe Access server to process CICS datasets for an OS/2 client program. The test programs used an extensive combination of file definitions (organization and access mode), open types (INPUT, I/O, OUTPUT, EXTEND, etc.), and I/O verbs (e.g. READ, WRITE, REWRITE) to examine the behavior of execution environment and the results of the file status information returned to the test programs.
In the table that follows, file status information obtained for the tests in each environment is displayed in the format 'a/b', where 'a' represents the first byte of the file status (file status 1) and 'b' represents the second byte of the file status (file status 2). For run-time errors, the first byte displayed is '9' and the value for the second byte is the ordinal value of the file status 2 field (e.g. 9/100). When an I/O operation is invalid, a key of 'N/A' is used. When an I/O operation is valid but was not tested because of the results of an earlier I/O operations, a file status of '-/-' is used.
| READ SEQUENTIAL TEST WITH EMPTY FILES | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| SEQ SEQ | OPEN I/O | 3/5 | 0/5 | 0/5 |
| READ NEXT | -/- | 1/0 | 1/0 | |
| SEQ SEQ | OPEN I/O REVERSED | N/A | 0/0 | 0/5 |
| READ NEXT | -/- | 1/0 | 1/0 | |
| REL SEQ | OPEN I/O | 3/5 | 0/5 | 0/5 |
| READ NEXT | -/- | 1/0 | 1/0 | |
| REL SEQ | OPEN I/O | 3/5 | 0/5 | 0/5 |
| START RRN=20 | -/- | 2/3 | 2/3 | |
| REL SEQ | OPEN I/O | 3/5 | 0/0 | 3/5 |
| START RRN=0 | -/- | 2/3 | -/- | |
| IDX SEQ | OPEN INPUT | 0/0 | 3/5 | 0/0 |
| READ NEXT | 1/0 | -/- | 1/0 | |
| IDX SEQ | OPEN I/O | 0/0 | 0/5 | 0/0 |
| START KEY < VALUE | N/A | 2/3 | 2/3 | |
Note: When Micro Focus COBOL attempts to open a sequential dataset for I/O REVERSED processing and that dataset does not exist, a status code of 3/5 is returned. If the dataset does exist but is empty, a status code of 0/0 is returned on the open request.
| WRITE SEQUENTIAL TEST WITH EMPTY FILES | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| IDX SEQ | OPEN OUTPUT | 0/0 | 0/0 | 0/0 |
| WRITE (RECORD W/DUPLICATE ALT KEY) | 0/2 | 0/2 | 0/0 | |
| IDX SEQ | OPEN EXTEND | 0/0 | 0/0 | 0/0 |
| WRITE (RECORD W/DUPLICATE ALT KEY) | 0/2 | 0/2 | 0/0 | |
Note: The CICS server cannot determine if the result of this write operation would cause any alternate indexes to have two or more records with the same key value.
| DELETE SEQUENTIAL TEST | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| IDX SEQ | OPEN I/O | 0/0 | 0/0 | 0/0 |
| START ALT KEY GTEQ LOW-VALUES | 0/0 | 0/2 | 0/0 | |
| READ (DUPLICATE ALT KEY) | 0/2 | 0/2 | 0/2 | |
| DELETE | 0/0 | 0/0 | 4/3 | |
Note: The CICS server does not permit the deletion of a record via the alternate index if another record in the file has the same key for the alternate index. A status code of 4/3 is returned. The current record position is unaffected by the failed request.
| RANDOM WRITE TEST | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| IDX RAN | OPEN I/O | 0/0 | 0/0 | 0/0 |
| WRITE (RECORD W/DUPLICATE ALT KEY) | 0/2 | 0/2 | 0/0 | |
Note: The CICS server cannot determine if the result of this write operation would cause any alternate indexes to have two or more records with the same key value.
| READ SEQUENTIAL TEST WITH DATA IN FILES | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| IDX SEQ | OPEN INPUT | 0/0 | 0/0 | 0/0 |
| START KEY GTEQ HIGH-VALUES | 2/3 | 2/3 | 0/0 | |
| READ NEXT | -/- | -/- | 1/0 | |
Note: VSAM treats this as: 'position the current record pointer to the end of the file'; a subsequent READ PREVIOUS request would return the last record in the file.
| READ DYNAMIC TEST WITH DATA IN FILES | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| IDX DYN | OPEN INPUT | 0/0 | 0/0 | 0/0 |
| START KEY GTEQ HIGH-VALUES | 2/3 | 2/3 | 0/0 | |
| READ NEXT | -/- | -/- | 1/0 | |
Note: VSAM treats this as: 'position the current record pointer to the end of the file'; a subsequent READ PREVIOUS request would return the last record in the file.
| DELETE DYNAMIC TEST WITH DATA IN FILES | ||||
| FILE ORG-ACC |
I/O STATEMENTS | FILE STATUS | ||
|---|---|---|---|---|
| MVS-BATCH COBOL II |
OS/2 MF/COBOL |
CICS Server |
||
| IDX DYN | OPEN I/O | 0/0 | 0/0 | 0/0 |
| START ALT KEY GTEQ LOW-VALUES | 0/0 | 0/0 | 0/0 | |
| READ NEXT (DUPLICATE KEY) | 0/2 | 0/2 | 0/2 | |
| READ NEXT (LAST OF DUPLICATE KEY) | 0/0 | 0/0 | 0/0 | |
| DELETE (LAST OF DUPLICATE KEY) | 0/0 | 0/0 | 4/3 | |
Note: The CICS server does not permit the deletion of a record via the alternate index if another record in the file has the same key for the alternate index. A status code of 4/3 is returned. The current record position is unaffected by the failed request.
Copyright © 2002 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.