0

Command executed normally.

1

Command executed normally, but no segments were retrieved. The current position is unchanged. Either the qualifying conditions failed to locate the desired record, or an end of chain condition occurred (no more target segment instances within the anchor segment).

760

Command not recognized. An invalid HLI command was issued. For example, NXT rather than the NEX command.

761

Too few arguments have been provided in the HLI command.

762

The command cannot be executed because the file has not yet been opened (no OPN command has been issued).

763

The server requires more virtual storage to operate. Restart the server in a larger region.

764

The requested Master File cannot be found by the server.

765

The requested Master File cannot be found by the server.

766

No data found in the specified file. The file must first be initialized by the CREATE command even if no data is entered.

767

An error was encountered in the Master File on the server.

768

An invalid parameter was encountered in an HLI call received by the server (for example, NTEST is less than zero).

769

The fieldname referenced in a SHO command does not exist in the Master File. Check the spelling or the structure of the NAMES array passed into the SHO command.

770

The file specified in the CLO command is not open. The CLO command has been ignored.

771

Segment name not recognized. The segment specified as a TARGET or an ANCHOR segment is not found in the Master File.

772

The HLI command passed to the server is recognized but is not yet supported.

773

No current position has been established from which to execute the command.

774

Test relation not recognized. An invalid test relation was passed to the server. Possibly the number of tests was specified incorrectly. Valid test conditions are LT, LE, GT, GE, EQ, NE, CO, and OM.

775

Improper use of virtual segment. An attempt was made to change or improperly use a cross-reference segment.

776

An attempt was made to include a second instance of a unique segment for a particular parent instance. The transaction is ignored.

777

The external security system (CA-ACF2, RACF, or CA-TOP SECRET, for example) has determined that you do not have access rights to a file controlled by a server.

778

The ANCHOR and TARGET segments specified do not lie on the same path in the file.

779

An error has occurred in the use of an indexed field, or a field named in an NXD command is not indexed.

780

On an NXD call, no tests on the target segment were provided.

781

No parent position has been established for the retrieval of a cross-reference segment. The key for the linked segment is not active, and so no retrieval can be performed.

782

The password does not provide file access rights. Check the password provided in the FCB.

783

The command issued is not allowed with the current password. Check the password provided in the FCB.

784

The segment instance identified by the key values is already in the database. The database has not been changed. (Analogous to FOCURRENT=1 in MODIFY/SU.)

785

Segment instances obtained with NXK or NXD may not be deleted.

786

Attempt to change the instance has not been performed, because the instance has been deleted by another user. (Analogous to FOCURRENT=2 in MODIFY/SU.)

787

An OPN command was issued for an FCB which was already open. Before reusing the FCB, it must be closed.

788

Too many files are open on the server (limit 4096) or too many FCBs are open (limit 512).

789

Attempt to change the instance has not been performed because it has already been changed by another user. (Analogous to FOCURRENT=3 in MODIFY/SU.)

790

SU cannot be used with more than 1,500 fields in a FOCUS file, including cross references.

791

The FOCUS USE command must designate that all of the files used in the COMBINE have the same server. Either they must all be controlled by the same server or they must all be local files.

793

You cannot update, delete or include records for a file that has been specified as read only for use with Multi-Threaded HLI/SU Reporting.

794

You cannot declare a file to be read via Multi-Threaded HLI/SU Reporting if it has been opened by another FCB not operating Multi-Threaded HLI/SU Reporting. You cannot open a file that will not be read via Multi-Threaded HLI/SU Reporting if it has already been opened by another FCB operating under Multi-Threaded HLI/SU Reporting.

798

The Master File read by the central data base server is not the same as the one used by the source or local machine.

800

The server has terminated because of a fatal error.

801

A communication error has occurred on the server.

802

The server has not been started or the wrong name has been used for the server.

803

A communication error has occurred. Check to see that the server is still active and, if not, restart it.

804

The server is not active. Check to see if it has been terminated, and restart it.

805

A fatal error has occurred on the server. Check to see if the server is active and, if not, restart it.

806

A fatal error has occurred on the server. Check to see if the server is active and, if not, restart it.