Destination: USER-TASK Routing code: Weight:
Warranty : NO
POSCOPY Copyright (C) '(&00)' '(&01)' All Rights Reserved
POSLOAD
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POSLOAD Program '(&00)', Version '(&01)' of '(&02)' loaded from file '(&03)'
POSSTRT
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POSSTRT Procedure '(&00)', Version '(&01)' of '(&02)' started from file '(&03)'
POS1000
Destination: USER-TASK, CONSOLE Routing code: # Weight: 30
Warranty : NO
POS1000 (&00)
Meaning
Message to indicate the state of the POSIX subsystem.
POS1010
Destination: USER-TASK, CONSOLE Routing code: # Weight: 50
Warranty : NO
POS1010 Message of the POSIX kernel: (&00)
Meaning
Note of the POSIX subsystem.
POS1020
Destination: USER-TASK, CONSOLE Routing code: # Weight: 70
Warranty : NO
POS1020 Message of the POSIX kernel:(&00)
Meaning
Warning of the POSIX subsystem.
Response
Contact the system administrator.
POS1030
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS1030 Message of the POSIX kernel: (&00)
Meaning
Message indicating unrecoverable error within POSIX subsystem.
Termination of the POSIX subsystem is initiated.
Response
Contact the system administrator.
POS1040
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS1040 BCAM has terminated; the POSIX subsystem must be re-started./
Meaning
After termination of BCAM, POSIX components using networking
functions will no longer work correctly.
Response
Re-start the POSIX subsystem.
This message will be acknowledged automatically.
POS1041
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS1041 Failure detected in POSIX: '(&00)'; diagnostic dump created./ACK
Meaning
A failure condition was detected by the POSIX subsystem and a system
dump was created for diagnostic purposes.
(&00): Description of the failure condition.
Response
Acknowledge this question and forward the dump to the service.
POS1042
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS1042 Failure detected in POSIX: '(&00)'; diagnostic dump not created
Meaning
A failure condition was detected by the POSIX subsystem. A system
dump was not created because the limit defined by POSSDMAX is already
reached.
(&00): Description of the failure condition.
POS1050
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS1050 The init process could not start a child process with the requested CPU limit.
Meaning
The child process was started with a lower CPU limit, so it is possible
that the process is terminated prematurely because of reaching the
CPU limit.
Response
For preventing disruptions of operations appropriate adaptions should
be made (e.g. job class definition) and the POSIX subsystem should
be restarted. This message will be acknowledged automatically.
POS2000
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2000 Subsystem private initialization of POSIX has been processed
Meaning
The private initialization routine of the POSIX subsystem has been
executed without error (Note: POSIX may not yet be used by any
application! Wait for the initialization by DSSM (message ESM0220)
and by the init process (message POS4100).)
POS2001
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2001 Subsystem private initialisation of POSIX has been proceeded (on base of the generic root file system)
Meaning
Start on base of the generic root file system is only allowed in case of
first installation. Init process is not started. The first installation
continues.
Response
1.) First installation: None.
2.) Start by mistake: Terminate subsystem, insert name of wanted root
file system into the POSIX information file and restart POSIX.
POS2010
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2010 Error occurred on reading POSIX information file
Meaning
POSIX is started with standard values.
POS2011
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2011 No reservation of system memory possible (class 4)
Meaning
No open on POSIX information file possible. POSIX start is continued
with standard values.
POS2012
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2012 The POSIX information file could not be opened
Meaning
POSIX start is continued with standard values.
POS2013
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2013 Record pointer could not be positioned in POSIX information file
Meaning
POSIX information file is closed and POSIX start is continued with
standard values.
POS2014
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2014 Error occurred during CLOSE of POSIX information file
Response
Inform the system administrator, please.
POS2015
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2015 POSIX cannot be started (REBOOT of first installation)
Meaning
The problems which occurred during POSIX start are described in detail
by corresponding console messages.
POS2016
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2016 Error occurred during erase of generic root file system (userid 'SYSROOT')
Response
Inform the system administrator, please.
POS2017
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2017 Userid 'SYSROOT' not available or locked
Response
Use /UNLOCK-USER USER-IDENTIFICATION=SYSROOT to unlock userid 'SYSROOT'.
POS2018
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2018 No information available on userid 'SYSROOT'
Meaning
For detailed information see SERSLOG file ($SJINFO return code).
POS2019
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2019 Error in call of IMON interface '(&00)' for the enter file of the init process
Meaning
The filename of the enter job for the init process could not be
determined.
Response
Inform the system administrator, please.
POS2020
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2020 Error while constructing the filename for the enter file of the init process
Meaning
The filename of the enter job for the init process could not be
determined.
Response
Inform the system administrator, please.
POS2100
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2100 Parameter file for automatic POSIX installation does not exist
Response
Supply parameter file for automatic POSIX installation, please.
POS2200
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS2200 Signal mask of process with pid (&00) destroyed. No further information available
Response
Inform system administrator, please. The system administrator can retrieve
more information about the erroneous process with BS2000 diagnostic
tools.
POS2201
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS2201 Process with pid (&00) is a zombie. No further information available
POS2202
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2202 Process structur of process with pid (&00) already released. No further information available
POS2203
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS2203 Task with TSN (&00) has no process structure. No further information available
Response
Inform system administrator, please. Possibly he can get more
information about the erroneous process by means of BS2000 tools for
diagnosis.
POS2204
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS2204 Task with TSN (&00) is no POSIX process. No further information available
Response
Inform system administrator, please. Possibly he can get more
information about the erroneous task by means of BS2000 tools of
diagnosis.
POS2800
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS2800 Diagnostic tool of subsystem POSIX creates a system dump
POS2900
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2900 The account number for rlogin could not be inserted into the user data
POS2901
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS2901 The user 'TSOS' has not been privileged as root
POS2902
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS2902 The userid does not exist
POS2903
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2903 The home directory could not be inserted into the POSIX user data
POS2904
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2904 The group number could not be inserted into the POSIX user data
POS2905
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2905 The program name could not be inserted into the POSIX user data
POS2906
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2906 Command 'ADD-POSIX-USER' processed without error
POS2907
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2907 The home directory exists. Its attributes have not been changed
POS2950
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2950 POSINST: Invalid procedure parameter '(&00)'
POS2951
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2951 POSINST: File '(&00)' not found or not accessible
POS2952
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2952 POSINST: Permission denied
POS2953
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2953 POSINST: Another instance of the POSIX installation tool is already running
POS2954
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2954 POSINST: Cannot load installation program
POS2955
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2955 POSINST: Fatal error in installation program
POS2956
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2956 POSINST: Installation program reports error at (or after) line '(&00)' of input file '(&01)'
Meaning
More detailed information is written to the POSIX file
'/var/sadm/pkg/insterr' (except of first installation).
POS2957
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS2957 POSINST: Timeout on wait for POSIX reboot. File '(&00)' is locked
POS3000
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3000 Error during check of tasks connected to subsystem POSIX
Meaning
Error during check of task state (program or task termination?) by means
of $EZRTSW (see SERSLOG file for error code).
POS3001
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3001 INIT PROCESS TERMINATED BY BS2000 SHUTDOWN
Meaning
The INIT process has been terminated by BS2000 shutdown.
POSIX termination continues without the INIT process.
POS3002
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3002 The command /HOLD-SUBSYSTEM POSIX is not allowed
Meaning
The command has been rejected by the subsystem without any effect.
The POSIX session is continued (new applications of POSIX may be
started).
POS3003
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3003 POSIX is terminated abnormally, because init process does not exist
Meaning
During regular termination init process has been terminated before
the necessary termination actions; therefore the subsystem is
terminated abnormally.
POS3004
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3004 Error during check of connected tasks
Meaning
The subsystem information function $ESMSWS returns an error code (see
SERSLOG file). the subsystem termination is continued in the abnormal
mode, if possible.
POS3007
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3007 Wait on init process interrupted. POSIX termination continues in abnormal mode
POS3008
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3008 Regular termination of POSIX timeout. The subsystem is still in use. New connections are not possible
Meaning
The time defined in POSIX parameter file as wait time for rc0 scripts
has run out. The subsystem termination has been interrupted.
The subsystem may be used furthermore by tasks already connected.
Response
No reaction necessary. The subsystem administrator may force the
termination by calling the command /STOP-SUBSYSTEM with parameter
SUBSYSTEM-PARAMETER='FORCED-BY-SUBSYSTEM'.
POS3009
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3009 Regular termination of POSIX interrupted because the subsystem is still in use. New connections are not possible
Meaning
During the subsystem private CLOSE-CONTROL routine the check of
tasks still connected to the subsystem was positive; therefore
the subsystem termination has been interrupted. The subsystem may
be used furthermore by tasks already connected to the subsystem.
Response
No reaction necessary. The subsystem administrator may force the
termination by calling the command /STOP-SUBSYSTEM with parameter
SUBSYSTEM-PARAMETER='FORCED-BY-SUBSYSTEM'.
POS3010
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3010 Subsystem POSIX has been terminated
POS3011
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3011 Normal POSIX termination during BS2000 shutdown
Meaning
Init process has been terminated during shutdown. POSIX is terminated by
force afterwards.
POS3012
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3012 Error occurred during POSIX termination (reboot of initial installation)
Meaning
Reboot interrupted.
POS3013
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3013 Error occurred on erase of generic root file system (copy under userid 'SYSROOT') during initial installation
Response
Inform the system administrator, please.
POS3014
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3014 Forced termination of POSIX initiated automatically
Meaning
After interrupt of regular subsystem termination forced termination has
been initiated due to parameter 'FORCEDTERM' in POSIX parameter file.
POS3015
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3015 Subsystem private STOP-COMMISSION routine has been processed (POSIX termination during BS2000 shutdown)
POS3016
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3016 Error during check of subsystem status of POSIX
POS3018
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3018 Wait for POSIX termination interrupted. Shutdown continues
POS3019
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3019 Wait for forced POSIX termination interrupted; shutdown continues
POS3020
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3020 New processes are created by fork() in spite of POSIX termination
Meaning
Wait on processing of fork calls has been interrupted. POSIX termination
is processed in the abnormal mode from now on.
POS3021
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3021 Wait on new processes created by fork has been interrupted (during abnormal POSIX termination)
Meaning
Wait on processes in state of creation (by fork) is interrupted.
POS3022
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3022 STOP-COMMISSION routine processed (forced POSIX termination during BS2000 shutdown)
POS3023
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3023 Wait for init process. POSIX termination continues
POS3024
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3024 SPOOL server has not been disconnected from POSIX subsystem during POSIX termination
Response
Inform the system administrator (to take a sled) please.
POS3025
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3025 At first call of command /STOP-SUBSYSTEM the operand SUBSYSTEM-PARAMETER= must not be used
Meaning
The operand SUBSYSTEM-PARAMETER= in command /STOP-SUBSYSTEM is
reserved for forced termination(as described in the manual).
POS3026
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3026 Wrong value of operand SUBSYSTEM-PARAMETER=
Response
Use the command /STOP-SUBSYSTEM SUBSYSTEM-NAME=POSIX,SUBSYSTEM-PARAMETER=
'FORCED-BY-SUBSYSTEM'.
POS3027
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3027 No operand SUBSYSTEM-PARAMETER= given in second call of command /STOP-SUBSYSTEM SUBSYSTEM-NAME=POSIX
POS3028
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3028 Invalid SUBSYSTEM-PARAMETER in command /START-SUBSYSTEM POSIX
Meaning
Valid SUBSTEM-PARAMETER operand values: 'CHECK-SYSTEM-FS' or
'CHECK-ALL-FS'.
POS3800
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3800 No disconnect of task (&00) from entry POSCALL because of an error
Meaning
See SERSLOG file for returncode supplied by interface $ESMDCN.
Response
Inform the system administrator, please.
POS3801
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3801 Error occurred during disconnection from POSIX subsystem
Meaning
Error during processing of $ESMDCN with parameter RETURN=DSL.
See SERSLOG file for error code.
POS3900
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3900 Termination of connected tasks during subsystem termination of POSIX
Meaning
STOP-COMMISSION routine (of subsystem POSIX) terminated the task.
POS3901
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3901 Abnormal task termination because of an error during subsystem termination
Meaning
Task terminated by POSIX private CLOSE-CONTROL routine.
POS3902
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3902 Task has been terminated normally in order to disconnect from the subsystem POSIX
POS3903
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3903 Abnormal task termination because of error during check of the task state during subsystem termination
Meaning
Task termination by STOP-COMMISSION routine.
POS3904
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3904 Abnormal task termination after panic()
POS3905
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3905 POSIX system server has terminated because of an error
POS3906
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3906 Abnormal task termination because of POSIX termination (task had been created by fork())
POS3907
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS3907 Rlogin rejected by system exit 030
POS4000
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4000 Termination of subsystem POSIX because of termination of a POSIX system process
POS4010
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4010 BS2000 file '(&00)' not found
Meaning
FSTAT for BS2000 file enden with error.
Response
FSTAT will be executed and error repaired.
POS4011
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4011 Error in READ/WRITE server
Meaning
A BS2000 macro returned an error.
The read/write server has been abnormally terminated.
Response
Contact the system administrator. The error record
has been written to the SERSLOG file.
POS4012
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4012 Error in OPEN/CLOSE server
Meaning
A BS2000 macro returned an error.
The open/close server has been terminated.
Response
Contact the system administrator. The error record has been written to
the SERSLOG file.
POS4013
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4013 Specified user id '(&00)' does not exist in HOME pubset
Meaning
No default pubset id could be found.
Response
Request the system administrator to join the user id to the system.
Reenter the 'mount' resp. 'umount' command.
POS4014
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4014 Filesystem '(&00)' could not be mounted due to protection of its container file
POS4015
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4015 Disk with container file of file system '(&00)' not available
Meaning
The disk with the mounted file system has been removed during
POSIX run (for example: /EXPORT-PUBSET, /DETACH-DEVICE).
Response
If you want to use the file system, the disk problem must be cleared
and POSIX has to be terminated and restarted.
POS4016
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4016 File system '(&00)' could not be mounted because its container file has been migrated
POS4017
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4017 File system '(&00)' could not be mounted because its container file has attribute BLKCTRL=*PAMKEY
Meaning
The container files of POSIX file systems must have BLKCTRL=*NO.
Response
Convert the container of the file system with PAMCONV and
retry the mount command.
POS4018
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4018 File system '(&00)' could not be mounted because pubset inaccessible or userid TSOS has the attribute ACCESS-CONTROL
POS4019
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4019 File system '(&00)' could not be mounted because its container file has been locked
POS4030
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4030 fsmond: WARNING! (&00)% allocation exceeds warn limit ((&01)%) on file system '(&02)'
Meaning
allocation exceeds warn limit
(&00) - actual allocation
(&01) - warn limit
(&02) - name of file system ('/' or '/var')
Response
delete files
POS4031
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4031 fsmond: ATTENTION! (&00)% allocation exceeds error limit ((&01)%) on file system '(&02)'
Meaning
allocation exceeds error limit
(&00) - actual allocation
(&01) - error limit
(&02) - name of file system ('/' or '/var')
Response
delete files and reply by answer tsn.ETX
POS4051
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4051 Error in SOCKET/XTI server
Meaning
A BS2000 macro has been executed with error.
The SOCKET/XTI server has been terminated abnormally.
Response
Contact the system administrator.
The error record has been written to SERSLOG file.
POS4100
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS4100 INIT: (&00)
Meaning
Message announced by init process.
POS5000
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5000 Error occurred during panic() processing (subsystem deletion could not be initiated)
Meaning
$ESMDEL (privileged interface for subsystem termination) returned
error (see SERSLOG file). Possible reasons are: subsystem is already
in termination, caller error or error during processing of $ESMDEL.
Response
Inform the system administrator, please.
POS5001
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5001 No rlogin possible because of overload of job class
POS5002
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5002 No rlogin possible due to memory shortage
POS5003
Destination: CONSOLE Routing code: C Weight: 99
Warranty : NO
POS5003 Termination of holder task because of severe error during POSIX start
POS5004
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5004 Initialization of subsystem POSIX has been interrupted because of an error
Meaning
Crash of the POSIX Holder Task succeeds in (DSSM) subsystem restart during
which the subsystem is not initialized completely. The init process cannot
start therefore. Use of the subsystem is not possible.
Response
After message ESM0220 terminate POSIX by command /STOP-SUBSYSTEM, please.
After termination of POSIX you can start again by command
/START-SUBSYSTEM (for instance with a new rep file).
POS5005
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5005 Container file of root file system does not exist (name of container file: see POSIX information file)
Meaning
None.
Response
Insert correct file name into information file, please.
POS5006
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5006 FSTAT error (container file of root file system)
Meaning
Returncode of FSTAT macro: see SERSLOG file.
POS5007
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5007 The root file system is not located under userid 'SYSROOT'
Meaning
For reasons of security the POSIX root file system must be located
under userid SYSROOT.
POS5008
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5008 No rlogin possible due to shortage of resources
POS5009
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5009 The name of the root file system in POSIX information file is invalid
Response
Insert correct name of root file system into POSIX information file.
POS5010
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5010 Connection error between UFS and READ/WRITE server
Meaning
A BS2000 macro returned an error.
Abnormal termination of POSIX subsystem.
Response
Contact the system administrator. The error record has been written into
the SERSLOG file.
POS5011
Destination: CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5011 Connection error between UFS and OPEN/CLOSE-Server
Meaning
A BS2000 macro returned an error.
Abnormal termination of POSIX Subsystem.
Response
Contact the system administrator. The error record has been written into
the SERSLOG file.
POS5100
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS5100 Internal error during fork() processing of son
Meaning
For details see the SERSLOG file.
Response
Start the program using fork() again later (especially in case of
system overload).
POS5200
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS5200 Task was terminated due to a signal
POS5201
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS5201 Wait for a lock has been interrupted by termination of process
Meaning
During POSIX termination processes waiting for a lock in vain are
terminated.
POS6010
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6010 BS2CP: BS2000 Source-files are defined with *BY-SOURCE
POS6011
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6011 BS2CP: BS2000 Source-library-elements are defined with *BY-SOURCE
POS6012
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6012 BS2CP: POSIX Source-files are defined with *BY-SOURCE
POS6013
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6013 BS2CP: More than one BS2000 target file indicated
POS6014
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6014 BS2CP: More than one BS2000 target library element indicated
POS6015
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6015 BS2CP: More than one POSIX target file indicated
POS6016
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6016 BS2CP: No POSIX directory indicated
POS6017
Destination: USER-TASK Routing code: Weight: 99
Warranty : NO
POS6017 BS2CP: BS2000 target file not defined with *BY-SOURCE
POS6018
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6018 BS2CP: SDF-Versions do not match - SDF-P-BASYS: (&00) SDF-P: (&01)
POS6019
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6019 BS2CP: Error during start of POSIX-Shell
POS6020
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6020 BS2CP: Error during execution of Shell-Command bs2cp; exit-Status = (&00)
POS6021
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6021 BS2CP: FILE-ATTRIBUTES indicated when copying from BS2000 to POSIX or working with PLAM elements
POS6022
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6022 BS2CP: Error during execution of Shell-Command bs2file; exit-Status = (&00)
POS6023
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6023 BS2CP: Error when using wildcard syntax
POS6024
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS6024 BS2CP: Invalid params when executing the /FILE-command for syntax check
POS6100
Destination: USER-TASK, CONSOLE Routing code: # Weight: 50
Warranty : NO
POS6100 '(&00)': CHANGE OF POSIX USER ID FROM '(&01)' TO '(&02)' SUCCEEDED
Meaning
(&00) - Command or function name, e.g. 'SU'
(&01) - Old user ID
(&02) - New user ID
POS6101
Destination: USER-TASK, CONSOLE Routing code: # Weight: 50
Warranty : NO
POS6101 '(&00)': CHANGE OF POSIX USER ID FROM '(&01)' TO '(&02)' FAILED
Meaning
(&00) - Command or function name, e.g. 'SU'
(&01) - Old user ID
(&02) - New user ID
POS9000
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS9000 POSIX '(&00)' '(&01)' '(&02)' Copyright (C) Fujitsu Technology Solutions 2009 All rights reserved.
Meaning
Start message of the POSIX shell
POS9001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS9001 The POSIX subsystem is not created
Response
Contact the system administrator.
POS9002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
POS9002 Start of /usr/bin/slogin failed
Meaning
/usr/bin/slogin in POSIX root file system is incorrect.
Response
Contact the system administrator.
POS9999
Destination: USER-TASK, CONSOLE Routing code: # Weight: 99
Warranty : NO
POS9999 (&00)