Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA000 Syntax analysis aborted
IMOA001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA001 Syntax analysis continues
IMOA002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA002 Too many syntax errors
IMOA020
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA020 Registration aborted
IMOA022
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA022 Registration successfully terminated
IMOA041
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA041 SHOW continues
IMOA100
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA100 Syntax error on IDF file (&00): file not readable
IMOA101
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA101 Syntax error on IDF file (&00): unknown format
IMOA102
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA102 Syntax error on file (&00): file not readable
IMOA104
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA104 Error in SOLIS2/IMON interface: unexpected movement file contents. Please contact the delivery responsible and provide installation definition file '(&00)' for diagnosis
IMOA200
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA200 Syntax error at line '(&00)': end of definition is missing
IMOA201
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA201 Syntax error at line '(&00)': '(&01)' '(&02)' '(&03)' does not identify valid devices
IMOA202
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA202 Syntax error at line '(&00)': operand '(&01)' not of specified type
IMOA203
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA203 Syntax error at line '(&00)': operand '(&01)' not within limits
IMOA204
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA204 Syntax error at line '(&00)': '(&01)' expected
IMOA205
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA205 Syntax error at line '(&00)': '(&01)'/'(&02)' expected
IMOA206
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA206 Syntax error at line '(&00)': '(&01)'/'(&02)'/'(&03)' expected
IMOA207
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA207 Syntax error at line '(&00)': '(&01)'/'(&02)'/'(&03)'/'(&04)' expected
IMOA208
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA208 Syntax error at line '(&00)': '(&01)'/'(&02)'/'(&03)'/'(&04)'/'(&05)' expected
IMOA211
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA211 Syntax error at line '(&00)': '(&01)'/'(&02)'/'(&03)'/'(&04)'/'(&05)'/'(&06)/' '(&07)'/'(&08)' expected
IMOA301
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA301 Registration of IUs from IDF file '(&00)' in user format
IMOA302
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA302 End of IDF has been reached
IMOA303
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA303 Following IUs are written in the SCI:
IMOA304
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA304 Registration of IUs from IDF generated by IMON
IMOA320
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA320 *** Error: installation unit '(&00)'((&01)(&02)) ***
IMOA321
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA321 *** Error: supply unit '(&00)'((&01)(&02)) ***
IMOA322
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA322 *** Warning: installation unit '(&00)'((&01)(&02)) ***
IMOA323
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA323 *** Warning: supply unit '(&00)'((&01)(&02)) ***
IMOA340
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA340 More than one SYSSII has been found
IMOA341
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA341 Duplicate installation unit found in IDF
IMOA342
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA342 Duplicate installation item '(&00)' found in IDF
IMOA343
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA343 Installation item '(&00)' not found in SYSSII
IMOA344
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA344 IU '(&00)'((&01)(&02)) in SYSSII does not describe current IU
IMOA345
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA345 IU '(&00)'((&01)(&02)) could not be written in SCI
IMOA347
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA347 Installation unit already existing in SCI
IMOA348
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA348 No item has been defined in the SYSSII (&00) or no item has been selected for specified BS2000/OSD version
IMOA349
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA349 Installation item '(&00)' has been created from installation item '(&01)'
IMOA350
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA350 Installation path '(&00)' has been chosen
IMOA351
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA351 Alternate installation path '(&00)' has been ignored
IMOA352
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA352 No SYSSII for this installation unit
IMOA353
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA353 Installation unit correction state ('(&00)') in SYSSII file does not match. Correction state taken from SYSSII file
IMOA354
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA354 Full filename attached to item ((&00)) defined with a partial filename
IMOA355
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA355 Partial filename attached to item ((&00)) defined with a full filename
IMOA356
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOA356 No installation path found for installation item '(&00)'
IMOBKPT
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOBKPT Diagnosis break-point (task-switch 11 ON). Continue with /RESUME-PROGRAM
Meaning
Task-switch "11" was ON.
IMON breaks after extraction of the installation files
in order to allow a modification of these ones.
Response
Enter /RESUME-PROGRAM to continue.
IMOCOPY
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOCOPY Copyright (C) (&00) (&01) All Rights Reserved
IMOLOAD
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOLOAD Program '(&00)', version '03.3B10' of '(&02)' loaded from file (&03)
IMOREVI
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOREVI COMP=IMOMF,VER=975,DATE=2013-05-17
IMOSTRT
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMOSTRT Procedure '(&00)', version '(&01)' of '(&02)' started from file (&03)
IMO0000
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0000 Internal error at line (&00) in file (&01)
Meaning
An internal error has been detected in IMON code
in source file (&01) at line (&00).
Response
Please contact the system administrator.
IMO0001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0001 Processing continues
IMO0100
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0100 Error when calling IMON TPR code. Return code: (&00)
Response
Please contact the system administrator.
IMO0103
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0103 Internal error at line (&00) in file (&01) when calling Pathname manager. Return code: (&02)
Meaning
An internal error has been detected in IMON code in source
file "(&01)" at line "(&00)" when calling the Pathname Manager.
Following error codes may appear:
- 10101 No enought memory space
- 1010F Bad VSN
- 10110 Bad device type
- 10111 Bad product version
- 10114 Duplicate logical-id
- 10115 Invalid RU attribute
- 10119 Bad unit name
- 1011F Bad target value
Response
Analyse the error code and take the appropriate reaction:
- Free memory space and retry,
- or correct input and retry,
- or contact the system administrator.
IMO0104
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0104 Invalid format for SCI: (&00)
Meaning
The SCI file (&00) has a wrong format.
Response
Please contact the system administrator.
IMO0105
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0105 Inconsistency detected between (&00) and (&01) SCIs. Processing continues
Response
Please contact the system administrator to
restore a correct state.
IMO0107
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0107 Completion of SCI (&00) successfully terminated
IMO0108
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0108 Completion of SCI (&00) abnormally terminated
IMO0109
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0109 Completion of SCI (&00) started
Meaning
At open time of the SCI, IMON detected an old or bad format
of the identification record. An automatic completion of the
SCI is started. This conversion may take a lot of time
depending on the size of the SCI to convert.
Response
Wait until end of the completion (IMO0107 bzw. IMO0108).
IMO0110
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0110 Processed SCI no more opened
Meaning
Completion of SCI stopped:
other task closed it or completion time expired.
Response
Open the SCI again.
IMO0200
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0200 Memory space exhausted
Meaning
A system error occurred when requesting memory space.
Response
Please contact the system administrator.
IMO0201
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0201 Invalid path name (&00)
Meaning
Possible reasons:
- The format of the path name contains an error.
More information can be found with /SHOW-FILE-ATTRIBUTES command.
- When placing SOLIS2 files, the userid where they are to be
catalogued does not exist.
- A system error occurred when completing file name.
- Completed file name is too long.
Response
- Please correct file name or contact the system administrator.
- Concerning the SOLIS2 userid error case, please contact the
system administrator to perform corresponding /ADD-USER command.
IMO0202
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0202 Unknown device type code: (&00)
Meaning
An error occurred when converting device type code into device name.
Response
Please contact the system administrator.
IMO0203
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0203 User is not allowed to issue the statement (&00)
Meaning
User has not the required privilege to issue the statement (&00).
IMO0204
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0204 Memory validation error
Meaning
A system error occurred when validating memory space.
Response
Please contact the system administrator.
IMO0205
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0205 Function not available
Meaning
The IMON(-GPN) subsystem is not available
or both TU and TPR parts of IMON-BAS are not compatible.
Response
Please contact the system administrator.
IMO0206
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0206 User is not allowed to see all information
Meaning
User has not the required privilege to see all information
(SUBSYSTEM-MANAGEMENT privilege).
IMO0207
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0207 Error occurred while writing on SYSLST. Return code: (&00)
Meaning
(4): Unrecoverable error.
(8): Operand error.
(12): The record to be written is truncated.
(16): No more memory space for the file assigned to SYSLSTn.
IMO0208
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0208 Error occurred while assigning SYSLST
IMO0209
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0209 Additional information may have been logged in file (&00)
IMO0210
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0210 Error occurred during synchronized batch processing
IMO0211
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0211 Error occurred during file(s) import with ARCHIVE or with SIR
IMO0213
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0213 Error when calling IMON RMS code. Return code: (&00)
Meaning
(&00): parameter error = 0x00 01 0003
not enough space = 0x00 40 0018
system error = 0x00 20 0100
internal error = 0x00 20 0101
function not supported = 0x00 01 FFFF
version of interface not supported = 0x00 03 FFFF
Response
Please contact the system administrator.
IMO0215
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0215 Error occurred while copying file (&00) to file (&01)
IMO0216
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0216 Installation-file (&00) could not be extracted from delivery medium
Meaning
Specified package name or user code is not correct or
format of the delivery not supported by current IMON version or
invalid descriptor-file format.
Response
Please correct package name or user code or
contact the system administrator to order a delivery in new format,
or use corresponding IMON version.
IMO0217
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0217 Error occurred while entering procedure (&00)
IMO0218
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0218 Error when calling the "(&00)" macro. Return code: (&01)
Response
Please contact the system administrator.
IMO0220
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0220 Error occurred during retrieval of delivery information
IMO0221
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0221 Version of generation procedure "(&00)" not supported by current IMON-BAS version
Meaning
Delivery in not supported old/new format was processed or
invalid file format.
Response
Contact the system administrator to order a delivery in correct format.
IMO0222
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0222 Syntax error on generation procedure (&00): unknown format
Meaning
Delivery in not supported old/new format was processed or
invalid file format.
Response
Contact the system administrator to order a delivery in correct format.
IMO0223
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0223 Error while processing correction procedure (&00). Processing continues
IMO0224
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0224 Error while processing IMON-BAS REP file (&00)
IMO0225
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0225 Version (&00) of generation procedure (&01) does not support target BS2000/OSD version (&02)
Meaning
Delivery in not supported old/new format was processed or
invalid file format or
invalid BS2000/OSD target version.
Response
Please correct BS2000/OSD target version or
contact the system administrator to order a delivery in correct format.
IMO0226
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0226 DMS error on pathname associated to the logical-id (&00) of the release unit (&01) (&02)
Response
Please contact the system administrator.
IMO0228
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0228 Too many supply units to process for a non-standard installation
Meaning
Due to some technical restrictions in FHS, it is not possible
to install more than 30 supply units at once with "Placement
mode" non standard.
Response
Process non-standard installation stepwise.
IMO0229
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0229 System error (probably memory space exhausted) when calling IMOKIT function
Response
Extend TSOS user address space to at least 32 MB and
start again the registration procedure or
contact the system administrator.
IMO0230
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0230 Invalid format in installation parameter file ((&00))
Response
Check format of the parameter file, correct it adequately
and start again the installation process.
IMO0231
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0231 Syntax error in "****DSSM-CAT" record
Response
Correct syntax is "****DSSM-CAT <catalog-name>" where
<catalog-name> = <filename_1..48_without_catid>
IMO0232
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0232 Syntax error the following "****SU" record: ((&00))
Response
Correct syntax is "****SU <SU-name> <userid>" where
<SU-name> = supply unit name Text_1..30
<userid> = name_1..8
IMO0233
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0233 Subsystem (&00) V(&01) currently started. Stop it before continuing deinstallation
IMO0234
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0234 ========== Deinstallation switched to "non-execution" mode ==========
IMO0235
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0235 file (&00) removed from (&01)
IMO0236
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0236 Subsystem (&00) removed from SDF parameter file (&01)
IMO0237
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0237 Subsystem (&00) V(&01) removed from catalog (&02)
IMO0238
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0238 DSSM catalog (&00) cannot be saved. Statement may be retried with ENFORCE=YES
IMO0239
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0239 DSSM catalog (&00) cannot be opened
IMO0240
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0240 Error during CHECK of DSSM catalog (&00)
IMO0241
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0241 Supply unit (&01) version (&02)(&03) (from package (&00)) removed
IMO0242
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0242 Supply unit (&00) removed from (&01)
IMO0243
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0243 IU (&00) version (&01)(&02) removed
IMO0244
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0244 File (&00) deleted
IMO0245
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0245 ========== Deinstallation performed with EXECUTION=*NO: ==========
IMO0246
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0246 MSG file (&00) cannot be deactivated
IMO0247
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0247 (&00) filename too long
IMO0248
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0248 Some target filenames for saving function are too long
IMO0249
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0249 Input conflict: prefix specified but saving with prefix not requested
IMO0250
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0250 Input conflict: file saving not allowed with "Direct Execution = No" or EXECUTION=*NO
IMO0251
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0251 "(&00)" is not a valid prefix for files to be saved
Meaning
Either the specified catid/userid is not accessible or the entered
prefix completed with catid/userid exceeds 16 characters (completion
value for userid is $.).
Response
Correct input
IMO0252
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0252 Message file (&00) removed from MIP parameter file (&01), when present
IMO0253
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO0253 Error occurred during deinstall process. Additional information logged in file '(&00)'
IMO0254
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0254 Message file (&00) deactivated from current system
IMO0255
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0255 Info about already delivered product(s) necessary for the correct installation of the present delivery not found in the SCI. See "(&00)" for more details
Meaning
IMON did not find in the SCI information about previous
delivered products which are mandatory to guarantee the correctness
of the current installation process.
The generated .HI file contains the list of these products with
version and the package name in which they were delivered.
Response
Please, check if the products referenced in the .HI file
are really installed. When yes, reply "2" to the error message
to continue the current delivery process, otherwise reply "1"
to abort the current delivery process and install first the
missing product(s) before to install again the current one(s).
IMO0256
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0256 Park location cleared using procedure (&00)
IMO0257
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0257 ========== UNDO-SUPPLY-UNITS performed with EXECUTION=*NO: ==========
IMO0258
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0258 Subsystem (&00) added in SDF parameter file (&01)
IMO0259
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0259 Invalid record format in file (&00)
IMO0260
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0260 File (&00) to be restored
IMO0261
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0261 ========== UNDO switched to "non-execution" mode ==========
IMO0262
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0262 DMS error (&00) on file (&01) to be activated. Further information: /HELP-MSG DMS(&00)
IMO0263
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0263 File (&00) to be activated does not exist
IMO0264
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0264 Syntax file (&00) added in SDF parameter file (&01) for subsystem (&02)
IMO0265
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0265 Message file (&00) added in MIP parameter file (&01)
IMO0266
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0266 DSSM catalog (&00) updated with SYSDTA "((&01),SU.SSCM,X)"
IMO0267
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0267 Error occured during UNDO batch process. Additional information logged in file (&00)
IMO0268
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0268 RMS file (&00) removed from RMS Depot. Corresponding SYSREP is generated
IMO0269
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0269 RMS file (part of SYSREP.BS2LADER) (&00) removed from RMS-Depot
IMO0270
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0270 SYSREP.BS2LADER. must be MANUALLY re-generated as following SYSRMS are removed:
IMO0271
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0271 Error occured during UNDO SSCM batch process. Additional information logged in file (&00)
Response
When the problem is due to an error in an SSCM statement this can
be mannually corrected or bypassed by updating the SSCM SYSDTA file
(file suffixed with '.DT') and retry the SSCM batch process
execution.
This is necessary in order to execute the following
SSCM statements.
IMO0272
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0272 Product (&00) version (&01) logical-id (&02) Target (&03) not found in GPN SCI (&04)
Meaning
IMON did not find the correspondence of an item of its SCI
and the associated information in the IMON-GPN SCI.
The problem is probably due to inconsistencies between the SCI
of IMON and the one of IMON-GPN.
Response
Restore the last correct state of the SCI using the /RESTORE-
SOFTWARE-INVENTORY command.
IMO0273
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0273 SU (&01) version (&02)(&03) (from package (&00)) in status "(&04)" removed
IMO0274
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0274 Package (&00) with user code (&01) removed
IMO0275
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0275 Error occured during UNDO SU GEN batch process. Additional information logged in file (&00)
IMO0276
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0276 Length of current SCI name does not allow //SAVE-SOFTWARE-INVENTORY TO-SCI=*STD
Meaning
Completion of current SCI name with <.YYYYMMDDhhmmss> leads to
a too long name.
Response
Use an explicit specification for the TO-SCI operand.
IMO0277
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0277 Old SCI contents will be restored (SU.GEN procedure)
IMO0278
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0278 Entered SCI name (&00) has no associated GPN file (.GPN)
IMO0279
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0279 Invalid identification record in the IMON parameter file: "(&00)"
Meaning
First record must be "*** IMON INSTALLATION PARAMETERS ***".
IMO0280
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0280 Syntax error at line (&00)
IMO0281
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0281 Error occurred while deleting file (&00)
IMO0282
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0282 POSIX file (&00) deactivated from current system
IMO0283
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0283 POSIX UNDO processing started for SU (&00)
IMO0284
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0284 Error occured during POSIX UNDO batch process. Additional information logged in file (&00)
IMO0285
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0285 The remove/add of POSIX products will be processed at next POSIX subsystem START. Requested actions are registered in $SYSROOT.IMON.ACTIONS.REM/ADD
IMO0286
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0286 File (&00) deleted if existing
IMO0287
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0287 Message file (&00) activated
IMO0300
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0300 DMS error (&00) on opening file (&01). Further information: /HELP-MSG DMS(&00)
IMO0301
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0301 DMS error (&00) on closing file (&01). Further information: /HELP-MSG DMS(&00)
IMO0302
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0302 DMS error (&00) on writing into file (&01). Further information: /HELP-MSG DMS(&00)
IMO0303
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0303 DMS error (&00) on reading from file (&01). Further information: /HELP-MSG DMS(&00)
IMO0304
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0304 DMS error (&00) on positioning into file (&01). Further information: /HELP-MSG DMS(&00)
IMO0305
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0305 File (&00) not catalogued
IMO0306
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0306 DMS error (&00) on file (&01). Further information: /HELP-MSG DMS(&00)
IMO0307
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0307 DMS error (&00) on deleting file (&01). Processing continues
IMO0308
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0308 DMS error (&00) when accessing file (&01). Further information: /HELP-MSG DMS(&00)
IMO0310
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0310 DMS error (&00) when saving file (&01) to (&02). Further information: /HELP-MSG DMS(&00)
IMO0311
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0311 Initialisation of LMSUP failed. Return Code: (&00)
IMO0312
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0312 Failed to add file (&00) as element "(&01)/(&02)" of type (&03) in library (&04). Further information: /HELP-MSG (&05)(&06)
IMO0313
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0313 Failed to select element '(&00)/(&01)' of type '(&02)' in library (&03) as file (&04). Further information: /HELP-MSG (&05)(&06)
IMO0400
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0400 Interface error. Statement unknown
IMO0401
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0401 SDF return code "(&00)" encountered (at line (&01) in IMON code). Statement abnormally terminated
Meaning
SDF return code received after a SDF call:
RC 60 : Program name not found due probably to an invalid
activated IMON syntax file.
RC 16 : //END statement missing.
Further information for other returned values may be found
in the SDF-A manual (CMDRST function).
Response
Activate correct syntax file of IMON-BAS or contact the
system administrator.
IMO0402
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0402 Installation unit (&00) version (&01) correction state (&02) is duplicate in list
IMO0403
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0403 Installation unit '(&00)' version '(&01)' correction state '(&02)' does not exist
IMO0404
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0404 Internal error. Total length of inserts too long for message "IMO(&00)"
Response
Please contact the system administrator.
IMO0405
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0405 Internal error. Report string too long
Response
Please contact the system administrator.
IMO0406
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0406 Statement abnormally terminated
IMO0407
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0407 Error on modifying the SCI. Skip back to previous correct one '(&00)' performed
IMO0408
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0408 Dialog not allowed in batch mode
IMO0409
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0409 No unit selected. Function not processed
IMO0410
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0410 Formatted file needed as input when OUTPUT=*INPUT-FORMATTED-FILE
IMO0411
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0411 Entered SCI name does not correspond to a standard SCI name. Processing continues
IMO0412
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0412 Item '(&00)' version '(&01)' of unit '(&02)' version '(&03)' correction state '(&04)' does not exist
IMO0413
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0413 Item '(&00)' version '(&01)' of unit '(&02)' version '(&03)' correction state '(&04)' is duplicate in list
IMO0414
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0414 '(&00)' is not a valid correction state
IMO0415
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0415 Statement //SWITCH-TO-FHS cannot be given in batch mode. Statement skipped
IMO0416
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0416 Starting FHS is not possible
IMO0417
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0417 '(&00)' is not a valid work file location
Meaning
Either the specified catid/userid is not accessible
or the prefix part (inclusive ending dot) exceeds 7 characters.
Response
Correct input
IMO0418
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0418 No item selected. Function not processed
IMO0420
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0420 Error occurred while inserting command '(&00)' on SDF stack
IMO0421
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0421 Supply unit '(&00)' version '(&01)' correction state '(&02)' is duplicate in list
IMO0422
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0422 Supply unit '(&02)' version '(&03)' correction state '(&04)' of package '(&00)' and user code '(&01)' does not exist
Meaning
In case of installation from registered or with REPLACE=*EXTEND, it may
also signify that the specified supply unit is not in a state allowing
an installation (e.g already "Installed" or "Being Installed").
IMO0423
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0423 Delivery corresponding to package '(&00)' and user code '(&01)' does not exist
IMO0424
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0424 '(&00)' is not a valid unit name
Meaning
The name '(&00)' is not a valid <unit-name>.
IMO0425
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0425 Supply unit '(&00)' version '(&01)' correction state '(&02)' does not exist
IMO0426
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0426 "(&00)" is not a valid BS2000/OSD version
IMO0427
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0427 Invalid userid '(&00)'
IMO0428
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0428 A delivery coming from a library cannot be parked
IMO0429
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0429 BS2000/OSD-BC version '(&00)' is not supported
IMO0430
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0430 No supply unit to process
Meaning
Empty delivery or all supply units have already been processed
or supply units to install with "customer-approved" feature
do not contain any delta items.
IMO0431
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0431 Hardware selection "(&00)" not allowed for this BS2000/OSD target version
Meaning
Only the following combinations are allowed:
- "*SPARC", "*CISC", "*ANY" or "*STD" for BS2000/OSD V5.0 to V7.0
- "*SPARC", "*CISC", "*X86", "*ANY" or "*STD" from BS2000/OSD V8.0
Response
Adapt hardware selection to target BS2000/OSD version.
IMO0432
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0432 Error: Saving with MAREN not possible for the current delivery
Meaning
The current delivery is too old (format < IMON V2.6) to support a save
using MAREN.
Response
Save with LMS/LMSCONV or ARCHIVE, or renounce to save.
IMO0433
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0433 ERROR DURING PROCESSING. 0=REPEAT, 1=ABORT, 2=IGNORE
Meaning
Error occured during processing.
Response
0 - Error eliminated; repeat step.
1 - Processing is aborted.
2 - Error is ignored. Processing continues.
IMO0434
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0434 Error: ARCHIVE not present. Saving with ARCHIVE not possible
Response
Save with LMS/LMSCONV or renounce to save.
IMO0435
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0435 Supply unit '(&00)' V(&01)(&02) may not be deinstalled
Meaning
Only supply units with status "INSTALLED" or "PARKED" may be deinstalled.
Response
Use "remove"-function if you want to clean the SCI.
IMO0436
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0436 Error: '(&00)' function only allowed in standard SCI
Response
Open a standard SCI (:<catid>:$TSOS.SYS.IMON.SCI).
IMO0437
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0437 Supply unit '(&00)' V(&01)(&02) may not be removed
Meaning
Only supply units with status different from "INSTALLED" or "PARKED"
may be removed.
Response
Use "deinstall"-function if you want to clean the SCI.
IMO0438
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0438 Supply unit '(&00)' version '(&01)' correction state '(&02)' may not be deinstalled
Meaning
The version and/or correction state specified for the supply unit
is ambiguous in regards to the SCI contents or there exists
in the SCI at least a lower one that must be previously deinstalled.
Response
Clarify version and/or correction state specification.
IMO0439
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0439 Supply unit '(&00)' version '(&01)' correction state '(&02)' may not be deinstalled
Meaning
The keyword *LOWEST-EXISTING or *EXCEPT-HIGHEST-EXISTING
may not be used if only one value in the SCI corresponds to the selection.
Response
Clarify version and/or correction state specification.
IMO0440
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0440 ERROR DURING PROCESSING. 0=SKIP, 1=ABORT, 2=IGNORE
Meaning
Error occured during processing.
Response
0 - Skip step.
1 - Processing is aborted.
2 - Error is ignored. Processing continues.
IMO0441
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0441 Package name '(&00)' user code '(&01)' duplicate in list
IMO0442
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0442 A user code different of "*ALL" cannot be specified with "PACKAGE-NAME=*BY-DIALOG"
IMO0443
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0443 UNDO cannot be performed for supply unit '(&00)' V(&01)(&02)'
Meaning
UNDO can be made only for supply units with status "INSTALLED".
Response
Use "remove"-function if you want to clean the SCI.
IMO0444
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0444 Warning: UNDO function not possible in the current system environment. UNDO request skipped
Meaning
The current installation environment does not allow an UNDO function:
- either because EDT was not found on the system ($.EDT nor $TSOS.EDT)
- or because the delivery is too old (format < IMON V2.5 or format <
IMON V2.7) for saving with LMS/LMSCONV.
IMO0445
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0445 Only one version of the supply unit '(&00)' can be selected for UNDO
Meaning
The UNDO is only possible for the latest installed version of each SU.
Response
Perform again the selection with the relevant SU version.
IMO0446
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0446 Selected supply unit '(&00)' differs from supply unit '(&01)' '(&02)' '(&03)' referenced in UNDO library '(&04)'
IMO0447
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0447 Selected supply unit '(&00)' '(&01)' '(&02)' '(&03)' '(&04)' differs from supply unit '(&05)' '(&06)' '(&07)' '(&08)' '(&09)' referenced in UNDO library '(&10)'
IMO0448
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0448 Warning: FILE-SAVING not allowed with "EXECUTION=*NO". Operand ignored
IMO0449
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0449 Error: MAREN not present. Saving with MAREN not possible
Response
Save with LMS/LMSCONV or ARCHIVE, or renounce to save.
IMO0450
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0450 Warning: ACTIVATION-SCOPE=*PERMANENT no more supported. Use new //ACTIVATE-UNITS function
Meaning
This functionality is no longer supported from IMON V2.6A.
Response
For direct activation of products, use the //ACTIVATE-UNITS statement.
IMO0451
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0451 No version of the unit '(&00)' is activable or matches the SELECT filter
IMO0452
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0452 Unit '(&00)' version '(&01)' correction state '(&02)' does not match the "SELECT" filter
IMO0453
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0453 Value "*BY-SUPPLY-UNIT" must be specified for both PACKAGE-NAME and USER-CODE operands
Response
Keyword "*BY-SUPPLY-UNIT" must be obligatory specified for both
PACKAGE-NAME and USER-CODE operands.
IMO0454
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0454 Warning: Supply unit '(&00)' V(&01)(&02) has no "INSTALLED" status. GENERATE-IDF not allowed, supply unit skipped
IMO0455
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0455 No complete package record found in the SCI. Function "INSTALL-FROM-SCI" not possible
Meaning
The function "INSTALL-FROM-SCI" is only possible from an SCI
where at least 1 package with all its installation environment
is present.
IMO0456
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0456 Warning: Supply unit '(&00)' version "(&01)(&02)" empty
Meaning
Empty supply unit may not be installed using the
"*FROM-SCI" or "*CUSTOMER-APPROVED" feature.
IMO0457
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0457 SU '(&00)' version '(&01)' correction state '(&02)' package name '(&03)' user code '(&04)' not activable
IMO0458
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0458 Error: ARCHIVE not present. Saving for UNDO with ARCHIVE not possible
Response
Check if saving with LMS/LMSCONV may be possible,
renounce to UNDO option or install ARCHIVE.
IMO0459
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0459 Entered reference file name does not correspond to a standard Reference File name. Processing continues
IMO0460
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0460 Warning: Configuration Check function not possible in current system environment. Function ignored
Meaning
The current installation environment does not allow a Configuration
Check function because the delivery is too old (format < IMON V2.7).
IMO0461
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0461 Error during modification of the reference file. Recovery of '(&00)' attempted
IMO0462
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0462 No object corresponding to selection parameters found. Function not processed
IMO0463
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0463 Warning: POSIX processing not possible in current system environment. Function ignored
Meaning
The current installation environment does not allow a POSIX processing
because the delivery is too old (format < IMON V2.8).
IMO0464
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0464 Warning: POSIX processing not possible in current system environment. Function ignored
Meaning
The current system environment does not allow a POSIX
installation processing because no POSIX configuration
file for IMON exists.
Response
To allow IMON-POSIX installation features, a configuration file
$SYSROOT.POSIX.CONFIGURATION must exist on the target system.
IMO0465
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0465 SU '(&00)' version '(&01)' correction state '(&02)' package name '(&03)' user code '(&04)' not checkable because not "installed"
IMO0466
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0466 Unit '(&00)' version '(&01)' correction state '(&02)' does not match *LAST-INSTALLED selection
IMO0467
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0467 Failed to create output variable. (&00) returns code (&01)
IMO0468
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0468 Syntax error in variable name
IMO0469
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0469 Variable does not exist
IMO0470
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0470 Variable must be a list of type 'STRUCTURE'
IMO0472
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0472 Warning: Supply unit '(&00)' version "(&01)(&02)" is not complete. Supply unit skipped.
Meaning
Incomplete supply unit may not be "INSTALLED-FROM-SCI".
Response
Some installation units contained by the original supply unit
structure are no more registered.
IMO0473
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0473 ERROR DURING PROCESSING. 1=ABORT, 2=IGNORE
Meaning
Error occurred during processing.
Response
1 - Processing is aborted.
2 - Error is ignored. Processing continues.
IMO0474
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0474 PROCESSING TO BE CONTINUED ? 1=ABORT, 2=CONTINUE
Response
1 - Processing is aborted.
2 - Processing continues.
IMO0500
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0500 Wrong SYSSII format for file (&00)
Meaning
The file '(&00)' has not the format of a SYSSII file.
Response
Regenerate a SYSSII file with same name or use another SYSSII file.
IMO0501
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0501 Invalid SYSSII file name (&00)
Meaning
The file name '(&00)' is not of type
<filename-without-generation-version>.
Response
Correct SYSSII file name.
IMO0510
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0510 (&00) operand value (&01) not supported
Meaning
The specified value is not supported by the GEN procedure
supplied in the SOLIS delivery
Response
Please specify a value matching the used GEN procedure or
request a SOLIS delivery with GEN procedure for the current
IMON version.
IMO0600
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0600 FHS error. Subcode 1 = '(&00)'. Subcode 2 = '(&01)'. Main code = '(&02)'. Msg Id = '(&03)'
Meaning
A FHS error occurred when giving a FHS macro.
The text of the macro is given in next message.
Main code '204002' means:
A wrong VTSU version (too low)
A wrong VTSU version on remote host (OMNIS call)
VTSU message file not activated
Response
Please contact the system administrator.
IMO0601
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0601 A FHS error occurred when giving macro '(&00)'
IMO0602
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0602 "(&00)" is not a valid file name. Re-enter correct file name or cancel input
IMO0603
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0603 "(&00)" is not a valid SYSLST number. Re-enter correct SYSLST number or cancel input
IMO0604
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0604 Invalid park location
Meaning
Correct syntax is <:catid:><$userid>
IMO0605
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0605 Formatted file name cannot be filled when output in a formatted file is not asked
IMO0606
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0606 Write-mode must be given when output in formatted file is requested
IMO0607
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0607 Write mode cannot be given when output in a formatted file is not asked
IMO0608
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0608 Contradictory inputs
Response
Correct input.
IMO0609
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0609 A version must be explicitly given when 'Other' has been chosen as version
IMO0611
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0611 A unit name must be explicitly given when 'Other' has been chosen as unit name
IMO0612
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0612 '(&00)' is not a valid version. Re-enter correct version or cancel input
IMO0614
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0614 A correction state must be explicitly given when 'Other' has been chosen as correction state
IMO0615
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0615 '(&00)' is not a valid item name. Re-enter correct item name or cancel input
IMO0616
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0616 One or several selected units do not exist anymore. Re-enter your selection
IMO0617
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0617 This field is mandatory
IMO0618
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0618 Item '(&00)' does not exist in SCI
IMO0619
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0619 SCI '(&00)' cannot be opened
Meaning
It is not possible to open the specified file name as SCI.
Possible reasons:
The file is locked
The file does not correspond to an SCI
Space saturation on the system
Invalid specified file name
Response
Check file name or contact system administrator.
IMO0620
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0620 Formatted file name is mandatory when output in a formatted file is asked
IMO0621
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0621 '(&00)' is not a valid unit name. Re-enter correct unit name or cancel input
IMO0622
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0622 Error while '(&00)' link name. FHS interface abnormally terminated
IMO0623
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0623 DMS error '(&00)' on FHS library '(&01)'. Further information: /HELP-MSG DMS(&00). FHS interface abnormally terminated
IMO0624
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0624 Command '(&00)' unknown, ignored by application
IMO0625
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0625 No pattern defined
Meaning
A pattern must be defined to use Search function or
F5/F6 can only be used when it is searched for a pattern.
Response
Please define pattern or use F7/F8.
IMO0626
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0626 No matching pattern
IMO0627
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0627 Invalid pattern. Re-enter correct pattern or cancel input
IMO0630
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0630 Invalid package name. Re-enter correct package name or cancel input
IMO0631
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0631 Invalid user code. Re-enter correct user code or cancel input
IMO0632
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0632 Tape identification cannot be given when distribution medium is not "SOLIS2/Local volume"
IMO0633
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0633 Tape identification must be given when distribution medium is "SOLIS2/Local volume"
Meaning
Tape identification: (VSN, volume-type)
- for SOLIS2 medium as specified in the delivery notice
- for local volume medium use as at copy time.
IMO0634
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0634 (&00): invalid volume. Re-enter correct volume or cancel input
IMO0635
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0635 (&00): invalid device type. Re-enter correct device type or cancel input
IMO0636
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0636 '(&00)' is not a valid work file location. Re-enter correct work file location or cancel input
Meaning
Possible reasons:
- Entered value is syntactically incorrect:
correct syntax is: <partial-filename 2..23>.
- Entered value is syntactically correct but not usable
(e.g. pubset not accessible, User-id not defined,...).
Response
Correct input or suppress origin of error.
IMO0637
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0637 A catid has to be given when standard pubset equals 'Other'
IMO0638
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0638 A catid cannot be given when standard pubset is 'Default'
IMO0639
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0639 '(&00)' is not a valid catid. Re-enter correct catid or cancel input
IMO0640
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0640 The location of the RMS depot has to be given when choice of REP processing is 'Yes'
IMO0641
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0641 The only allowed values are '2' and '3'
Meaning
Selection does not contain any SYSREP file.
IMO0642
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0642 Tape identification has to be given when saving old files with ARCHIVE
IMO0643
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0643 Tape identification cannot be given when old files are not saved with ARCHIVE
IMO0644
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0644 Name of password file has to be given
IMO0645
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0645 Password fields may not be given with "Passwort file = 2 (No)"
IMO0646
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0646 Given read password is not valid. Re-enter correct read password or cancel input
IMO0651
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0651 "(&00)" is not a valid RMS depot location. Re-enter correct RMS depot location or cancel input
IMO0652
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0652 "(&00)" is not a valid BS2000/OSD-BC version. Re-enter correct BS2000/OSD-BC version or cancel input
IMO0653
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0653 File does not exist. Correct filename or select "Generation File = New"
IMO0654
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0654 The only allowed values are "Y" and "N"
IMO0656
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0656 Invalid userid: (&00). Re-enter correct userid or cancel input
IMO0657
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0657 Invalid prefix: (&00). Re-enter correct prefix or cancel input
Meaning
Entered prefix should match SDF-Type "full-filename-1..8"
,i.o. it must contain at least one letter.
IMO0658
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0658 Invalid combination of userid '(&00)' and prefix '(&01)'. Re-enter correct userid and prefix or cancel input
Meaning
Userid must be explicitely given when a prefix is specified.
IMO0659
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0659 The only allowed values are "Y", "N" and "M"
IMO0660
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0660 A userid must be explicitly given when 'Other' has been chosen as Userid
IMO0661
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0661 DMS error '(&00)' on delivery library '(&01)'. Further information: /HELP-MSG DMS(&00)
Meaning
Specified package name or user code is not valid or
library does not exist.
Response
Please correct package name or user code or
contact the system administrator.
IMO0662
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0662 '(&00)' is not a valid partial file name. Re-enter correct save file location or cancel input
IMO0663
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0663 This field is mandatory when the other corresponding one is given
IMO0664
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0664 '(&00)' is not a valid prefix. Re-enter correct prefix or cancel input
IMO0665
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0665 A SCI name has to be given when choice of SCI is 'Other'
IMO0666
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0666 A SCI name cannot be given when choice of SCI is 'Std'
IMO0667
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0667 '(&00)' is not a valid location. Re-enter correct location or cancel input
Meaning
Possible reasons:
- Entered value is syntactically incorrect:
correct syntax is: <partial-filename 2..23>.
Response
Correct input.
IMO0668
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0668 The only allowed values are "A", "C" and "N"
IMO0672
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0672 Invalid field
IMO0673
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0673 Field must not be filled
IMO0675
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0675 Supply unit '(&00)' version '(&01)' correction state '(&02)' of package '(&03)' and user code '(&04)' set to "Customer Approved"
IMO0679
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0679 (&00) parameter value (&01) not supported
Meaning
The value preset in the IMON parameter file is not supported
by the GEN procedure supplied by the SOLIS delivery
Response
Please change the parameter to a value compatible to the
used GEN procedure or request a SOLIS delivery with a GEN
procedure for the current IMON version.
IMO0680
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0680 The only allowed values are "A" and "N"
Meaning
The GEN procedure supplied by the SOLIS delivery does only
support the values "A" and "N".
Response
Please change the parameter to "A" or "N" or request a SOLIS
delivery with a GEN procedure compatible to the current IMON
version.
IMO0681
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0681 IMON default for Posix processing changed from "Cfg" to "All"
Meaning
The GEN procedure supplied by the SOLIS delivery does only
support the values "All" and "No". Therefore the IMON default
has been changed to "All" and only "All" or "No" can be selected.
Response
Please select either "All" or "No" or request a SOLIS delivery
with a GEN procedure compatible to the current IMON version
IMO0700
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0700 File (&00) is not a formatted file
Meaning
The formatted file specified as input or output file
is not a valid formatted file.
Response
Regenerate a formatted file with same name or use another one.
IMO0701
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0701 Not enough information in the specified input formatted file to process the SHOW statement
IMO0750
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0750 Job '(&00)' has been generated and must be manually entered with the /ENTER-PROCEDURE command
IMO0751
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0751 Job '(&00)' has been generated and entered
IMO0752
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0752 Job '(&00)' is being generated. '(&01)' supply unit has been selected
IMO0753
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0753 Job '(&00)' is being generated. '(&01)' supply units have been selected
IMO0754
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0754 Error during creation of PBD-file
IMO0755
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0755 No complete installation environment found for the selected supply units
Meaning
In order to perform the "install-from-SCI" function, at least
one selected supply unit must have all its original installation
files still present on the system.
IMO0756
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0756 Access error on "PBD"-file (&00). Processing aborted
Meaning
PBD-file either not present or may not be opened.
IMO0757
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0757 Error: Supply unit '(&00)' version '(&01)' correction state '(&02)' must be in status "INSTALLED" for installation "*FROM-SCI"
Meaning
The installation of a supply unit from the SCI list is interpreted by
IMON as the installation "*FROM-SCI" to a foreign system for that SCI.
Such installation can only be done when the supply unit is in status
"INSTALLED".
Response
To install a supply unit on the system of the opened SCI, the related
SOLIS2 delivery must be opened and the supply unit must be installed
from that SOLIS2 delivery list.
IMO0758
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0758 Warning: TSOS user address space may be insufficient for installation process (min. 32 MB needed)
Meaning
The user address space of TSOS may be insufficient for a
correct run of the installation procedure.
In fact, for a big installation, a minimum of 32 MB is needed.
Response
Extend user address space up to 32 MB before starting manually
the generated installation procedure with the /ENTER-PROC command.
IMO0759
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0759 Warning: TSOS user address space may be insufficient for installation process (min. 32 MB needed). Installation job not started automatically
Meaning
The user address space of TSOS may be insufficient for a
correct run of the installation procedure.
In fact, for a big installation, a minimum of 32 MB is needed.
Response
Extend user address space up to 32 MB before starting manually
the generated installation procedure with the /ENTER-PROC command.
IMO0760
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0760 Error: Install function with "*FROM-SCI" parameter only allowed with standard SCI
Response
Open a standard SCI (:<catid>:$TSOS.SYS.IMON.SCI).
IMO0761
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0761 Installation option "*FROM-SCI" or "*CUSTOMER-APPROVED" only possible with the same OSD version for source and target systems
Meaning
The installation "*FROM-SCI" or "*CUSTOMER-APPROVED" can not
be performed for a target system with an OSD version different
from the original system.
IMO0762
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0762 Installation option "*FROM-SCI" only possible with the source pubset different from target pubset
IMO0763
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0763 No complete installation environment found
IMO0764
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0764 Supply unit '(&00)' '(&01)' '(&02)' not found in the PBD file
IMO0765
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0765 Supply unit '(&00)' '(&01)(&02)' not installable on target system. Reply: 0 = skip supply unit and continue; 1 = abort installation; 2 = ignore error and continue with the supply unit
Meaning
The "system dependence" record defined for the supply unit prevents
its run on the specified target system.
IMO0766
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0766 Error(s) found in checked configuration. For more information: see '(&00)'. Reply: 1=abort installation; 2=ignore error(s) and continue
Meaning
All "Product dependences" records defined for the selected supply unit(s)
may not be resolved on the target system.
IMO0767
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0767 Configuration Check error. Installation aborted
IMO0768
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0768 All selected supply units have been skipped due to error(s) during the configuration check process. No more supply unit to install
IMO0769
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0769 You can now restart the supply unit selection
IMO0770
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0770 Dependence file '(&00)' not found. Configuration check process skipped
IMO0771
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0771 Syntax error at line '(&00)' in dependence file '(&01)'
Response
Please contact the delivery responsible and provide the dependence
file '(&01)' for diagnosis
IMO0772
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0772 No PBD or only correction package(s) found for supply unit '(&00)' version '(&01)'
Meaning
A supply unit may be installed *FROM-SCI only if at least one complete
delivery exists for it in the SCI.
Response
Select this supply unit from its original package starting from the
package view of the SCI to install it with the *FROM-SCI functionality
(instead of a direct selection in the supply unit view).
IMO0773
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0773 Warning: Invalid version specification "(&00)". Value "120*" assumed
IMO0774
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0774 Warning: Invalid target specification "(&00)". Value "A" assumed
IMO0775
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0775 No installation unit in the selected supply unit(s)
IMO0776
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0776 No PBD found for supply unit '(&00)' '(&01)(&02)' from package '(&03)' and user code '(&04)'
Meaning
A supply unit may be installed with the "*CUSTOMER-APPROVED" feature
only if the corresponding PBD still exists on the system.
IMO0777
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0777 "*CUSTOMER-APPROVED" supply unit '(&00)' '(&01)(&02)' will not be installed because last installed target supply unit '(&03)' '(&04)(&05)' is more recent
Meaning
A supply unit may be installed with the *CUSTOMER-APPROVED
feature only if its CUSTOMER-APPROVAL timestamp is higher than
the installation timestamp of corresponding target supply unit.
IMO0778
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0778 "*CUSTOMER-APPROVED" supply unit '(&00)' '(&01)(&02)' cannot be installed because last installed target supply unit '(&03)' '(&04)(&05)' has not appropriate correction state
Meaning
A supply unit may be installed with the *CUSTOMER-APPROVED
feature only if its correction state is higher than these of
the last installed target supply unit.
IMO0779
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0779 Supply unit '(&00)' '(&01)(&02)' cannot be installed with "*CUSTOMER-APPROVED" feature on target system because file '(&03)' of installation unit '(&04)' '(&05)(&06)' has no valid timestamp
Meaning
A supply unit may be installed with the *CUSTOMER-APPROVED
feature only if all its contained files have a timestamp
lower than the "*CUSTOMER-APPROVED" timestamp.
IMO0780
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0780 Error: Supply unit '(&00)' version '(&01)(&02)' must be in status "INSTALLED" and set to "CUSTOMER-APPROVED" to be installed "*FROM-SCI" with the "*CUSTOMER-APPROVED" feature
Meaning
A supply unit may be installed "*FROM-SCI" with the *CUSTOMER-APPROVED
feature only if it is "INSTALLED" and if it was previously set to
"*CUSTOMER-APPROVED" using the SET-CUSTOMER-APPROVAL statement.
IMO0781
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0781 Installation with "*CUSTOMER-APPROVED" feature aborted
IMO0782
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0782 Error: Installation from local volume not possible for the current delivery
Meaning
The current delivery is too old (format < IMON V2.9) to support
installation from local volume.
IMO0783
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0783 Error: Parking from local volume not possible for the current delivery
Meaning
The current delivery is too old (format < IMON V2.9) to support parking
from local volume.
IMO0784
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0784 Error: Selected supply units must be in status "INSTALLED" for installation "*FROM-SCI"
Meaning
The installation of a supply unit from the SCI list is interpreted by
IMON as the installation "*FROM-SCI" to a foreign system for that SCI.
Such installation can only be done when the supply unit is in status
"INSTALLED".
Response
To install the supply units on the system of the opened SCI, the related
SOLIS2 deliveries must be opened and the supply units must be installed
from these SOLIS2 deliveries lists.
IMO0785
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0785 Error: Selected supply units must be in status "INSTALLED" and set to "CUSTOMER-APPROVED" to be installed "*FROM-SCI" with the "*CUSTOMER-APPROVED" feature
Meaning
A supply unit may be installed "*FROM-SCI" with the *CUSTOMER-APPROVED
feature only if it is "INSTALLED" and if it was previously set to
"*CUSTOMER-APPROVED" using the SET-CUSTOMER-APPROVAL statement.
IMO0800
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0800 Installation path '(&00)' does not correspond to any item
IMO0850
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0850 Filename '(&00)' mandatory for item '(&01)' of supply unit '(&02)' cannot be prefixed by '(&03)'. Prefix '(&04)' must be specified for the supply unit
IMO0851
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0851 Filename '(&00)' mandatory for item '(&01)' of release unit '(&02)' cannot be prefixed by '(&03)'. Prefix '(&04)' must be specified for the release unit
IMO0852
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0852 Userid '(&00)' mandatory for item '(&01)' is in contradiction with userid '(&02)' specified for supply unit '(&03)'. Userid '(&04)' must be specified for the supply unit or userid '(&02)' must be forced
IMO0853
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0853 Userid '(&00)' mandatory for item '(&01)' is in contradiction with userid '(&02)' specified for release unit '(&03)'. Userid '(&04)' must be specified for the release unit or userid '(&02)' must be forced
IMO0854
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0854 Userid '(&00)' mandatory for release unit '(&01)' is in contradiction with userid '(&02)' specified for supply unit '(&03)'. Userid '(&04)' must be specified for the supply unit or userid '(&02)' must be forced
IMO0855
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0855 Userid '(&00)' mandatory for release unit '(&01)' is in contradiction with userid '(&02)' specified for that release unit. Userid '(&03)' must be specified for the release unit or userid '(&02)' must be forced
IMO0856
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0856 Pubset with catid '(&00)' not accessible
IMO0857
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0857 Userid '(&00)' does not exist on HOME pubset. Please create userid with the /ADD-USER command
IMO0858
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0858 Userid '(&00)' does not exist on pubset with catid '(&01)'. Please create userid with the /ADD-USER command
IMO0859
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0859 Catid '(&00)' corresponds to a '(&01)' disk
IMO0860
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0860 Supply unit '(&00)' version '(&01)' correction state '(&02)' must be installed on PAMKEY disk
IMO0861
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0861 Supply unit '(&00)' version '(&01)' correction state '(&02)' must be installed on PAMKEY or NK2 disks
IMO0862
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0862 Release unit '(&00)' version '(&01)' correction state '(&02)' must be installed on PAMKEY disk
IMO0863
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0863 Release unit '(&00)' version '(&01)' correction state '(&02)' must be installed on PAMKEY or NK2 disk
IMO0864
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0864 Userid '(&00)' may not be specified for supply unit '(&01)' version '(&02)' correction state '(&03)'
Meaning
No release unit information has been defined for the
supply unit '(&01)' version '(&02)' correction state '(&03)'.
IMO0866
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0866 Target system pubset '(&00)' corresponds to a NK2 disk. Work file location '(&01)' defined on a '(&02)' disk must be defined on a NK2 or NK4 disk
IMO0867
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0867 Target system pubset '(&00)' corresponds to a NK4 disk. Work file location '(&01)' defined on a '(&02)' disk must be defined on a NK4 disk
IMO0868
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0868 Userid '(&00)' and prefix '(&01)' mandatory for release item '(&02)' used although userid '(&03)' and prefix '(&04)' have been specified for supply unit '(&05)'
IMO0869
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0869 Userid '(&00)' and prefix '(&01)' mandatory for release item '(&02)' used although userid '(&03)' and prefix '(&04)' have been specified for release unit '(&05)'
IMO0870
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0870 Mandatory userid '(&00)' for release unit '(&01)' taken although userid '(&02)' has been specified for supply unit '(&03)'
IMO0871
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0871 Userid '(&00)' mandatory for release unit '(&01)' taken although userid '(&02)' has been specified for that release unit
IMO0872
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0872 Userid '(&00)' and prefix '(&01)' mandatory for release item '(&02)' ignored. Userid '(&03)' and prefix '(&04)' specified for supply unit '(&05)' have been taken instead
IMO0873
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0873 Userid '(&00)' and prefix '(&01)' mandatory for release item '(&02)' ignored. Userid '(&03)' and prefix '(&04)' specified for release unit '(&05)' have been taken instead
IMO0874
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0874 Userid '(&00)' mandatory for release unit '(&01)' ignored. Userid '(&02)' specified for supply unit '(&03)' has been taken instead
IMO0875
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0875 Userid '(&00)' mandatory for release unit '(&01)' ignored. Userid '(&02)' specified for that release unit has been taken instead
IMO0876
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0876 Disk type '(&00)' of installation file '(&01)' not compatible with disk type '(&02)' of work file location '(&03)'
IMO0907
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0907 No RMS parameter found in SOLIS2 parameter file '(&00)'. RMS processing skipped. Processing continues
IMO0908
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0908 An error occurred while W2GEN interpreted script '(&00)'. Further information: /HELP-MSG SOL(&01)
IMO0911
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0911 Abnormal program termination in W2GEN script '(&00)'. Some key was not found in movement file '(&01)'
Response
Please contact the system administrator.
IMO0912
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0912 TERMJ encountered in W2GEN script '(&00)'. Additional information has been logged in file (&01)
IMO0914
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0914 Supply unit '(&00)' of delivery corresponding to package '(&01)' and user code '(&02)' does not exist in SOLIS2 movement file
IMO0917
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0917 An error occurred while accessing SOLIS2 interpreter
IMO0918
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0918 Error occurred during creation of the documentation library due to invalid delivery format
IMO0950
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0950 Warning: Delivery already registered in SCI. If you continue then all registered information on SU, previously installed from this delivery, will be lost. More details in help text IMO0950
Meaning
A delivery with the specified package name and user code is already
registered in the current SCI.
Any subsequent action on this delivery will automatically overwrite
the registered data, i.e. registered information on all supply
units previously installed from this delivery will be lost.
The "INSTALLED" status of the supply units will be reset when
they are not reinstalled and are so not available as input for
any further COPY-installation (FROM-SCI).
Response
Continue and so overwrite already registered information
or close the delivery and open it again as "REGISTERED".
IMO0951
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0951 Delivery with package name '(&00)' and user code '(&01)' up to now not registered in SCI
IMO0952
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0952 Warning: Information on the delivery with package name '(&00)' and user code '(&01)' have been overwritten in the SCI
IMO0953
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0953 Subsystem '(&00)' '(&01)' did not reach status '(&02)' in the given time ((&03) seconds)
IMO0954
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0954 Subsystem '(&00)' '(&01)' has reached status '(&02)'
IMO0955
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0955 Subsystem '(&00)' '(&01)' not removed
IMO0956
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0956 Subsystem '(&00)' '(&01)' removed
IMO0957
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0957 Subsystem '(&00)' '(&01)' not found
IMO0958
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO0958 Subsystem '(&00)' not found
IMO1000
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1000 This message is reserved to the FHS interface
IMO1001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1001 CMD call error '(&00)' (SC1: '(&01)', SC2: '(&02)') when executing command '(&03)'
IMO1002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1002 Command not allowed in EXECUTE-CMD statement
IMO1003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1003 MANDATORY-LOCATION = *YES and REPLACE-OLD-FILES = *NO is not allowed
Meaning
During the installation process, an existing file may not be
neither overwritten nor renamed. IMON is so not able to proceed
with the installation.
Response
Suppress existing file or correct invalid operand.
IMO1004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1004 S-Variable '(&00)' wrong or has init error
IMO1005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1005 S-Variable '(&00)' does not exist
IMO1006
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1006 Unknown file import source type (tape/disk/library expected)
IMO1007
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1007 Placement tools init error
Response
Please contact the system administrator.
IMO1008
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1008 Files which are not SDF or MSG, or which are SDF but without subsystem name cannot be deactivated (unlocked)
Meaning
FILE-TYPE operand is not *MSG or *SDF,
or is *SDF with SUBSYSTEM-NAME=*NOT-RELEVANT and
the file is currently locked.
IMO1009
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1009 Message file '(&00)' cannot be deactivated
IMO1010
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1010 Syntax file (&00) cannot be deactivated
IMO1011
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1011 Message file (&00) cannot be activated
IMO1012
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1012 Syntax file (&00) cannot be activated
IMO1013
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1013 Renamed file (&00) cannot be removed
IMO1014
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1014 Init file not existing. Processing continues
IMO1015
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1015 File (&00) cannot be renamed
IMO1016
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1016 ERROR IN INSTALLATION: FILE '(&00)' CANNOT BE UNLOCKED. TSN.0=REPEAT, TSN. 1=ABORT, TSN.2=IGNORE
Meaning
Error occurred while attempting to unlock the file '(&00)'.
Response
Eliminate error cause and reply
tsn.0 to repeat installation step.
tsn.1 Installation is aborted.
tsn.2 Error is ignored. Installation continues.
Error cause can be found in logging file:
<work-file-location>.<package>.<timestamp>.IL.
IMO1017
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1017 Catalog entry of file (&00) cannot be updated
IMO1018
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1018 Item '(&00)' not contained in corresponding unit
IMO1019
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1019 SDF-File (&00) (no subsystem name given) locked: no update possible; downloaded file (&00) deleted
IMO1020
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1020 Logical-id '(&00)' not found in release unit '(&01)'. Processing continues.
Meaning
The pathname corresponding to logical-id (&00) cannot be updated
in DSSM catalog as it is not found in given release unit (&01).
IMO1021
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO1021 Access error on file (&00). Processing abnormally terminated
IMO1030
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO1030 Automatic overwrite of file '(&00)' not allowed. New file installed as '(&01)'. Enter TSN. to continue
Meaning
The library $TSOS.SYSPRC.IMON-BAS cannot be overwritten while
an other IMON application is running.
Response
Once a new version of IMON is installed and before using it
please, replace manually the library $TSOS.SYSPRC.IMON-BAS
by the new installed library saved as (&01).
Enter TSN. to continue this installation process.
IMO2001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2001 FSTAT-RENAME : analyse of target system
Meaning
This installation process sets all necessary S-variables, checks
accessibility and saves file attributes of already existing files
and builds eventually a temporary filename for locked files.
IMO2002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2002 SAVE-OLD-FILES procedure generation
Meaning
A procedure calling ARCHIVE or LMSCONV is generated to save already
existing items and modified containers (e.g. MIP and SDF parameter
files, DSSM catalog, RMS depot,...).
Name: <work-file-location>.<package>.<usercode>.CS
IMO2003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2003 SAVE-OLD-FILES procedure call
IMO2004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2004 RESERVE-FILE : preparation of target system
Meaning
This installation process reserves disk space for new installed
items and updates the file attributes of already existing files
to allow a correct IMPORT process.
IMO2005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2005 IMPORT-FILE : import-procedure generation
Meaning
A procedure, calling SIR/ARCHIVE or LMSCONV, is generated
to import the selected items from the delivery medium.
Name: <work-file-location>.<package>.<usercode>.CD
IMO2006
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2006 UPDATE-CATALOG-ENTRY : set file attributes
Meaning
This installation process sets (or resets) the file attributes
of all installed files.
It performs also deactivation, replacement and reactivation of
currently activated message and syntax files.
IMO2007
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2007 Library processing
IMO2008
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2008 ADD-INSTALLATION-UNITS : register installation units in SCI
Meaning
The installation units produced by the installed configuration
are registered in the standard SCI of the target system.
Registration result can be found in the logging file:
<work-file-location>.<package>.<usercode>.II
IMO2009
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2009 RMS-PROCESSING: Revision packet put into RMS depot and loader selection
IMO2010
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2010 RMS-PROCESSING: loader generation
IMO2011
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2011 RMS-PROCESSING: Revision packet put into RMS Depot
IMO2012
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2012 RMS-PROCESSING: Error while taking in revision packet (&00). See error-logging (&01) for more information
IMO2013
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2013 RMS-PROCESSING: Error during loader selection based upon revision packet (&00). See error-logging (&01) for more information
IMO2014
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2014 RMS-PROCESSING: Error during loader generation. See error-logging (&00) for more information
IMO2015
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2015 Reference file generation
Meaning
A Reference file containing all supply units registered in the IMON SCI
will be created on the user-id SERVICE. File name: SOLREF.IMON.SW-CONF
IMO2016
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2016 Processing of delivered SYSSII files
Meaning
All delivered SYSSII files will be merged into a PLAM library on the
user-id SERVICE and then erased. Library name: SOLLIB.IMON.SYSSII
IMO2017
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2017 Generation of the UNDO libraries
Meaning
All files necessary for a later UNDO of the supply units are merged
into a library on the user-id SYSSAG (or TSOS).
Library name: IMON.UNDO.<SU-name>.
IMO2018
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2018 ACTIVATION PROCESS INITIATED FOR RELEASE UNIT: '(&00)'
IMO2019
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2019 INSTALLATION FUNCTION EXECUTED FOR PACKAGE '(&00)'
IMO2020
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2020 INSTALLATION ABNORMALLY TERMINATED FOR PACKAGE '(&00)'
IMO2021
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2021 INSTALLATION NORMALLY TERMINATED FOR PACKAGE '(&00)'
IMO2023
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2023 ACTIVATE-UNIT
IMO2024
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2024 IMPORT-FILE : import-procedure call
IMO2025
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2025 PARK FUNCTION EXECUTED FOR PACKAGE '(&00)'
IMO2026
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2026 PARK FUNCTION ABNORMALLY TERMINATED FOR PACKAGE '(&00)'
IMO2027
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2027 SSCM global processing
IMO2028
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2028 PARK FUNCTION NORMALLY TERMINATED FOR PACKAGE '(&00)'
IMO2029
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2029 USER-MODIF : user procedure '(&00)' call
IMO2030
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2030 RMS-PROCESSING: Revision packets put into RMS Depot
IMO2031
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2031 RMS-PROCESSING: Error while taking in the revision packets
IMO2032
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2032 SAVE-OLD-FILES for UNDO procedure generation
Meaning
A procedure, calling ARCHIVE, is generated to save for
later UNDO processing already existing files.
Name: <work-file-location>.<package>.<usercode>.CS
IMO2033
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2033 SAVE-OLD-FILES for UNDO procedure call
IMO2034
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2034 POSIX processing
IMO2100
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2100 ERROR IN STEP '(&00)' DURING PROCESSING OF PACKAGE '(&01)'. TSN.0=REPEAT, TSN.1=ABORT, TSN.2=IGNORE
Meaning
Error occurred in step '(&00)' during processing of package '(&01)'.
Response
tsn.0 - Error eliminated; repeat installation/park step.
tsn.1 - Processing (Installation or park) is aborted.
- After correction of error, installation/park procedure (.IE/.PE
file) must be restarted using /ENTER-PROCEDURE command.
tsn.2 - Error is ignored. Processing continues.
Error cause can be found in logging file:
<work-file-location>.<package>.<timestamp>.IL
IMO2101
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2101 INSTALLATION RESTART FUNCTION EXECUTED FOR PACKAGE '(&00)'
IMO2102
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2102 INSTALLATION RESTART FUNCTION FOR PACKAGE '(&00)' REJECTED
IMO2103
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2103 PLEASE CHECK ERROR LOG: '(&00)'
IMO2104
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2104 ATTENTION !!! PLEASE CREATE A NEW SVL IMMEDIATELY
Meaning
Boot loader files have been overwritten. SVL chaining may be destroyed.
In this case BS2000 startup would failed ! ! !
Response
Chain the SVL files by using SIR-IP.
IMO2105
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2105 ERROR IN RECOVERY PROCEDURE '(&00)' OF INSTALLATION OR PARK PROCESSING OF PACKAGE '(&01)'
Meaning
Error occurred in the recovery procedure '(&00)' during processing
of delivery '(&01)'.
Response
Error cause can be found in logging file:
<work-file-location>.<package>.<timestamp>.IL
Action: 1. Please correct the procedure (&00).
2. Call the procedure manually with /CALL-PROCEDURE (&00)
command.
3. Call the installation/park procedure for RESTART processing.
IMO2106
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2106 LOGGING FILE (&00) LOCKED. PROCESSING OF PACKAGE '(&01)' ABORTED
Meaning
Standard logging file '(&00)' not accessible for SYSLST assignment.
Processing of delivery '(&01)' is aborted.
Response
Unlock corresponding logging file and start installation of package
again.
IMO2107
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2107 LOGGING FILE (&00) LOCKED. TSN.0=CONTINUE (AFTER UNLOCK OF FILE), TSN. 1=ABORT
Meaning
Standard logging file '(&00)' not accessible for SYSLST assignment.
Response
Unlock corresponding logging file.
TSN.0: The installation continues.
TSN.1: The installation is aborted.
IMO2108
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2108 ERROR IN STEP '(&00)' DURING PROCESSING OF PACKAGE '(&01)'.
Meaning
Error occurred in step '(&00)' during processing of delivery '(&01)'.
Response
Error cause can be found in logging file:
<work-file-location>.<package>.<timestamp>.IL
IMO2109
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2109 The system REP file has been cataloged on '(&00)'. Enter TSN. to continue
IMO2110
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2110 Installation hint: Please check file attributes. Enter TSN. to continue
Meaning
During the installation process of already installed files, IMON
detected, for some ones, differences between the current file attributes
(USER-ACCESS, ACCESS, MIGRATE) and the recommended values.
A warning file with the detected differences has been created with the
name: <work-file-location>.<package>.<timestamp>.IW
Response
Analyse the generated warning file and enter the generated
/MODIFY-FILE-ATTRIBUTES commands for the files for which a difference
may cause trouble on your system.
IMO2111
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2111 Warning: POSIX post-procedure "(&00)" created. Enter TSN. to continue
Meaning
During the POSIX process, IMON detected, for some POSIX products,
post-installation-script(s) to run after the POSIX-installation of the
concerned product(s). A specific procedure calling all these scripts
sequentially has been created for this purpose with the name:
<work-file-location>.<package>.<timestamp>.PX
Response
After the complete POSIX-installation process, start this procedure
using the /CALL-PROCEDURE command.
IMO2200
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2200 ERROR IN STEP '(&00)' DURING PROCESSING OF PACKAGE '(&01)'. TSN.0=REPEAT, TSN.1=ABORT
Meaning
Error occurred in step '(&00)' during processing of delivery '(&01)'.
Response
tsn.0 - Error eliminated; repeat installation step.
tsn.1 - Installation processing is aborted.
- After correction of the error, installation procedure (.IE file)
must be restarted using /ENTER-PROCEDURE command.
Error cause can be found in logging file:
<work-file-location>.<package>.<timestamp>.IL.
IMO2301
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2301 ACTIVATION RESTART FUNCTION EXECUTED WITH TIMESTAMP '(&00)'
IMO2302
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2302 ACTIVATION RESTART FUNCTION WITH TIMESTAMP '(&00)' HAS BEEN REJECTED
IMO2303
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2303 ERROR IN STEP '(&00)' DURING ACTIVATION WITH TIMESTAMP '(&01)'. TSN. 0=REPEAT, TSN.1=ABORT, TSN.2=IGNORE
Meaning
Error occurred in step '(&00)' during activation with timestamp '(&01)'.
Response
tsn.0 - Error eliminated; repeat activation step.
tsn.1 - Activation is aborted.
- After correction of error, activation procedure (.DA
file) must be restarted using /ENTER-PROCEDURE command.
tsn.2 - Error is ignored. Processing continues.
Error cause can be found in logging file:
<work-file-location>.<file-prefix>.<timestamp>.AL
IMO2305
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2305 ERROR IN RECOVERY PROCEDURE '(&00)' OF ACTIVATION PROCESSING '(&01)'
Meaning
Error occurred in the recovery proc '(&00)' during activation '(&01)'.
Response
Error cause can be found in logging file:
<work-file-location>.<file-prefix>.<timestamp>.AL
Action: 1. Please correct the procedure (&00).
2. call the procedure manually with /CALL-PROCEDURE (&00) command
3. call the activation procedure for RESTART processing.
IMO2306
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2306 LOGGING FILE (&00) LOCKED. PROCESSING OF ACTIVATION '(&01)' ABORTED
Meaning
Standard logging file '(&00)' not accessible for SYSLST assignment.
Processing of activation '(&01)' is aborted.
Response
Unlock corresponding logging file and start activation
again.
IMO2319
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2319 ACTIVATION FUNCTION EXECUTED WITH TIMESTAMP '(&00)'
IMO2320
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2320 ACTIVATION WITH TIMESTAMP '(&00)' ABNORMALLY TERMINATED
IMO2321
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2321 ACTIVATION WITH TIMESTAMP '(&00)' NORMALLY TERMINATED
IMO2350
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2350 UNLOCK-PRODUCT-VERSION : unlock of installation units
Meaning
This activation process sets all /UNLOCK-PRODUCT-VERSION commands
which are necessary to unlock the installation units.
IMO2351
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2351 DSSM catalog creation
Meaning
This activation process creates the necessary DSSM catalogs for all
subsystems of the selected installation units.
IMO2352
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2352 MODIFY-SDF-PAR : deactivation of syntax file(s) defined with "DEL"
Meaning
This activation step deactivates all the syntax files that are
referenced with a "DEL" parameter text in the SDF items.
IMO2353
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2353 STOP-SUBSYSTEM : deactivation of subsystems defined with "DEL"
Meaning
This activation step deactivates all subsystems which are referenced
by "DEL" parameter text in the processed SSC items.
IMO2354
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2354 STOP-SUBSYSTEM : stop subsystem(s)
IMO2355
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2355 REMOVE-SUBSYSTEM : remove subsystem(s)
IMO2356
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2356 MODIFY-MESSAGE-FILE-ASSIGNMENT : message file activation
IMO2357
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2357 MODIFY-SDF-PARAMETERS : syntax file activation
IMO2358
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2358 ADD-SUBSYSTEM : add new subsystem catalogs in dynamic DSSM catalog
IMO2359
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2359 START-SUBSYSTEM : start subsystem(s)
IMO2360
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2360 POSIX PROCESSING
Meaning
This activation step processes all *PS items contained in the selected
installation units. The POSIX packages contained in the corresponding
SINLIB file are registered in the POSIX system.
IMO2361
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2361 MODIFY-SUBSYSTEM-PARAMETER : reset creation-time attribute for level2 subsystem(s)
IMO2362
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO2362 START-SUBSYSTEM : restore subsystem(s) status of dependence subsystem(s)
Meaning
This activation step starts subsystem(s) which were stopped
by the activation process due to dependence reasons.
IMO3001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3001 Activate process inhibited from a foreign SCI. Function only allowed for standard SCI of current system
IMO3002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3002 The SAVE-CATALOG command to save the dynamic catalog performed to find dependences to subsystem (&00) (&01) failed. Generation of activation procedure of the IU stopped
IMO3003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3003 IU (&00) (&01)(&02) cannot be activated because "(&03)" item to be activated does not exist
IMO3004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3004 Item "(&00)" cannot be opened. Activation process for IU (&01) (&02)(&03) stopped
IMO3005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3005 No subsystem found in "(&00)" item. Activation process for IU (&01) (&02)(&03) stopped
IMO3006
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3006 Warning: Installation unit set "not-activable"
IMO3007
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3007 Type of activation for subsystem (&00) (&01) cannot be identified. Activation process for IU (&02) (&03)(&04) stopped
IMO3008
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3008 Subsystem (&00) has to be stopped and its attributes inhibit to stop it. Activation process for IU (&01) (&02)(&03) stopped
IMO3009
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3009 Job "(&00)" has been generated and entered
IMO3011
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3011 Error when calling SSCM to find dependences to the subsystem '(&00)' '(&01)' in '(&02)'. Function abnormally terminated
Meaning
Minimal SSCM environment not found.
IMON needs at least SSCM V02.3B10 with the correction
to the problem A0475587. IMON finds them in the library
<work-file-location>.SOLLIB.IMON.020.
IMO3012
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3012 Job "(&00)" generated but not successfully entered
IMO3013
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3013 No unit selected for activation. Function abnormally terminated
IMO3014
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3014 No unit activable. Function abnormally terminated
Meaning
Possible reasons:
- No activable unit found in SCI matching with the user selection.
- Unit(s) selected by the user are level4 ones: they are no longer
supported from IMON V02.8A.
IMO3015
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3015 Warning: More than one version of the installation unit '(&00)' selected. Only the highest one is kept
IMO3018
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3018 Error when calling /SHOW-SDF-PARAMETERS to get activated syntaxfile of the subsystem (&00). Activation process for IU (&01) (&02)(&03) stopped
IMO3019
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3019 Warning: More than one version of the installation unit '(&00)' contained in the different selected supply units. Only highest one kept
IMO3020
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3020 Level3 subsystem (&00) (&01) has to be stopped or started and its attributes inhibit to stop or start it. Activation process for IU (&02) (&03)(&04) stopped
IMO3021
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3021 Activation aborted
IMO3022
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3022 Job for creation of catalog for subsystem (&00) (&01) started
IMO3023
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3023 Creation of catalog for subsystem '(&00)' '(&01)' abnormally terminated. See '(&02)' for more details. Activation process for IU '(&03)' '(&04)(&05)' stopped
IMO3024
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3024 File (&00) does not exist
Meaning
A file required for the processing does not exist.
When this message is sent at //ACTIVATE-UNITS for the 4 work files
IMON.SYSREP.SSCM, IMON.SYSSDF.SSCM.USER, IMON.SYSMES.SSCM and
SOLLIB.IMON.020, the files have been created by the installation of the
supply unit but they are not all located in the same path ($SYSSAG. or
Work file location or $TSOS). In this case, also the file
SOLLIB.SOLIS2.050 must be located in the same path as the 4 reported
files.
Response
Update the system with the missing file.
In the case of the 4 work files reported for //ACTIVATE-UNITS, the 5 files
mentionned in the meaning text must all be copied in the same path
($SYSSAG. or work file location or $TSOS.).
IMO3026
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3026 Some selected units not activable
IMO3028
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3028 Subsystem '(&00)' is defined as dependence or reference for subsystem '(&01)' '(&02)' in file (&03)
IMO3031
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3031 Subsystem '(&00)' '(&01)' not created and its attributes inhibit to start it. Activation process for IU '(&02)' '(&03)(&04)' stopped
IMO3032
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3032 Subsystem '(&00)' not found in DSSM dynamic catalog or existing version(s) outside its defined range of dependences.Activation process for IU '(&01)' '(&02)(&03)' stopped
IMO3035
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3035 Error when calling SSCM to find dependences for subsystem '(&00)' '(&01)' in '(&02)'. Function abnormally terminated
Meaning
Minimal SSCM environment not found.
IMON needs at least SSCM V02.3B10 with the correction
to the problem A0475587. IMON finds them in the library
<work-file-location>.SOLLIB.IMON.020.
IMO3037
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3037 Version(s) '(&00)' of subsystem '(&01)' not in status "CREATED" or "NOT CREATED"
IMO3038
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3038 Subsystem '(&00)' has dependence or reference to subsystem '(&01)' '(&02)'
IMO3039
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3039 Warning: Syntaxfile '(&00)' for subsystem '(&01)' not processed by IMON: it will be activated by DSSM. Activation process for IU '(&02)' '(&03)(&04)' continues
IMO3040
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3040 Syntaxfile '(&00)' for subsystem '(&01)' cannot be deactivated by IMON because previously activated by DSSM. Activation process for IU '(&02)' '(&03)(&04)' stopped
IMO3043
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3043 No installation unit found in supply unit '(&00)' '(&01)(&02)' (&03) (&04)
IMO3044
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3044 Installation unit '(&00)' '(&01)(&02)' not found in supply unit '(&03)' '(&04)(&05)'
IMO3045
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3045 Subsystem '(&00)' version '(&01)' not found in "(&02)" item
IMO3050
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3050 Subsystem '(&00)' '(&01)' not activable on '(&02)' running system due to following defined CP dependences ('(&03)' - '(&04)'). Activation process for IU '(&05)' '(&06)(&07)' stopped
IMO3051
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3051 SSCM error '(&00)' on reading attributes for subsystem '(&01)' '(&02)' from file (&03)
IMO3052
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3052 SSCM error '(&00)' on reading dependences for subsystem '(&01)' '(&02)' from file (&03)
IMO3053
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3053 SSCM error '(&00)' on reading dependences to subsystem '(&01)' '(&02)' from file (&03)
IMO3054
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3054 Warning: Installation unit set "NOT ACTIVABLE" because only SSD-item '(&00)' to process
Meaning
To be activable, an installation unit, defined as DSSM subsystem,
must contain at least one processed SSC item.
IMO3055
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3055 Warning: SSD-item '(&00)' ignored for determination of the activable status of installation unit '(&01)' '(&02)(&03)'
Meaning
SSD-items not supported by SSCM interface reading dependences.
Only the SSC-items are relevant to determine the activability of
an installation unit.
IMO3056
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3056 Warning: Installation unit '(&00)' '(&01)(&02)' is not candidate to activation because contained in the system CP
IMO3057
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3057 SDF item "(&00)" registered in SCI without its corresponding subsystem name. Activation process for IU '(&01)' '(&02)(&03)' stopped
IMO3058
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3058 Subsystem '(&00)' not found in "(&01)" item. Activation process for IU '(&02)' '(&03)(&04)' stopped
IMO3059
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3059 Warning: Installation unit '(&00)' '(&01)(&02)' processed as level4 unit due to dependence to it found in current catalog
IMO3060
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3060 Subsystem '(&00)' '(&01)' created and its attributes inhibit to stop it. Activation process for IU '(&02)' '(&03)(&04)' stopped
IMO3061
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO3061 ACTIVATE actions reported in file (&00)
IMO4000
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4000 MIP-PF '(&00)'
Meaning
Name of the MIP parameter file.
IMO4001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4001 MIP-SMF '(&00)'
Meaning
Name of the MIP system message file.
IMO4002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4002 SDF-PF '(&00)'
Meaning
Name of the SDF parameter file.
IMO4003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4003 SSC-CAT '(&00)'
Meaning
Name of subsystem catalogue.
IMO4004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4004 RMS-DEP '(&00)'
Meaning
Name of the RMS Depot.
IMO4005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4005 SDF-SSF '(&00)'
Meaning
Name of the SDF system syntax file.
IMO4009
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4009 SUPPLY UNIT '(&00)' '(&01)' '(&02)' PROCESSED
Meaning
Activation of SU '(&00)' version '(&01)' correction state '(&02)'.
IMO4010
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4010 ACTIVATE-UNIT '(&00)' '(&01)' '(&02)'
Meaning
IMON activation for release unit '(&00)'
version '(&01)' correction state '(&02)'.
IMO4011
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4011 MIP-PF extended with '(&00)' SCOPE='(&01)'
IMO4012
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4012 MIP-SMF extended with '(&00)'
IMO4013
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4013 SDF-PF extended with '(&00)' SCOPE='(&01)' SF-TYPE='(&02)' '(&03)'
IMO4014
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4014 SSC-CAT extended with '(&00)'
IMO4021
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4021 '(&00)' SCOPE='(&01)'
IMO4022
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4022 '(&00)'
IMO4023
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4023 '(&00)' SCOPE='(&01)' SF-TYPE='(&02)' '(&03)'
IMO4024
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4024 '(&00)'
IMO4030
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4030 Global Information
IMO4031
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4031 Output sorted by installation units
IMO4032
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4032 Output sorted by item types
IMO4033
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4033 (&00)
IMO4034
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4034 MIP-PF extended with:
IMO4035
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4035 MIP-SMF extended with:
IMO4036
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4036 SDF-PF extended with:
IMO4037
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4037 SSC-CAT extended with:
IMO4038
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4038 DO/ENT processing
IMO4039
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4039 '(&00)' (type DO) must be manually started
Meaning
As the installation was not performed for the HOME pubset,
the procedure (&00) could not be started automatically.
Response
The procedure must first be checked and, if necessary, adapted
to the modified installation conditions and then manually
started using the /CALL-PROCEDURE command.
In case of compiled procedure, please refer to the related product
documentation and eventually contact the product support to get
a procedure adapted to your configuration.
IMO4040
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4040 '(&00)' (type ENT) must be manually entered
Meaning
As the installation was not performed in its standard way, the job (&00)
could not be started automatically. It must first be checked and, if
necessary, adapted to the modified installation conditions and then
manually started using the /ENTER-JOB command.
Response
Enter job manually after checking it.
IMO4041
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4041 '(&00)' (type DO) has been called
IMO4042
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4042 '(&00)' (type ENT) has been entered
IMO4043
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4043 Abbreviations
IMO4044
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4044 MF: Message File
IMO4045
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4045 SMF: System Message File
IMO4046
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4046 SSF: System Syntax File
IMO4047
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4047 SF: Syntax File
IMO4048
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4048 PF: Parameter File
IMO4049
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4049 CAT: Catalogue
IMO4050
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4050 DEP: Depot
IMO4051
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4051 SF '(&00)' referenced in subsystem-declaration
IMO4052
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4052 Syntax file(s) activated by DSSM:
IMO4060
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO4060 ERROR DURING INSTALLATION PROCEDURE '(&00)' - PLEASE ENTER TSN. TO CONTINUE
Meaning
The installation procedure (&00) could not be performed properly.
The installation job can be continued with TSN.
After the installation job has been logged off, the installation
procedure (&00) must be started manually under TSOS.
- (&00): name of the erroneous installation procedure
Response
Enter TSN. to continue.
IMO5001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5001 No unit to be checked. Function abnormally terminated
IMO5002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5002 No unit selected for checking. Function abnormally terminated
IMO5003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5003 *** SU '(&00)' '(&01)(&02)' '(&03)' '(&04)'
IMO5004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5004 ****** IU '(&00)' '(&01)(&02)'
IMO5005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5005 Internal error when '(&00)' file (&01)
IMO5006
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5006 Warning: Initial creation attributes '(&00) (&01)' different from current creation attributes '(&02) (&03)' for file (&04)
IMO5007
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5007 Warning: File (&00) modified since its last installation
IMO5008
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5008 Error: Container (&00) of '(&01)' does not exist
IMO5009
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5009 Info: File (&00) not merged during installation
IMO5010
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5010 Error: File (&00) cannot be opened
IMO5011
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5011 Error: No Subsystem found in SSC '(&00)'
IMO5012
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5012 Error: Subsystem '(&00) (&01)' contained in SSC (&02) not merged in catalog (&03)
IMO5013
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5013 Warning: Subsystem '(&00) (&01)' contained in SSC (&02) merged in (&03) catalog
IMO5014
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5014 Check process of item '(&00)' stopped
IMO5015
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5015 Error: File '(&00)' not merged in parameter file '(&01)'
IMO5016
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5016 Warning: File '(&00)' merged in parameter file '(&01)'
IMO5017
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5017 Warning: No pathname assigned to REP-item '(&00)'
IMO5018
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5018 Error: Item '(&00)' is missing (delivery error).Check process of item '(&01)' stopped
IMO5019
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5019 Error: Check process of items '(&00)' and '(&01)' stopped
IMO5020
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5020 Warning: Item '(&00)' has been generated by user himself
IMO5021
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5021 Error: Item '(&00)' has to be generated by user himself
IMO5022
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5022 Error: Item '(&00)' has to be generated by user himself but file (&01) does not exist
IMO5023
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5023 Error: File '(&00)' not merged in current '(&01)' system REP file
IMO5024
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5024 Warning: IU name '(&00)' not found in file '(&01)'
IMO5025
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5025 Error: revision packet '(&00)' of file '(&01)' different from revision packet '(&02)' of item '(&03)'
IMO5026
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5026 Error: revision packet '(&00)' for IU '(&01)' in file '(&02)' different from revision packet '(&03)' of item '(&04)'
IMO5027
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5027 Error: Check function inhibited from a foreign SCI. Function only allowed for standard SCI of current system
IMO5028
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5028 Warning: SU '(&00)' '(&01)(&02)' '(&03)' '(&04)' not processed because created for IMON internal use
IMO5029
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO5029 Warning: IU '(&00)' '(&01)(&02)' not processed because created for IMON internal use
IMO6000
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6000 Delivery date must be higher than today
IMO6001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6001 Parameter (&00) not defined in file (&01)
IMO6002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6002 Request written in file (&00). Please, send this file to the following address: (&01)
IMO6003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6003 Request, written in file (&00), could not be sent automatically
IMO6004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6004 Please, send this file to the following address: (&00)
IMO6005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6005 Request written in file (&00) and sent to the following address: (&01)
IMO6006
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6006 Duplicate supply units found in selection
IMO6007
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6007 All selected supply units must have the same user code
IMO6008
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO6008 Device type (&00) not allowed for user code (&01). The available values are listed in file (&02)
IMO7000
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7000 POSIX subsystem not available for POSIX package installation. TSN.0=Wait, TSN.1=Abort installation in POSIX
Meaning
POSIX subsystem is not started or not yet available.
This subsystem is mandatory to perform the installation
of the products in POSIX.
Response
Please type TSN.0 to continue waiting till POSIX is available
or type TSN.1 to abort the POSIX package installation.
IMO7001
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7001 Installation of products in POSIX aborted. Reason: '(&00)'
Meaning
(&00): 1, POSIX subsystem is not available.
2, File $SYSROOT.POSIX.CONFIGURATION cannot be read.
3, File $SYSROOT.POSIX-STARTUP.SYSOUT is locked.
4, Unexpected error while accessing the file
$SYSROOT.IMON.ACTIVATE-UNIT.SYSLST99
IMO7002
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 00
Warranty : NO
IMO7002 Removal of product '(&00)' from POSIX started
Meaning
The removal processing of product (&00) from POSIX
has been started.
IMO7003
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 00
Warranty : NO
IMO7003 Product '(&00)' successfully removed from POSIX
Meaning
The product (&00) has been successfully removed from POSIX.
IMO7004
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 00
Warranty : NO
IMO7004 Installation of product '(&00)' in POSIX started
Meaning
The installation processing of product (&00) in POSIX
has been started.
IMO7005
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 00
Warranty : NO
IMO7005 Product '(&00)' successfully installed in POSIX
Meaning
The product (&00) has been successfully installed in POSIX.
IMO7006
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7006 Installation of product '(&00)' in POSIX failed. See '(&01)' for details
Meaning
The POSIX package installation of product (&00) failed.
Response
Please, see details in file (&01).
IMO7007
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7007 Installation of product '(&00)' in POSIX failed. POSIX error code: '(&01)'. See '(&02)' for details
Meaning
The product (&00) installation failed due to a POSIX error (&01)
returned by the /START-POSIX-INSTALLATION command.
Response
In system mode: /HELP-MSG with the POSIX error code
Please, see details in the file (&02).
IMO7008
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7008 Removal of product '(&00)' from POSIX failed. See '(&01)' for details
Meaning
The product (&00) removal failed.
Response
Please, see details in the file (&01).
IMO7009
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7009 Removal of product '(&00)' from POSIX failed. POSIX error code: '(&01)'. See '(&02)' for details
Meaning
The product (&00) removal failed due to a POSIX error (&01)
returned by the /START-POSIX-INSTALLATION command.
Response
In system mode: /HELP-MSG with the POSIX error code.
Please, see details in the file (&02).
IMO7010
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7010 Processing of .NEW files failed. Reason: '(&00)'. See '(&01)' for details
Meaning
(&00): 1, the list of LOGICAL-IDENTIFIER related to POSIX items
is empty
2, error during /UPDATE-RELEASE-ITEMS command
3, error during /RESTORE-RELEASE-ITEMS command
4, error during /DELETE-SAVED-RELEASE-ITEMS command
5, internal error
6, invalid call sequence
7, ADD file contains invalid lines.
Response
Please, see details in the file (&01).
IMO7011
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7011 File '(&00)' could not be deleted, processing continues
Meaning
Error occurred during the deletion of file (&00).
IMO7012
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7012 Removal of products from POSIX failed. TSN.0=Continue deinstallation, TSN. 1=Abort deinstallation
Meaning
An error occurred during the removal of products from POSIX.
Response
Please, type TSN.0 to ignore the error and continue the
deinstallation processing or type TSN.1 to abort the
deinstallation processing.
IMO7013
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7013 Fatal error during restore of original files after error for product '(&00)'. Manual recovery necessary. See '(&01)' for details
Meaning
Restore of original files for product (&00) failed
Response
Perform manually the following operations:
- open log file &01 to find which file restore failed
- if, for the product (&00), .SAV suffixed files exist,
rename not suffixed files <filename> into
<filename>.NEW
- rename suffixed files <filename>.SAV into not
suffixed file <filename>.
IMO7014
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7014 Error during cleanup of work files for product '(&00)'. Manual cleanup necessary. See '(&01)' for details
Meaning
Delete of work files for product (&00) failed
Response
Perform manually the following operations:
- open log file (&01) to find which file cleanup failed
- delete any existing files suffixed by .SAV
IMO7015
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7015 Unexpected error during POSIX processing. See '(&00)' for details
Response
See details in the file (&00).
Original $SYSROOT.IMON.ACTIONS.ADD and
$SYSROOT.IMON.ACTIONS.REM have been saved under
$SYSROOT.IMON.ACTIONS.ADD.<timestamp>.SAV and
$SYSROOT.IMON.ACTIONS.REM.<timestamp>.SAV.
IMO7016
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7016 Waiting for POSIX...
IMO7017
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7017 Deinstallation of products from POSIX cannot be executed. Reason: '(&00)'. See details in '(&01)'
Meaning
(&00): 1, No input parameter file available
2, Input parameter file cannot be read
3, Input parameter file is empty
4, Input parameter file does not contain any *REMITEM
5, :<catid>:$SYSROOT.IMON.ACTIONS.REM.# cannot be deleted
6, :<catid>:$SYSROOT.IMON.ACTIONS.ADD.# cannot be deleted
7, :<catid>:$SYSROOT.IMON.ACTIONS.REM.# does not exist
8, No POSIX product found in
:<catid>:$SYSROOT.IMON.ACTIONS.REM.#
9, File $SYSROOT.POSIX.CONFIGURATION cannot be updated
POSIX subsystem probably not available
10, REMOVE parameter file is invalid. No PVS specified
11, No REMOVE parameter file available
12, Unexpected error when reading the ADD parameter file
13, ADD parameter file is invalid. Minimum information
not available
14, Unexpected error during /START-IMON-PSX execution
15, ADD parameter file is invalid. No PVS specified
16, Unexpected error during the creation of the ADD/REMOVE
parameter file for undo processing
17, Unexpected error when reading the REMOVE parameter file
18, REMOVE parameter file is invalid. Minimum information
not available
19, No POSIX product to remove
20, :<catid>:$SYSROOT.IMON.ACTIONS.REM.# cannot be read
21, Unexpected error during update of file
:<catid>:$SYSROOT.IMON.ACTIONS.ADD or
:<catid>:$SYSROOT.IMON.ACTIONS.REM
Details can be found in (&01).
IMO7018
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7018 Deinstallation of products from POSIX on imported foreign pubset '(&00)' cannot be executed. See details in '(&01)'. Enter TSN. to continue
Meaning
(&00) = PVS on which deinstallation is requested
It is not possible to execute a dynamic deinstallation of products
from POSIX on an imported foreign pubset. You should abort
deinstallation processing otherwise POSIX files may be deleted
and further deinstallation of those products from POSIX may not
work properly.
Details can be found in (&01))
Response
Reply TSN.
The deinstall of products from POSIX is aborted and a dialog
box is displayed in IMON program to select how to continue
the deinstall processing
IMO7019
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7019 POSIX configuration file cannot be updated. TSN.0=Retry, TSN.1=Abort
Meaning
Possible reasons:
- POSIX subsystem is not started or not available
- The POSIX configuration file is still in use
or currently updated
Response
Please, type TSN.0 to continue waiting till update is possible
or type TSN.1 to stop waiting.
If you want to stop waiting, you will have to reactivate
manually the previous state of the products that have been
removed from the POSIX configuration during the undo
processing
IMO7020
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7020 POSIX configuration file not updated
Meaning
The POSIX configuration file has not been updated.
You have to reactivate manually the previous state of the
the products that have been removed from POSIX during the
undo processing.
IMO7021
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7021 Removal of products from POSIX failed. TSN.0=Continue undo processing, TSN. 1=Abort undo processing
Meaning
An error occurred during the removal of product from POSIX.
Response
Please, type TSN.0 to ignore the error and continue the
undo processing or type TSN.1 to abort the
undo processing.
IMO7022
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7022 UNDO processing continues
IMO7023
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7023 UNDO processing is aborted
IMO7024
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7024 DEINSTALL processing continues
IMO7025
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7025 Deinstall processing aborted
IMO7026
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7026 Library $TSOS.SYSPRC.IMON-BAS not compatible with current .IE procedure. Installation processing aborted. Enter TSN. to terminate
Meaning
The library $TSOS.SYSPRC.IMON-BAS is not the correct
one. Possible reasons:
- it has been overwritten by an old version
- a old version of IMON has been installed
Response
Restore the $TSOS.SYSPRC.IMON-BAS corresponding to
the installed IMON version and restart the .IE
installation procedure via /ENTER-PROC.
IMO7027
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 98
Warranty : NO
IMO7027 Product '(&00)' version '(&01)' locked. POSIX cannot be updated
Meaning
The product (&00) version (&01) is locked in the
IMON software configuration. Installation or
deinstallation in POSIX cannot be executed.
Response
To update POSIX:
- reboot the BS2000 or
- execute //ACTIVATE-UNITS or
- unlock the product with /UNLOCK-PRODUCT-VERSION command,
then restart the POSIX subsystem.
IMO7028
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7028 Unexpected error during release items update processing. Activation of product '(&00)' in POSIX not performed. See '(&01)' for details
Meaning
Error occurred during the processing of the POSIX release
items (*PS/*NP) of the product (&00). The activation of
this product is aborted.
Response
See details in file (&01).
IMO7029
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7029 No product to deinstall from POSIX. Processing continues
IMO7030
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO7030 ACTIVATE-UNITS statement suspended due to execution of other ACTIVATE-UNITS statement or POSIX product activation by POSIX startup
Meaning
A product activation for another ACTIVATE-UNITS statement or for POSIX
startup is currently executed. The execution of the current ACTIVATE-
UNITS is suspended (lock on file $SYSROOT.IMON.ACTIVATE-UNIT.SYSLST99).
IMO7031
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7031 POSIX package installation during POSIX startup suspended due to running ACTIVATE-UNITS statement
Meaning
An ACTIVATE-UNITS procedure is currently executed. The installation of
POSIX products at POSIX startup is delayed until the end of this procedure
(lock on file $SYSROOT.IMON.ACTIVATE-UNIT.SYSLST99).
IMO7032
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7032 POSIX package installation during POSIX startup resumed
Meaning
The installation of POSIX products during the POSIX startup is resumed.
IMO7033
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO7033 Product activation by ACTIVATE-UNITS resumed
Meaning
The product activation with the statement ACTIVATE-UNITS is resumed.
IMO7501
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7501 Command '(&00)' successfully processed
Meaning
Command (&00) successfully processed.
IMO7502
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7502 Command '(&00)' partially processed
Meaning
There had been at least one element not treated during
the processing of the command (&00).
IMO7503
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7503 Command '(&00)' not executed
IMO7601
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7601 User not authorized to issue command '(&00)'
Meaning
User has not the required privileges to issue the command (&00).
IMO7602
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7602 Invalid Installation Unit name
IMO7603
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7603 Invalid Installation Unit version
IMO7604
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7604 Invalid Logical Identifier
IMO7605
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7605 GET-INSTALLATION-PATH error '(&00)' for Installation Unit '(&01)', version '(&02)', Logical-Id '(&03)'
IMO7606
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7606 No .NEW file found: assuming installation of new main version or first installation or installation overwriting old files. Processing continues
IMO7607
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7607 No .SAV file found: assuming installation of new main version or first installation or installation overwriting old files. Processing continues
IMO7608
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7608 GET-INSTALLATION-VERSION error '(&00)' for Installation Unit '(&01)' version '(&02)'
Meaning
Possible reasons:
- Invalid product name or product not registered
- Invalid version or version not registered
- product/version locked
IMO7701
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7701 Internal error during processing of IMON system command '(&00)'. RC = '(&01)'
Meaning
An internal error has been detected in IMON
during the processing of (&00), RC=(&01).
Response
Contact the system administrator so that
diagnosic material can be produced if necessary
and possible.
IMO7801
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7801 DMS error '(&00)' during renaming of file '(&01)' to '(&02)'
IMO7802
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7802 DMS error '(&00)' during delete of file '(&01)'
IMO7803
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7803 DMS error '(&00)' during renaming of file '(&01)' into '(&02)'
IMO7804
Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70
Warranty : NO
IMO7804 Error during rollback of command '(&00)'
IMO7805
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO7805 Program (&00) of current package not found. Processing continues with program (&01) of current system
IMO8000
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8000 Internal error at line '(&00)' in file '(&01)'
Meaning
An internal error has been detected in IMON-SIC code in source file
(&00) at line (&01).
Response
Please contact the system administrator.
IMO8001
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8001 Memory space exhausted
Meaning
A system error occurred when requesting memory space.
Response
Please contact the system administrator.
IMO8002
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8002 Error occurred while writing on SYSLST
IMO8003
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8003 Error during call to EDT. No update of logging (EDTMRC '(&00)')
IMO8004
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8004 FHS error: '(&00)'
IMO8005
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8005 OPS error: '(&00)'
IMO8100
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8100 Invalid RI name
Meaning
The RI name is not a
<filename 1..30 without-cat-id-user-id-generation-version>
IMO8101
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8101 RI name too long
Meaning
After expansion of the meta-character "+", the RI name is longer
than 30 characters.
IMO8102
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8102 RU name too long for existing RI names with meta-character '+'
Meaning
After expansion of the meta-character "+" some RI names are longer
than 30 characters.
Response
Enter a shorter RU name or reduce all erroneous RI names.
IMO8103
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8103 Incorrect version
IMO8105
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8105 Invalid information in SYSSII : file not saved
Meaning
Some values are not allowed, regarding the view.
Response
Modify values or change view.
IMO8150
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8150 Invalid character entered
IMO8151
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8151 Invalid key pressed
IMO8152
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8152 Invalid choice
IMO8153
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8153 Selection only possible with "/"
IMO8154
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8154 Correct the invalid values or cancel input
IMO8155
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8155 Fill the mandatory fields or cancel input
IMO8156
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8156 Enter mandatory parameter texts or cancel input
Meaning
The specified item type requests at least a mandatory
parameter text as follows:
Type *DA: at least VER nnn or VER nnn* expected
Type PL*: at least LIB <libname> expected
Type SSD: at least SYS XS31 and/or SYS NXS31 expected
Type SDF: DYN <name 1..8> for Syntax-file from OSD V2.0 and/or
SYS SYSTEM,UPD-SDF-GLOB=NO for Syntax-file in OSD V1.0
Response
Enter corresponding parameter text or cancel
function with K1 and modify the entered item type.
IMO8157
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8157 Suppress parameter text or cancel input
Meaning
The specified item type does not allow parameter text
Response
Suppress entered parameter texts or cancel
function with K1 and modify the entered item type.
IMO8158
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8158 Value "P" for "Associated Filename" field not allowed for SYSREP item
IMO8159
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8159 The Default Pathname must be blank or of type <$userid>.<filename>
IMO8200
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8200 Duplicate RI name
Meaning
The same RI name has been given more than once.
Response
Remove RI name or rename RI.
IMO8201
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8201 Invalid operation on item
IMO8203
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8203 Invalid dummy flag (only "y" or " " accepted)
IMO8204
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8204 Invalid value on blank line
IMO8205
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8205 Duplicate RU
Meaning
The same RU has been given more than once.
Response
Remove RU or modify RU.
IMO8206
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8206 Invalid target-ID (A=COM, S=390, R=SRM, U=SRU, P=SPARC, I=IA64)
IMO8207
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8207 Invalid "no delivery" flag (only "y" or " " accepted)
IMO8301
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8301 File is not a SYSSII file
IMO8302
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8302 Missing information in SYSSII (record '(&00)')
IMO8303
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8303 Bad SYSSII file format (record '(&00)')
Meaning
The file has not the format of a SYSSII file.
Response
Regenerate a SYSSII file with same name or use another SYSSII file.
IMO8304
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8304 Invalid file name. Re-enter correct file name or cancel input
IMO8305
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8305 Version of SYSSII file no more supported
IMO8306
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8306 Comments truncated
IMO8307
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8307 DMS error '(&00)' on opening LOGGING file. Further information: /HELP-MSG DMS(&00)
IMO8308
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8308 Error during reading of the LOGGING file. Changes lost
IMO8309
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8309 Error during writing of the LOGGING file
IMO8400
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8400 DMS error '(&00)' on opening file '(&01)'. Further information: /HELP-MSG DMS(&00)
IMO8401
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8401 Error on writing into file '(&01)'
IMO8402
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8402 File not catalogued
IMO8404
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8404 File already catalogued
IMO8405
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8405 DMS error '(&00)' while setting a link name. Further information: /HELP-MSG DMS(&00)
IMO8406
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8406 DMS error by access on pathname associated to the logical-id '(&00)' of the release unit '(&01)' '(&02)'
Response
Please contact the system administrator.
IMO8501
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8501 SDF internal error "(&00)" at line "(&01)"
IMO8506
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8506 Invalid "FROM" version
IMO8507
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8507 Invalid "TO" version
IMO8600
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8600 Error in SYSSII '(&00)'. File not saved
IMO8601
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8601 (&00) Error(s) - (&01) Warning(s)
IMO8602
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8602 (&00): ETPND information missing
IMO8603
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8603 WARNING: missing item (&00)
IMO8604
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8604 ERROR: missing item (&00)
IMO8605
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8605 Item (&00) is not correct
IMO8606
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8606 (&00): item should be of type "DAT", "*DF" or "*DP"
IMO8607
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8607 (&00): "AAABBB" of item differs from "AAABBB" of logical id
IMO8608
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8608 (&00): "AAABBB" of the item does not match with its specified type
IMO8609
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8609 (&00): the <ruvers>-part of the item-name differs from the version of the processed release unit
IMO8610
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8610 (&00): mandatory associated item '(&01)' missing
IMO8611
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8611 (&00): superfluous "SYSREP"-item with "SYSRMS" ('(&01)') defined with "to be merged"
IMO8612
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8612 (&00): target '(&01)' and item-name not coherent
IMO8613
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8613 (&00): suffixes of the item and its logical-id ('(&01)') are not identical
IMO8614
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8614 (&00): logical-id must begin by "SYS" for SRM-item (logid: '(&01)' )
IMO8615
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8615 (&00): logical-id should begin by "SYS" or "SRU" for SRU-item (logid: '(&01)' )
IMO8616
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8616 (&00): logical-id '(&01)' may not contain BS2000-version suffix
IMO8617
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8617 (&00): superfluous language code
IMO8618
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8618 (&00): item type "*FE" does not match with language code of item
IMO8619
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8619 (&00): item type "*FG" does not match with language code of item
IMO8620
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8620 (&00): "language" value '(&01)' does not match with item suffix
IMO8621
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8621 (&00): target "(&01)" invalid, must be "A" or "S"
IMO8622
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8622 (&00): item outside checked range of versions
IMO8623
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8623 Checked version: "(&00)" Item version: "(&01)"
IMO8624
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8624 (&00): BS2000-version suffix "(&01)" of the item does not correspond to the entered parameter text
IMO8625
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8625 (&00): USER-ACCESS field must be set to "SPECIAL" and MIGRATE to "INHIBIT"
IMO8626
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8626 (&00): USER-ACCESS or/and MIGRATE fields not matching standard value
IMO8627
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8627 (&00): "IPL file" field must be set to "Y"
IMO8628
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8628 (&00): "IPL file" field should be set to "N"
IMO8629
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8629 (&00): item with BS2000-version suffix must have parameter text
IMO8630
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8630 (&00): mandatory parameter text missing
IMO8631
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8631 (&00): item with typ "(&01)" must not have parameter text
IMO8632
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8632 (&00): logical-id must begin by "SYS" for SPM-item (logid: '(&01)' )
IMO8633
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8633 (&00): invalid value or too many blanks between keyword and associated value in the following parameter text
IMO8634
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8634 LINE: '(&00)'
IMO8635
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8635 (&00): missing value in following parameter text
IMO8636
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8636 (&00): mandatory keyword missing in parameter text
IMO8637
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8637 (&00): contradiction between keyword and specified range of version in following parameter text
IMO8638
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8638 (&00): duplicate "DYN" keyword in parameter text for "SDF" item
IMO8639
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8639 (&00): logical-id should begin by "SYS" or "SPU" for SPU-item (logid: '(&01)' )
IMO8640
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8640 (&00): duplicate "VER" keyword with same version in parameter text
IMO8641
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8641 (&00): a "SDF" item contains two identical parameter texts "SYS" for a same BS2000 version
IMO8642
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8642 (&00): a "SDF" item contains two identical parameter texts "GRP" for a same BS2000 version
IMO8643
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8643 (&00): a "SDF" item contains two identical parameter texts "DEL" for a same BS2000 version
IMO8645
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8645 (&00): a "SSC" item contains two identical parameter texts "SYS" for a same BS2000 version
IMO8646
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8646 (&00): a "SSC" item contains two identical parameter texts "ADD" for a same BS2000 version
IMO8647
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8647 (&00): a "SSC" item contains two identical parameter texts "DEL" for a same BS2000 version
IMO8648
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8648 (&00): a "SSC" item contains two identical parameter texts "OPT" for a same BS2000 version
IMO8649
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8649 (&00): a "SSD" item contains two identical parameter texts "SYS" for a same BS2000 version
IMO8651
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8651 (&00): a "SSD" item contains two identical parameter texts "ADD" for a same BS2000 version
IMO8652
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8652 (&00): a "SSD" item contains two identical parameter texts "DEL" for a same BS2000 version
IMO8653
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8653 (&00): a "SSD" item contains two identical parameter texts "OPT" for a same BS2000 version
IMO8654
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8654 (&00): a "SDF" item contains two exclusive parameter texts "SYS" and "GRP" for a same BS2000 version
IMO8655
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8655 (&00): missing "SYS" parameter text for "SSD" item
IMO8656
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8656 (&00): in parameter text of library-item "LIB" keyword must follow "TYP" keyword
IMO8657
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8657 (&00): inconsistency between "TYP" parameter text and item type
IMO8658
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8658 (&00): parameter text "DEL" misplaced for library item (must follow "LIB" or "DEL")
IMO8659
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8659 (&00) : duplicate parameter text "DEL" with same value for library item
IMO8660
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8660 (&00): logical-id of item '(&01)' already defined inside a same BS2000 version
IMO8661
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8661 (&00): same "DYN" parameter text for same BS2000/OSD version than item '(&01)'
IMO8662
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8662 (&00): Corresponding "SxxSSC" item not found
IMO8663
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8663 (&00): version definition in parameter text does not match with corresponding item "(&01)"
IMO8664
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8664 (&00): Corresponding "SxxSSD" item not found
IMO8666
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8666
IMO8667
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8667 (&00) : item '(&01)' is also of type "(&02)"", at least one must be "DAT" or "*DA"
IMO8668
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8668 (&00): "To be merged"-field of SYSRMS should be "N" when a corresponding SYSREP ('(&01)') exists
IMO8669
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8669 (&00) : Item must not exist inside the range of BS2000-versions "(&01)"
IMO8670
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8670 (&00) : The corresponding "MES" item must exist inside the range of BS2000-versions "(&01)"
IMO8671
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8671 (&00) : The corresponding "MSV" item must exist inside the range of BS2000-versions "(&01)"
IMO8672
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8672 (&00) : item must not exist in BS2000-version "(&01)"
IMO8673
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8673 ITEMS PROCESSED IN ALL VERSIONS OF RANGE "(&00)"
IMO8674
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8674 ITEMS PROCESSED IN VERSION "(&00)"
IMO8675
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8675 ADDITIONAL ITEMS PROCESSED ONLY IN VERSION "(&00)"
IMO8676
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8676 (&00)
IMO8677
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8677 ----------------------------------------------------
IMO8678
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8678 --------------------------------
IMO8679
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8679 ------------------------------------------------
IMO8680
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8680 *NONE
IMO8681
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8681 (&00): "AAABBB" part of the item name does not follow the convention 57
IMO8682
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8682 (&00): SYSSII item mandatory for products defined also before BS2000/OSD V3.0 (BS2000 V12.0)
IMO8683
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8683 (&00): "LIB" parameter text missing
IMO8684
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8684 (&00): "DYN" parameter text mandatory from BS2000/OSD V2.0 (BS2000 V11.2)
IMO8685
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8685 (&00): "SYS" or "GRP" parameter text mandatory for "SDF" item up to BS2000/OSD V1.0 (BS2000 V11.0)
IMO8686
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8686 (&00): value of "LIB" parameter text must be '$TSOS.SYSDMP.DAMP'
IMO8687
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8687 (&00): value of the first "LIB" parameter text must be '$TSOS.SYSSMB.DAMP'
IMO8688
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8688 (&00): value of "VER" parameter text must be "130" or "130*"
IMO8689
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8689 (&00): The <runame> part of the item name differs from the name of the processed release unit
IMO8691
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8691 (&00): ACCESS=WRITE and USER-ACCESS=ALL/SPECIAL for item do not match with standard file protections; item can be modified by everyone
IMO8692
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8692 (&00): logical id "UNUSED" only available with types "DAT" and "*DA"
IMO8693
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8693 (&00): Invalid target for the specified single version
IMO8694
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8694 (&00): The item name associated to the logical id "SYSSII" must be "SYSSII. <runame>.<ruvers>"
IMO8695
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8695 (&00): The value of a "DYN" parameter text must not exceed 8 characters
IMO8696
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8696 (&00): logical-id must begin by "SYS" for SRU-item (logid: '(&01)' )
IMO8697
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8697 (&00): logical-id must begin by "SYS" for SPU-item (logid: '(&01)' )
IMO8698
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8698 (&00): No "*SYSTEM" record specified in the RU dependencies
IMO8699
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8699 (&00): Product not installable in following version(s) of the specified range:
IMO8700
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8700 Dependence (&00) (&01)(&02) (&03) (&04)/(&05) is not correct
IMO8701
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8701 (&00): The couple SYS/TID does not match with *SYSTEM record(s)
IMO8702
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8702 (&00): Conflict with dependence (&01) (&02)(&03) (&04) (&05)/(&06)
IMO8703
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8703 (&00): Only one global 'COPY' parameter text can be specified
IMO8704
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8704 (&00): Operand must be <filename> with or without userid
IMO8705
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8705 (&00): RI "S*NLIB" is not of type "*PS" or "*NP". It will not be treated by automatic POSIX mecanisms
IMO8706
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8706 (&00): Operand must be of SDF-Type <composed-name_1..64_with-underscore>
IMO8707
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8707 (&00): logical-id must begin by "SIN" for SRMLIB-item or SPMLIB-item (logid: '(&01)')
IMO8708
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8708 *PS or *NP item must be USER-ACCESS=ALL and ACCESS=READ
IMO8709
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8709 (&00): a "MES" item contains two identical "DEL" parameter texts for the same BS2000 version
IMO8710
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8710 (&00): logical-ID must begin with "SYS" for SIM-item (logid: '(&01)' )
IMO8711
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8711 (&00): logical-id must begin with "SYS" or "SIU" for SIU-item (logid: '(&01)' )
IMO8712
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8712 (&00): logical-id must begin with "SYS" for SIU-item (logid: '(&01)')
IMO8713
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8713 (&00): logical-ID must begin with "SYS" for SKM-item (logid: '(&01)')
IMO8714
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8714 (&00): logical-ID must begin with "SYS" or "SKU" for SKU-item (logid: '(&01)' )
IMO8715
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8715 (&00): logical-ID must begin with "SYS" for SKU-item (logid: '(&01)' )
IMO8716
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8716 (&00): The text of the "DEL" parameter must not exceed 8 characters
IMO8717
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8717 (&00): Target not supported
IMO8800
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8800 Error on '(&00)' link name. FHS interface abnormally terminated
IMO8801
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8801 DMS error '(&00)' on FHS library '(&01)'. Further information: /HELP-MSG DMS(&00). FHS interface abnormally terminated
IMO8900
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8900 File '(&00)' not saved
IMO8901
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8901 File '(&00)' saved
IMO8902
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8902 No previous item
IMO8903
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8903 No more items
IMO8904
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8904 Existing logging removed
IMO8905
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8905 No logging to remove
IMO8906
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8906 No RI selected
IMO8907
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8907 The opened SYSSII file has been created with '(&00)' with errors
IMO8908
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8908 File '(&00)' saved with errors (unusable for further processing except by IMON-SIC from V2.3)
IMO8909
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8909 Installation parameters are inhibited with the specified type
IMO8910
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8910 The opened SYSSII file has been created with '(&00)' without error
IMO8911
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8911 SYSSII file opened
IMO8912
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8912 The version of IMON-SIC used for the creation of this SYSSII is higher than the current version
IMO8913
Destination: USER-TASK Routing code: Weight:
Warranty : NO
IMO8913 Only 3 comment lines permitted for customer SYSSII
IMO9001
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9001 Command successfully processed
IMO9002
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9002 Installation unit '(&00)' not found in IMON-GPN SCI. Command abnormally terminated
IMO9003
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9003 Installation unit '(&00)' version '(&01)' not found in IMON-GPN SCI. Command abnormally terminated
IMO9004
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9004 Logical-id '(&00)' of installation unit '(&01)' version '(&02)' not found in IMON-GPN SCI. Command abnormally terminated
Meaning
Possible Reasons :
- Logical-id does not exist in IMON-GPN SCI.
- Logical-id exists in IMON-GPN SCI but not for the current system.
To get it, the right TARGET value must be used in the command.
IMO9005
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9005 Pathname cannot be modified as specified. Command abnormally terminated
IMO9006
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9006 Required privilege missing. Command abnormally terminated
Meaning
Required privilege: SUBSYSTEM-MANAGEMENT.
IMO9007
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9007 Version '(&00)' syntactically incorrect. Command abnormally terminated
Meaning
Syntax of VERSION Operand: (V)nn.n(@(nn)) (n=digit, @=upper case).
IMO9008
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9008 Files of installation unit '(&00)' version '(&01)' not accessible. Command abnormally terminated
Meaning
The user has not the DMS access on files that are necessary to
execute the command.
IMO9009
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9009 Syntax error in input for IMOPSXX server: error # '(&00)'. Command abnormally terminated
Meaning
(&00): error type. Possible values are
01: Input string too long
02: String 'INSTALLATION-UNIT=' not found
03: Invalid length for installation unit value
04: String 'VERSION=' not found
05: Invalid length for version value
06: String 'LOGICAL-ID-<i>' not found
07: Invalid length for logical-id value
08: String 'DEFAULT-PATH-<i>' not found
09: String 'DEFAULT-PATH-<i>' not found after corresponding
'LOGICAL-ID-<i>'
10: Invalid length for pathname value
11: String 'COMMAND=' not found
12: Invalid length for command string
13: Invalid command string
14: Undefined '%<logical-id>' used in the command string
15: Invalid Installation Unit name
Response
Please contact the system administrator.
IMO9011
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9011 No information corresponding to the selection found in IMON-GPN SCI
IMO9012
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9012 Insufficient privilege to show more information
IMO9013
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9013 Logical-id '(&00)' of installation unit '(&01)' version '(&02)' not found in IMON-GPN SCI. Default value is used
Meaning
The user has no access to all logical-ids necessary to
execute the command.
IMO9014
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9014 Invalid pathname '(&00)'
Meaning
Possible Reasons :
- The format of the pathname is syntactically not correct.
Further information: /SHOW-FILE-ATTRIBUTES '(&00)'.
- A system error occurred when completing file name.
IMO9015
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9015 Product '(&00)' not found. Command abnormally terminated
IMO9016
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9016 Product '(&00)' version '(&01)' not found. Command abnormally terminated
IMO9017
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9017 Command cancelled with K2-key
IMO9018
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9018 Syntax error in operand INSTALLATION-UNIT '(&00)'. Command abnormally terminated
Meaning
Syntax of INSTALLATION-UNIT operand: 1..30 characters:
- the first character must be an upper case, a digit or "@",
- the other characters must be upper cases, digits, "@", "+", "-",
"/" or ".".
IMO9019
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9019 Syntax error in operand PRODUCT-NAME '(&00)'. Command abnormally terminated
Meaning
Syntax of PRODUCT-NAME operand: 1..30 characters:
- the first character must be an upper case, a digit or "@",
- the other characters must be upper cases, digits, "@", "+", "-",
"/" or ".".
IMO9020
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9020 The product '(&00)' version '(&01)' is not selectable. Command abnormally terminated
Meaning
Possible Reasons :
- It is a TPR DSSM subsystem.
- It is a DSSM subsystem and SCOPE=SYSTEM is given.
- The specified version of the product is not a subsystem loadable with
DSSM. Another version of the product can be loaded by DSSM.
- DSSM version is V3.5.
IMO9021
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9021 Pathname modification has been enforced
IMO9022
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9022 PUBSET "(&00)" not referred in the SCI. Command successfully processed
IMO9023
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9023 Nothing presently selected. Command successfully processed
IMO9024
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9024 Product '(&00)' version '(&01)' not selectable
Meaning
Possible Reasons :
- It is a TPR DSSM subsystem.
- It is a DSSM subsystem and SCOPE=SYSTEM is given.
- The specified version of the product is not a subsystem loadable with
DSSM. Another version of the product can be loaded by DSSM.
- DSSM version is V3.5.
IMO9025
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9025 File name "(&00)" cannot be completed. Command abnormally terminated
IMO9026
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9026 IMON subsystem cannot be started. Command abnormally terminated
IMO9027
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9027 File '(&00)' not cataloged. Processing continues
IMO9028
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9028 Invalid TARGET value "(&00)". Command abnormally terminated
Meaning
Allowed values : A/S/R/U/P/I/K and *STD
IMO9029
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9029 Logical-id '(&00)' (Target '(&03)') of installation unit '(&01)' version '(&02)' not found in IMON-GPN SCI. Command abnormally terminated
IMO9030
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9030 Product '(&00)' is a not started DSSM subsystem that is not registered in the IMON-GPN SCI. Command abnormally terminated
IMO9031
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9031 No logical-id for the installation unit '(&00)' version '(&01)' defined in the IMON-GPN SCI. Command abnormally terminated
IMO9032
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9032 Logical-id '(&00)' of installation unit '(&01)' version '(&02)' not found in IMON-GPN SCI. Command abnormally terminated
Meaning
The user has no access to all logical-ids that are necessary to
execute the command.
IMO9033
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9033 Version selected but related product not found. Command successfully processed
Meaning
No version of this product is defined neither in IMON-GPN SCI nor
in the DSSM catalog. However since DSSM V3.6, the version is selected.
A further START-XXX command will load the product using the default
path name.
IMO9034
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9034 Temporary file character "#" not allowed for new prefix
IMO9035
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9035 Invalid Logical-id
Meaning
The wildcard specification accepts only following syntax:
"**" or "xxx*" or "*xxx*".
IMO9036
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9036 Subsystem IMON loaded. Command abnormally terminated
Meaning
When the subsystem IMON is started, his SCI is locked and
can not be saved or restored.
Response
Stop the subsystem IMON and enter the command again.
IMO9037
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9037 Selected product '(&00)' version '(&01)' not accessible
Meaning
Possible reasons:
- This version of product has been deinstalled or removed.
- This version of product is currently locked.
IMO9038
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9038 Error when restoring the SCI. Reason :'(&00)'. Command abnormally terminated
Meaning
Possible reason:
01 - Filename must be < 50 long
02 - Error during /SECURE on IMON SCI
03 - New Imon SCI not valid
04 - New Imon-GPN SCI not valid
05 - DMS error (See CONSLOG for more information)
IMO9039
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9039 DMS error during copy of SCI
Meaning
For more information, consult the console logging.
IMO9090
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9090 System error: RC= '(&00)'. Command abnormally terminated
Meaning
A system error has been detected.
Further information can be found in the SERSLOG file (record IMO9000).
Response
Please contact the system administrator.
IMO9091
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9091 Internal error:. RC= '(&00)'. Command abnormally terminated
Meaning
An internal error has occurred. Further information possibly
in the SERSLOG file (record IMO9000).
Specific error situation : RC 0000000A
- happens when access is performed to a very old SCI for
which an IMON conversion is necessary. In this case,
the accessed SCI must be previously converted as follows:
/START-IMON IN=SDF
//MODIFY-IMON-OPTIONS <SCI-name>
//END
Response
Please contact the system administrator.
IMO9092
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9092 Error when calling '(&01)' function. Return code: '(&00)'
Meaning
The function '(&01)' returns an unexpected return code.
Further information in the SERSLOG file (record IMO9000)
Response
Please contact the system administrator.
IMO9100
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9100 Command abnormally terminated
IMO9101
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9101 System or internal error. Command abnormally terminated
IMO9103
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9103 Command partially performed
IMO9200
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9200 DMS error '(&00)' on '(&01)' IMON-GPN SCI. DMS function: '(&02)'. Further information: /HELP-MSG DMS(&00)
IMO9201
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9201 Error occurred during IMON-GPN initialisation. Subsystem not initiated
IMO9202
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9202 IMON-GPN SCI version not supported. Subsystem not initiated or command abnormally terminated
IMO9203
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9203 '(&00)': Bad IMON-GPN SCI format. Subsystem not initiated or command abnormally terminated
IMO9204
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9204 IMON-GPN SCI '(&00)' invalid. Do you want to enter another file name? answer (*NO=session aborted; <filename>)
Meaning
*NO : session will be aborted
<filename> : name of an IMON-GPN SCI file.
IMO9205
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9205 Inconsistency in record number '(&00)' of IMON-GPN SCI. Subsystem not initiated or command abnormally terminated
IMO9206
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9206 IMON-GPN initialisation successfully processed. '(&00)' used as IMON-GPN SCI
IMO9207
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9207 '(&00)': Non-standard IMON-GPN SCI was used in the session. Do you want to copy it under the standard name? answer (Y=copy; N=no copy)
Meaning
IMON-GPN has been started with a not standard SCI.
Y: Contents of the current SCI will be available for the next
session.
N: Changes in the current session are lost for the next
session.
IMO9208
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9208 Rename of PUBSET for file '(&00)' not performed. Processing continues
Meaning
Possible reason:
- A pathname with the new catid is too long.
IMO9209
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9209 '(&00)' is an invalid IMON-GPN SCI filename. Command abnormally terminated
IMO9210
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9210 SCI '(&00)' does not exist. Command abnormally terminated
IMO9211
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9211 DMS error '(&00)' on '(&01)' IMON SCI. Further information: /HELP-MSG DMS(&00)
IMO9212
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9212 Rename of PUBSET/USERID/PREFIX for file '(&00)' not performed.
Meaning
Reason:
- The pathname with the new catid/userid/prefix is too long.
IMO9213
Destination: CONSOLE Routing code: * (main console) Weight: 99
Warranty : YES
IMO9213 Rename of PUBSET/USERID/PREFIX for file '(&00)' not performed.
Meaning
Reason: The pathname has been defined with "UPDATE=NO".
Response
Enter command again with operand "ENFORCE=*YES".
IMO9214
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9214 Specified "OLD-STRING" '(&00)' not referred in the SCI. Command successfully processed
IMO9215
Destination: USER-TASK Routing code: Weight: 50
Warranty : YES
IMO9215 Due to previous problems, the SCI is left unchanged. Command abnormally terminated