Destination: USER-TASK, CONSOLE Routing code: A Weight: 99
Warranty : NO
OMS0001 USER IS CONNECTED TO OMNIS (TERMINAL=((&00)/(&01)); TID=(&02))
Meaning
(&00): station name
(&01): processor name
(&02): terminal identifier.
OMS0002
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0002 OMNIS VERSION (&00) READY
OMS0004
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0004 INVALID COMMAND OR ERROR IN OPERAND LIST ((&00)). COMMAND NOT EXECUTED
Meaning
Upon validation the command or associated operand list was found to
contain a syntax error.
The incorrect string is emphasized in the insert.
Response
Correct the command and try again.
OMS0005
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0005 (&00) ERROR '(&01)' AT ADDRESS '(&02)' (PAC=(&03), PTN=(&04), PRO=(&05))
Meaning
An error occurred during a (EXEC, DCAM, DMS) system call.
For the meaning of the error code, refer to the relevant BS2000 manual.
In the case of DCAM calls (i.e. when (&00) starts with 'Y'),
the meaning of the error code can be obtained
with the OMNIS command 'HELP YDDcccc',
where cccc are the first four characters of (&01).
In the case of DMS calls (i.e. (&01) begins with '0' or '1'), more
detailed information about the DMS error code can be requested in
system mode using /HELP-MSG DMS (&01) or taken from the BS2000 manual
'System Messages'.
(&00): name of the call
(&01): error code from R15
(&02): address of the call
(&03): partner address code, if the error can be ascribed to a partner
(&04): partner name
(&05): processor name.
Response
Depends on the error code (&01); if necessary, contact the OMNIS or
system administrator, because a generation error is possible.
OMS0006
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0006 CONNECTION TO PARTNER ((&00)/(&01)) LOST (PAC=(&02); CODE=(&03))
Meaning
The connection to the partner (&00)/(&01) with the address code (&02)
no longer exists.
(&00): application name
(&01): processor name
(&02): partner address code (PAC)
(&03): indicates the reason for abortion:
00, connection cleared down by the partner
04, invalid DEPROT/EDIT combination
08, processing error
0C, partner has failed
10, connection aborted by the network administrator
14, connection interrupted in the network
18, network error
1C, reserved
20, connection aborted; reason undefined
24, reserved
28, connection cleared after request by the system administrator
2C, error in connection element of the station services
30, reserved
34, error in the station services protocol
38, error in the transport system
3C, reserved
40, error in the connection message for the user from the station
services
44, wrong authorization name
48, authorization name already connected
4C, wrong password
50, proposed transport services class not accepted by the
communication partner
54, proposed priority in the data transmission network not
accepted by the partner
58, connection cleared down due to shortage of DCM memory space
5C, partner's VTSU not active
60, Protocol inconsistency by partner
64, Unrecoverable UCON error
68, Wrong Station
6C, Wrong Processor
70, No Task fuer Password check
74, Wrong CID for operator identification
78, Internal UCON error
7C, No ECRNAM entry available
80, DCAM version < V10, Chipcard check not possible
84, Chipcard check not possible
88, Letter does not correspond to new protocol
8C, No chipcard subsystem
90, Error in KVP protocol
94, Letter during authorization protocol missing
98, Connection identification not unique.
Response
Reestablish the connection; if necessary, contact the network
administrator.
OMS0007
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0007 PAC '(&00)' NOT FOUND. INPUT REJECTED
Meaning
(&00): partner address code (PAC).
OMS0008
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0008 STXIT ROUTINE ACTIVATED AT ADDRESS '(&00)' (IW=(&01)). OMNIS ABORTED
Meaning
An error was detected at address (&00), forcing the system to abort
OMNIS.
(&01): indicates the interrupt weight; the following values are
possible:
48, address translation error
4C, page not in memory
54, privileged operation
58, illegal op code or invalid SVC
5C, addressing error
60, data error
64, exponent overflow
68, division error
80, time runout
88, system error
8C, CANCEL
94, hardware address translation error.
Response
Save dump, logging and configuration file for error diagnosis,
contact the systems support staff and restart OMNIS.
You should also send the SYSOUT and SYSLST protocol of the OMNIS
enter-job
to the system staff.
OMS0009
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0009 PAC '(&00)' NOT FOUND. COMMAND NOT EXECUTED
Response
Correct the partner address code (PAC).
OMS0010
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0010 PAC '(&00)' ALREADY ASSIGNED TO PARTNER OR GROUP. COMMAND NOT EXECUTED
Response
Use a different partner address code (PAC).
OMS0011
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0011 WARNING: OLD OWNER AND NEW OWNER DO NOT HAVE THE SAME TERMINAL TYPE
Meaning
In an OCCCUPY command, the old and new owners were found to have
different terminal types. Problems may arise with the representation
of output on the screen.
OMS0012
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0012 'OPNCON' COMMAND ACCEPTED (PAC=(&00), PID=(&01), APPNAME=((&02)/(&03)))
Meaning
The OPNCON command was accepted and the connection request
successfully passed to the data communication system. The connection
has not been established. No messages can be sent to
(or received from) the partner yet.
OMS0013
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0013 OMNIS TERMINATED NORMALLY
OMS0014
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0014 'OPNCON' COMMAND EXECUTED SUCCESSFULLY (PARTNER=((&00)/(&01)), PAC=(&02))
Meaning
A connection (OPNCON) has been successfully established to
partner (&00)/(&01) with partner address code (PAC=(&02)).
The partner can send and receive messages now.
OMS0015
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0015 MESSAGE FROM TERMINAL WITH TID=(&00): (&01)
Meaning
The terminal with TID (&00) has sent the message (&01)
(via the /MESSAGE command).
Response
If necessary, send a reply to the sender.
OMS0016
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0016 BROADCAST FROM TERMINAL (&00): (&01)
Meaning
The terminal with TID (&00) has sent the message (&01) to all
OMNIS users (broadcast message via /SEND-MESSAGE command).
OMS0017
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0017 FILE '(&00)' CANNOT BE READ
Meaning
The file (&00) cannot be accessed.
Possible reasons:
- The file does not exist.
- The file is stored under another user ID.
- The file is not shareable.
- The file is protected by a password.
Response
Correct the file name or make file accessible, as appropriate.
OMS0018
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0018 ERROR WHEN OPENING NEW LOGGING FILE '(&00)'. COMMAND NOT EXECUTED
Meaning
The new logging file (&00) could not be opened using the CHANGELOG
command. Some messages may have been lost.
Response
Check the new logging file; if necessary, delete it.
OMS0019
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0019 EXIT ROUTINE '(&00)' COULD NOT BE LOADED. 'EXIT' OPERAND IGNORED
Meaning
Possible reason:
The exit routine could not be found in the module library defined by the
start parameters.
The LINK error code was given in the previous message OMS0005.
Response
Correct the name of the exit routine or make the exit routine available
in the module library; if necessary, contact the OMNIS administrator.
OMS0020
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0020 OMNIS SESSION TERMINATED NORMALLY (TERMINAL=((&00)/(&01)); TID=(&02))
Meaning
(&00): station name
(&01): processor name
(&02): terminal identifier.
OMS0021
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0021 PAC LIMIT EXCEEDED. COMMAND NOT EXECUTED
Meaning
The number of partners a terminal can be connected to
simultaneously
has been restricted by the OMNIS administrator (SET command).
Response
Clear any connections to partners no longer required or raise the PAC
limit (OMNIS administrator). The current PAC limit can be queried with
'INF S'.
OMS0022
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0022 PARTNER LIMIT EXCEEDED. CURRENT COMMAND NOT EXECUTED
Meaning
The number of partners available concurrently to all OMNIS users
has been restricted by the OMNIS administrator (SET command).
Response
Close any connections to partners no longer required or raise the partner
limit (OMNIS administrator). The current partner limit can be queried
with the 'INF S' command.
OMS0023
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0023 UTM SUPPORTS STRICT DIALOG ONLY. INPUT FOR PARTNER '(&00)' IGNORED
Meaning
With a UTM application, a strict dialog must be observed, i.e.
input and output must alternate. An attempt was made to enter
two messages consecutively for the UTM application with partner
address code (PAC=(&00)).
Response
Wait for the output from the partner (&00) before repeating input.
OMS0024
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0024 INVALID OR MISSING PASSWORD. COMMAND NOT EXECUTED
Meaning
In a command, an action was requested that requires a password to
be specified. An incorrect password, or no password at all, was
entered.
Response
Repeat command with correct password.
OMS0025
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0025 NO MODULE NAME WAS SPECIFIED WHEN CREATING OR MODIFYING EXIT GROUP '(&00)'. COMMAND NOT EXECUTED
Meaning
At least one module name must be specified when creating or modifying an
exit group.
OMS0026
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0026 PARTNER '(&00)' IN GROUP '(&01)' NOT FOUND
Meaning
The partner with PAC (&00) in group (&01) could not be deleted.
Response
Repeat command, specifying correct partner or group.
OMS0027
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0027 GROUP ADDRESS CODE '(&00)' NOT ADDED TO GROUP '(&01)'
Meaning
The members of a group must be partners; other groups are not permitted.
OMS0028
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0028 EXIT-MODULE (&00) WITH OLD INTERFACE IS NO LONGER SUPPORTED BY OMNIS
Meaning
The old EXIT interface is no longer supported by OMNIS.
Response
Migrate EXIT routine (&00) to the new OMNIS EXIT interface.
OMS0029
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0029 RESOURCE '(&00)=(&01)' NOT AVAILABLE. OMNIS RUN ABORTED
Meaning
When OMNIS is started more than once, each OMNIS run must be assigned
to its own logging file, an unique application name and an unique
prefix for auxiliary applications (start parameter).
Response
Make sure the required resources are exclusive.
OMS0030
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0030 'PAC=(&00)' IN GROUP '(&01)'. COMMAND NOT EXECUTED
Response
Use a different partner address code (PAC).
OMS0031
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0031 GROUP '(&00)' NOT FOUND. COMMAND NOT EXECUTED
OMS0032
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0032 INTERNAL OMNIS ERROR AT ADDRESS '(&00)'. DUMP GENERATED
Meaning
Inconsistencies in the data structure were detected during an internal
check.
A main memory dump was taken by means of PDUMP.
Response
Keep the dump and contact the systems support staff.
You should also supply the loggingfile, the SYSLST and SYSOUT protocol of
the OMNIS enter job an the startparameters.
OMS0033
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0033 INVALID PAGE-TURNING COMMAND: PLEASE ENTER 0, +, -, ++, --, +NNN OR -NNN
Response
Correct the command and try again.
OMS0034
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0034 COMMAND ACCEPTED
Meaning
The local OMNIS has accepted a command and transferred it to a remote
OMNIS
for further processing. The command has not been executed yet.
OMS0035
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0035 END OF LOGGING FILE
Meaning
This message reports that the last record of the logging file has already
been output (page-turning mode).
OMS0036
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0036 START OF LOGGING FILE
Meaning
This message reports that the first record of the logging file has
already
been output (page-turning mode).
OMS0037
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0037 '(&00)' COMMAND CANNOT BE USED FOR THE OWN TERMINAL SESSION
Meaning
The session selected by the command parameters ist your own session.
However, (&00) can only be used for foreign sessions.
Response
Correct the command and try again.
OMS0038
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0038 MESSAGE TABLE '(&00)' ALREADY EXISTS. COMMAND NOT EXECUTED
Response
Specify a different name for the message table.
OMS0039
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0039 MESSAGE TABLE '(&00)' NOT FOUND. COMMAND NOT EXECUTED
Response
Create message table or correct message table name.
OMS0040
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0040 MESSAGE TABLE '(&00)' CREATED
OMS0042
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0042 MESSAGE TABLE '(&00)' NOT FOUND. OPERAND 'MTAB' IGNORED
Response
Create message table or correct message table name.
OMS0043
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0043 PARTNER OR TERMINAL NOT FOUND (ID=(&00)). COMMAND NOT EXECUTED
Response
Repeat command with correct PID or TID.
OMS0044
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0044 PAC OR NEWPAC '(&00)' ALREADY ASSIGNED TO A PARTNER OR A GROUP. PARTNER NOT TAKEN OVER
Response
Specify a different NEWPAC.
OMS0045
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0045 FORMAT RECEIVED FROM PARTNER '(&00)' CANNOT BE DISPLAYED ON CONSOLE
OMS0046
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0046 LOGGING FILE EMPTY
Meaning
There is no partner record in the logging file (page-turning mode).
OMS0047
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0047 '(&00)' ALREADY EXISTING AS PARTNER ADDRESS CODE. COMMAND NOT EXECUTED
Response
Use a different group address code.
OMS0048
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0048 DECLARED OPTIONS FOR TERMINAL CANNOT BE CHANGED. COMMAND NOT EXECUTED
Meaning
The declared options cannot be changed because the terminal was
declared with CHANGE=NO.
OMS0049
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0049 NTACK ERROR (PAC=(&00)). DATA LOST
Meaning
A negative transport acknowledgment was received on the connection
to the partner with partner address code (PAC=(&00)). At least one
message
for this partner was lost.
OMS0050
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0050 DECLARED OPTIONS FOR PARTNER CANNOT BE CHANGED. COMMAND NOT EXECUTED
Meaning
The declared options cannot be changed because the partner was
declared with CHANGE=NO.
OMS0051
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0051 ONLY DECLARED PARTNERS ARE PERMITTED. COMMAND NOT EXECUTED
Meaning
The terminal was declared with OPNCON=DECLARED, i.e. it can
only communicate with the partners assigned to it at declaration time.
OMS0052
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0052 OMNIS IN PROCESSOR '(&00)' NOT DECLARED. COMMAND NOT EXECUTED
Meaning
Indirect connections can only be established to a partner if an
OMNIS-OMNIS connection has been declared to the partner processor.
Response
Establish a direct connection; if necessary, declare the OMNIS-OMNIS
connection.
OMS0053
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0053 PROCESSOR NAME MISSING. COMMAND NOT EXECUTED
Meaning
Indirect connections can only be established to another processor.
This processor was not specified.
OMS0054
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0054 'CLSCON' COMMAND ACCEPTED (PAC=(&00))
Meaning
The CLSCON command for the partner with partner address code (&00) has
been accepted and forwarded to a remote OMNIS for processing.
The connection has not yet been cleared.
OMS0055
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0055 CONNECTION TO PARTNER ((&00)/(&01)) CLEARED DOWN (PAC=(&02))
OMS0056
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0056 TWO OR MORE SESSION HAVE BEEN FOUND. SELECT THE APPROPRIATE ONE BY USING THE FOLLOWING LIST
Meaning
The command ist only applicable to a unique session.
However, two or more sessions corresponding to the slected parameter
have been found. The list of those session will follow.
Response
The easiest way to select a session is to use the TID or PID parameter.
OMS0057
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0057 TERMINAL LIMIT EXCEEDED. TERMINAL ((&00)/(&01)) NOT CONNECTED
Meaning
The maximum number of terminals that can use OMNIS simultaneously
has been limited by the OMNIS administrator (SET command).
The terminal limit can be queried by means of 'INF=S'.
Response
Ask the OMNIS administrator to increase the terminal limit and,
if necessary, try again later.
OMS0058
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0058 MESSAGES IN LOGGING FILE THAT CAN BE OUTPUT USING 'TURN', FOLLOWED BY '--' OR 'OCCUPY' WAS PERFORMED AUTOMATICALLY
Meaning
The logging file already contains messages that were generated before the
terminal was connected and therefore cannot be output.
An automatic 'OCCUPY' may also have been performed for the terminal.
OMS0059
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0059 CONFIGURATION FILE '(&00)' NOT PROCESSED
Meaning
A predeclared configuration was not established because the
configuration file '(&00)' could not be read. This message can be ignored
if no configuration file is required.
OMS0060
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0060 USER NOT CONNECTED TO OMNIS IN PROCESSOR '(&00)' (OAC=(&01)). COMMAND NOT EXECUTED
Response
Establish connection to remote OMNIS and repeat command.
OMS0061
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0061 SIZE OF (&00) FILE '(&01)' NOT A MULTIPLE OF (&02). OMNIS RUN ABORTED
Meaning
Primary and secondary allocation must be a multiple of (&02).
Response
Erase the file and then restart OMNIS.
OMS0062
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0062 PARTNER ((&00)/(&01)) NOT ACTIVE (PAC=(&02)). COMMAND NOT EXECUTED
OMS0063
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0063 USER TERMINAL ((&00)/(&01)) NOT DECLARED. CONNECTION REQUEST REJECTED
Meaning
The terminal (&00)/(&01) has not been declared and the OMNIS
administrator
has authorized declared terminals only (SET OPNCON=DECLARED).
Response
Contact the OMNIS administrator.
OMS0064
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0064 FUNCTION '(&00)' NOT YET IMPLEMENTED
OMS0065
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0065 'OCCUPY' FOR TERMINAL WITH 'OPNCON=DECLARED' ONLY PERMITTED FOR SAME TERMINAL
Meaning
Terminals with OPNCON=DECLARED can only OCCUPY themselves.
OMS0066
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0066 INVALID VERSION OF EXIT ROUTINE '(&00)'. MODULE NOT LOADED
Response
Recompile the exit module using the current macro library.
OMS0067
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0067 CONNECTION TO OMNIS ((&00)/(&01)) ABORTED (OAC=(&02), CODE=(&03))
Meaning
The connection to OMNIS (&00)/(&01) with the OMNIS address code (&02)
has
been lost.
(&03) indicates the reason for abortion :
00, connection cleared down by partner
04, invalid DEPROT/EDIT combination
08, processing error
0C, partner no longer available
10, connection aborted by network administrator
14, connection interrupted in network
18, network error
1C, reserved
20, connection aborted; reason undefined
24, reserved
28, connection closed after request by system administrator
2C, error in connection element of the station services
30, reserved
34, error in the station services protocol
38, error in the transport system
3C, reserved
40, error in the connection message for the user from the station
services
44, reserved
48, reserved
4C, reserved
50, proposed transport services class not accepted by the
communication partner
54, proposed priority in the data network not accepted by the partner
58, disconnection due to shortage of DCM memory space
5C, partner's VTSU not active.
Response
Reestablish the connection; if necessary, contact the network
administrator.
OMS0068
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0068 NTACK ERROR (OAC=(&00)). MESSAGE NOT RECEIVED. CONNECTION TO OMNIS ((&01)/(&02)) CLEARED
Meaning
A negative transport acknowledgment was received on the connection to
OMNIS (&01)/(&02) with the OMNIS address code (&00), i.e. a message
transmitted did not reach its destination. As a result the connection was
cleared down.
Response
If necessary, contact the network administrator.
OMS0069
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0069 ACK-ACK ERROR (OAC=(&00)). CONNECTION TO OMNIS ((&01)/(&02)) CLEARED
Meaning
During the monitoring of an OMNIS-OMNIS connection to OMNIS (&01)
in processor (&02) with OMNIS address code (&00), a monitoring message
was
not answered. The OMNIS-OMNIS connection was cleared down.
Response
Reestablish the connection; if necessary, contact the network
administrator.
OMS0070
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0070 THE INDIRECT PARTNER (&00) WITH PID=(&01) IN OPN STATUS MUST NOT BE OCCUPIED
Meaning
When an indirect partner is in the OPN state, it must not be occupied by
the OCCUPY command. The OCCUPY command has been rejected for partner
(&00).
OMS0071
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0071 'OCCUPY' COMMAND ACCEPTED (PAC=(&00),PID=(&01)). PARTNER NOT YET TAKEN OVER
Meaning
The OCCUPY command was accepted and has been forwarded to a remote
OMNIS for further processing.
OMS0072
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0072 'OCCUPY' COMMAND COMPLETED (PAC=(&00),PID=(&01))
OMS0073
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0073 OPERAND 'ROUTE=MUX' ONLY PERMITTED WHEN 'TYP=UTM'
OMS0074
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0074 'CONMODE' OF OLD OR NEW TERMINAL IS 'SINGLE'. 'OCCUPY' COMMAND REJECTED
Meaning
The CONMODE of a terminal affected by the OCCUPY command is SINGLE.
The OCCUPY command is not permitted in this case.
OMS0075
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0075 TOO MANY OPERANDS. 'MTAB' COMMAND NOT EXECUTED
Meaning
The MTAB comand has not been executed, as the operands are inconsistent.
Response
Enter the command with correct operands.
OMS0076
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0076 CONNECTION TO PARTNER ((&00)/(&01)) NO LONGER AVAILABLE (PAC=(&02))
Meaning
The indirect connection to partner (&00) in processor (&01) has
been broken because the OMNIS-OMNIS connection to OMNIS in
processor (&01) has been lost. The partner will not be available
until the OMNIS-OMNIS connection has been reestablished.
Response
Establish a new OMNIS-OMNIS connection; if necessary, contact the network
or OMNIS administrator.
OMS0077
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0077 OMNIS RESTART ACCEPTED (OAC=(&00), OID=(&01))
Meaning
The RESTART command for an OMNIS-OMNIS connection has been accepted.
OMS0078
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0078 OMNIS RESTART COMPLETED NORMALLY (OAC=(&00),OID=(&01))
OMS0079
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0079 CONNECTION TO OMNIS ((&00)/(&01)) NOT AVAILABLE (OAC=(&02)). COMMAND NOT EXECUTED
Response
Establish a new OMNIS-OMNIS connection; if necessary, contact the network
or OMNIS administrator.
OMS0080
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0080 COMMAND CAN ONLY BE ACCEPTED LOCALLY. COMMAND REJECTED
Meaning
This command can only be executed locally; it cannot be issued to a
remote
OMNIS with an OMNIS address code not equal to '@'.
OMS0081
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0081 (RE)START OF OMNIS '(&00)' ALREADY INITIATED. COMMAND REJECTED
Meaning
The restart of the OMNIS-OMNIS connection with address code (&00) has
already been initiated, but has not been completed.
OMS0082
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0082 PARTNER '(&02) ((&00)/(&01))' NOT ACTIVE. MESSAGE NOT DELIVERED
Meaning
There is no connection to partner (&00)/(&01) with address code (&02).
The message cannot therefore be forwarded to the partner and will be
lost.
Response
Set up a connection to the partner and repeat the command, or send
the message to the correct partner, as appropriate.
OMS0083
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0083 CONNECTION TO PARTNER '(&02) ((&00)/(&01))' FAILED
Meaning
The connection to the indirect partner (&00/&01) with partner address
code (&02) is not available because the OMNIS-OMNIS connection to
processor
(&01) has been lost. No messages may be sent or received
until the OMNIS-OMNIS connection has been reestablished.
Response
Establish a new OMNIS-OMNIS connection using the RESTART command;
if necessary, contact the network or OMNIS administrator.
OMS0084
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0084 WARNING: OMNIS 'TERMTYP' AND PDN 'STATTYP' DO NOT MATCH
Meaning
The terminal type specified when the terminal was declared with
OMNISKD is not the same as the one defined in the PDN generation.
This is only important if a TIAM partner was declared with
CONNECT=START (in which case there is no guarantee that the dialog
with the partner can be executed correctly).
Response
Correct the OMNIS declaration or PDN generation.
OMS0085
Destination: CONSOLE Routing code: A Weight: 99
Warranty : NO
OMS0085 OMNIS VERSION '(&00)' STARTED BY USER WITH USER ID '(&01)'
Meaning
This message tells the operator that OMNIS has been started.
OMS0086
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0086 TERMINAL CONNECTION CANCELLED BY (&00) (TERMINAL=((&01)/(&02)); TID=(&03))
Meaning
The user connection has been cancelled by the OMNIS-administrator
or by the user by means of the /CANCEL command.
(&01): station name
(&02): processor name
(&03): terminal identifier.
Response
Ask OMNIS-administrator why OMNIS connection was cancelled.
OMS0087
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0087 CONNECTION TO PARTNER '(&00) ((&01)/(&02))' CANCELLED BY (&03)
Meaning
The connection to partner (&01)/(&02) with the address code (&00)
has been cancelled by the OMNIS-administrator or by the user
by means of the /CANCEL command.
Response
Ask OMNIS-administrator why connection was cancelled.
OMS0088
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0088 HC CONNECTION TO '(&00) ((&01)/(&02))' CANCELLED BY OMNIS ADMINISTRATOR
Meaning
The connection to printer (&01)/(&02) with address code (&00)
has been cancelled by the OMNIS administrator by means of the /CANCEL
command.
This message will be sent to all terminals that are using this printer.
Response
Ask OMNIS administrator why connection was cancelled.
OMS0089
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0089 HC CONNECTION TO '(&00) ((&01)/(&02))' LOST. (REASON: (&03))
Meaning
The connection to printer (&01)/(&02) with address code (&00)
has been lost (LOSCON).
(&03): indicates the reason for abortion:
00, connection cleared down by the partner
04, invalid DEPROT/EDIT combination
08, processing error
0C, partner has failed
10, connection aborted by the network administrator
14, connection interrupted in the network
18, network error
1C, reserved
20, connection aborted; reason undefined
24, reserved
28, connection cleared after request by the system administrator
2C, error in connection element of the station services
30, reserved
34, error in the station services protocol
38, error in the transport system
3C, reserved
40, error in the connection message for the user from the station
services
44, reserved
48, reserved
4C, reserved
50, proposed transport services class not accepted by the
communication partner
54, proposed priority in the data transmission network not
accepted by the partner
58, connection cleared down due to shortage of DCM memory space
5C, partner's VTSU not active.
Response
Reestablish connection to printer with RESTART command; if necessary,
contact the OMNIS or network administrator.
OMS0090
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0090 HARDCOPY UNIT '(&00)' NOT DECLARED
Meaning
No printer has been declared with address code (&00).
Response
Use another printer or declare this printer.
OMS0091
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0091 LOGGING STARTET ON '(&00)' AT '(&01)'
Meaning
Start message in the logging file.
OMS0092
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0092 PERMANENT LOGGING ERROR. LOGGING DEACTIVATED
Meaning
A DMS error was reported when accessing the logging file (see preceding
message OMS0005). The logging has been switched off; i.e. functions that
require logging (e.g. message saving, page-turning, resource shortage
handling) are no longer possible. The most likely cause is
'insufficient PUB space' (logging file may have become too big).
Response
Eliminate the problem, then end and restart OMNIS as soon as possible.
OMS0093
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0093 NTACK ERROR FOR (&00) ((&01)/(&02)). CONNECTION TO (&03) CLEARED
Meaning
A negative transport acknowledgment was received from (&00)
(&01)/(&02), i.e. at least one message could not be sent to the
terminal.
The most likely cause is a network failure.
OMS0094
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0094 'HOLD=YES' AND NO 'OPASS' SPECIFIED
Meaning
HOLD=YES was specified in a command although no OPASS had been defined.
HOLD=YES has been accepted, but will have no effect until an OPASS is
specified.
If the command was a HALT command, it has not been executed.
If the command was a OPNCON command, HOLD=STD has been used.
Response
Specify OPASS as well.
OMS0095
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0095 (RE)START OF HARDCOPY UNIT '(&00) ((&01)/(&02))' INITIATED
Meaning
The (re)start of printer (&01)/(&02) with address code (&00)
was initiated after a connection failure. The printer may only
be used once the (re)start has been completed (message OMS0097).
OMS0096
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0096 (RE)START OF HARDCOPY UNIT '(&00) ((&01)/(&02))' ALREADY INITIATED. COMMAND REJECTED
Meaning
A (re)start of printer (&01)/(&02) with address code (&01) has
already been initiated, but not yet completed.
OMS0097
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0097 RESTART OF HARDCOPY UNIT '(&00) ((&01)/(&02))' SUCCESSFULLY COMPLETED
Meaning
A restart of printer (&01)/(&02) with address code (&00)
initiated with the RESTART command has been successfully completed.
OMS0098
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0098 HARDCOPY UNIT '(&00) ((&01)/(&02))' ACTIVE. 'RESTART' COMMAND REJECTED
Meaning
The printer (&01)/(&02) with address code (&00) is active.
OMS0099
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0099 HARDCOPY UNIT '(&00) ((&01)/(&02))' AVAILABLE AGAIN
Meaning
The printer (&01)/(&02) with address code (&00) is available again.
This message is sent to all the terminals that are using the relevant
printer.
OMS0100
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0100 RESTART OF HARDCOPY UNIT '(&00) ((&01)/(&02))' UNSUCCESSFUL. PRINTER NOT AVAILABLE
Meaning
A restart, using the RESTART command, of printer (&01)/(&02) with
address
code (&00) has failed.
Response
Attempt new restart; if necessary, contact the OMNIS or network
administrator.
OMS0101
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0101 ALTERNATE HARDCOPY UNIT '(&00) ((&01)/(&02))' FOR '(&03) ((&04)/(&05))' NOT AVAILABLE
Meaning
The alternate device (&01)/(&02) with address code (&00) for the
failed printer (&04)/(&05) with address code (&03) is not available;
i.e. also inoperable. Any messages for this printer (&00) will be lost.
This message is issued to all the terminals that are using printer
(&03).
Response
Reestablish the connection to printer (&00) and/or printer (&03) by
means
of the RESTART command; if necessary, contact the OMNIS or network
administrator.
OMS0102
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0102 ALTERNATE HARDCOPY UNIT '(&00) ((&01)/(&02))' SUCCESSFULLY ASSIGNED TO '(&03) ((&04)/(&05))'
Meaning
The messages sent to the inoperable printer (&01)/(&02) with
address code (&00) will be rerouted to printer (&04)/(&05) with
address code (&03) until printer (&00) is available again.
This message is sent to all the terminals that are using printer (&01).
OMS0103
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0103 NO ALTERNATE DEVICE DEFINED FOR HARDCOPY UNIT '(&00) ((&01)/(&02))'
Meaning
No alternate printer has been defined to replace the inoperable printer
(&01)/(&02) with address code (&00). This message is sent
to all the terminals that are using the printer.
OMS0104
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0104 NTACK ERROR ON HARDCOPY UNIT '(&00) ((&01)/(&02))'
Meaning
A negative transport acknowledgment has been received from printer
(&01)/(&02) with address code (&00), i.e. at least one message could
not
be delivered. The most likely reason is a network failure.
Response
Reestablish a connection to the printer with the RESTART command;
if necessary, contact the OMNIS or network administrator.
OMS0105
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0105 ALTERNATE DEVICE '(&00)' FOR HARDCOPY UNIT '(&01) ((&02)/(&03))' NOT DECLARED. COMMAND NOT EXECUTED
Meaning
The alternate device (&00) for printer (&02)/(&03) with address code
(&01) specified in the command has not been declared.
Response
Use a different alternate device or declare the printer.
OMS0106
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0106 EXIT GROUP '(&00)' NOT FOUND
Meaning
No exit group with address code (&00) is known to OMNIS.
Response
Define exit group (EXIT command) or use a correct address code, as
appropriate.
OMS0107
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0107 EXIT GROUP '(&00)' DECLARED
Meaning
The exit group with address code (&00) has been created successfully.
OMS0108
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0108 EXIT GROUP '(&00)' ALREADY DECLARED. COMMAND REJECTED
Meaning
The exit group with address code (&00) has been already declared.
OMS0109
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0109 EXIT GROUP '(&00)' CANNOT BE CHANGED. COMMAND REJECTED
Meaning
The exit group with address code (&00) cannot be changed because it
was declared with CHANGE=NO.
OMS0110
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0110 MODULE SPECIFIED MORE THAN ONCE IN EXIT GROUP '(&00)'. COMMAND REJECTED
Meaning
When the modules belonging to the exit group with address code (&00)
were defined, one module was specified more than once.
Response
Correct the command.
OMS0111
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0111 TERMINAL '((&00)/(&01)) (&02)' NOT ACTIVE. COMMAND REJECTED
Meaning
The terminal (&00)/(&01) with TID (&02) is not active.
Response
Correct the TID.
OMS0112
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0112 HARDCOPY UNIT '(&00)' NOT ACTIVE. COMMAND REJECTED
Meaning
The printer with address code (&00) is not active.
OMS0113
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0113 K KEY '(&00)' AMBIGUOUS
Meaning
The K key specified is already being used for something else (e.g. KPAC
for another partner, CALL-KEY, BREAK-KEY).
Response
Use another K key.
OMS0114
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0114 HARDCOPY UNIT '(&00)' DECLARED WITH 'USE=DECLARED'. COMMAND REJECTED
Meaning
The printer with address code (&00) is reserved for the terminals
to which it was assigned by declaration.
Response
Use another printer or do without.
OMS0115
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0115 'KPAC' ONLY PERMITTED FOR 'TYP=UTM'. COMMAND REJECTED
Meaning
The KPAC operand can only be assigned to UTM-type partners.
Response
Either do not specify KPAC or define TYP=UTM.
OMS0116
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0116 COMMAND '(&00)' ONLY PERMITTED IN TEST MODE
Meaning
The DUMP and CMD commands are only permitted in test mode.
Response
Switch on test mode.
OMS0117
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0117 TELEPHONE NUMBER '(&00)' TRANSMITTED TO AUTOMATIC SELECTION UNIT
OMS0118
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0118 OMNIS '(&00)' DECLARED WITH 'OPNCON=DECLARED'. COMMAND REJECTED
Meaning
Only declared indirect connections are permitted on the OMNIS
connection with address code (&00).
Response
Use a direct connection or declare an indirect connection or declare
OMNIS
with OPNCON=FREE.
OMS0119
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0119 TERMINAL ((&00)/(&01)) STILL ACTIVE. CONNECTION REQUEST REJECTED
Meaning
The terminal with network address (&00)/(&01) is still active.
This happens if the terminal was previously connected indirectly to
OMNIS,
the connection was interrupted and HOLD=YES had been specified
or an ISO application connects to omnis more than once.
Response
CANCEL the connection.
OMS0120
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0120 INPUT REQUEST REJECTED BY SVP '(&00)'. LAST INPUT LOST
Meaning
The SVP has rejected one of the input requests generated by OMNIS.
Response
Repeat input.
OMS0121
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0121 'PTNNAME' AND/OR 'PRONAME' MISSING. COMMAND REJECTED
Meaning
For SVP-type partners a full network address must be specified. At least
part of the network address is missing.
Response
Specify full network address.
OMS0122
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0122 MESSAGE OF LENGTH 0 FOR PARTNER '(&00)' IGNORED
Meaning
Messages of length zero cannot be sent to partner (&00)
(constraint of DCAM). The input has been ignored.
Response
Correct the input.
OMS0123
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0123 INVALID 'HELP' COMMAND
Meaning
The operand specified in the HELP command is unknown to OMNIS.
Response
Correct the operand; if necessary, try 'HELP HELP' or 'HELP' without
any operands.
OMS0124
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0124 INVALID FUNCTION KEY. INPUT IGNORED
Meaning
A message to the SVP was entered without F1 (system), F2 (console
processor), F3 (service processor) or SEND (system). The input
destination could therefore not be identified.
Response
Repeat message using the correct key or use correct address code,
as appropriate.
OMS0125
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0125 OVERLONG INPUT FOR SVP IGNORED
Meaning
The maximum length for input via SPV connection is 80 characters.
As a longer message was entered, it has not been forwarded to the SVP.
Response
Correct the input or use correct address code, as appropriate.
OMS0126
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0126 ERROR WHEN LOADING MODULE OF EXIT GROUP '(&00)'
Meaning
An error occurred during the loading of at least one module of
exit group (&00) (see preceding message OMS0005).
The exit group is considered as not declared.
Possible reasons:
- module not found
- unresolved external references.
Response
Depends on error code supplied by DLL.
OMS0127
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0127 GROUP '(&00)' DECLARED WITH 'CHANGE=NO'. COMMAND REJECTED
Meaning
Groups declared with 'CHANGE=NO' cannot be changed.
Response
Declare a new group.
OMS0128
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0128 A HARDCOPY UNIT CANNOT BE ITS OWN ALTERNATE DEVICE. COMMAND REJECTED
Response
Choose another alternate printer.
OMS0129
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0129 WARNING: PARTNER '(&00)' AWAITING FORMAT INPUT
Meaning
A partner which is awaiting a format input has been taken over with the
OCCUPY command. Problems may arise if messages are sent to this partner.
This would be a protocol infringement.
OMS0130
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0130 ASSIGNED EXIT GROUP '(&00)' MAY NOT BE CHANGED
Meaning
The exit group assigned to the terminal with the SET or OPTION
command cannot be changed. OMNIS may execute the command from a routine
in the exit group and reload the module; there is, however, no
guarantee that the code at the return address will be correct.
Response
Cancel the exit group assignment by means of OPT EXIT=NO. Then enter
a new EXIT command.
OMS0131
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0131 ERROR ON FILE MACRO FOR PARTNER (&00); KDCSIGN/LOGON SEQUENCE NOT PROCESSED
Meaning
An error occurred during the execution of the FILE macro for the text
file
containing the KDCSIGN sequence or the LOGON sequence of partner (&00).
For more details, see the preceding message OMS0005.
Response
Depends on DMS error code.
OMS0132
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0132 OPEN ERROR ON TEXT FILE FOR PARTNER '(&00)'; KDCSIGN/LOGON SEQUENCE NOT PROCESSED
Meaning
An error occurred during execution of the OPEN macro for the text file
containing the KDCSIGN/LOGON sequence of partner (&00).
For more details, see the preceding message OMS0005.
Response
Depends on DMS error code.
OMS0133
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0133 KEY SPECIFIED '(&01)' IN 'OPNCON' COMMAND OF PARTNER '(&00)' NOT FOUND IN TEXT FILE; KDCSIGN/LOGON SEQUENCE NOT PROCESSED
Meaning
For further information, see preceding message OMS0005.
Response
Depends on DMS error code.
OMS0134
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0134 OMNIS COULD NOT POSITION TO LAST RECORD READ IN KDCSIGN/LOGON SEQUENCE OF PARTNER '(&00)'. PROCESSING OF KDCSIGN/LOGON SEQUENCE ABORTED
Meaning
An error occurred during positioning at the last read record of
partner (&00).
For further information, see the preceding message OMS0005.
Response
Depends on DMS error code.
OMS0135
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0135 ERROR ON READING NEXT RECORD IN KDCSIGN/LOGON SEQUENCE OF PARTNER '(&00)'. PROCESSING OF KDCSIGN/LOGON SEQUENCE ABORTED
Meaning
An error occurred on reading the next record in the KDCSIGN/LOGON
sequence for partner (&00).
For further information, see the preceding message OMS0005.
Response
Depends on DMS error code.
OMS0136
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0136 TEXT FILE COULD NOT BE CLOSED
Meaning
An error may occur if a new OPNCON command is issued with the
operand START-SEQUENCE.
For further information, see preceding message OMS005.
Response
Depends on DMS error code.
OMS0137
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0137 PLEASE ENTER '(&00)':
Meaning
OMNIS requests the (&00) in blanking mode.
Response
Enter (&00).
OMS0138
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0138 AT LEAST ONE PARTNER PER GROUP MUST BE DECLARED. COMMAND REJECTED
Meaning
Group command ADD without a partner is not allowed.
Response
Correct the input.
OMS0142
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0142 PAGE-TURNING MODE ABORTED BECAUSE PARTNER '(&00)' NO LONGER AVAILABLE
Meaning
The partner (&00) cleared down the connection during 'TURN <PAC>'.
Response
Try another OMNIS command.
OMS0143
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0143 'EXIT' COMMAND RESERVED FOR OMNIS ADMINISTRATOR
Meaning
Only the OMNIS administrator can issue an EXIT command.
Response
Specify the APASS or have the EXIT command authorization extended
to all users.
OMS0144
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0144 'MDEF' COMMAND RESERVED FOR OMNIS ADMINISTRATOR
Meaning
Only the OMNIS administrator can issue an MDEF command.
Response
Specify the APASS.
OMS0145
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0145 CONNECTION TO OMNIS '(&00)' NOW AVAILABLE
Meaning
The slave OMNIS (&00) has been started and you can now work with
indirect
partners.
OMS0146
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0146 INDIRECT PARTNER '(&00)' NOW AVAILABLE
Meaning
The slave OMNIS has been started and the declared indirect
partner (&00) is now available.
OMS0147
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0147 TERMINAL ((&00)/(&01)) COULD NOT BE FOUND
Meaning
The terminal with partner name (&00) and processor name (&01)
could not be found when executing the MESSAGE command.
Response
Enter correct partner and processor name.
OMS0148
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0148 'MTAB' ONLY PERMITTED FOR PARTNER OF TYPE 'UCON' OR 'SVP'. COMMAND REJECTED
Response
Correct the command.
OMS0149
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0149 IN THE FILE SPECIFIED IN THE 'FILE' COMMAND OMNIS PASSWORDS MAY NOT BE REQUESTED IN BLANKING MODE. COMMAND REJECTED
Response
Correct the commands in the command file.
OMS0150
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0150 PARTNER '(&00)' TAKEN OVER BY ANOTHER TERMINAL WITH 'OCCUPY' COMMAND
Meaning
The partner is no longer available to this terminal.
OMS0151
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0151 INVALID MESSAGE RECEIVED FROM SKP PARTNER '(&00)'
Meaning
The SKP partner (&00) sent a message of an invalid type.
Response
Check the protocol between OMNIS and SKP.
OMS0152
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0152 MESSAGE OF LENGTH '0' NOT SENT TO SKP PARTNER '(&00)'
Meaning
The message has not been forwarded.
Response
Enter correct message.
OMS0153
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0153 MUX PARTNER ((&00)/(&01)) REJECTED BIND REQUEST FOR PARTNER (PAC=(&02)). (CODE=(&03))
Response
Reasons for negative BIND processing:
00, session established
01, specified interface version incorrect
02, sign-on data incomplete or incorrect
03, maximum number of sessions reached
04, general error code (see neg. K036 message in SYSLOG)
- KCSWAIT: CHECK-STATION-NAME
- KCSWAIT: UR-NO-SCB-AVAILABLE
- STATE-APPLICATION NE NORMAL-RUN
- after KDCSIGN: general return code
05, specified terminal already connected
06, specified user already connected
07, terminal or processor name missing
08, terminal information in BIND invalid
09, invalid KDCSIGN password
0A, BIND request lost
0B, terminal characteristics or protocol version missing
0C, terminal is not an interactive terminal; ANNOAMSG=N, PTYPE=APPLI
or USAGE=NO has been generated in UTM
0D, PROTOCOL=NO was generated in UTM
0E, no send authorization
0F, connection cleardown for transport connection in progress
10, wrong ID card information in BIND
11, invalid USER in BIND request
12, KSET for terminal missing
13, USER locked
15, wrong response type
16, BIND includes user message
17, the defined station is still in state "RELEASE-PENDING"
18, transaction recovery; the user may not enter KDCSIGN now
19, error during authentification
1A, chipcard authentification is running
1B, error during authentification; no reason specified
1C, password is being checked (intern);
1D, the new password is not complex enough
1E, error in the new password; new password = old password
1F, the new passwort is required (internal)
20, KDCSIGN not allowed at the moment; user aleady connected
21, there are no more user allowed to connect; MAX-CON-USER reached
22, no new password specified
23, timeout for passwort reached
24, the new password is too short
25, lack of resources
26, the application will be ended; SHUT WARN has been entered
27, the station does not possess the right key to continue the
conversation
28, after transmission of the password by KDCUPD the password is not
complex enough or too short;.
29, PTERM name unknown;
2A, processorname unknown;
2B, STATUS=OFF for this PTERM;
2C, STATUS=OFF for this LTERM;
2D, establishing of connection in progress;
2E, the station/connection is generated at an other BCAM application;
2F, processorname unknown and no terminalpool name;
30, no terminalpool corresponding to station type or PTERM name
unknown;
31, no free entry in the terminalpool;
32, establishing of connection in progress;
33, the terminalpool is generated in an other application;
34, the connection request has been rejected by contention;
35, connection request rejected by VTSU; e.g. the station type is not
supported or invalid connection letter;
36, BCAM letterlength too short;
37, BCAM returncode not ok.
OMS0154
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0154 INVALID SESSION REFERENCE RECEIVED BY OMNIS FROM PARTNER ((&00)/(&01)). DIAGNOSTIC INFO=(&02), ADDRESS='(&03)', MESSAGE HAS BEEN IGNORED
Meaning
A message was sent to OMNIS by partner ((&00)/&01)) with an invalid
session reference. OMNIS could not assign a partner to the message.
Response
diagnostic info:
00, positiv returncode;
04, invalid OPCODE;
08, block-number too large
0C, invalide session-reference;
10, session-reference not allocated;
14, REQM-error;
18, invalide session adress.
OMS0155
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0155 MUX PARTNER ((&00)/(&01)) HAS DISCONNECTED SESSION FOR PARTNER (PAC=(&02)) WITH 'UNBIND' (CODE=(&03))
Meaning
The partner (&02) is no longer available.
Response
For information about the reason, see the manual 'UTM Generating and
Administering Applications'.
Reasons for the UNBIND request:
01, KDCOFF entered
02, KDCOFF BUT entered
03, internal UTM event (administration, timeout, etc.)
04, protocol error; send authorization violated
05, protocol error; invalid session reference
06, protocol error; message sent without receive mode
07, protocol error; empty user message sent
08, no chip card reader
09, chip card user already connected
0A, wrong chip card
0B, communication error with chip card reader
0C, communication error with security module
0D, internal UTM reason
0E, message could not be read (LETTER LOST)
81, UTM resource bottleneck.
OMS0156
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0156 ONLY DIRECT CONNECTIONS ARE PERMITTED FOR MUX PARTNERS
Meaning
Indirect connections are not permitted for MUX partners.
OMS0157
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0157 MUX PARTNER ((&00)/(&01)) NOT DECLARED
Meaning
All MUX partners (PTNNAME/PRONAME) must be declared by the OMNIS
administrator.
Response
Contact the OMNIS administrator to declare MUX partner (&00)/(&01).
OMS0158
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0158 PARTNER '(&00)' EXPECTS 'FORM' OR 'PHYS' MESSAGE. MESSAGE IGNORED
Meaning
A LINE message was entered at the terminal and may not be sent to TIAM.
Response
Send a message of length 0 or define KPAC for partner and press K key.
OMS0159
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0159 CONNECTION TO MUX PARTNER '((&00)/(&01)),PAC=(&02)' LOST; (CODE=(&03))
Meaning
The connection to MUX partner (&00)/(&01) with PAC=(&02) has been
lost.
(&03): reasons for abortion:
00, connection cleared down by the partner
04, invalid DEPROT/EDIT combination
08, processing error
0C, partner no longer available
10, connection aborted by the network administrator
14, connection interrupted in network
18, network error
1C, reserved
20, connection aborted; reason undefined
24, reserved
28, connection closed by the system administrator
2C, error in connection element of the station services
30, reserved
34, error in station services protocol
38, error in transport system
3C, reserved
40, error in connection message for the user from the station services
44, reserved
48, reserved
4C, reserved
50, proposed transport services class not accepted
by communication partner
54, proposed priority in the data network not accepted
by partner
58, disconnection due to shortage of DCM memory space
5C, partner's VTSU not active.
Response
Reestablish the connection; if necessary, contact the network
administrator.
OMS0160
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0160 SENDING MESSAGES TO OMNIS VIA SKP PARTNER '(&00)' ONLY PERMITTED IN TEST MODE
Response
Switch on the test mode.
OMS0161
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0161 NO OMNIS ADMINISTRATOR PASSWORD DEFINED. OMNIS RUN ABORTED
Meaning
No OMNIS administrator password was defined in the startup file.
To prevent unprotected OMNIS operation, OMNIS has been terminated.
Response
Define OMNIS administrator password in startup file.
OMS0162
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0162 ACKNOWLEDGMENT RECEIVED FROM SVP '(&00)' FOR LAST INPUT SENT
OMS0163
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0163 'CODE=BINARY' ONLY PERMITTED FOR PARTNER OF TYPE 'DCAM'. COMMAND REJECTED
Response
Correct the command.
OMS0164
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0164 OPERANDS (BERID, LPASS, MTAB, CMSG OR LMSG) NOT PERMITTED FOR SPECIFIED PARTNERTYPE
Response
Correct the command.
OMS0165
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0165 PAC '(&00)' ALREADY IN GROUP. SECOND ENTRY IGNORED
OMS0166
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0166 VERSIONS OF 'OMNISKD' AND 'OMNIS' INCOMPATIBLE. CONFIGURATION FILE NOT PROCESSED
Meaning
OMNISKD and OMNIS must be of the same version.
Response
Create configuration file using current version of OMNISKD.
OMS0167
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0167 HAC '(&00)' NOT UNIQUE. COMMAND REJECTED
Meaning
All printers must have unique address codes. A printer with the
address code (&00) has already been entered.
OMS0168
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0168 HARDCOPY UNIT ((&00)/(&01)) NOT UNIQUE. COMMAND REJECTED
Meaning
All printers must have unique network addresses. A printer with the
network address (&00)/(&01) has already been entered.
Response
Correct HCOPY command.
OMS0169
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0169 'CANCEL' COMMAND ILLEGAL FOR A GROUP; COMMAND NOT EXECUTED
Meaning
The CANCEL command is not permitted for the <pid> of a group.
The <pid> must be a partner.
OMS0170
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0170 OMNIS MUX ERROR AT ADDRESS '(&00)'. SOME MESSAGES MAY HAVE BEEN LOST. DUMP TAKEN
Meaning
An error occurred in the PUTMMUX protocol between OMNIS and UTM.
OMS0171
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0171 OPERAND 'HOLD=AUTO' NOT PERMITTED FOR PARTNER '(&00)'
Meaning
HOLD=AUTO may only be specified in the SET or OPTION command.
OMS0172
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0172 NO MESSAGE NUMBER SPECIFIED IN COMMAND 'MTAB' FOR MESSAGE TABLE '(&00)'
Meaning
When using ACTION=MODIFY in the MDEF command a message ID has to be
specified.
OMS0173
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0173 OPERAND 'KPAC=STD' NOT PERMITTED FOR PARTNER '(&00)'
Meaning
Partners can only be assigned with KPAC=<number> or KPAC=NO.
OMS0174
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0174 OMNIS RECEIVED MESSAGE WITH LENGTH LESS THAN ZERO. MESSAGE IGNORED
Meaning
OMNIS has received a message with invalid EDIT options.
Response
Try input again.
OMS0175
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0175 COMMAND '(&00)' NOT PERMITTED IN THIS USER ID
Meaning
For security reasons the command (&00) must not be issued in this user
ID.
OMS0176
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0176 OMNIS HAS TRIED TO WRITE RECORD INTO LOGGING FILE. LENGTH TOO SHORT. RECORD NOT WRITTEN
Meaning
All records to be written into the OMNIS logging file must have a
minimum length. If the length is too short, the record cannot be written
into the OMNIS logging file.
OMS0177
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0177 VALUE FOR OPERAND 'START-SEQUENCE' OF PARTNER '(&00)' TOO LONG. COMMAND REJECTED
Meaning
When starting OMNIS, the number of relevant characters for the key of the
text file can be defined. However, for the partner with partner address
code (&00) a longer key has been defined.
Response
Increase the maximum key length at OMNIS startup or define another key
for this partner.
OMS0178
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0178 'START-SEQUENCE' OPERAND NOT PERMITTED. COMMAND REJECTED
Meaning
The OMNIS administrator has not permitted the START-SEQUENCE operand in
the OPNCON command.
OMS0179
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0179 WHEN 'SECURITY LEVEL=HIGH' NO FILE NAME PERMITTED IN COMMAND '(&00)'
Meaning
The OMNIS administrator has prohibited access to BS2000 files with the
command (&00).
OMS0180
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0180 ONLY OMNIS ADMINISTRATOR CAN SPECIFY FILE NAME IN COMMAND '(&00)'
Meaning
The OMNIS administrator can access BS2000 Files in command (&00).
OMS0181
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0181 COMMAND '(&00)' NOT PERMITTED DUE TO 'SECURITY LEVEL<>LOW'
Meaning
By defining SECURITY LEVEL=MEDIUM or =HIGH, the OMNIS administrator has
prohibited command '(&00)'.
OMS0182
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0182 COMMAND '(&00)' RESTRICTED TO OMNIS ADMINISTRATOR DUE TO 'SECURITY LEVEL=MEDIUM'
OMS0183
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0183 LATEST MESSAGE HAS NOT YET BEEN SENT TO SVP. MESSAGE NOT FORWARDED TO PARTNER '(&00)'
Meaning
Before sending the message, OMNIS issues a call to the SVP. The message
is
only sent when the SVP has acknowledged receipt of the call. Messages
entered at the terminal between the call and the receipt of the
acknowledgment cannot be sent to the SVP partner (&00).
Response
Enter the message again.
OMS0184
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0184 WHEN 'SECURITY LEVEL=MEDIUM' FILE NAME CANNOT BE SPECIFIED IN COMMAND '(&00)' WHEN OMNIS RUNNING UNDER USER ID 'TSOS'
Meaning
Reason: data protection.
OMS0185
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0185 OMNIS HAS RECEIVED A NEGATIVE PRINT ACKNOWLEDGMENT FROM LOCAL PRINTER
OMS0186
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0186 PARTNER '(&00)' MAY NOT BE OCCUPIED
Meaning
For data protection reasons the OCCUPY command is not permitted for
partner (&00).
OMS0187
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0187 ERROR IN PROTOCOL WITH PARTNER '(&00)' ((&01)/(&02)); CONNECTION CLEARED. DUMP TAKEN
Meaning
The partner (&01)/(&02) with PAC=(&00) has violated the protocol
defined
with OMNIS. OMNIS has therefore taken a user dump and cleared down the
connection.
Response
Contact the systems support staff.
OMS0188
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0188 APPLICATION ((&00)/(&01)) AS A TERMINAL HAS VIOLATED PROTOCOL SPECIFIED WITH OMNIS. CONNECTION CLEARED. DUMP TAKEN
Meaning
The application (&00)/(&01), which has been declared as a terminal with
PROTOCOL=VTSU, has violated the protocol.
Response
Check if the application obeys the protocol defined with OMNIS.
OMS0189
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0189 OPERAND '(&00)' NOT PERMITTED WHEN 'SECURITY LEVEL=HIGH'
OMS0190
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0190 WHEN 'SECURITY LEVEL=HIGH' 'APASS' MAY NOT BE SPECIFIED. COMMAND REJECTED
Meaning
When SECURITY LEVEL=HIGH OMNIS may be administered only from BS2000
consoles and APASS may not be specified.
OMS0191
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0191 CONNECTIONS TO PARTNERS FOR SESSIONS WITHOUT USERNAME WILL BE CLOSED EVEN IF HOLD=YES/AUTO SET.
Meaning
When disconnecting a terminal, OMNIS checks wheather HOLD=YES/AUTO pro-
cessing applies. If SECURITY-LEVEL <> LOW and no USERNAME is assigned,
the connections to the partners will be closed, too.
OMS0192
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0192 F3 KEY NOT ALLOWED FOR SKP PARTNER
Meaning
When pressing F3 key the message is sent to the SVP. The SVP returns a
full screen message. This full screen message is not supported by OMNIS.
OMS0193
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0193 SPECFICATION OF PAC AND PID IS AMBIGUOUS IN THE 'INF PARTNER' COMMAND
Meaning
When entering the 'INF PARTNER' command you may specify the partner
either by PAC or by PID.
Response
Correct the command and try again.
OMS0194
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0194 OMNIS HAS RECEIVED AN INVALID PROTOCOL VERSION FROM UCON PARTNER (&00)
Meaning
OMNIS has received a message with unknown UCON protocol version from UCON
partner (&00). For further investigations a dump has been taken.
OMS0195
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0195 FROM UCON PARTNER (&00) AN INVALID IDENTIFICATION DIALOG HAS BEEN RECEIVED
Meaning
OMNIS has received an identifcation dialog from UCON partner (&00) which
is not defined between UCON and OMNIS.
OMS0196
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0196 OMNIS HAS RECEIVED A NEGATIVE PRINT ACKNOWLEDGEMENT FROM HARDCOPY UNIT '(&00) ((&01)/(&02))'
Meaning
From hardcopy unit '(&01)/(&02)' with address code (&00) a negative
ack-
nowledgement has been received, i.e. at least one message could not be
delivered. The reason may be a message containing an illegal control
character for this printer.
Response
Reestablish the connection to the hardcopy unit with the RESTART command.
OMS0197
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0197 THE MESSAGE CANNOT BE SENT TO THE HARDCOPY UNIT '(&00) ((&01)/(&02))' BECAUSE OF INVALID CONTROL CHARACTERS
Meaning
OMNIS cannot prepare the message to be sent to the hardcopy unit
'(&01)/(&02)' with adresscode (&00). The message has not been sent
to the printer.
OMS0198
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0198 NO PARTNER OF GROUP '(&00)' ACTIVE
Meaning
As there is no active partner in group '(&00)', the input was ignored.
OMS0199
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0199 OMNIS ENDED BECAUSE OF BCLOSE COMMAND OR DCM SHUTDOWN
Meaning
As OMNIS will be ended by the BCLOSE COMMAND or
as the DCM will be ended, OMNIS will also be ended.
OMS0200
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0200 AS THE MESSAGE IS, INCLUDING A PROTOCOL, TOO LONG, IT WILL BE IGNORED
Meaning
OMNIS tries to augment a message with a protocol element; the resulting
message is too long to be sent to the partner.
Response
Set a higher value for the message length in the start parameters.
OMS0201
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0201 OPERAND PROTOCOL MAY ONLY BE SPECIFIED WITH PARTNER TYPE=DCAM.
Meaning
The operand protocol may only be specified with partner type=DCAM.
The operand has been ignored.
OMS0202
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0202 THE COMMAND '(&00)' MUST NOT BE ENTERED WHEN SECURITY-LEVEL=HIGH.
Meaning
By defining SECURITY LEVEL=HIGH, the OMNIS administrator has
prohibited command "HELP bs2000-message-number".
OMS0203
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0203 THE MESSAGE HAS BEEN TOO LONG AND THEREFORE HAS BEEN TRUNCATED.
OMS0204
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0204 THE PARAMETER (&00) IS NOT SUPPORTED BY THE SLAVE OMNIS; PAC=(&01) PTNNAME=(&02), PRONAME=(&03)
Meaning
The specified parameter (&00) is not supported by the slave-OMNIS
and therefore has been ignored for partner ((&02)/(&03)) with
pac=(&01).
OMS0205
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0205 CONFIGURATION CHANGED SUCCESSFULLY
OMS0206
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0206 CONFIGURATION COULDN'T BE CHANGED
OMS0207
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0207 ACCESS TO FILE WITH FILENAME '(&00)' DENIED, AS THE FILE IS MIGRATED BY HSMS.
Meaning
When a file is migrated by HSMS, no access is allowed to that file,
because the
access would result in a long waiting time for the user.
Response
Import file to disk and retry command again.
OMS0208
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0208 FULL-SCREEN MESSAGES ARE NOT SUPPORTED BY SKP2
Meaning
SKP2 has sent a full screen message to OMNIS, which is not supported by
OMNIS.
OMS0209
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0209 OMNIS CANNOT REQUEST A NEW REFERENCE FOR THE (&00) ENTRY ((&01)/(&02))
OMS0210
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0210 MUX-CONNECTION '((&00)/(&01)) (&02)' NOT ACTIVE. COMMAND REJECTED
Meaning
The MUX connection (&00)/(&01) with MID (&02) is not active.
Enter the correct MID or PTNNAME/PRONAME.
OMS0211
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0211 WARNING: CLASS-OPERAND WILL BE RESET
OMS0212
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0212 PARTNER (&00) HAS ANNOUNCED ASYNCHRONOUS MESSAGE(S)
Meaning
Partner (&00) has announced asynchronous message(s). If you change to
that partner, you will see the message.
OMS0214
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0214 MESSAGE FROM PARTNER (&00) RECEIVED
OMS0215
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0215 PARTNER (&00) EXPECTS INPUT
OMS0216
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0216 OMNIS HAS RECEIVED FROM UTM APPLICATION ((&00)/(&01)) AN INVALID PROTOCOL ELEMENT (&02).
Meaning
OMNIS has received from UTM application ((&00)/(&01)) a message with an
invalid operation code. The invalid code is (&02). The message
has been discarded.
Response
Check if the UTM version is supported by OMNIS.
OMS0217
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0217 NO "(&00)" ENTRY CORRESPONDING TO SPECIFIED OPERANDS OR TO YOUR AUTHORIZATION FOUND
OMS0218
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0218 INVALID SESSION REFERENCE RECEIVED BY OMNIS FROM REMOTE OMNIS ((&00)/(&01)). DIAGNOSTIC INFO=(&02). MESSAGE HAS BEEN IGNORED
Meaning
A message has been sent to OMNIS by remote OMNIS ((&00)/(&01)) with an
invalid session reference. OMNIS could not assign a partner to the
message.
(&02) supports further diagnosis.
OMS0219
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0219 SPOOLOUT ACCEPTED
OMS0220
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0220 SPOOLOUT NOT ACCEPTED. IN '(&00)'-MACRO OCCURED '(&01)'-ERROR
Meaning
An error occurred during a (DMS, SPOOL) system call.
For the meaning of the error code, see the relevant BS2000 manual.
Response
Depends on the error code (&01)of the (&00) macro; if necessary,
contact the OMNIS or system administrator, because a generation
error is possible.
OMS0221
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0221 COMMAND NOT ALLOWED FOR A GROUP
Meaning
The command just entered must not be applied to a group.
OMS0222
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0222 AS THE K-KEY IS ALREADY ASSIGNED, IT WILL BE RESET (WARNING)
Meaning
The command just entered would result in an ambiguous
K-KEY; it will be reset therefore.
OMS0223
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0223 AS CONNECT=DECLARED AND THE CONFIGURATION FILE CANNOT BE FOUND, OMNIS WILL BE TERMINATED
Meaning
When CONNECT=DECLARE there is no use in starting OMNIS
without configuration file.
OMS0224
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0224 CONNECTION TO PARTNER '(&00) ((&01)/(&02))' NO LONGER AVAILABLE
Meaning
The connection to the partner (&01)/(&02) with the address code
(&00) has been broken because the MUX connection has been lost.
The partner will not be available until the MUX connection has
been reestablished.
Response
Restart the UTM application.
OMS0225
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0225 CONNECTION TO PARTNER '(&00)' IN HOLD
Meaning
The connection to the partner (&00) is in hold.
Open connection is not allowed.
Response
Restart the UTM application.
OMS0226
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0226 CONNECTION TO MUX-PARTNER '(&00)' NOW AVAILABLE
Meaning
The MUX-application has been started and the MUX partner (&00)
is now available.
OMS0227
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0227 LISTENING FUNCTION FOR THE TERMINAL ACTIVATED
OMS0228
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0228 LISTENING FUNCTION FOR THE TERMINAL IS ALREADY ACTIV
OMS0229
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0229 LISTENING FUNCTION FOR THE TERMINAL WILL BE ONLY ACTIVATED WITH THE OPTION COMAND
OMS0230
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0230 TERMINAL-TYP DOES NOT MATCH
OMS0231
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0231 HARDCOPY UNIT '(&00) ((&01)/(&02))' NOT UNIQUE
Meaning
The printer (&01)/(&02) with address code (&00) is not unique.
Declaration ignored.
OMS0232
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0232 HARDCOPY UNIT '(&00)' NO LONGER AVAILABLE. 'CONFUPDATE' IN PROCESS
Meaning
To assign the printer (&00) is not possible. The HCY-declaration
is in delete because a CONFUPDATE is in process.
OMS0233
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0233 MUX-CONNECTION '((&00)/(&01))' NO LONGER AVAILABLE. 'CONFUPDATE' IN PROCESSING
Meaning
The connection to MUX-application (&00)/(&01) no longer
available. The MUX-declaration is in delete because a
CONFUPDATE is in process.
OMS0234
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0234 OMNIS-OMNIS CONNECTION '(&00) ((&01)/(&02))' NOT UNIQUE
Meaning
The OMNIS-OMNIS connection (&01)/(&02) with address code (&00)
is not unique. Declaration ignored.
OMS0235
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0235 OMNIS-OMNIS CONNECTION '(&00) ((&00)/(&01))' NO LONGER AVAILABLE. 'CONFUPDATE' IN PROCESSING
Meaning
The connection to OMNIS (&00)/(&01) no longer
available. The OMNIS-declaration is in delete because a
CONFUPDATE is in process.
OMS0236
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0236 YOU ARE NOT ALLOWED TO SEND THE ANSWER TO PARTNER '(&00)'.
Meaning
When REPLY=RESTRICTED is defined you may only answer those
questions, which have been received from the partner.
OMS0237
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0237 LISTENING FUNCTION FOR THE TERMINAL DEACTIVATED
OMS0238
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0238 THE SUPPRESSION OF ANSWERS IS DEACTIVATED BECAUSE OF MEMORY SHORTAGE NO ENTRIES CAN BE WRITTEN ANY LONGER
Meaning
There are too many unanswered questions in the pool and therefore
there is a buffer overflow
Response
Answer unanswered questions via OMNIS
OMS0239
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0239 OMNIS-OMNIS-CONNECTION '((&00)/(&01)) (&02)' (OAC='(&03)') NOT ACTIVE. COMMAND NOT EXECUTED
Meaning
The OMNIS-OMNIS connection (&00)/(&01) with MID (&02) is not
active. Enter the correct OID or OAC
OMS0240
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0240 RESTART NOT ALLOWED FOR ENTRY '(&00)' AS IT MUST NOT BE USED ANY LONGER
Meaning
You must not enter RESTART for entry (&00) as it has been
deleted from the configuration file.
OMS0241
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0241 '(&00)' COMMAND WITH STARTUP-DATEI='(&01)' NOT ALLOWED
OMS0242
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0242 INVALID SESSION REFERENCE RECEIVED BY OMNIS. MESSAGE HAS BEEN IGNORED
OMS0243
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0243 OMNIS CANNOT CREATE A SESSIONREFERENCE-TABLE.
OMS0244
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0244 NO MORE INPUT MESSAGE.
OMS0245
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0245 TRACE STARTED '(&00)'.
OMS0246
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0246 TRACE ENDED '(&00)'.
OMS0247
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0247 SECURE INPUT.
OMS0248
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0248 WARNING: OLD VERSION OF CONFIGURATION FILE PROCESSED
Meaning
OMNIS got a configuration file of an older version
and converted it only for the current start of OMNIS.
Response
Create configuration file for performance reason
with current version of OMNISKD.
OMS0249
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0249 OMNIS DUMP BEING PROCESSED. PLEASE HOLD ON
Meaning
This informs the user that OMNIS dump output has
been initiated.
OMS0250
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0250 OMNIS DUMP WRITTEN
Meaning
This informs the user that OMNIS dump output has
been finished.
OMS0251
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0251 MUX CONNECTION TO '((&00)/(&01)),PAC=(&02)' CANCELLED BY OMNIS ADMINISTRATOR
Meaning
The MUX connection (&00)/(&01) with PAC=(&02) has been cancelled
by the OMNIS administrator by means of the /CANCEL command.
Response
Ask OMNIS administrator why connection was cancelled.
OMS0252
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0252 CONNECTION TO OMNIS '(&00) ((&01)/(&02))' CANCELLED BY OMNIS ADMINISTRATOR
Meaning
The connection to OMNIS (&01)/(&02) with the address code (&00)
has been cancelled by the OMNIS-administrator by means of the
/CANCEL command.
Response
Ask OMNIS administrator why connection was cancelled.
OMS0253
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0253 PROZESSOR NAME *ANY MAY ONLY BE SPECIFIED FOR PARTNER TYPE DCAM OR TIAM
Meaning
Load distribution with *ANY is only possible for partner of
type DCAM or TIAM.
Response
Correct the command and try again.
OMS0254
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0254 PROZESSOR NAME *ANY MUST NOT BE SPECIFIED FOR PARTNER WITH ROUTE=INDIRECT
Meaning
Load distribution with *ANY is not possible for partner with
route INDIRECT.
Response
Correct the command and try again.
OMS0255
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0255 CONNECTION TO FIRST PROCESSOR CHOICE ((&00)/(&01)) OF LOAD DISTRIBUTION DENIED, CONNECTION WILL BE ESTABLISHED WITH THE SECOND CHOICE ((&00)/(&02))
Meaning
The connection to the optimal processor choice could not be established
successfully, the connection to the second best processor will
be established.
Response
Contact HIPLEX administrator, possible HIPLEX configuration problem.
OMS0256
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0256 OMNIS MESSAGEEXIT MAY BE DEFINED IN EXIT GROUP ONLY ALONE
Meaning
The OMNIS messageexit may be defined in the EXIT group only alone,
no further modules are permitted.
OMS0257
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0257 OMNIS MESSAGEEXIT ALREADY DECLARED
Meaning
The OMNIS messageexit has been already declared.
OMS0258
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0258 OMNIS MESSAGEEXIT CANNOT BE ASSIGNED
Meaning
To assign the OMNIS messageexit ist not possible, it is
already active by creating with the command EXIT.
OMS0259
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0259 PROCESSOR NAME *ANY MAY ONLY BE SPECIFIED SINCE OSD V4.0
Meaning
Load distribution with *ANY is only possible since OSD V4.0
OMS0260
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0260 ERROR AT PROCESSOR SELECTION FOR *ANY (RC=(&00))
Meaning
Error during processor selection for load distribution
by JMS (RC=(&00))
OMS0261
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0261 PAGING FILE FULL, FILE WILL BE LOGICALLY RESET
Meaning
Previous stored data in the paging file will not be processed
OMS0262
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0262 CODED-CHARACTER-SET ((&00)) NOT SUPPORTED (VTSUCB-ERROR '(&01)', PAC=(&02), PTN=(&03), PRO=(&04))
Meaning
CODED-CHARACTER-SET is not supported by the OMNIS-host
Response
Back up to system mode and install CODED-CHARACTER-SET.
OMS0263
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0263 CONFIGURATION VARIABLE ((&00)) CANNOT BE SUBSTITUTED
Meaning
A configuration variable has no current value assigned
OMS0264
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0264 OVERFLOW AT SUBSTITUTION OF CONFIGURATION VARIABLE ((&00)) BY ACTUAL VALUE ((&01))
Meaning
No substitution of the variable is made
OMS0265
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0265 PAGING FILE PHYSICALLY RESET ((&00))
Meaning
Paging file has been erased and newly created
OMS0266
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0266 FOR 'ACTION=CHANGE' THE OPERAND 'NAME' MUST NOT BE SET
Meaning
The name of the new logging file will be generated automatically
OMS0267
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0267 FOR 'ACTION=COPY' THE OPERAND 'DELETE=YES' MUST NOT BE SET
Meaning
The logging file may be deleted only when the logging file is changed
OMS0268
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0268 OPERAND 'NAME' MUST BE SET
Meaning
Generated name is too long, a name for the copy must be given.
Response
Correct the command and try again.
OMS0269
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0269 SPECIFIED TIME ALREADY OVER
Meaning
Asynchronous change of logging file cannot be set,
REPEAT has been reset.
Response
Correct the command and try again.
OMS0270
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0270 INVALID DATE
Meaning
Specified day extends the end of the month,
REPEAT has been reset.
Response
Correct the command and try again.
OMS0271
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0271 FOR 'SIZELIMIT' THE OPERAND 'ACTION=COPY' MUST NOT BE SET
Meaning
For SIZELIMIT the changing of the logging file must be set
OMS0272
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0272 OPERAND 'ACTION=COPY' NOT COMPATIBLE WITH SIZELIMIT SETTING
Meaning
SIZELIMIT is set by former CHANGELOG command
OMS0273
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0273 OPERAND 'ACTION=COPY' NOT COMPATIBLE WITH DELETE SETTING
Meaning
'DELETE=YES' is set by former CHANGELOG command
OMS0274
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0274 OPERAND 'SIZELIMIT' NOT COMPATIBLE WITH ACTION SETTING
Meaning
'ACTION=COPY' is set by former CHANGELOG command
OMS0275
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0275 OPERAND 'DELETE=YES' NOT COMPATIBLE WITH ACTION SETTING
Meaning
'ACTION=COPY' is set by former CHANGELOG command
OMS0276
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0276 KEY SPECIFIED '(&01)' IN 'OPNCON' COMMAND OF PARTNER '(&00)' LOCKED IN TEXT FILE; KDCSIGN/LOGON SEQUENCE NOT PROCESSED
Meaning
During write back of the KDCSIGN/LOGON sequence into the text file
OMNISMD has locked the key.
Response
Proceed without KDCSIGN/LOGON sequence or KDCOFF/LOGOFF and try again.
OMS0500
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0500 OMNISFC VERSION "(&00)" STARTED
Meaning
The current version of OMNISFC is (&00).
OMS0501
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0501 FILE (&00) : GENERATED BY OMNIS(-MENU) (&01)
Meaning
The File (&00) was generated by generation tool version (&01).
Response
none.
OMS0502
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0502 OMNISFC TERMINATED NORMALLY
OMS0503
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0503 OMNISFC TERMINATED ABNORMALLY
OMS0504
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0504 (&00)-ERROR (&01) AT ADDRESS (&02). INFO = (&03). KEY = (&04)
Meaning
An error occurred during a (DVS, LNK) call to the operating system.
(&00) is the name of the call, (&01) the error code from R15 and
(&02) the address of the call. (&03) supplies further information about
the call in question (file, library member). (&04) supplies the key of
the record.
Response
For the meaning of the error code, see the relevant BS2000 manual.
OMS0505
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0505 INCOMPATIBLE FORMAT IN FILE (&00)
Response
Maybe the file (&00) was not generated by means of OMNISKD.
OMS0506
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0506 (&00) RECORDS PROCESSED IN FILE (&01)
Meaning
(&00) records were processed during the editing of file (&01).
OMS0507
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0507 UNEXPECTED END OF FILE. OMNISFC RUN ABORTED
OMS0508
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0508 (&00)-ERROR IN FUNCTION (&01); FILE = (&02); ERROR CODE=(&03)
Meaning
An error occurred during a (DVS, LNK) call to the operating system.
(&00) is the name of the call, (&03) the error code and
(&01) the function of the call. (&02) supplies further information
about the call in question (file, library member).
Response
For the meaning of the error code, see the relevant BS2000 manual.
OMS0509
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0509 UNKNOWN ZVT-TYP: (&00)
OMS0510
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0510 INCOMPATIBLE ENTRY; FILE = (&00); KEY = (&01)
Meaning
A table entry with an incompatible version (< V2.0) was read.
Response
Check your configuration files.
OMS0600
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0600 PLEASE ENTER COMMAND OR 'HELP'
OMS0601
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0601 '(&00)' ERROR '(&01)' AT ADDRESS '(&02)'
Meaning
An error occurred in an (EXEC, DCAM, DMS) operating system call.
For the meaning of the error code, see the relevant BS2000 manuals.
(&00): name of call
(&01): error code from R15
(&02): address of call.
Response
Different actions are required depending on the error code; if necessary,
contact the OMNIS or system administrator.
OMS0602
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0602 SYNTAX ERROR. COMMAND NOT EXECUTED
Response
Correct the command.
OMS0603
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0603 OMNISLC VERSION '(&00)' STARTED
OMS0604
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0604 INPUT FILE NAME MISSING. '(&00)' ASSUMED
Meaning
Editing was started by means of RUN without an input file having been
assigned. OMNIS assumes the default name <(&00)>.
OMS0605
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0605 OUTPUT FILE NAME MISSING. '(&00)' ASSUMED
Meaning
Editing was started by means of RUN without an output file having
been assigned with the OUTPUT command. OMNIS assumes the default
output file <(&00)>.<edit>.
OMS0606
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0606 'OMNISLC' TERMINATED WITHOUT ERRORS
OMS0607
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0607 (&00) RECORDS WRITTEN TO OUTPUT FILE '(&01)'. CONVERSION TERMINATED
OMS0608
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0608 UNEXPECTED END OF FILE. OMNISLC RUN ABORTED
Meaning
Upon reading the next command, EOF was detected.
OMNISLC has terminated.
OMS0609
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0609 INPUT FILE NOT AN OMNIS LOGGING FILE
OMS0610
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0610 LOGGING FILE NOT SAME OMNIS VERSION AS 'OMNISLC'
Meaning
The OMNISLC, used to edit the logging file, is of a different OMNIS
version.
Response
Use current version of OMNISLC for the editing.
OMS0611
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0611 LOGGING FILE IS NOT A PAM FILE
Meaning
An OMNIS logging file must always have FCBTYPE=PAM.
Response
Enter file name of an OMNIS logging file as input file
OMS0612
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0612 LOGGING FILE EMPTY
Meaning
There are no logging records in the OMNIS logging file specified.
Response
Repeat command with correct OMNIS logging file name.
OMS0613
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0613 OMNISLC CANNOT CONVERT THE FORMAT TO A LINE MESSAGE. THE LOGGING RECORD HAS NOT BEEN PROCESSED
Meaning
OMNIS converts all format messages to printable line messages. As an
error
has occured, the record cannot be converted.
OMS0614
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0614 GENERATED FILENAME '(&00)' TOO LONG
Meaning
Editing was started by means of RUN without an output file having
been assigned with the OUTPUT command. Because of the length of the name
of the input file the generated file name is too long.
Response
Enter filename of output file.
OMS0700
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0700 '(&00)' ERROR '(&01)' AT ADDRESS '(&02)'; INFO = (&03) KEY = (&04)
Meaning
An error occurred during an (EXEC, DMS) operating system call.
(&00): name of call
(&01): error code from R15
(&02): address of call.
(&03): supplies further information about the call in question
(file, library member).
(&04): supplies the key of the record.
Response
Depends on the error code. For the meaning of the error code output with
the message, see the relevant BS2000 manual; if necessary, contact the
system administrator.
OMS0701
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0701 SYNTAX ERROR ((&00)). STATEMENT REJECTED
Response
Correct the input file and repeat OMNISKD.
OMS0702
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0702 TOO LONG INPUT RECORD REJECTED
Response
Correct the input file and repeat OMNISKD.
OMS0703
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0703 'DECLARE-OMNIS' ILLEGAL AT THIS POINT
Meaning
The OMNIS declaration must be given before all other declarations.
Response
Correct the order of the declarations.
OMS0704
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0704 OMNIS DECLARED MORE THAN ONCE IN PROCESSOR '(&00)'. SECOND DECLARATION REJECTED
Meaning
An attempt was made to declare two OMNIS-OMNIS connections to the
same processor.
Response
Correct the input file and repeat OMNISKD.
OMS0705
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0705 TERMINAL ((&00)/(&01)) DECLARED MORE THAN ONCE. SECOND DECLARATION REJECTED
Meaning
A terminal with the name (&00)/(&01) has already been declared.
Response
Correct the input file and repeat OMNISKD.
OMS0706
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0706 'DECLARE-PARTNER' ILLEGAL AT THIS POINT
Meaning
A partner was declared before a terminal had been declared.
Response
Correct the input file and repeat OMNISKD.
OMS0707
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0707 TRANSACTION CODE '(&00)' ALREADY DECLARED
Meaning
The address codes of all partners and groups must be unique.
The rule was violated for address code (&00).
Response
Correct the input file and repeat OMNISKD.
OMS0708
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0708 OMNIS IN PROCESSOR '(&00)' NOT DECLARED
Meaning
An OMNIS-OMNIS connection must be declared before an indirect
connection can be established to processor (&00). This rule was
violated.
Response
Correct the input file, i.e. declare OMNIS-OMNIS connection
or change indirect connection to a direct one, and repeat OMNISKD.
OMS0709
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0709 OMNISKD COULD NOT OPEN CONFIGURATION FILE
Meaning
Possible reasons:
- the assignment with the SET-FILE-LINK command had been forgotten
- the file is write-protected
- the file is not shareable or locked.
The DMS error code was given in the preceding message OMS0700.
Response
Make the configuration file accessible and repeat OMNISKD.
OMS0710
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0710 RDATA ERROR ON CONFIGURATION INPUT FILE
Meaning
An error occurred on reading a command from SYSDTA. The error code
was given in the preceding message OMS0700.
Response
Depends on the RDATA error code.
OMS0711
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0711 INTERNAL ERROR AT ADDRESS '(&00)'. OMNISKD GENERATED DUMP
Meaning
A data structure inconsistency was detected during an internal
validity check (programming error).
Response
Send the diagnostic information (dump, SYSOUT log, input file)
to the system administrator.
OMS0712
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0712 WRITE ERROR ON CONFIGURATION FILE
Meaning
An error occurred when writing a record to the configuration file.
The error code has been given in the preceding message OMS0700.
Response
Depends on the PUT error code.
OMS0713
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0713 OMNISKD VERSION "(&00)" STARTED
Meaning
(&00): the current version of OMNISKD.
OMS0714
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0714 CONFIGURATION FILE(S) GENERATED WITHOUT ERRORS
Meaning
The configuration file(s) can be used as input for
OMNIS-(MENU).
OMS0715
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0715 CONFIGURATION FILE(S) GENERATED WITH ERRORS
Meaning
This configuration file(s) must not be used as input for OMNIS-(MENU).
Response
Check the OMNISKD log for error messages; if necessary,
correct the input file and repeat OMNISKD.
OMS0716
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0716 PAC '(&00)' IS A GROUP PAC. ENTRY IGNORED
Meaning
Only partners can be group members, not other groups, entry will be
ignored.
Response
Correct the input file and repeat OMNISKD.
OMS0717
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0717 PARTNER '(&00)' ALREADY MEMBER OF GROUP '(&01)'
Meaning
A partner can only be declared once as a group member.
An attempt was made to assign partner (&00) to group (&01) more than
once.
Response
Correct the input file and repeat OMNISKD.
OMS0718
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0718 DECLARATION OF 'OAC=(&00)' NOT UNIQUE. SECOND DECLARATION IGNORED
Meaning
All OMNIS runs must have unique address codes. An OMNIS with the address
code (&00) has already been declared.
Response
Correct the input file and repeat OMNISKD.
OMS0719
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0719 CONFIGURATION FILE COULD NOT BE GENERATED
Response
Check OMNISKD log for error messages, correct the errors
and repeat OMNISKD.
OMS0720
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0720 'DECLARE-HARDCOPY' ILLEGAL AT THIS POINT
Meaning
All printer declarations must precede the declaration of
the first terminal.
Response
Correct the order of the commands.
OMS0721
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0721 DECLARATION OF 'HAC=(&00)' NOT UNIQUE. SECOND DECLARATION IGNORED
Meaning
All printers must have unique address codes. A printer with the
address code (&00) has already been declared.
OMS0722
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0722 DECLARATION OF HARDCOPY UNIT ((&00)/(&01)) NOT UNIQUE. SECOND DECLARATION IGNORED
Meaning
All printers must have unique network addresses. A printer with the
network address (&00)/(&01) has already been declared.
Response
Remove declaration or correct network address.
OMS0723
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0723 A HARDCOPY UNIT CANNOT BE ITS OWN ALTERNATE DEVICE
Response
Correct the INOP operand.
OMS0724
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0724 ALTERNATE HARDCOPY UNIT '(&00)' NOT DECLARED
Response
Declare printer or specify another alternate hardcopy unit.
OMS0725
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0725 'DECLARE-EXIT' INVALID AT THIS POINT
Meaning
All exit group declarations must precede the declaration
of the first terminal.
Response
Correct the order of the commands.
OMS0726
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0726 DECLARATION OF EAC '(&00)' NOT UNIQUE. SECOND DECLARATION IGNORED
Meaning
All exit groups must have unique address codes. An exit group
with address code (&00) has already been declared.
Response
Remove command or use another exit address code.
OMS0727
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0727 MODULE '(&00)' OCCURS MORE THAN ONCE IN LIST OF MODULES
Meaning
A module may only appear once in the list of modules making up
an exit group.
Response
Correct the command.
OMS0728
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0728 DECLARATION OF K KEY NOT UNIQUE
Meaning
The K key defined is already being used for something else
(KPAC for another UTM partner, CALL-KEY or BREAK-KEY).
Response
Correct the command; if necessary, use a different K key.
OMS0729
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0729 'KPAC' ONLY PERMITTED WITH 'TYP=UTM'
Meaning
The KPAC operand can only be specified for UTM partners.
Response
Correct the command.
OMS0730
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0730 TOO MANY OMNIS-OMNIS CONNECTIONS DECLARED
Meaning
A maximum of 256 OMNIS-OMNIS connections are permitted in
the configuration file.
Response
Correct the input file.
OMS0731
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0731 TOO MANY PARTNERS DECLARED FOR THIS TERMINAL
Meaning
A maximum number of 256 partners are permitted per terminal.
Response
Correct the input file.
OMS0732
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0732 TOO MANY TERMINALS DECLARED
Meaning
A maximum of 32767 terminals may be declared.
Response
Correct the input file.
OMS0733
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0733 TOO MANY HARDCOPY UNITS DECLARED
Meaning
A maximum of 256 hardcopy units may be declared.
Response
Correct the input file.
OMS0734
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0734 TOO MANY EXIT GROUPS DECLARED
Meaning
A maximum of 256 exit groups may be declared.
Response
Correct the input file.
OMS0735
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0735 TOO MANY MUX CONNECTIONS DECLARED
Meaning
A maximum of 512 MUX connections may be declared.
Response
Correct the input file.
OMS0736
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0736 DECLARE GROUP ILLEGAL AT THIS POINT
Meaning
A group was declared before a terminal had been declared.
Response
Correct the input file and repeat OMNISKD.
OMS0737
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0737 DECLARATION OF MUX PARTNER ((&00)/(&01)) NOT UNIQUE. SECOND DECLARATION IGNORED
Meaning
All MUX partners must have unique partner/processor names.
A MUX partner with the partner/processor name (&00)/(&01) has already
been
declared.
Response
Remove declaration or correct partner/processor name.
OMS0738
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0738 PARTNER NAME AND/OR PROCESSOR NAME MISSING
Meaning
A processor name and/or partner name has to be specified in this
declaration.
Response
Correct the input file.
OMS0739
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0739 'SYSCODE=BINARY' ONLY PERMITTED FOR PARTNER OF TYPE 'DCAM'
Response
Correct the input file.
OMS0740
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0740 'PAC=(&00)' ALREADY IN GROUP. SECOND ENTRY IGNORED
Meaning
PAC (&00) can only be added once to the group.
OMS0741
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0741 GROUP ADDRESS CODE '(&00)' NOT ADDED TO GROUP '(&01)'
Meaning
The members of a group must be partners; other groups are not permitted.
OMS0742
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0742 EXIT ROUTINE '(&00)' NOT DECLARED; ENTER USING 'EXIT' COMMAND
Meaning
An exit routine must be declared before it can be assigned to a partner
or terminal.
Response
Correct the input file.
OMS0743
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0743 HARDCOPY UNIT '(&00)' NOT DECLARED; ENTER USING 'HCOPY' COMMAND
Meaning
A hardcopy unit must be declared before it can be assigned to a partner
or
terminal.
Response
Correct the input file.
OMS0744
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0744 MUX PARTNER '(&00)' NOT DECLARED
Meaning
Before using a multiplex connection, the connection must be
declared with DECLARE-MUX.
Response
Correct the input file.
OMS0745
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0745 OPERAND 'HOLD=AUTO' NOT PERMITTED FOR PARTNER '(&00)'
Meaning
The HOLD=AUTO operand can only be specified by means of DECLARE-TERMINAL.
OMS0746
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0746 'HOLD=YES' AND NO 'OPASS' SPECIFIED
Meaning
If HOLD=YES, you must also specify an OPASS.
Response
Specify OPASS and repeat OMNISKD.
OMS0747
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0747 'DECLARE-MUX' ILLEGAL AT THIS POINT
Meaning
All multiplex declarations must precede the declaration of
the first terminal.
Response
Correct the order of the commands.
OMS0748
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0748 'ROUTE=MUX' ONLY PERMITTED FOR PARTNERS WITH 'TYP=UTM'
OMS0749
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0749 PROTOCOL FOR A TERMINAL DECLARED WITH 'TERMTYP<>APPL'. OPERAND HAS BEEN IGNORED.
OMS0750
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0750 THE OPERAND PROTOCOL MUST ONLY BE SPECIFIED WITH PARTNER TYP=DCAM.
Meaning
The operand PROTOCOL must only be specified with partner TYP=DCAM.
The operand has been ignored.
OMS0751
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0751 A PARAMETER IS MISSING IN THIS DECLARATION
OMS0752
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0752 WARNING: MENU (&00) NOT DEFINED FOR USER (&01)
Meaning
For the user name a menu must be entered in
the menu table.
OMS0753
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0753 WARNING: APPLICATION (&00) IN APPLICATION TABLE NOT DEFINED (USER=(&01))
Meaning
For each application in the menu there must be a corresponding record in
the application table.
OMS0754
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0754 INPUT OUT OF RANGE: OPERAND='(&00)'
Meaning
The input exceeds the permitted range. The command has not been
executed.
OMS0755
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0755 NO PAC DEFINED FOR APPLICATION
Meaning
Each application must have a partner address code.
OMS0756
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0756 NO K KEY DEFINED FOR P KEY
OMS0757
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0757 OMNIS COMMAND KEY IS AMBIGUOUS.
Meaning
The key is already defined.
OMS0758
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0758 INFO IN HEX AND LENGTH NOT EVEN. COMMAND NOT EXECUTED
Meaning
If the information is in hexadecimal notation, the length must be even.
OMS0759
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0759 INVALID HEX INFORMATION. COMMAND NOT EXECUTED
Meaning
If the information is in hexadecimal notation, the characters entered
must be
in the range 0 through F.
OMS0760
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0760 NO K KEY OR F KEY DEFINED FOR P KEY (PATH=((&00),(&01)))
Meaning
If you want a P key to be loaded, you need to specify an associated K key
or F key as well.
OMS0761
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0761 F OR K KEY IS AMBIGUOUS (PATH=((&00),(&01)))
Meaning
A F or K key can only be assigned once in each menu.
OMS0762
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0762 P KEY IS AMBIGUOUS (PATH=((&00),(&01)))
Meaning
A P key can only be assigned once in each menu.
OMS0763
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0763 PAC (&00) IN MENU (&01) IS AMBIGUOUS
Meaning
A PAC can only be assigned once in each menu.
OMS0764
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0764 INCOMPATIBLE FORMAT IN FILE (&00)
Meaning
Maybe the file (&00) was not generated with the current
version of OMNISKD.
OMS0765
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0765 BLOCK SIZE OF FILE '(&00)' IS DIFFERENT FROM CURRENT BLOCK SIZE
Meaning
The BLKSIZE operand specified in the catalog entry does not match
the current OMNIS-MENU BLOCK SIZE.
Response
Convert OMNIS-MENU tables (program OMNISFC)
OMS0766
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0766 INVALID COMMENT
OMS0767
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0767 OPERAND CPASS ONLY FOR UTM AND DCAM ALLOWED
OMS0768
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0768 OPERAND CMSG ONLY FOR UCON AND DCAM ALLOWED
OMS0770
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0770 ENTRY '(&00)' IN THE '(&01)' TABLE IS AMBIGUOUS
OMS0771
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0771 WRONG RECORD IN TAC TABLE (TAC='(&00)',NETWORK ADDRESS='(&01)'/'(&02)')
OMS0772
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0772 GROUP TAC '(&00)' TOO LONG
Meaning
The length of a group tac must not exceed 4.
OMS0773
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0773 OPERAND '(&00)' IS MISSING
OMS0774
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0774 IMPLICIT APPLICATION SWITCH KEY IS AMBIGUOUS.
Meaning
The key is already defined.
OMS0775
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0775 OPERAND INFO AND PRINCIPAL ARE NOT ALLOWED
OMS0789
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0789 DEFECTIVE CONFIGURATION FILE
Meaning
Possible reasons:
- the file is not a textfile.
- the file includes wrong declarations.
Wrong declaration is given in the status bar.
Response
Correct the configuration file and repeat.
OMS0790
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0790 DELETE NOT POSSIBLE
OMS0805
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0805 PROZESSOR NAME *ANY MAY ONLY BE SPECIFIED FOR PARTNER TYPE DCAM OR TIAM
Meaning
Load distribution with *ANY is only possible for partner of
type DCAM or TIAM.
Response
Correct the command and try again.
OMS0806
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0806 PROZESSOR NAME *ANY MUST NOT BE SPECIFIED FOR PARTNER WITH ROUTE=INDIRECT
Meaning
Load distribution with *ANY is not possible for partner with
route INDIRECT.
Response
Correct the command and try again.
OMS0807
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0807 OMNIS MESSAGEEXIT MAY BE DEFINED IN EXIT GROUP ONLY ALONE
Meaning
The OMNIS messageexit may be defined in the EXIT group only alone,
no further modules are permitted.
OMS0808
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0808 OMNIS MESSAGEEXIT ALREADY DECLARED
Meaning
The OMNIS messageexit has been already declared.
OMS0809
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0809 OMNIS MESSAGEEXIT CANNOT BE ASSIGNED
Meaning
To assign the OMNIS messageexit ist not possible, it is
already active by creating with the command EXIT.
OMS0810
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0810 RESET-KKEY IN DECLARE-PARAMETER MISSING
Meaning
For an OMNIS-MENU configuration a K Key must be defined
as a go-back and logout key.
OMS0811
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0811 OPERAND 'BERID' AND/OR 'PRONAME' MISSING
Meaning
An authorization and/or processor name has to be specified for a SKP
partner.
Response
Correct the input file.
OMS0812
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0812 OPERAND 'CMSG/LMSG' NOT PERMITTED FOR PARTNER 'TIAM/UTM'
Meaning
CMSG/LMSG may only be specified for partner of type DCAM or UCON.
Response
Correct the input file.
OMS0813
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0813 OPERAND 'CPASS/LPASS' NOT PERMITTED FOR PARTNER 'UCON' NOT EQUAL '$VMCONS'
Meaning
CPASS/LPASS may only be specified for partner of type UCON, if
PTNNAME=$VMCONS.
Response
Correct the input file.
OMS0814
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0814 OPERAND 'BERID' ONLY PERMITTED FOR PARTNER 'SKP'
Response
Correct the input file.
OMS0815
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0815 OPERAND 'CPASS/LPASS' NOT PERMITTED FOR PARTNER 'TIAM'
Response
Correct the input file.
OMS0816
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0816 PAC='(&00)' NOT DECLARED, BUT WILL BE ASSIGNED TO THE GROUP
Meaning
PAC is not declared yet, it will be assigned to the group.
Response
Check and eventually modify input file.
OMS0900
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0900 OMNIS HELP: OVERVIEW OF COMMANDS
Meaning
BREAK - Terminate connection HELP - Assistance
CALL - Expect input INF - Output information
CANCEL - Close connection MDEF - Define message table
CHANGELOG - Switch logging file MESSAGE - Send message to a terminal
CLSCON - Close connection OCCUPY - Take over connection
CMD - Execute BS2000 cmd. OPNCON - Open connection to partner
CONFUPDATE- configuration update OPTION - Define terminal-spec. attrs.
DUMP - Output dump PARAM - Define partner-spec. attrs.
END - Terminate OMNIS PRIORITY - Define scope of commands
EXIT - Admin. exit-routine RESTART - Restart connection
FILE - Process command file SET - Set operating parameters
GROUP - Define partner group TRACE - Switch on/off TRACE function
HALT - Sign off terminal TURN - Page-turn in logging file
HCOPY - Enter hardcopy unit
A more detailed description of a command can be obtained by
entering '@:HELP :command:'.
OMS0901
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0901 OMNIS HELP: BREAK
Meaning
BREAK causes OMNIS to discard all the messages from a partner.
It is effected by
* pressing the BREAK key defined with OPTION or SET
('OPTION BREAK-KEY=<number>', 'SET BREAK-KEY=<number>').
The BREAK affects the partner to which the last input was sent
(general addressing rule).
* entering a partner address code not followed by any text
('<pac>:', eg. 'A:'). The BREAK affects the specified partner.
In case of TIAM partners, the current program or procedure is
also interrupted. The current BREAK key can be queried with
'INF T,TID=OWN' or 'INF SYSTEM,TYPE=SETTINGS'.
OMS0902
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0902 OMNIS HELP: 'CLSCON' COMMAND
Meaning
The CLSCON command clears a connection to a partner or group of partners.
CLSCON :pac: ! :gac: ! *C ! *D ! *K ! *S ! *T ! *U ! *
< ,KILL >
One partner (:pac:), a group of partners (:gac:), all the partner of
a particular type (*C,*D,*K,*T,*S,*U) or all partners (*) can be
processed.
OMS0903
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0903 OMNIS HELP: 'END' COMMAND
Meaning
The END command terminates OMNIS. All existing connections to
terminals, partners and remote OMNIS runs are cleared down.
END APASS= :password: ! ? .
For security reasons a password must be specified, even if the
terminal has the attribute ADM=YES.
OMS0904
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0904 OMNIS HELP: 'FILE' COMMAND
Meaning
The FILE command initiates command processing of a command file.
The command file may contain any OMNIS commands or messages to partners.
The commands are processed sequentially as if entered at the terminal
FILE INPUT= :filename: ! :library(element):
< ,DISPLAY= NO ! YES >
< ,APASS= :password: ! ? >
When DISPLAY=YES, the commands read from the file are logged on the
terminal screen. In this case, specification of the administration
password APASS or the attribute ADM=YES (OPTION command) is required.
OMS0905
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0905 OMNIS HELP: 'GROUP' COMMAND
Meaning
The GROUP command serves to define an address code that allows
several partners to be accessed simultaneously.
GROUP : gac :
< ,ADD= :pac: ! (:pac: <,...>) >
< ,DEL= :pac: ! (:pac: <,...>) >
:gac: refers to the group to be (re)defined. The partners of the ADD
list are taken into the group which erases the DEL list.
Note: Partners to which no connection (as yet) exists, can also be taken
into the group.
OMS0906
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0906 OMNIS HELP: 'HALT' COMMAND
Meaning
The HALT command terminates interaction between a terminal and OMNIS.
HALT < HOLD= AUTO ! NO ! YES ! STD >
< ,OPASS= :password: ! ? >
Where HOLD=NO was specified, the connections to the partners are cleared.
Where HOLD=YES, they will remain unchanged. Where nothing was specified,
the value defined with OPTION or SET applies.
When HOLD=YES, a lock can be set with OPASS. This :password: then has to
be specified as a key in the OCCUPY command.
When HOLD=AUTO, all partners are available to the terminal again after
connection setup with OMNIS. The scope of the AUTO operand can be
adjusted by means of the PRIORITY command.
OMS0907
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0907 OMNIS HELP: 'HELP' COMMAND
Meaning
The HELP command displays more information about commands, messages,
return codes (the first four characters of :code: in the
message 'OMS0005 :macro: ERROR :code: AT :address:') and BS2000
messages.
HELP 'command overview'
HELP :bs2000-message: 'BS2000-Message'
HELP :commandname: 'command syntax'
HELP :messagenumber: 'explanation of message'
HELP OMY:dcamreturncode: 'explanation of DCAM return code'
The following metasyntax is used: names in uppercase letters must
remain as they stand; names in lowercase letters must be replaced by
current values; operands in angle brackets are optional; variables are
additionally enclosed in colons; comments are enclosed in quotes.
BS2000 messages must not be entered, when SECURITY-LEVEL=HIGH ist set.
OMS0908
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0908 OMNIS HELP: 'MDEF' COMMAND
Meaning
The MDEF command is used for message table administration.
MDEF :table-name:
< ,ACTION= CREATE ! DELETE ! MODIFY >
< ,BELL= YES ! NO >
< ,DISPLAY= YES ! NO >
< ,ID= :string: ! (:string:,:position:) >
< ,INSERT= (:string:,:insertnummer:) >
< ,MSG= :message-number: ! (:message-number:,:position:)>
< ,REPLY= :string: ! (:string:,...) >
< ,APASS= :password: ! ? >
CREATE creates message tables.
DELETE deletes message tables.
MODIFY is used to generate/update an entry.
MSG and ID/INSERT identify the message and its position.
position specifies the position of MSG or ID within the message text
REPLY defines one or more automatic replies.
DISPLAY=NO suppresses message output.
BELL=YES triggers an audible alarm.
OMS0909
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0909 OMNIS HELP: 'MESSAGE' COMMAND
Meaning
The MESSAGE command sends a message either to a particular terminal
or a group of terminals.
MESSAGE < TID= OWN ! :zahl: >
< ALL >
< ADM >
< < TERMINAL= > ( < :ptnname: > , < :proname:: > ) >
< ,USER = :user : >
,:message: ! ,INPUT= :filename: ! :library(element):
< ,APASS= :password: ! ?>
The :message: or contents of the file :filename: (here the administration
password or ADM=YES (see OPTION) is required) will be sent to the
terminal specified by :tid: or by (:ptnname:,:proname:),
to all terminals, or to all administrator consoles, or terminal with
username USER, as appropriate.
OMS0910
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0910 OMNIS HELP: 'OCCUPY' COMMAND
Meaning
The OCCUPY command enables a terminal to access partners or groups of a
different terminal.
OCCUPY PID= :pid: < ,NEWPAC= :pac: > !
PAC= :pac: < ,NEWPAC= :pac: >
< ,TID= OWN ! :tid: > !
< ,< TERMINAL= > ( < :ptnname: > , <:proname :> ) >
< ,USER= :user: >
< ,OPASS= :password: ! ? >
< ,APASS= :password: ! ? >
OCCUPY < TID= :tid: > !
< < TERMINAL= > ( < :ptnname: > , <:proname :> ) >
< ,USER= :user: >
< ,OPASS= :password: ! ? >
< ,APASS= :password: ! ? >
For the execution of the command, an OPASS is required (as the key) which
matches the OPASS of the object being taken over (the lock). Instead, the
APASS can be specified, i.e. the administrator can take over all partners
without knowing the locks.
OMS0911
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0911 OMNIS HELP: 'OPNCON' COMMAND
Meaning
The OPNCON command sets up a connection to a partner.
OPNCON :pac: ! :gac: ! *C ! *D ! *K ! *S ! *T ! *U ! *
< ,APPNAME= :appname: >
< ,BERID= :password ! ? >
< ,CLASS= OUTPUT ! SAVE ! DELETE >
< ,CODE= SYSCODE ! BINARY >
< ,COLOR= NO ! YELLOW ! RED ! WHITE ! GREEN !
BLUE ! CYAN ! MAGENTA >
< ,CPASS= :password: ! ? >
< ,EXIT= STD ! NO ! :eac: >
< ,HCOPY= STD ! NO ! YES ! :hac: >
< ,HOLD= STD ! NO ! YES ! >
< ,KPAC= :number ! NO >
< ,LCASE= YES ! NO >
< ,LINE25= STD ! NO ! YES ! OMNIS>
< ,LOGGING= STD ! NO ! YES >
< ,LPASS= :password: ! ? >
< ,MTAB= STD ! NO ! :name: >
< ,OPASS= :password: ! NONE ! ? >
< ,PAC= STD ! NO ! LINE ! PREFIX >
< ,PRONAME= :proname: ! *ANY >
< ,PROTOCOL= DSSIM ! OMNIS >
< ,PTNNAME= :ptnname: >
< ,ROUTE= DIRECT ! INDIRECT ! MUX >
< ,SAVE= STD ! SCREEN ! PKEY ! ALL ! NO >
< ,SNMP= NO ! YES >
< ,START-SEQUENCE= :number: >
< ,TYP= TIAM ! DCAM ! UTM ! UCON ! SKP ! SVP >
< ,CMSG= :connection-message: >
< ,LMSG= :connection-message: >
CMSG oder LMSG (if specified) must be the last operand of the command.
OMS0912
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0912 OMNIS HELP: 'OPTION' COMMAND
Meaning
The OPTION command defines terminal-specific parameters.
OPTION < ,ACK= STD ! NO ! YES ! LINE >
< ,ADM= YES ! NO ! >
< ,APASS= :password: ! ? >
< ,BREAK-KEY= STD ! NO ! :number: >
< ,CALL-INF= STD ! NO ! YES >
< ,CALL-KEY= STD ! NO ! :number: >
< ,COLOR= NO ! YELLOW ! RED ! WHITE ! GREEN !
BLUE ! CYAN ! MAGENTA >
< ,DISPLAY-MODE= STD ! SYSTEM ! MIXED ! OMNIS >
< ,EXCLUSIVE-PARTNER= STD ! NO ! YES >
< ,EXIT= STD ! NO ! :eac: !
< ,HCOPY= STD ! NO ! YES ! :hac: !
(DEV=:devname:,KEY=:number:,FORM=STD!:form:) >
< ,HOLD= STD ! NO ! YES ! AUTO >
< ,INPUT-LOGGING= STD ! REC ! SEND ! BOTH >
< ,INPUT-SAVE= STD ! NO ! K:number: ! F:number: !:number: !
(K:number:,:number:) ! (F:number:,:number:) !
(:number:,:number:) >
< ,KPAC= :number: ! STD ! NO >
< ,LINE25= STD ! NO ! YES ! OMNIS >
< ,LISTENING= NO ! :hac: ! >
< ,LOGGING= STD ! NO ! YES >
< ,MTAB= STD ! NO ! :tabname: >
< ,OPASS= :password: ! NONE ! ? >
< ,OUTPUT-LOGGING= STD ! REC ! SEND ! BOTH >
< ,PAC= STD ! NO ! LINE ! PREFIX >
< ,REPLY= STD ! RESTRICTED ! ALL >
< ,SAVE= STD ! SCREEN ! PKEY ! ALL ! NO >
< ,TESTMODE= NO ! YES >.
OMS0913
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0913 OMNIS HELP: 'PARAM' COMMAND
Meaning
The PARAM command serves to specify partner-specific parameters.
PARAM :pac: ! :gac: ! *C ! *D ! *K ! *S ! *T ! *U ! *
< ,CLASS= OUTPUT ! DELETE ! SAVE >
< ,COLOR= NO ! YELLOW ! RED ! WHITE ! GREEN !
BLUE ! CYAN ! MAGENTA >
< ,EXIT= STD ! NO ! :eac: >
< ,HCOPY= STD ! NO ! YES ! :hac: >
< ,HOLD= STD ! NO ! YES >
< ,KPAC= :zahl ! NO >
< ,LINE25= STD ! NO ! YES ! OMNIS >
< ,LOGGING= STD ! NO ! YES >
< ,MTAB= STD ! NO ! :tabname: >
< ,OPASS= :password: ! NONE ! ? >
< ,PAC= STD ! NO ! LINE ! PREFIX >
< ,SAVE= STD ! SCREEN ! PKEY ! ALL ! NO >
< ,SNMP= NO ! YES >.
OMS0914
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0914 OMNIS HELP: SET COMMAND
Meaning
The SET command defines global parameters for the administrator only.
SET < ACK= STD ! NO ! YES ! LINE >
< ,APASS= :password: ! ? >
< ,AUDIT= ON ! OFF >
< ,BREAK-KEY= STD ! NO ! :number: >
< ,CALL-INF= STD ! NO ! YES >
< ,CALL-KEY= STD ! NO ! :number: >
< ,DISPLAY-MODE= STD ! SYSTEM ! MIXED ! OMNIS >
< ,DSTMAX= :number: >
< ,EXCLUSIVE-PARTNER= STD ! NO ! YES >
< ,EXIT= STD ! NO ! :eac: >
< ,HCOPY= STD ! NO ! YES ! :hac: !
(DEV=:devname:,KEY=:number:,FORM=STD!:form:) >
< ,HOLD= STD ! NO ! YES ! AUTO >
< ,INPUT-LOGGING= STD ! REC ! SEND ! BOTH >
< ,INPUT-SAVE= STD ! NO ! K:number: ! F:number: !:number: !
(K:number:,:number:) ! (F:number:,:number:) !
(:number:,:number:) >
< ,KPAC= :number: ! STD ! NO >
< ,LINE25= STD ! NO ! YES ! OMNIS >
< ,LOGGING= STD ! NO ! YES >
< ,MTAB= STD ! NO ! :tabname: >
< ,NPASS= :password: ! NONE ! ? >
< ,OPNCON= STD ! FREE ! DECLARED >
< ,OPNSTART= YES ! NO >
< ,OUTPUT-LOGGING= STD ! REC ! SEND ! BOTH
< ,PAC= STD ! NO ! LINE ! PREFIX >
< ,PACMAX= :number: >
< ,PTNMAX= :number: >
< ,REPLY= STD ! RESTRICTED ! ALL >
< ,RTIMER= ON ! OFF >
< ,SAVE= STD ! SCREEN ! PKEY ! ALL ! NO >
OMS0915
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0915 OMNIS HELP: CALL
Meaning
CALL tells OMNIS to wait for input from the terminal before
issuing any more messages. The CALL state is activated by
* pressing the CALL key set with CALL-KEY (OPTION, SET
commands )
* an empty message (EM,SEND or Kx) if no CALL key has
been defined.
CALL is not possible for formats as their use necessarily
entails a strict dialog.
OMS0916
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0916 OMNIS HELP: 'INF' COMMAND
Meaning
The INF command is used to query a wide range of information.
INF ALL
SYSTEM < ,TYPE= PARAMETERS ! SETTINGS ! DIAGNOSTICS ! SUMMARY >
PARTNER < ,PID= :pid: > !
< ,PAC= :pac: >
< ,TID= OWN ! :tid: > !
< ,<TERMINAL= > ( < :ptnname: >,< :proname: > ) >
< ,USER= :user: >
< ,ACTIV= YES ! ALL ! HOLD ! NO >
< ,APASS= :password: ! ? >
TERMINAL < ,TID= OWN ! :tid: > !
< ,<TERMINAL= > ( < :ptnname: >,< :proname: > ) >
< ,USER= :user: >
< ,ACTIV= YES ! ALL ! HOLD ! NO >
< ,APASS= :password: ! ? >
TRACE
GROUP < ,TID= OWN ! :tid: >
< ,APASS= :password: ! ? >
MTAB < ,MTAB= :name: ! ALL >
< ,MSG= :messagenumber: ! ALL >
MUX < ,MID= :mid: >
< ,ACTIV= YES ! NO ! ALL >
EXIT < ,EXIT= :eac: >
HCOPY < ,HID= :hid: >
< ,ACTIV= YES ! NO ! ALL >
OMNIS < ,OID= :oid: >
< ,ACTIV= YES ! NO ! ALL >.
OMS0917
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0917 OMNIS HELP: 'TURN' COMMAND
Meaning
The TURN command activates the page-turning mode.
TURN <:pac:>
The following commands are accepted in paging mode:
+ page forward one screen (toward end of file)
- page back one screen (toward start of file)
+n advance n records (toward end of file)
-n page back n records
++ advance to end of file
-- page back to start of file
0 end paging mode.
OMS0918
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0918 OMNIS HELP: 'RESTART' COMMAND
Meaning
The RESTART command (re)activates a connection
RESTART OMNIS= :oac: !
HCOPY= :hac:.
OMS0919
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0919 OMNIS HELP: 'CANCEL' COMMAND
Meaning
The CANCEL command aborts the connection to a partner,
a terminal, a printer or a MUX-connection.
CANCEL < PID= :pid: > !
< PAC= :pac: >
< ,< TERMINAL = > ( <:ptnname:>, <:proname:> ) >
< USER = :user: >
< TID= :tid: > !
< HID= :hid:, FAILURE= :hac: ! *IGNORE ! *SAVE >
< HCOPY= :hac:, FAILURE= :hac: ! *IGNORE ! *SAVE >
< MID= :mid: > !
< MUX= ( :ptnname: , :proname: ) >
< OID= :oid: > !
< OAC= :oac: >
< ,KILL >
< ,APASS= :password: ! ? >
The CANCEL command is reserved for the administrator or restricted to the
own username
OMS0920
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0920 OMNIS HELP: 'CMD' COMMAND
Meaning
The CMD command lets you issue a BS2000 command.
CMD :BS2000 command:
The command CMD is reserved for the administrator and only
accepted if test mode is activated.
OMS0921
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0921 OMNIS HELP: 'DUMP' COMMAND
Meaning
The DUMP command generates a dump of OMNIS. OMNIS is not terminated.
DUMP < ,DUMP-MESSAGE = <omnis-messagenumber> >
< ,INSERT=(string,insertnumber) >
The DUMP command is reserved for the administrator and only
accepted when test mode is activated.
OMS0922
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0922 OMNIS HELP: 'EXIT' COMMAND
Meaning
The EXIT command is used for the administration of the exit routines.
EXIT :eac:
< ,ACTION= CREATE ! DELETE ! MODIFY >
< ,MODULES= :modname: ! (:modname: <,...>) >
< ,LOAD= NO ! YES >
< ,APASS= :password: ! ? >
:eac: is the name of the exit group.
CREATE generates a new exit group.
DELETE deletes an exit group.
MODIFY changes an exit group.
MODULES specifies the names of the exit routines. The first one is near
the partner, the last one near the terminal.
When specifying LOAD=YES all modules are loaded again, even when
they have already been loaded.
OMS0923
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0923 OMNIS HELP: 'CHANGELOG' COMMAND
Meaning
The CHANGELOG command releases the actual logging file and
initializes a new one or makes a copy of the current logging file.
CHANGELOG < ,ACTION= CHANGE ! COPY >
< ,SIZELIMIT= :number: ! RESET ! UNCHANGED >
< ,NAME= :string: ! STD >
< ,DELETE= YES ! NO >
< ,REPEAT=NO (TIME=:hh:mm: ! STD,DATE=:mm-dd: ! TODAY >
< PERIOD (TIME=:hh:mm: ! STD,HOURS=:number: ! STD >
< DAILY (TIME=:hh:mm: ! STD >
< WEEKLY (TIME=:hh:mm: ! STD,WDAY =:number: ! STD >
< MONTHLY(TIME=:hh:mm: ! STD,MDAY =:number: ! STD >
< RESET >
< UNCHANGED >
< ,APASS= :kennwort: ! ? >
The CHANGELOG command is reserved for the administrator.
OMS0924
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0924 OMNIS HELP: 'PRIORITY' COMMAND
Meaning
The PRIORITY command determines the sequence in which the LOGGING
and EXIT parameters are evaluated and which users are authorized to
use the EXIT and MDEF commands.
PRIORITY < ,EXIT-PRIORITY= PAR-OPT-SET ! SET-PAR-OPT >
< ,HOLD-PRIORITY= SET-OPT ! OPT-SET >
< ,LOGGING-PRIORITY= PAR-OPT-SET ! SET-PAR-OPT >
< ,EXIT-AUTHORIZATION= ADM ! ALL >
< ,MDEF-AUTHORIZATION= ADM ! ALL >
< ,APASS= :password: ! ? >
The PRIORITY command is reserved for the administrator.
OMS0925
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0925 OMNIS HELP: 'HCOPY' COMMAND
Meaning
The HCOPY command enters a new hardcopy unit in the printer table.
HCOPY :hac:
,PRONAME= :proname:
,PTNNAME= :ptnname:
< ,CONNECT= START ! USE >
< ,FAILURE= *IGNORE ! *SAVE ! :hac: >
:hac:, PRONAME and PTNNAME must be specified.
OMS0926
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0926 OMNIS HELP: 'TRACE' COMMAND
Meaning
The command TRACE is used to switch on or off the OMNIS TRACE
function for connections and EXIT-Routines.
TRACE < CONNECTION = YES / NO >
< ,EXIT = YES / NO >
< ,TRANSPORT = YES / NO / SELECT( TERMINAL=(:ptn:,:proc:) >
< ,HCOPY=hac >
< ,MID=mid >
< ,OMNIS=oac) >
The TRACE command is reserved for the administrator.
OMS0927
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
OMS0927 OMNIS HELP: 'CONFUPDATE' COMMAND
Meaning
The CONFUPDATE command causes OMNIS to read the configuration file.
CONFUPDATE < ,APASS= :kennwort: ! ? >
The CONFUPDATE command is restricted to the administrator.