Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POPAAAA Current DUMP-LIMIT-PER-HOUR ((&00)) of SYSTEMDUMP-MANAGERs reached or exceeded by (&01)! Continue? Response:Y/N
Meaning
If you want this system error to be handled by the
SYSTEMDUMP-MANAGER despite the fact that DUMP-LIMIT-PER-HOUR
has been exceeded, respond with "Y".
You can also adjust DUMP-LIMIT-PER-HOUR to a changed situation
using the MODIFY-SDM-PARAMETER command.
If it no longer makes sense to use the SYSTEMDUMP-MANAGER, terminate,
the administration process by responding with "N"
Until this question has been answered, no new dump messages can
be processed by the SYSTEMDUMP-MANAGER.
POPAAAB
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POPAAAB DUMP-LIMIT-PER-HOUR not in defined range of values (<integer 0..255>)
Response
Correct and restart the administration process.
POPAAAC
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POPAAAC DUMP-OCCURRENCE not in defined range of values (<integer 1..255> or *ANY)
Response
Correct and restart the administration process.
POPAAAD
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POPAAAD HISTORY-FILE not a SAM file. Command not executed
POPAAAE
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POPAAAE Problems signing on to PROP-XT subsystem
Meaning
The SYSTEMDUMP-MANAGER may only be used once per system or
PROP-XT is not installed.
Response
Terminate any administration process that is running and restart the
SYSTEMDUMP-MANAGER using ENTER-PROCEDURE or install PROP-XT.
POPAAAF
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POPAAAF OPERATOR-ROLE not specified or incorrect
Response
Correct and restart the administration process.
POPAAA1
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POPAAA1 SYSTEMDUMP MANAGER terminated (MC=(&00))
Meaning
SYSTEMDUMP MANAGER was terminated.
Cause: See maincode MC (PROP-XT User Guide).
POPAAA2
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POPAAA2 SYSTEMDUMP MANAGER working with empty HISTORY-FILE
POPAAA3
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POPAAA3 MODUL-LIST-FILE not a SAM or ISAM file (KEY-LEN=8). Command not executed
POPAAA4
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POPAAA4 SYSTEMDUMP MANAGER working with empty MODUL-LIST-FILE
POP0A0A
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A0A Too many operands in command
Meaning
The command defined as an event in the SDF-P variable
cannot be processed since the number of operands is greater than 20.
POP0A0B
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A0B Command operands cannot be edited
Meaning
The command defined as an event in the SDF-P variable
cannot be edited since the value of the operand(s) is neither
STRING nor INTEGER.
POP0A0C
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A0C /BEGIN-PROP-PROCESS must be first PROP-XT command in an administration procedure.
POP0A0D
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A0D Specified command is not a PROP-XT system command
Meaning
The command received could not be identified as a PROP-XT
system command on account of the internal command name.
It might be a PROP-XT administration command, but if so
it may not be used in an administration procedure.
POP0A0E
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A0E No such PROP-XT system command in syntax file
Meaning
In the syntax file a command was marked as an PROP-XT
system command although it is not one.
POP0A0F
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A0F Total length of inserts too great
Meaning
The combined length of all the inserts in a system
message may not exceed 180 characters.
POP0A00
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A00 No PROP-XT authorization
Meaning
The user ID which was used to try to sign on to
PROP-XT does not have the PROP-ADMINISTRATION privilege.
POP0A01
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A01 Administration process with this name has already signed on
POP0A02
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A02 Memory bottleneck
Meaning
The message buffer (MTBUFF) for communicating
with the main task cannot be created.
POP0A03
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A03 Resource bottleneck on system
Meaning
GENERAL
Access to initialized PROP-XT data is faulty.
BEGIN-PROP-PROCESS
Bourse error in communication between administration task
and main task.
System error in querying the user ID of the administration process.
System error in querying the TSN of the administration process.
END-PROP-PROCESS
Bourse error in communication between administration task
and main task.
Error in releasing AP name for NAME-MANAGER.
Error in releasing communication buffer (MTBUFF).
START-PROP-EVENT-MONITORING
Bourse error in communication between administration task and
main task. No acknowledgment was received within 600 sec when
signing on a command. A negative acknowledgment was received from
UCON when signing on a command as an event.
STOP-PROP-EVENT-MONITORING, STOP-PROP-OBJECT-MONITORING
Bourse error in communication between administration task
and main task. An internal error has occurred.
START-PROP-OBJECT-MONITORING
Bourse error in communication between administration task
and main task. No acknowledgment was received withihin 600 sec
when setting up a connection to the administration entity.
SEND-TO-PROP-ADMINISTRATOR, SIMULATE-PROP-EVENT
Bourse error in communication between administration task
and main task.
SEND-TO-PROP-OBJECT
Bourse error for main task.
POP0A04
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A04 Event type specified cannot be handled by PROP-XT
POP0A08
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A08 None of the specified events defined for administration process
Meaning
No events that can be waited for have been defined by,
the administration process.
The events specified in the list are not defined.
POP0A09
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A09 Invalid message received
Meaning
Message received does not match the event type specified.
POP0A1A
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A1A Simulation not possible for administration entities or events
POP0A1B
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A1B No administration entities defined for administration process
Meaning
WAIT-FOR-PROP-EVENTS, START-PROP-EVENT-MONITORING
None of the specified administration entities are defined
for the administration process.
STOP-PROP-OBJECT-MONITORING
None of the specified administration entities are defined
for the administration process.
NOTE: When *ALL is specified for the administration entities
there is no check to see which ones have been defined.
POP0A1C
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A1C Port signals error when sending over administration connection
POP0A1D
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A1D Error in connection to one or more administration entities
Meaning
WAIT-FOR-PROP-EVENT, START-PROP-EVENT-MONITORING
The connection no longer exists to all the administration
entities specified in the command.
Message POP9A06 is output for each such administration entity.
START-PROP-OBJECT-MONITORING
A negative acknowledgment was received when setting up the
connection to the administration entity.
SEND-TO-PROP-OBJECT
The connection to the administration entity
specified by /SEND-TO-PROP-OBJECT is cleared.
Port signals an error when sending over administration entity
connection.
POP0A1E
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A1E Not all specified administration entities are defined. Processing continues
Meaning
WAIT-FOR-PROP-EVENTS, START-PROP-EVENT-MONITORING
Some of the administration entities specified for the
administration process are not defined.
Message POP9A07 is output for each administration entity.
Message POP9A06 is output for each defined administration
entity to which the connection is not active.
STOP-PROP-OBJECT-MONITORING
Some of the specified administration entities are not
defined for the administration process.
Message POP9A07 is output for each administration entity.
SEND-TO-PROP-OBJECT
The specified administration entity is not defined for the
administration process.
POP0A1F
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A1F Not all specified events are defined. Processing continues
Meaning
The list of specified events includes some which are,
not defined.
Message POP9A04 is output for each such event.
POP0A10
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A10 Syntax error in command
Meaning
GENERAL
The syntax of the command received could not be analyzed
by PROP-XT (SDF command analysis).
SIMULATE-PROP-EVENT
The syntax of the command to be simulated is incorrect.
POP0A11
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A11 Command allowed again only after END-PROP-PROCESS
Meaning
A second BEGIN-PROP-PROCESS command is only permitted in
an administration task after an END-PROP-PROCESS command.
POP0A13
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A13 Arriving events can no longer be buffered for the administration process
Meaning
The memory space required exceeds the value permitted by
the administration command MODIFY-PROP-PARAMETERS.
POP0A14
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A14 Termination requested
Meaning
Via the administration command SEND-TO-PROP-PROCESS
the administration process was requested to terminate.
WAIT-FOR-PROP-EVENT
Via the Administration command SEND-TO-PROP-PROCESS the
administration process was requested to terminate. Any wait
time started can thus be terminated.
POP0A15
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A15 Data inconsistency when processing system command
Response
- Create fault documentation
- notify system service
POP0A16
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A16 Error in accessing administration entity management data
Meaning
GENERAL
Error in accessing the administration entity management data.
SEND-TO-PROP-OBJECT
Error in the administration entity management when sending data
to the administration entity.
POP0A17
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A17 Error in accessing event management data
Meaning
GENERAL
Error in accessing event management data.
START-PROP-EVENT-MONITORING
No acknowledgment was received within 600 sec when signing
on a command. A negative acknowledgment was received from
UCON when signing on a command as an event.
SEND-TO-PROP-OBJECT
No job could be generated for sending data to the
administrator.
POP0A18
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A18 Error in accessing administration process management data
POP0A19
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A19 Event could not be simulated for some administration entities. Processing continues
POP0A20
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A20 Subsystem PROP-XT stopped
POP0A21
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0A21 The specification of a user-id requires also the specification of a password
POP0A22
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A22 Variable SYSPOP or <RESULT-VAR> could not be assigned. Processing continues
Meaning
The variable SYSPOP or the specified result variable could not be
assigned because of missing or invalid declaration.
Response
Insert a correct declaration of the variable into the PROP-XT
procedure.
POP0A30
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0A30 Illegal Value for OWN-APPLICATION
Meaning
The name may not start with "*" or "$".
Response
Correct and try again.
POP0B0A
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B0A Unknown REFERENCE-NAME
Meaning
The user has specified a REFERENCE-NAME that does
not identify an order in this administration process.
The order may already have been terminated.
Response
Check the REFERENCE-NAME.
POP0B0B
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B0B Although order elements are expected, no REFERENCE-NAME was given
Response
Specify REFERENCE-NAME.
POP0B0C
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B0C Event name already used
POP0B0D
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B0D Event name already used as group name
POP0B0E
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B0E Group name already used as event name
POP0B00
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B00 Illegal event type
POP0B01
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B01 Illegal data type
POP0B08
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B08 Specified REFERENCE-NAME already exists. Command ignored.
Meaning
The specified REFERENCE-NAME already exists. The command was ignored.
or was not unambiguous in the specified length.
When sending queries and commands, the REFERENCE-NAME
must be unambiguous in the first 3 characters.
Response
Choose another REFERENCE-NAME.
POP0B09
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B09 Resource bottleneck with internal PROP-XT reference name
Meaning
Too many commands and inquiries for which PROP-XT
has assigned an internal reference name (max.: >1300!)
have not been terminated.
Response
Check the administration procedures for endless loops.
POP0B1B
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B1B Not all specified elements of list defined.
Meaning
In case of wait or check event: No events occurred
POP0B1C
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0B1C Command server no longer connected
Meaning
The command event is no longer defined in the server
administration process.
POP0B1D
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0B1D Command could not be transferred to server administration process
Meaning
- Buffer overflow owing to problems with server
administration process.
POP0B1F
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B1F PROP-XT does not support jobs for this entity type. Processing continues
Meaning
An operand was specified that is only relevant for job processing
(e.g. REFERENCE-NAME, IMPLICIT-EVENT).
However, PROP-XT does not support any jobs with this administration
type (DCAM/UTM).
POP0B10
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B10 Permitted number of servers for operator special commands reached
POP0B11
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B11 Connection error in signing on operator special command
POP0B12
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B12 Message type currently not allowed
Meaning
The order identified by the specified REFERENCE-NAME
is in a status in which the specified message type is not
allowed.
Response
Check the REFERENCE-NAME, message type and status of the order.
POP0B13
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B13 Time specified for time event already elapsed
POP0B14
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B14 Illegal time specification
POP0B18
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B18 No events occurred for selection criterion
Meaning
WAIT-FOR-PROP-EVENT
No more events have occurred for the specified events since
those that have already been fetched/transferred, and the
wait time for the WAIT command (TIME-LIMIT=) has elapsed.
If OPERATIONAL-MODE=SIMULATION applies for the administration,
process, an event generated by the SIMULATE-PROP-EVENT command
(TIME-LIMIT-REACHED) aborts the WAIT command.
CHECK-PROP-EVENT-OCCURRENCE
No more events have occurred for the specified events since
those that have already been fetched/transferred.
POP0B19
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B19 The events specified in the command were not defined beforehand
POP0B20
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B20 Message type not supported. Processing continues
Meaning
For entities of type DCAM or UTM no message types are supported.
The TYPE Specification is ignored.
POP0B22
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B22 Internal error in ONEVT call
Meaning
Failed to enable CJC monitoring for job variable(s).
Response
Take user dump for further diagnosis.
POP0B23
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0B23 Internal error in DONEVT call
Meaning
Failed to disable CJC monitoring for job variable(s).
Response
Take user dump for further diagnosis.
POP0C00
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0C00 Administration entity description not in database
Meaning
No administration entity description is contained in the database
for the administration entity.
Response
The attributes of the administration entity must be
supplied with START-PROP-OBJECT-MONITORING or the
administration entity must be defined in the database
by the PROP-XT administrator.
POP0C01
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0C01 No authorization to use the administration entity description from the database
Meaning
The user is not authorized to use this administration entity
description from the database.
Response
The PROP-XT administrator must authorize this user (user ID)
to use this administration entity description from the
database.
POP0E0C
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E0C Connection already exists
Meaning
A connection already exists between OWN-APPLICATION
and APPLICATION
Response
Select a different name for OWN-APPLICATION and try again
POP0E0E
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E0E OWN-APPLICATION cannot be opened.
Meaning
The auxiliary application specified under OWN-APPLICATION
could not be opened.
Possible reasons:
- Application is pregenerated and protected by a user password
- BCAM problems such as
- shortage of memory space
- threshold values exceeded
- name reserves or AP ID exhausted
- BCAM shutdown announced
Response
Retry command later.
POP0E0F
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E0F Application specified in OWN-APPLICATION already open
Meaning
The connection to the application entity could not be set up
because the auxiliary application OWN-APPLICATION has already
been opened exclusively or with password protection by another task.
Response
Specify a different name for OWN-APPLICATION.
POP0E05
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E05 No data specified.
Meaning
The user attempted to send an empty string to an
entity of the type DCAM or UTM. Empty strings may
only be sent to entities of the type Operating.
POP0E06
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E06 Letter length error reported by BCAM
Meaning
The message or connection letter could not be
sent.
Possible reasons:
- BCAM threshold values exceeded
Response
Check BCAM threshold values and/or take
system dump of PROP-XT holder task for
further diagnosis.
POP0E10
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E10 Connection rejected by partner.
Meaning
The partner or his transport system rejected
the connection request. BCAM issues
Station Information YDB_STCONREJ.
Possible reason: incorrect password
POP0E11
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E11 Partner Application not known
Response
Correct and try again.
POP0E12
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E12 Name of partner system not known
Response
Correct and try again
POP0E13
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E13 Maximum number of connections per application exceeded.
Meaning
BCAM limits the number of connections that an
application may open.
This number has been exceeded for the application specified
under OWN-APPLICATION.
Note: Other tasks can also open connections from this
application.
If an error occurs with START-PROP-OBJ-MON <name>, type=*OPERATING
too many connections within PROP have already been set up
to computers within the user's own MSCF network (of the type
CCS) without a user ID being specified.
Response
With type = DCAM/UTM: select a different value
for APPLICATION.
With type = OPERATING: notify the system administrator.
POP0E14
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E14 Computer not in common MSCF network
Meaning
The user attempted to set up a connection to an entity of
the type Operating on a foreign system without specifying
the user ID. This works only if the partner system and the
local system are both in a common MSCF network of the type
CCS, the network is active and the BS2000 version used on
the partner system is >= V11.2.
Response
Notify the system administrator or specify an operator
user ID.
POP0E15
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E15 Illegal operator role
Meaning
Operator role unknown or not permitted for this User-Id
Response
Correct and try again.
POP0E16
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0E16 Incorrect authorization information
Meaning
Either the User ID or password specified in the
START-PROP-OBJECT-MONITORING command is incorrect
Response
Correct and try again
POP0001
Destination: CONSOLE Routing code: * (main console) Weight: 50
Warranty : YES
POP0001 SUBSYSTEM '(&00)' VERSION '(&01)' STARTED
POP010A
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP010A Connection to administration entity already exists
Meaning
The administration entity defined in the command was
already defined and the connection is active.
POP010B
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP010B SDF communication area could not be set up correctly
Meaning
IMPLEMENTOR=TPR(ENTRY=DUMMY,CALL=NEW) must be
specified in the command definition.
A user command may not contain more than 20 operands.
Response
Correct the command and recompile with SDF-A.
POP010C
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP010C Syntax error in name
Meaning
Possible cause: The REFERENCE-NAME specified
cannot be abbreviated so that it is a valid reference
name for UCON, or the name includes "$" or "-".
Response
Correct the name and retry the command.
POP0100
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0100 Administration entity already in database
Meaning
The administration entity definition in the command
already exists.
Response
Check the name specified for the administration entity,
definition and overwrite if required.
POP0102
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0102 No administration entity definition
Meaning
The administration entity definition in the command
does not exist.
Response
Check the name specified for the administration entity,
definition and correct it.
POP0107
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0107 Administration entity not of type UCON
Meaning
Specified type is not supported in this PROP-XT version.
Response
Change the administration entity type.
POP0108
Destination: USER-TASK, CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0108 No more administration processes/entities allowed
Meaning
The maximum number of administration processes/entities
currently permissible have already signed on.
POP020F
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP020F Subsystem JV not available
POP021D
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP021D Message code does not exist. Alternate message was generated
Meaning
The message could not be found in the message files assigned.
Response
Define the message and/or attach the message file
POP0211
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0211 Syntax error - Command privilege "PROP-ADMINISTRATION" does not exist
Meaning
The command originator (administrator) does not have
the "PROP-ADMINISTRATION" privilege.
Response
Assign the administrator the "PROP-ADMINISTRATION" privilege
POP0212
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0212 User-Id could not be found
Meaning
There is no user-id to check syntax or authorisation
Wrong NBMHE-Header version.
Response
Use at least OSD V2.0 or UCON-rep.
POP0213
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0213 Specified system message could not be generated
Meaning
SEND-TO-PROP-ADMINISTRATOR
The specified system message could not be generated (Message with
MSG-ID not in the message file or message file not assigned).
SIMULATE-PROP-EVENT
The message to be simulated could not be generated.
Error in accessing the message file. Check whether this file
actually contains the message with the specified MSG-ID.
POP0214
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0214 Syntax error - Command ignored
Meaning
The command syntax is incorrect. Detailed information
on the syntax error is supplied in the subsequent messages.
Response
Correct and reenter the command.
POP022A
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP022A New databasefile was created
POP0223
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0223 Syntax error - SDF environment cannot be set up
Meaning
An error occurred while setting up the environment
assigned to the command originator.
Response
Check the command originator's user ID and set up correctly.
POP0225
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0225 Access to job variable not possible
Meaning
The job variable cannot be accessed (not defined,
not shareable).
POP0229
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP0229 ENCRYPTION-PASSWORD (OLD-PASSWORD) specified for the required database file is incorrect
Meaning
The passwords contained in the file were not all encrypted
with the specified password, or the file is not a PROP-XT
database file. The command was not executed.
POP0235
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP0235 Version of database file incorrect
Meaning
PROP-XT cannot work with the version specified in the database
file, or the file is not a PROP-XT database file. The command was
not executed.
POP0240
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0240 Specified timestamp ambigious. Processing continues
Meaning
The time specified is in the time overlap when switching from
daylight saving time to normal time. Depending on the SEASON operand,
an alternative time has been fixed.
POP0241
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0241 Calculated time ambiguous. Processing continues
Meaning
The time specified is in the time overlap when switching from
daylight saving time to normal time. Depending on the SEASON operand,
an alternative time has been fixed.
POP0242
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP0242 Specified timestamp does not exist. Processing continues
Meaning
Owing to the switch from normal to daylight saving time, the time
specified for the timestamp does not exist. Depending on the SEASON
operand, an alternative time has been fixed.
POP0705
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0705 ENCRYPTION-PASSWORD (OLD-PASSWORD) password is different from the current one current one
Meaning
The command was not executed. Changes to the database will only be
implemented after the current password has been entered.
Response
Enter the correct password and try again.
POP0707
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0707 Internal error when switching the database file
Meaning
Errors occurred in PROP-XT (DVS error or resource bottleneck
Possible reasons:
- The open DB file cannot be closed.
- The DB file cannot be created, opened, read or written to.
- The password cannot be encrypted.
Response
- Try again with a different database file.
- Notify the system administrator.
POP0708
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0708 Internal error when accessing the database
Meaning
Errors occurred in PROP-XT (resource bottleneck, data inconsistency).
The status of the database is undefined.
Response
- Notify the system administrator.
POP090B
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP090B Internal error. Command not executed fully
Meaning
Errors occurred in PROP-XT (resource bottleneck, data inconsistency).
The command was not executed fully.
Response
Retry.
POP090C
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP090C No administration process specified in command exists
Meaning
None of the administration processes specified in the
command is signed on to PROP-XT.
Response
Correct names of administration processes.
POP090D
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP090D Not all administration processes exist
Meaning
Not all the administration processes specified in the
command are signed on to PROP-XT.
Response
Correct names of administration processes.
POP090E
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP090E No response administration entity definition
Meaning
No administration entity definition exists for the
response administration entity specified in the command.
Response
Create an administration entity definition for the
response administration entity.
POP090F
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP090F No administration entity definition for STD-ACTION administration entity
Meaning
No administration entity definition exists for
the STD-ACTION administration entity.
Response
Create an administration entity definition for the
STD-ACTION administration entity.
POP0900
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0900 No such command
Meaning
PROP-XT does not recognize the command entered.
Response
Correct the command if it is incorrect.
- Check whether PROP-XT can be administered. If it cannot,
subsystem PROP-XT must be started again.
POP0901
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0901 STD-ACTION already exists. Command not executed.
Meaning
The STD-ACTION specified in the command is already
signed on to PROP-XT.
Response
Check the name specified for STD-ACTION, and if required
overwrite using the REPLACE-OLD-ACTION=YES operand.
POP0902
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0902 Internal error. STD-ACTION could not be accepted
Meaning
Errors occurred in PROP-XT (resource bottleneck, data inconsistency).
POP0903
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0903 STD-ACTION does not exist
Meaning
The STD-ACTION specified in the command is not known
to PROP-XT.
Response
Check and correct the name specified for the STD-ACTION.
POP0904
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0904 Internal error. STD-ACTION could not be deleted
Meaning
Errors occurred in PROP-XT (resource bottleneck, data inconsistency).
POP0906
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0906 None of specified STD-ACTIONs exists
Meaning
Specified STD-ACTIONs are not signed on to PROP-XT.
Response
Correct the names of the specified STD-ACTIONs.
POP0907
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0907 Not all specified STD-ACTIONs exist
Meaning
Not all specified STD-ACTIONs are signed on to PROP-XT.
Response
Check the names of the STD-ACTIONs and retry command.
POP0908
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0908 Internal error. Administration entity could not be accepted
Meaning
Errors occurred in PROP-XT (resource bottleneck, data inconsistency).
POP0909
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0909 Internal error. Administration entity could not be deleted
Meaning
Errors occurred in PROP-XT (resource bottleneck, data inconsistency).
POP0910
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0910 Specified type of STD-ACTION administration entity not supported
Meaning
Specified type is not supported in this PROP-XT version.
Response
Change the administration entity type.
POP0911
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0911 No administration object specified in command exists
Meaning
None of the administration objects specified in the
command is signed on to PROP-XT.
Response
Correct names of administration objects.
POP0912
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP0912 Not all administration objects exist
Meaning
Not all the administration objects specified in the
command are signed on to PROP-XT.
Response
Correct names of administration objects.
POP0913
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP0913 No administration object defined
POP9A01
Destination: CONSOLE Routing code: @ (conslog) Weight: 50
Warranty : NO
POP9A01 PROP-XT Administration process '(&01)' started
Meaning
Command BEGIN-PROP-PROCESS executed.
POP9A02
Destination: CONSOLE Routing code: @ (conslog) Weight: 50
Warranty : NO
POP9A02 PROP-XT Administration process '(&01)' terminated
Meaning
Command END-PROP-PROCESS executed.
POP9A04
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP9A04 Event '(&01)' not known
POP9A06
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP9A06 Connection to administration entity '(&01)' not active
POP9A07
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
POP9A07 Administration entity '(&01)' not defined for administration process
POP9A11
Destination: CONSOLE Routing code: @ (conslog) Weight: 50
Warranty : NO
POP9A11 START-PROP-OBJECT-MONITORING executed for '(&00)'; Partner: (&01)/(&02)
Meaning
(&00) - Object name
(&01) - Name of partner application or *FROM-DB
(&02) - Processor name of partner application or
*LOCAL or *FROM-DB
POP9A12
Destination: CONSOLE Routing code: @ (conslog) Weight: 50
Warranty : NO
POP9A12 STOP-PROP-OBJECT-MONITORING executed for '(&00)'
Meaning
(&00) - Object name or *ALL
POP9A13
Destination: CONSOLE Routing code: @ (conslog) Weight: 50
Warranty : NO
POP9A13 Connection to PROP administration object '(&00)' broken
Meaning
(&00) - Object name
POP9A14
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9A14 Task terminating due to MSCF request
Meaning
MSCF is terminating abnormally because of serious
problems. The task locks a shared PVS that is to
be exported, and therefore must be terminated.
POP9B01
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9B01 COMMAND SERVER NOT FOUND
Meaning
The command server was not found in the PROP-XT
command list or the command server is not active
or the entered command is ambigous from SDF point
of view.
POP9B02
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9B02 COMMAND COULD NOT BE TRANSMITTED TO SERVER
Meaning
A bourse error occured during the transmittal of
the command to the server procedure.
POP9B03
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9B03 COMMAND SERVER TERMINATED
Meaning
The PROP-XT administration process that had been
the server of this command, has terminated.
POP9F01
Destination: CONSOLE Routing code: R Weight: 50
Warranty : YES
POP9F01 Connection to administration entity '(&01)' could not be established
Meaning
No connection could be established to the administration
entity specified in the STD-ACTION.
POP9F02
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9F02 Loss of connection to administration entity '(&01)' of STD-ACTION
Meaning
Loss of data must be anticipated. PROP-XT initiates
connection setup automatically when this is required.
POP9500
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9500 PROP-XT cannot be administered
Meaning
The administration connection to the local
application $CONSOLE could not be established
or is refused, or some error occured during the
command connection of the PROP-XT administration
commands.
Response
Check if BCAM is ready and the PROP-XT
administration commands are not occupied by any
other appliction (command SHOW-CMD-ATTRIBUTES).
POP990A
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP990A Error in command analysis for user '(&01)'
Meaning
Check whether the command is contained in the relevant SDF syntax
file. As command analysis of PROP-XT user commands is performed
in both the command originator's environment and in the command-
processing administration procedure, you are notified here of
the environment in which errors occurred.
POP990C
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP990C Administration object '(&01)' not known
Meaning
Specified object is not signed on to PROP-XT.
Response
Correct the object name in the command.
POP9900
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9900 All PROP-XT administration commands available
Meaning
PROP-XT can now be administered.
POP9902
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9902 STD-ACTION '(&01)' not known
Meaning
STD-ACTION is not signed on to PROP-XT.
Response
Sign on STD-ACTION or correct name of STD-ACTION in command.
POP9903
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9903 No administration process found
Meaning
No administration process is signed on to PROP-XT.
POP9904
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9904 Administration process '(&01)' not known
Meaning
Specified process is not signed on to PROP-XT.
Response
Correct the process name in the command.
POP9905
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9905 No administration entity exists for administration process '(&01)'
Meaning
The specified administration process is not
monitoring any administration entities.
POP9906
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9906 No event exists for administration process '(&01)'
Meaning
Specified administration process is not monitoring any events.
POP9908
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9908 Administration process '(&01)' could not be notified
Meaning
The specified administration process could not be notified
by setting a return code.
POP9909
Destination: CONSOLE Routing code: R Weight: 50
Warranty : NO
POP9909 Administration process '(&01)' could be notified
Meaning
The specified administration process was notified by
setting a return code.