Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIC001 The command /CHANGE-TASK-CPU-LIMIT could not be executed successfully for the specified task.
Meaning
Possible reasons are:
- the specified task does not exist
- the MONJV does not identify an existing task
- the MONJV is owned by another system in the MSCF network
- parameter error (wrong value: seconds or percent)
Response
Correct the command!
NTITD01
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD01 SHORTAGE OF RESOURCES. FUNCTION TERMINATED ABNORMALLY.
NTITD02
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD02 INVALID CALL OF SUBSYSTEM TASKDATE.
NTITD03
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD03 SYSTEM FUNCTION '(&00)' COULD NOT BE EXECUTED SUCCESSFULLY . RETURNCODE '(&01)'.
NTITD04
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD04 COMMAND NOT ALLOWED WHILE PROGRAM IS LOADED.
NTITD05
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD05 VALUE OF PARAMETER 'DATE' NOT IN THE ALLOWED RANGE.
NTITD06
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NTITD06 LOADING OF SUBSYSTEM ABORTED BECAUSE OF MISSING REPS IN SUBSYSTEM GET-TIME (PM A0394142).
Meaning
It is necessary to include the Reps A0394142 into the subsystem ^
GET-TIME, before starting TASKDATE
NTITD07
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
NTITD07 LOADING OF SUBSYSTEM ABORTED BECAUSE OF MISSING REPS IN BS2000-GA (PM A0394142).
Meaning
It is necessary to include the Reps A0394142 into BS2000-GA, ^
before starting TASKDATE
NTITD08
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD08 INSTALLATION OF TASKDATE FAILED. REPLY: <tsn>.
Meaning
Please inform the system administrator.
NTITD09
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD09 TERMINATION OF SUBSYSTEM NOT POSSIBLE NOW. TERMINATE ALL THE ENTER-JOBS INDICATED BY /SHOW-TASK-CLOCK *TSN(TSN=*ALL). AFTERWARDS: TRY AGAIN TO TERMINATE THE SUBSYSTEM.
NTITD10
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD10 NO INFORMATION AVAILABLE BECAUSE NO SIMULATED TIME IS DEFINED
NTITD11
Destination: USER-TASK Routing code: Weight:
Warranty : NO
NTITD11 SPECIFIED TASK NOT (RESP.: NO MORE) EXISTING
NTIX100
Destination: CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIX100 Join of XCS can not be performed. System error occured in run of task "TIME".
Meaning
An internal error inhibits the join of a XCS.
Diagnose data are generated automatically.
Response
To make possible the joining of XCS the system has to be
restarted (STARTUP).
NTIX101
Destination: CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIX101 '(&00)' seconds wait time for synchronization of system time with the time of the XCS
Meaning
Before the system can join the XCS, the system time has to be adjusted
to XCS time. This adjustment requires the given time span.
Response
If the systems building the XCS are already started with synchronized
times, the wait time diminishes to unsignificant value.
NTIX102
Destination: CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIX102 Join of XCS not possible. Difference between the system times of the local system and the XCS node system too large.
Meaning
For joining the XCS the maximal difference between
the system times must not be exceeded.
Response
New startup with convenient system time.
NTIX103
Destination: CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIX103 Join of XCS not possible. TimeServer/radio clock disables synchronisation and the actual difference between system times is too large
Response
Before the next try of join connect the TimeServer/radio clock to the
XCS or disconnect the TimeServer/radio clock from the local system.
NTIX104
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : NO
NTIX104 XCS-TIME aborts XCS-session, Reason: '(&00)'
Meaning
XCS-TIME will abort the actual XCS-session
(&00): Reason for abort:
1: Internal error during resource allocation
2: Time synchronisation during join failed
3: Time difference during join to large
4: No time synchronisation possible for a long time
due to communication failure
5: Internal error during load of subsystem XCS-TIME
6: A radio-clock is installed, the XCS-time is greater
than the local time and at least one XCS-partner
has OSD before V4.0
7: Time difference to large
Response
Reason 3,6,7:
Correct the time of the existing XCS.
Else:
Save the Serslogfile and inform the diagnosegroup.
NTIX110
Destination: CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIX110 Abort of XCS. The difference between the system times of the local system and the XCS node systems is too large.
Meaning
The time supported from any partner system is larger than
the local system time plus a allowed difference.
A possible reason is the configuration error, that only a few
systems in the XCS have a radio clock.
Response
The configuration error must be corrected.
NTIX112
Destination: CONSOLE Routing code: * (main console) Weight: 80
Warranty : NO
NTIX112 Warning: no time synchronisation for a long time.
Meaning
No time update from other hosts of the XCS arrived during a long time.
A possible reason is that the token of NSM is broken.
Response
The configuration error must be corrected.