## HSMCOPY

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSMCOPY Copyright (C) (&01) (&00). All rights reserved

## HSMLOAD

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSMLOAD Program '(&00)', version '(&01)' of '(&02)' loaded from file '(&03)'

## HSM0000

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0000 TEST MESSAGE '(&00)', '(&01)'

## HSM0001

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0001 HSMS VERSION '(&00)' READY

### Meaning

The TU program HSMS is ready to accept statements.

### Response

Enter HSMS statements.

## HSM0002

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0002 HSMS STATEMENT ACCEPTED

### Meaning

The statement was accepted for execution by a HSMS server task.
The status of the statement can be displayed by means of SHOW-REQUESTS.

### Response

After the request is terminated more detailed information can be
obtained from the statement report.

## HSM0003

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0003 HSMS STATEMENT COMPLETED

### Meaning

The statement was executed without error.

### Response

See statement report, if created, for further details.

## HSM0004

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0004 HSMS STATEMENT COMPLETED WITH WARNINGS

### Meaning

Warnings were issued during execution of the statement.
For action statements warnings are issued into the statement report
by HSMS or ARCHIVE when objects specified by the user (e.g. files)
cannot be processed.

### Response

Check statement report, if created.

## HSM0005

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0005 HSMS STATEMENT COMPLETED WITH ERRORS

### Meaning

Errors were detected by HSMS during execution of the statement.
For action statements the errors are shown in the statement report.

### Response

For more detailed information about the error cause see the previous
message or the statement report.

## HSM0006

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0006 ERROR DURING VALIDATION. HSMS STATEMENT REJECTED

### Meaning

For more detailed information see the previous message.

### Response

Re-enter statement with corrected operands.

## HSM0007

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0007 MAXIMUM WAIT TIME EXPIRED. PROCESSING OF HSMS STATEMENT CONTINUES ASYNCHRONOUSLY

### Meaning

The maximum time allowed for waiting for a statement to terminate has
expired. HSMS continues processing of the statement asynchronously.

### Response

Monitor statement processing by means of the SHOW-REQUESTS statement,
possibly check statement report.

## HSM0008

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0008 ERROR DETECTED DURING EXECUTION. HSMS STATEMENT ABORTED

### Meaning

An error was detected which prevents further processing.

### Response

For more detailed information about the error cause see the statement
report or information sent to the operator console in case of system
error.
After removal of the error cause the request may be restarted if it has
the status INTERRUPTED.

## HSM0009

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0009 ERROR DETECTED DURING EXECUTION. HSMS STATEMENT REJECTED

### Meaning

An error was detected which prevents further processing.

### Response

For more detailed information about the error cause see the statement
report.

## HSM0010

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0010 HSMS STATEMENT ACCEPTED FOR SIMULATION

### Meaning

The statement was accepted for simulated execution by a HSMS server
task. No real access to volumes and devices will occur!

### Response

After statement termination check the reduced statement report.

## HSM0011

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0011 HSMS STATEMENT SIMULATION COMPLETED

### Meaning

The statement was processed without error while HSMS was operating in
simulated mode. No real access to volumes and devices occurred.

### Response

For more detailed information see the reduced statement report.

## HSM0012

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0012 END OF OUTPUT LIST REACHED

## HSM0013

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0013 END OF DISPLAY REACHED

## HSM0014

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0014 HSMS PROGRAM TERMINATED

### Meaning

The END statement was recognized and the HSMS-Program was unloaded.

## HSM0015

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0015 ACCESS TO S2 STORAGE LEVEL. PLEASE WAIT

### Meaning

The current file has been migrated to S2 storage level (tapes or
cartridges). The recall of the migrated data may take some time.

### Response

Please wait!

## HSM0016

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0016 ERROR DURING RECALL PROCESSING. RECALL PROCESSING ABORTED

### Meaning

The migrated data could not be recalled due to an internal error.

### Response

An additional error report will be printed if the error occurred
in a HSMS server task.

## HSM0017

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0017 END OF FILE REACHED. NO END STATEMENT FOUND

### Meaning

During read from SYSDTA the logical end of file was reached without
processing of the END statement. HSMS will be terminated abnormally.

### Response

Check SYSDTA assignment and correct input, if necessary.

## HSM0018

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0018 HSMS ABNORMALLY TERMINATED

### Meaning

For more detailed information see the previous message.

## HSM0019

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0019 HSMS SERVER TASK TERMINATED ABNORMALLY. THE REQUEST WAS ABORTED: NO REPORT CREATED

### Meaning

The assigned HSMS server task terminated abnormally while processing
this request, the request was aborted.
A report file could not be created. It is possible, however, that a dump
exists.

### Response

Use the SHOW-REQUESTS statement for information about the current request
state. If necessary, restart the request.

## HSM0020

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0020 REQUEST IS SENT TO '(&01)' '(&00)'

### Meaning

A request for a shared-pubset is given on a system:
(&00) : BCAM/MSCF name of the system that receives the request.
(&01) : defines whether the request is sent to a master system
or to a backup server.

## HSM0021

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0021 PARAMETER LIST IS NOT ALIGNED ON FULLWORD-BOUNDARY. STATEMENT REJECTED

### Response

The parameter list must be fullword-aligned.
Correct the program and try again.

## HSM0022

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0022 MAXIMUM WAIT TIME EXPIRED. STATEMENT REJECTED

### Meaning

Possible reasons:
- tape handling currently not permitted,
- request not started by HSMS server task within maximum wait time,
(no server task available, all occupied by other requests).
- maximum wait time for shared update conflict expired.

### Response

Repeat request after a while, maybe asynchronously
(WAIT-FOR-COMPLETION=*NO).

## HSM0030

Destination: USER-TASK Routing code: Weight: 80

Warranty : YES

HSM0030 REQUEST '(&00)' CREATED IN ENVIRONMENT '(&01)' WITH DATE '(&02)' AND TIME '(&03)'

### Meaning

The request was accepted by HSMS.
This message displays the parameters which identify the request:
(&00) : Request name, given by the user or default-generated by HSMS.
(&01) : Request environment SF for SINGLE-FEATURE
or SM(<cat-id>) for a specific SM-pubset environment.
(&02) : Request Date assigned by HSMS.
(&03) : Request Time assigned by HSMS.
These parameters may be given in subsequent management statements
such as SHOW-REQUESTS, RESTART-REQUESTS and DELETE-REQUESTS
to address uniquely the request.

## HSM0040

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0040 CHECK OF FILES FROM THE VERSION BACKUP ARCHIVE '(&00)' STARTED.

### Meaning

The message indicates the start of the check whether there are
files in the archive directory that have been deleted from the
processing level or have already been recognized as deleted and
now exist again.
(&00) : archive name

## HSM0041

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0041 FILE '(&00)' - NUMBER OF BACKUP VERSIONS IS UPDATED TO '(&01)' FROM CATALOG ENTRY.

### Meaning

The number of backup versions in the directory is updated from
catalog entry of file. The file still exists on the processing
level. If there was a deletion mark, it was removed.
(&00) : file name
(&01) : new number of backup versions

## HSM0042

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0042 FILE '(&00)' - NUMBER OF BACKUP VERSIONS IS UPDATED TO '(&01)' FROM MANAGEMENT CLASS.

### Meaning

The number of backup versions in the directory is updated from
management class of file. The file still exists on the processing
level. If there was a deletion mark, it was removed.
(&00) : file name
(&01) : new number of backup versions

## HSM0043

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0043 FILE '(&00)' - RECOGNIZED AS DELETED, DELETION DATE SET TO '(&01)'.

### Meaning

The file does not exist on the pubset. Current date was written
as deletion date in the directory.
(&00) : file name
(&01) : current date

## HSM0044

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0044 FILE '(&00)' - RECOGNIZED AS EXISTING AGAIN, DELETION DATE HAS BEEN REMOVED.

### Meaning

The file detected as deleted exist again on the pubset. The deletion
date in the directory has been removed. If there was a mark for
deletion, it was removed.
(&00) : file name

## HSM0045

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0045 FILE '(&00)' - FORCE DELETION MARK HAS BEEN REMOVED.

### Meaning

The force deletion mark of the file has been removed from the
directory as the file still exists on the pubset.
(&00) : file name

### Response

Perform REORGANIZE-VERSION-BACKUP statement right after
MODIFY-ARCHIVE FILES=*FORCE-DELETION to delete all the file
versions from the directory.

## HSM0046

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0046 NO CHANGES IN FILES STATES HAVE BEEN DETECTED.

### Meaning

No files from the version backup archive have been changed on the
processing level.

## HSM0047

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0047 CHECK OF FILE '(&00)' HAS FAILED (REASON '(&01)').

### Meaning

(&00) : file name,
(&01) : reason of error:
'1' : the file resides on not imported pubset,
'2' : FSTAT macro reported an error for the file,
'3' : F-record in directory is corrupted.

### Response

In the last case do not modify the directory (!) and
pass it for diagnosis together with statement report.

## HSM0050

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0050 NOT SUITABLE RESTORE STRATEGY FOR VERSION BACKUP ARCHIVES.

### Meaning

Restoring from version backup archives via //RESTORE-FILES
or //RESTORE-LIBRARY-ELEMENTS is done according to
original save versions. So, when restoring from version backup
archives, it is allowed only to specify SELECT-SAVE-VERSIONS=*STD
or SELECT-SAVE-VERSIONS=*BY-ATTRIBUTES(SAVE-VERSION-DATE=
*BY-ORIGINAL-DATE).

### Response

Correct statement and retry

## HSM0100

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0100 SUBSYSTEM HSMS READY FOR NORMAL OPERATION

### Meaning

The subsystem HSMS has either been successfully loaded for normal
operation or been switched to this operating mode.
Action statements may be issued and will be executed, if any HSMS server
task is available.

## HSM0101

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0101 SUBSYSTEM HSMS READY FOR DEFINITION AND INFORMATION OPERATION

### Meaning

The subsystem HSMS has either been successfully loaded for definition
and information operation or been switched to this operating mode.
No action statements will be accepted.

### Response

Switch to operational mode for action statements to be accepted.

## HSM0102

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0102 SUBSYSTEM HSMS READY FOR SIMULATED OPERATION

### Meaning

The subsystem HSMS has either been successfully loaded for simulated
operation or been switched to this operating mode.
Action statements will be accepted, but no real access to volumes or
devices will occur.

### Response

Switch to operational mode to allow real access.

## HSM0103

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0103 HSMS REQUEST FILE INCONSISTENT. SWITCH TO DEFINITION AND INFORMATION OPERATION

### Meaning

The HSMS request file is inconsistent and cannot be used.
Any errors detected by DMS/CMS were reported in previous message HSM0432.
HSMS switched back to definition and information operation.

### Response

Upon a subsequent switch to the desired operation mode
the defective entries in the request file will be ignored.
For definitive correction delete the request file.

## HSM0104

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0104 HSMS CONTROL FILE INITIALIZED WITH PARAMETERS FOR INITIAL INSTALLATION

## HSM0105

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0105 HSMS SERVER TASK STARTED

### Meaning

This task (with type subtask) is available in the system to process
HSMS action statements until it is terminated by HSMS.

## HSM0106

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0106 HSMS SERVER TASK TERMINATED

### Meaning

This task was terminated by HSMS.

## HSM0107

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0107 RESCHEDULING OF '(&00)' REQUESTS COMPLETED FOR ENVIRONMENT '(&01)' (NUMBER OF REQUESTS ACCEPTED = '(&02)', NUMBER OF REQUESTS INTERRUPTED = '(&03)')

### Meaning

The message is issued when the rescheduling processing for a given
request-file is completed. The rescheduling occurs at subsystem creation
and at SM-pubset import.
(&00) : BS2000 for central requests.
HSMS-CL for remote HSMS-client (UNIX) requests.
(&01) : SF for Single-Feature environment.
SM(<cat-id>) for a specific SM-pubset environment.
(&02) : Number of requests found with status ACCEPTED.
These requests are automatically reactivated by the rescheduling
process.
(&03) : Number of requests found with status INTERRUPTED.
These requests may be restarted or deleted by the use of the
statements RESTART-REQUESTS or DELETE-REQUESTS.
For HSMS-Client requests, the restart or deletion may be done by
the client using the CLI commands bsrstrt or bsrm.

## HSM0108

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0108 HSMS REQUEST '(&00)' REMOVED FROM WAIT QUEUE

### Meaning

The /EXPORT-PUBSET of the SM-pubset prevented the scheduling of the
request. The request will be restarted at the next import of the
environment. For Concurrent Copy requests, the deinitialization of the
session has been processed, and the restart of the request will not be
possible.

## HSM0109

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0109 HSMS '(&00)' COMMUNICATION TASK STARTED

### Meaning

This task is available in the system to process HSMS statements coming
from the network until it is terminated by HSMS.
&00 : FIRST/SUB/ANSWER

## HSM011A

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM011A ERROR '(&00)' WHEN CALLING SYSTEM INTERFACE '(&01)' FOR CATID '(&02)'

### Meaning

The system interface (&01), called by HSMS for catid (&02), reported an
error, i.e. returned the unexpected return code (&00).

### Response

Interpret the return code (&00) using the interface documentation.
If necessary contact system diagnosis.
For some interface errors ($GCF, ...) an entry is created in SERSLOG
file with identificator HSM0115 for diagnose purpose.

## HSM011B

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM011B NODE '(&00)' WITH IP-ADDRESS '(&01)' IS NOT DEFINED AS CALENDAR NODE

### Response

To be used as Calendar Node, a node must be defined in HSMS parameters
as PRIMARY_CN or SECONDARY_CN.

## HSM0110

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0110 BS2000 VERSION '(&00)' NOT SUPPORTED. HSMS CANNOT BE LOADED

### Meaning

The subsystem HSMS cannot be loaded in the current BS2000 version.

### Response

Contact the system administrator, install a compatible HSMS version and
load subsystem again.

## HSM0111

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0111 SUBSYSTEM ARCHIVE VERSION '(&00)' '(&01)'. HSMS CANNOT BE LOADED

### Meaning

The subsystem HSMS cannot be loaded with the current ARCHIVE
version (&00) and status (&01).

### Response

Contact the system administrator.

## HSM0112

Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70

Warranty : NO

HSM0112 ACTION '(&01)' NOT ALLOWED FOR SUBSYSTEM '(&01)'

### Meaning

An action has been requested for a subsystem, although this action is
internally not allowed by HSMS.
&00: requested action
&01: subsystem

### Response

Contact your service engineer.

## HSM0113

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0113 NO JOIN ENTRY AVAILABLE FOR USER ID 'SYSHSMS' CATALOG-ID '(&00)'

### Meaning

No JOIN entry exists for the HSMS administrator ID SYSHSMS.

### Response

Create JOIN entry without account number and load the subsystem again.

## HSM0114

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0114 INTERNAL ERROR. SWITCH TO DEFINITION AND INFORMATION OPERATION

### Meaning

An HSMS-internal error was detected which prevents further processing in
operational mode.

### Response

Check the previous HSMS message, remove the error cause and possibly
contact the HSMS administrator.

## HSM0115

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0115 ERROR '(&00)' WHEN CALLING SYSTEM INTERFACE '(&01)'

### Meaning

The system interface (&01), called by HSMS, reported an error
i.e. returned the unexpected return code (&00).

### Response

Interpret the return code (&00) using the interface documentation.
If necessary contact system diagnosis.
For some interface errors ($GCF, ...) an entry is created in SERSLOG
file with identificator HSM0115 for diagnose purpose.

## HSM0116

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0116 INSUFFICIENT CLASS 5 MEMORY

### Meaning

A class 5 memory request cannot be satisfied because there is
either not enough contiguous user address space available or
the system suffers from memory saturation.

## HSM0117

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0117 NOT ENOUGH VIRTUAL ADDRESS SPACE FOR HSMS MEMORY POOL

### Meaning

The common memory pool, used for communication with HSMS server tasks,
cannot be created in memory class 5. Subsystem HSMS is not loaded.

### Response

Create a smaller memory pool, i.e. load subsystem using
START-HSMS ...,COMMON-MEMORY-SIZE=xxx.
CAUTION: Change memory pool size in HSMS control file
using MODIFY-HSMS-PARAMETERS statement with VALID=PERMANENT.

## HSM0118

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0118 INTERNAL ERROR '(&00)' IN MODULE '(&01)'

### Meaning

A module of the HSMS control program detected an internal error.

### Response

Pass system dump, console log and HSMS report for diagnosis.

## HSM0119

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0119 ERROR '(&00)' DURING '(&01)'-ACCESS TO JOB VARIABLE '(&02)'

### Response

For more detailed information about the error code see the BS2000 manual
'Job Variables'.

## HSM012A

Destination: CONSOLE Routing code: U Weight: 30

Warranty : YES

HSM012A PREPARE FOR REQUEST '(&00)' OF USER '(&01)' WITH REQUEST-DESCRIPTOR '(&02)'

### Meaning

This message is issued when a user submits a request with a descriptor.
The descriptor is destinated to the operator.
&00: Request name.
&01: User who issued the request.
&02: Request descriptor.

## HSM0120

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0120 REQUEST '(&00)' STARTED FOR TSN '(&01)'

### Meaning

This message is used to relate the request (&00), created by the task with
TSN (&01), to a HSMS server task whose TSN is shown in the console log.

## HSM0121

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0121 COLLECTOR REQUEST STARTED

### Meaning

Several requests for a system archive and its standard save file are
combined into a collector request and will be processed together.

## HSM0122

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0122 INVALID FORMAT IN HSMS REQUEST FILE. REQUESTS CANNOT BE PROCESSED

### Meaning

Some requests in the HSMS request file were created by an older version
of HSMS. These requests cannot be processed any more.

### Response

For definitive correction of this error delete the request file.

## HSM0123

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0123 ACCOUNT NUMBER '(&00)' INVALID FOR TSOS/SYSHSMS. HSMS SERVER/COMMUNICATION TASK CANNOT BE CREATED

### Meaning

No (server/communication) task can be created for user ID TSOS/SYSHSMS
using the assigned account number.

### Response

Declare a valid account number for HSMS server tasks using
MODIFY-HSMS-PARAMETERS for the running session or permanent and,
possibly using the same statement, repeat creation of subtasks.

## HSM0124

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0124 USER ID '(&00)' OF REQUEST '(&01)' INVALID. REQUEST IS IN 'INTERRUPT' STATE

### Meaning

The user ID has been severed between acceptance and start of the request.

### Response

Restart request after reactivating of the user ID.

## HSM0125

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0125 CONTROL FILE AND REQUEST FILE MUST RESIDE ON AN EXCLUSIVELY IMPORTED PUBSET

### Response

User ID SYSHSMS must be assigned to another default cat ID or pubset
of the default cat ID of user ID SYSHSMS must be accessible, locally and
exclusively imported.

## HSM0126

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0126 CONTROL FILE DESTROYED. LOADING OF HSMS ABORTED

### Meaning

During access to control file a DMS error occurred. The existing file
cannot be used. Loading of HSMS cannot be continued.

### Response

Analyse the detected DMS error with help of the preceding message HSM0432.
Correct or delete control file, start HSMS again.

## HSM0127

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0127 INTERNAL ERROR '(&00)' WHEN CALLING BOURSE INTERFACE '(&01)'

### Meaning

After calling the above mentioned bourse interface HSMS gets an unexpected
return code. The communication between tasks operating within HSMS is
deeply damaged. During unloading of the HSMS bourse errors may occur due
to the destruction of the HSMS bourses and there are no effects.

### Response

In case of normal running it will be useful to stop HSMS and to start it
again, because a secure run of HSMS is not longer guarantied.
Contact the system administrator.

## HSM0128

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0128 INTERNAL ERROR '(&00)' WHEN CALLING INTERFACE '(&01)' OF SUBSYSTEM MANAGEMENT (DSSM)

### Meaning

After calling the above mentioned DSSM function HSMS gets an unexpected
return code. This may be a result of an incorrect installation of the
subsystems HSMS and ARCHIVE.

### Response

Check, whether the installed versions of HSMS and ARCHIVE are compatible
and no wrong version of ARCHIVE has been started before start of HSMS.
If necessary correct the installation error.
Contact the system administrator.

## HSM0129

Destination: CONSOLE Routing code: U Weight: 70

Warranty : NO

HSM0129 AFTER NOTIFICATION OF SUBSYSTEM MANAGEMENT (DSSM) HSMS GETS ERROR CODE '(&00)'

### Meaning

HSMS has called DSSM in order to notify the subsystem management that the
subsystem specific initialization or 'stop-commission' is completed,
and it has got an unexpected error return code. During the BS2000 session
running, HSMS cannot be used longer.

### Response

HSMS can be started after a new start of the whole system.

## HSM013A

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM013A REMOTE NODE '(&00)' WITH ADDRESS '(&01)' TRIED TO BE USED AS A CALENDAR NODE

### Meaning

This node is not authorized to be a calendar node for current HSMS server.

## HSM0130

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0130 WARNING : SOME COMMUNICATION TASKS NOT CREATED

## HSM0131

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0131 ERROR. COMMUNICATION WITH HSMS CLIENT NOT POSSIBLE

### Meaning

Either first communication task or answer task or all communication
tasks cannot be created so that communication is not possible.

## HSM0132

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0132 HSMS '(&00)' COMMUNICATION TASK TERMINATED

### Meaning

This task was terminated by HSMS.

## HSM0133

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0133 HSMS '(&00)' COMMUNICATION TASK REPORTS '(&01)'

### Meaning

A communication task reports an EVENT.
&01: HSMS communication task type (FIRST, SUB OR ANSWER)
&01: HSMS EVENT.

## HSM0134

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0134 HSMS ANSWER-COMMUNICATION-TASK STARTS SENDING ANSWERS TO NODE '(&00)'

## HSM0135

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0135 NO CONNECTION POSSIBLE TO SUBSYSTEM HSMS-SV

### Meaning

Subsystem creation/connection failed. No NODE-S0 will be supported
by HSMS.

## HSM0136

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0136 NO CONNECTION TO SUBSYSTEM '(&00)' POSSIBLE. '(&01)' INOPERABLE

### Meaning

&00: called subsystem.
&01: inoperable function/task of HSMS.
Possible reason: subsystem not started.

## HSM0137

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0137 HSMS CLIENT PROTOCOL ERROR DETECTED DURING '(&00)' (DIAGNOSE INFO '(&01)'). CONNECTION CANCELLED

### Meaning

&00: communication step which detected the error.
&01: diagnose information.
An HSMS CLIENT is sending a network message which does not
meet the HSMS CLIENT protocol.
The communication task is not able to handle the
client. The connection is cancelled.

### Response

Determine which CLIENT is sending messages.
Verify whether the CLIENT version is compatible with HSMS.
If necessary, pass the information for diagnosis.
Verify that another product is not using the same communication port as
HSMS-SV.

## HSM0138

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0138 WARNING: HSMS OUTPUT REPORT FOR USER CANNOT BE BUILT. INTERMEDIATE REPORT '(&00)' STILL AVAILABLE

### Meaning

The final HSMS report in printable format cannot be built.
The intermediate report is however still available but more difficult
to be read.

## HSM0139

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0139 HSMS REQUEST FILE VERSION NOT COMPATIBLE. HSMS CANNOT BE LOADED

### Meaning

The version of the HSMS request file is not compatible with the current
HSMS version.

### Response

Delete the request file and restart HSMS.

## HSM0140

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0140 REMOTE NODES-S0 CONTAINED IN THE HSMS CONTROL FILE ARE SKIPPED

### Meaning

HSMS-SV not present; remote nodes-S0 are not supported by HSMS.

## HSM0141

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0141 NO MORE S1 LEVEL DEFINED FOR THE SM-PUBSET '(&00)'

### Meaning

Excat completed for the volume defined as S1 level.
'&00': SM-pubset catid

## HSM0142

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0142 INCONSISTENCY IN CONTROL-FILE, ERROR '(&00)'

## HSM0143

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0143 STARTUP '(&00)' FOR SM-PUBSET '(&01)'

### Meaning

This message is issued at subsystem creation for each SM-pubset which
is accessible.
Startup status are :
- IN PROCESS: the startup is in process
- COMPLETED : the startup is completed, the SM-pubset is under
HSMS control
- ABORTED : an error occurred during the startup processing of the
SM-pubset, subsystem creation continues but the SM-pubset
in not declared to HSMS.

## HSM0144

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0144 CLEANUP CALLED FOR SERVER TASK '(&00)'

### Meaning

When a HSMS server task fails, the HSMS main task does a recovery
for each request which is under the server task control.

## HSM0145

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0145 EXPORT TASK IS WAITING FOR THE COMPLETION OF REQUESTS STARTED BY HSMS SERVER TASK '(&00)'

## HSM0146

Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70

Warranty : NO

HSM0146 HSMS CONCURRENT COPY REQUEST '(&00)' CANCELLED

### Meaning

The Concurrent Copy request could not be scheduled due to the export of
the SM-Pubset.
The Concurrent Copy session has been deinitialized, and the request
deleted. Nothing has been processed, and no report has been generated.

### Response

Re-enter the Concurrent Copy request when the SM-pubset is available.

## HSM0150

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0150 WARNING: SM-PUBSET '(&00)' CURRENTLY NOT ACCESSIBLE

## HSM0155

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0155 '(&00)' ERROR DETECTED, RC = '(&01)'

### Meaning

&00: Identifier of the interface
&01: error code
For more information, see the following messages.

## HSM0156

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0156 ERROR REPORTED BY '(&00)' DURING '(&01)'

### Meaning

&00 : Identifier of the interface or HSMS processing step which returns
an unexpected return code.
&01 : HSMS processing step.
For more detailed information, see the following and/or preceding
messages.

## HSM0157

Destination: CONSOLE Routing code: U Weight: 90

Warranty : NO

HSM0157 ERROR REPORTED BY '(&00)' DURING '(&01)', RC = '(&02)'

### Meaning

&00: Identifier of the interface or HSMS processing step which returns
an unexpected return code.
&01: HSMS processing step.
&02: error code.

### Response

Contact the HSMS administrator.

## HSM0158

Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70

Warranty : NO

HSM0158 UNABLE TO TREAT INTERNAL VERSION '(&00)' (REQUESTED VERSION = '(&01)') IN MODULE '(&02)'

### Response

Contact your service engineer.

## HSM0159

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0159 CONNECTION TO PARTNER '(&00)' LOST

### Meaning

A CMX error implies a loss of openend connection to the specified
workstation.

## HSM0160

Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70

Warranty : NO

HSM0160 HSMS CONTROL FILE UPDATED

### Meaning

The HSMS control file has been updated during the startup processing.
Reasons are:
- a parameter was found to be false (such as a SM-pubset CAT-ID)
- the control file was created by a previous version of HSMS

## HSM0161

Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70

Warranty : NO

HSM0161 WARNING: DUPLICATE NODE-S0 '(&00)' SKIPPED

### Meaning

The HSMS Control File of the SM-pubset under IMPORT contains a node-s0
definition already present in the HSMS Common Memory Pool. The node-s0 is
skipped.
'(&00)': node-s0-id

## HSM019A

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM019A ARCHIVE '(&00)' IN ENVIRONMENT '(&01)' LOCKED BY TSN '(&02)' ON HOST '(&03)'

### Meaning

Current task will wait until the lock is released.
&00: name of the locked archive
&01: environment
&02: task having locked the archive
&03: host name

## HSM019B

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM019B ACCESS TO DIRECTORY '(&00)' NOT POSSIBLE AT THE MOMENT

### Meaning

Concurrent access on directory by another task.
&00: directory or repository name

## HSM019C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM019C UNLOCK FAILED ON REPOSITORY '(&00)' (LOCKING TSN = '(&01)', LOCKING HOST = '(&02)')

### Meaning

An error occurs during unlock processing of the repository.
When happening before processing:
processing is aborted because an error occurs during recovery of
senseless lock
When happening after processing:
Lock got by current task on repository cannot be freed.
Further save operations from other hosts on the concerned repository are
no more possible without manual operation.

### Response

Use //MDA DIRECTORY-LOCK=*REMOVE to remove the lock.

## HSM0190

Destination: CONSOLE Routing code: * (main console) Weight: 30

Warranty : NO

HSM0190 HSMS LOGGING FILE '(&00)' OPENED

### Meaning

(&00): file name.

## HSM0191

Destination: CONSOLE Routing code: * (main console) Weight: 30

Warranty : NO

HSM0191 HSMS LOGGING FILE '(&00)' CLOSED

### Meaning

(&00): file name.

## HSM0198

Destination: CONSOLE Routing code: * (main console) Weight: 00

Warranty : NO

HSM0198 DIAGNOSTIC INFORMATION: STEP (&00) REACHED IN (&01)

## HSM0199

Destination: CONSOLE Routing code: U Weight: 30

Warranty : NO

HSM0199 HSMS COMMENT '(&00)'

### Meaning

Contact the system administrator to get the meaning.

## HSM02A0

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM02A0 RECOVERY-REQUEST MUST BE ISSUED ON MASTER SHARER OF SM-PUBSET '(&00)'

### Meaning

The RECOVER-REQUESTS statement cannot be processed on a slave sharer of
the SM-pubset.
(&00): SM-pubset-id

### Response

Issue the recovery on the master sharer host.

## HSM02A1

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM02A1 HOST '(&00)' IS AN ACTIVE SHARER OF SM-PUBSET '(&01)'. OPERAND 'FORCE' REQUIRED

### Meaning

The RECOVER-REQUESTS statement checks if the host under recovery is an
active sharer of the SM-pubset. If the host is active, the operand FORCE
is required.
Beware that forcing a recovery is quite dangerous, as some requests may be
started twice.
(&00): host name
(&01): SM-pubset-id

### Response

Check the HSMS activity on the host under recovery. Supply the operand
FORCE if a recovery is required.

## HSM02A2

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM02A2 NEW-CATALOG-ID MUST BELONG TO OUTPUT ARCHIVE ENVIRONMENT

### Meaning

The new file/JV names must match the output archive environment.

### Response

Adapt the NEW-CATALOG-ID of the NEW-FILENAME and/or NEW-JVNAME operand
and re-enter statement.

## HSM02A3

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM02A3 FILES/JV MUST BE RENAMED TO CATCH AN SF-PUBSET CATALOG ID

### Meaning

The new file/JV names must match the output archive environment.

### Response

Use the NEW-FILENAME or/and NEW-JVNAME operand with a NEW-CATALOG-ID
and re-enter statement.

## HSM02A4

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM02A4 ARCHIVE NAME '(&00)' NOT KNOWN BY HSMS

### Meaning

No archive with the specified name has been
defined in HSMS.

### Response

Create archive or re-enter statement with a different archive name.

## HSM02A5

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM02A5 CURRENT HSMS VERSION DOES NOT SUPPORT THE FUNCTIONALITY OF '(&00)' '(&01)'

### Meaning

The object '(&00)' requires a new functionality no supported by the
current HSMS version.
'(&00)': 'ARCHIVE' or 'NODE-S0' or 'SM-PUBSET'
'(&01)': name of the object.
The processing was aborted for the given object.

### Response

Issue the statement on a system running a higher HSMS version.
If possible, issue the statement on the system which created the object.

## HSM0200

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0200 CONNECTION ERROR '(&00)' FOR SUBSYSTEM HSMS. HSMS CANNOT BE CALLED

### Meaning

The HSMS SVC returns a linkage error with '(&00)' as SUBCODE1
in the standard header of the parameter list.
'1': The requested function is not supported,
'2': The requested function is not available,
'65': The subsystem has not been created,
'130': The subsystem is in DELETE or HOLD.

### Response

Contact the system administrator.

## HSM0201

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0201 PROGRAM SDF NOT AVAILABLE. HSMS CANNOT BE CALLED

### Response

Contact the system administrator.

## HSM0202

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0202 HSMS NOT AVAILABLE IN ANY ACTIVE SYNTAX FILE OR VERSION OF SYNTAX FILE DOES NOT CORRESPOND WITH LOADED HSMS. HSMS CANNOT BE CALLED

### Meaning

Possible reasons :
- HSMS statements are not declared in any assigned syntax file.
- The version of the used syntax file does not correspond with
the version of the loaded HSMS.

### Response

Check the syntax file / HSMS versions and ask the system
administrator to install HSMS correctly.

## HSM0203

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0203 SDF ERROR '(&00)'. HSMS STATEMENT CANNOT BE READ

### Meaning

Meaning of the subcode (for more details see SDF manual):
- 12: SDF area too small for statement.
- 28: syntax error in statement.
- 40: the lists of messages returned by SDF are too long.

### Response

Correct and re-enter statement.

## HSM0204

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0204 HSMS TU-PROGRAM NOT IN HSMS OML. HSMS CANNOT BE CALLED

### Meaning

Some parts of the HSMS program cannot be linked dynamically because
they are not entered in the HSMS OML.

### Response

Ask the system administrator to install HSMS completely.

## HSM0205

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0205 VERSION '(&00)' OF HSMS SVC INTERFACE NOT SUPPORTED. HSMS CANNOT BE CALLED

### Meaning

The version of the HSMS SVC interface used by the caller is not
supported by the loaded HSMS version.

### Response

Generate SVC calls using the HSMS macro. If the error still occurs,
contact the system administrator.

## HSM0206

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0206 VERSION '(&00)' OF HSMS STATEMENT NOT SUPPORTED. HSMS CANNOT BE CALLED

### Meaning

The version of the HSMS statement declared in one of the active syntax
files is not supported by the loaded HSMS version.

### Response

Ask the system administrator to install HSMS completely.

## HSM0207

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0207 CALLED HSMS FUNCTION NOT SUPPORTED. HSMS CANNOT BE CALLED

### Meaning

The HSMS statement declared in one of the active syntax files is not
supported by the loaded HSMS version.

### Response

Ask the system administrator to install HSMS completely.

## HSM0208

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0208 HSMS NOT READY

### Meaning

Subsystem not yet completely loaded or initialized.

### Response

Repeat statement after a while.

## HSM0209

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0209 NOT ENOUGH VIRTUAL ADDRESS SPACE FOR HSMS COMMON MEMORY

### Meaning

The common memory pool is saturated, e.g. too many connected tasks
or too many requests in status ACCEPTED waiting for processing.

### Response

Possible solutions:
- prohibit creation of additional requests (switch to definition and
information operation)
- activate these waiting requests by modifying tape handling periods
- increase the memory pool size
(does not become valid until the next HSMS session; when unloading HSMS
wait for termination of requests still active!).

## HSM021A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM021A HSMS ADMINISTRATOR IS NOT ALLOWED TO PROCESS THIS STATEMENT

### Meaning

Usage of this statement is not allowed to the HSMS administrator.

## HSM021B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM021B SYSTEM ARCHIVE '(&00)' NOT DEFINED IN THE GLOBAL HSMS PARAMETERS

## HSM021C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM021C CURRENTLY IT IS NOT POSSIBLE TO USE SM PUBSETS AS S1 STORAGE LEVEL

### Meaning

Currently it is not possible to use a SM pubset as S1 storage level
during BACKUP-FILES, ARCHIVE-FILES, COPY-SAVE-FILES, MIGRATE-FILES.
This is possible only in HSMS versions V10.0A or higher and only
in mode SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE

### Response

Contact the HSMS administrator.

## HSM021D

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM021D CURRENTLY IT IS NOT POSSIBLE TO USE ALL VOLUME SETS RESERVED FOR HSMS USAGE AS S1 STORAGE LEVEL

### Meaning

Currently it is not possible to use all volume sets
reserved for HSMS usage as S1 storage level
during BACKUP-FILES, ARCHIVE-FILES, COPY-SAVE-FILES, MIGRATE-FILES
and REPAIR-... in SM-environment.
This is possible only in BS2000 OSD/BC and HSMS versions V11.0A or higher
and only in mode SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE.
In case of a shared SM pubset, the master system also
must have BS2000 OSD/BC version V11.0A or higher.

### Response

Contact the system or/and HSMS administrator.

## HSM021E

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM021E CURRENTLY THE VERSION BACKUP FUNCTIONALITY IS RESTRICTED

### Meaning

Possible reasons:
- The statements BACKUP-FILE-VERSIONS and REORGANIZE-VERSION-BACKUP
are only supported from BS2000 OSD/BC V11.0B and only
in mode SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE.
- REPAIR-CATALOG-BY-RESTORE and REPLACE-SAVE-FILE-BY-RESTORE from
version backup archives are only supported from BS2000 OSD/BC V11.0B
and only in mode SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE.
- The statement CHECK-CATALOGED-FILES is only supported from
BS2000 OSD/BC V11.0B.
- RESTORE-FILES and RESTORE-LIBRARY-ELEMENTS from version backup archives
are only supported from BS2000 OSD/BC V11.0B.
In case of shared pubset environment the same prerequisites
are obligatory for processing system (master or backup server).

### Response

Contact the system or/and HSMS administrator.

## HSM0210

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0210 STATEMENT NOT PERMITTED IN CURRENT OPERATING MODE

### Meaning

The entered HSMS statement cannot be processed in the current operating
mode.

### Response

Ask the HSMS administrator to switch HSMS into operational
or simulated mode.

## HSM0211

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0211 SYSTEM ARCHIVE '(&00)' FOR PUBSET '(&01)' NOT DEFINED

### Meaning

Possible reasons:
- there is no system archive definition for the version backup in the
pubset parameters.
- assignment of the system archive in the pubset parameters is *STD, but
the corresponding value in the global HSMS parameters is set to
*UNDEFINED.
- the name of the archive assigned to the symbolic archive
'(&00)' is not known to HSMS, e.g. because the archive was
deleted after it had been assigned as the system archive.

### Response

Contact the HSMS administrator for having the assignments
corrected or, in case of a deleted archive, for having it re-created.

## HSM0212

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0212 ASSIGNMENT FOR SYSTEM ARCHIVE '(&00)' NOT UNIQUE

### Meaning

Possible reasons:
- files or job variables from different Pubsets which do not have the same
system archive cannot be processed in the same statement.
- when determining the system archive through the Pubsets known to HSMS
(S0 Pubsets for *SYSMIGRATE) there are at least two (S0) Pubsets which
have different archives defined for the system archive in their Pubset
parameters (explicitly or via the *STD assignment).
- only for the SHOW-ARCHIVE
(SELECT = *SAVE-VERSIONS / *SAVE-FILES / *VOLUMES) statement:
when determining the system archive through the Pubsets
known by HSMS (S0 Pubsets for *SYSMIGRATE) there is at least one (S0)
Pubset which has *STD assigned for the system archive in its Pubset
parameters, but there is no global assignment (*UNDEFINED) or these are
no (S0) Pubsets at all.

### Response

Possible solutions:
- start several requests, each with files / job variables for a separate
pubset.
- specify a system archive not by its symbolic name, but explicitly.
- ask the HSMS administrator to change archive or pubset assignment.

## HSM0213

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0213 S1 STORAGE NOT DEFINED FOR PUBSET '(&00)'

### Meaning

Possible reasons :
- Some files to be processed belong to a pubset on S0 level,
for which no S1 storage has been defined.
- Some files to be processed belong to a pubset not declared
as S0 level.
- Some files to be processed belong to an SM pubset
and no global S1 storage level is defined.

### Response

- If the statement is not processed, ask the HSMS administrator to
assign a pubset for S1 storage level.
- If the statement is processed, the concerned files are processed
with those of the S0 level pubset.
- Information is asked about a S1 level storage which is not available
or not defined.

## HSM0214

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0214 ASSIGNMENT OF S1 STORAGE NOT POSSIBLE

### Meaning

S1 storage is not globally defined or cannot be assigned uniquely
because files from several pubsets with different S1 storage definitions
are specified in the same statement.

### Response

Start several requests, each with files for a different pubset,
or ask the HSMS administrator to change the S1 storage assignment.

## HSM0215

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0215 PUBSET '(&00)' IS NOT S0 STORAGE

### Meaning

The specified Pubset is not assigned to the S0 storage level.

### Response

Ask the HSMS administrator to assign the pubset to HSMS.

## HSM0216

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0216 MAXIMUM WAIT TIME EXPIRED

### Meaning

Possible reasons:
- tape handling currently not permitted.
- request not started by HSMS server task within maximum wait time,
(no server task available, all occupied by other requests).
- maximum wait time for shared update conflict expired.

### Response

Repeat request after a while, maybe asynchronously
(WAIT-FOR-COMPLETION=NO).

## HSM0217

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0217 MIGRATION FROM PUBSET '(&00)' NOT PERMITTED

### Meaning

The specified pubset is subject to a general migration lock.

## HSM0218

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0218 MIGRATION TO S1 FROM PUBSET '(&00)' NOT PERMITTED

### Meaning

Migration to S1 storage is not permitted for the specified pubset.

## HSM0219

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0219 USER NOT AUTHORIZED TO PROCESS STATEMENT

### Meaning

Usage of this statement is restricted to the HSMS administrator.

## HSM022A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM022A AT LEAST ONE X-RECORD, WHICH CONTAINS USER-INFORMATION, NOT PRESENT IN THE DIRECTORY. RESULT OF MODIFY-ARCHIVE NOT PREDICTABLE

### Meaning

There is at least one save version which does not have a X-record in the
directory. MODIFY-ARCHIVE SAVE-VERSIONS=*MODIFY-USER-INFORMATION cannot
modify the user data for that save version(s).
This situation can occur if one tries to modify records which were created
by an ARCHIVE run (without control by HSMS), or by an //EXPORT-FILES.

## HSM0220

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0220 USER IS NOT AUTHORIZED TO SPECIFY 'EXPRESS-REQUEST=*YES'

### Meaning

The user is not authorized to enter express jobs;
this is a HSMS administrator privilege.

## HSM0221

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0221 USER IS NOT AUTHORIZED TO SPECIFY 'SAVE-FILE=*NEW/*CONTINUE'

### Meaning

The user may only save data to a standard save file.

## HSM0222

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0222 USER IS NOT AUTHORIZED TO SPECIFY 'FILE-EXPIRATION-DATE=*UNRESTRICTED'

### Meaning

The user is not authorized to permit an unrestricted file expiration
date for the archive.

## HSM0223

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0223 USER IS NOT AUTHORIZED TO SPECIFY 'USER-ACCESS=*ALL-USERS'

### Meaning

The user is not authorized to specify that the archive may be used by
other users.

## HSM0224

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0224 USER NOT AUTHORIZED FOR S1 STORAGE MIGRATION RESPECTIVELY S2 STORAGE MIGRATION

### Meaning

Migration and reorganization of S1 or S2 is restricted
to the HSMS administrator.

## HSM0225

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0225 USER HAS NO ACCESS RIGHTS TO ARCHIVE '(&00)' IN ENVIRONMENT '(&01)'

### Meaning

The user is not authorized to access the archive in the specified manner.

## HSM0226

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0226 USER HAS NO ACCESS RIGHTS TO USER ID '(&00)'

### Meaning

The user is not authorized to specify objects under the specified
user ID.

## HSM0227

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0227 USER '(&00)' NOT PERMITTED ON PUBSET '(&01)'

### Meaning

The user has no JOIN entry on the specified pubset.

## HSM0228

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0228 USER '(&00)' NOT PERMITTED TO USE S1 STORAGE

### Meaning

It is not possible to create a save file on S1 storage under the
specified user ID.

### Response

Contact the system administrator to join user ID on the S1 storage.

## HSM0229

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0229 PUBSET '(&00)' IS NOT S1 STORAGE

### Meaning

The specified pubset is not assigned to the S1 storage level.

### Response

Ask the HSMS administrator to assign the pubset to HSMS.

## HSM023A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM023A USER IS NOT AUTHORIZED TO SPECIFY 'ALLOWED-USAGE=*SHADOW'. STATEMENT REJECTED

### Meaning

The user is not authorized to set up a shadow archive. Administration
of shadow archives is restricted to the HSMS administrator.

## HSM023B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM023B INVALID ORIGINAL ARCHIVE TYPE

## HSM023C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM023C ORIGINAL BACKUP ARCHIVE MUST HAVE A SEVERAL SVID STRUCTURE

## HSM023D

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM023D ARCHIVE ALREADY LINKED TO ANOTHER ONE

## HSM023E

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM023E LINKED ARCHIVE NOT FOUND

## HSM023F

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM023F AUTOMATIC DUPLICATION SKIPPED BECAUSE TO-STORAGE IS NOT *S2-STORAGE-LEVEL

### Meaning

The statement specifies that the ARCHIVE.SAVE.FILE should be created on
disk, and the value of the operand SHADOW-COPY=*ALLOWED. This message must
warn the user that the shadow mechanism is not used when saving on disk.

## HSM0230

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0230 ARCHIVE '(&00)' NOT ASSIGNED TO USER ID 'SYSHSMS' IN ENVIRONMENT '(&01)'

### Meaning

The specified archive does not belong to the HSMS administrator
and therefore cannot be used as the system archive.

### Response

Assign archive (and directory file) to the HSMS administrator's user ID
for the specified environment.

## HSM0231

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0231 USER IS NOT AUTHORIZED TO SPECIFY 'ALLOWED-USAGE=*MIGRATION'

### Meaning

The user is not authorized to set up a migration archive.
Administration of migration archives is restricted to the
HSMS administrator.

## HSM0232

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0232 ARCHIVE DIRECTORY ALREADY ASSIGNED

### Meaning

The archive cannot be set up with the specified directory
as this directory has already been assigned to another archive.

### Response

Create archive with another directory file.

## HSM0233

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0233 ARCHIVE CANNOT CURRENTLY BE DELETED

### Meaning

Requests are still being processed for the specified archive.
These requests have the status ACCEPTED, STARTED or INTERRUPTED.
Requests stay in status ACCEPTED
- if, for example, no HSMS server tasks are available.
- if requests are suspended due to tape handling restrictions.

### Response

Call down relevant requests using SHOW-REQUESTS ARCHIVE-NAME=archive name.
Activate, restart or delete these requests; then delete the archive.

## HSM0234

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0234 USER IS NOT AUTHORIZED TO SPECIFY 'PROTECTION-RESPECTED=*NONE'

### Meaning

Only the HSMS administrator is allowed to ignore file protection.

## HSM0235

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0235 USER IS NOT AUTHORIZED TO USE SPECIFIED PARAMETERS IN THE 'SELECT' OPERAND

## HSM0236

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0236 PUBSET '(&00)' IMPORTED IN 'SLAVE MODE'. PUBSET SKIPPED

### Meaning

A request applies to local Pubsets and a shared pubset imported in
slave mode. The request is executed for the local Pubsets only.

### Response

Give a separate request for the rejected Pubset.

## HSM0237

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0237 USER MAY ONLY SAVE OWN DIRECTORY FILE

### Meaning

Implicit save of an archive (or its directory file) is allowed
only for the archive owner.

### Response

Enter statement again, but without using the implicit directory save,
i.e. use parameter SAVE-DIRECTORY=*NO.

## HSM0238

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0238 SELECTED OPTION FOR 'CONTINUE' ALLOWED ONLY WITH DIRECTORY FILE

### Meaning

Requests continuing a save file or a save version must use
an assigned archive (or its directory file).

### Response

Re-enter statement with additional directory assignment.

## HSM0239

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0239 RESTART OF REQUEST '(&00)' IS NOT POSSIBLE DUE TO NOT EXISTING OR EMPTY RESULT FILE '(&01)'. PROCESSING ABORTED

## HSM024A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM024A ERROR (&00) DURING CONTROL-JV ACCESS. IN SYSTEM MODE: /HELP-MSG JVS(&00)

## HSM024B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM024B FILE '(&00)' NOT SAVED IN THE ARCHIVE '(&01)' OF USERID '(&02)'

### Meaning

&00: filename
&01: archive name
&02: userid of archives owner
- a nonprivileged user is not allowed to save files from the
own userid to the public archive of any other user.

## HSM024C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM024C DIRECTORY '(&00)' NOT LOCKED

### Meaning

&00: directory filename

## HSM024D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM024D DIRECTORY '(&00)' UNLOCKED

### Meaning

&00: directory filename

## HSM024E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM024E DIRECTORY '(&00)' LOCKED BY TSN '(&01)' ON HOST '(&02)'

### Meaning

&00: directory filename
&01: task having locked the directory
&02: host name

## HSM024F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM024F JOBVARIABLE '(&00)' NOT SAVED IN THE ARCHIVE '(&01)' OF USERID '(&02)'

### Meaning

&00: name of the jobvariable
&01: archive name
&02: userid of archives owner
- a nonprivileged user is not allowed to save jobvariables from the
own userid to the public archive of any other user.

## HSM0240

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0240 USER IS NOT AUTHORIZED TO SPECIFY '(&00)'

### Meaning

The user is not authorized to mention the (&00) operand.
Possible reasons are:
- TO-STORAGE=*PUBLIC-DISK or *S1-STORAGE-LEVEL: a backup on public disk
or on S1 level is only allowed for the HSMS administrator.
- Renaming at BACKUP is reserved to the HSMS administrator.
- MANAGEMENT-CLASS may only be specified by the HSMS administrator in a
SYSTEM-MANAGED environment.

### Response

Re-enter statement with correct assignment.

## HSM0241

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0241 DIRECTORY TYPE NOT COMPATIBLE WITH ARCHIVE USAGE

### Meaning

BS2000 archives require BS2000 directories.
NODE archives require NODE directories.
Version backup archives require version backup directories.
Version backup archive cannot be created from ARCHIVE directory.
Version backup directories cannot be used for other types of archives.

### Response

Use a correct directory type or create a new directory.

## HSM0242

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0242 INTERNAL DATA LOCKED BY ANOTHER TASK. PROCESSING INTERRUPTED

### Meaning

Processing aborted after TIME-OUT.

### Response

Retry later or contact HSMS administrator.

## HSM0243

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0243 SYSTEM ARCHIVE '(&00)' FOR NODE '(&01)' IN ENVIRONMENT '(&02)' NOT DEFINED

### Meaning

The assignment of the system archive in the node parameters declared in
the specified environment is *STD, but the corresponding value in the
global HSMS parameters (if SF environment) or in the SM-pubset parameters
is set to *UNDEFINED.

### Response

Contact the HSMS administrator.

## HSM0244

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0244 OPERAND '(&00)' NOT PERMITTED ON BS2000-UFS

### Meaning

A RESTORE operation on BS2000-UFS, into the directory reserved for remote
workstations, is not permitted.

## HSM0245

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0245 PROCESSING OF STANDARD SAVE FILE NOT ALLOWED FOR A BACKUP ARCHIVE WITH A 'SINGLE-SVID'-STRUCTURE

### Meaning

The operand 'SAVE-FILE=*STD' is not supported when the concerned archive
has a SINGLE-SVID save file structure.

### Response

Either issue the statement with 'SAVE-FILE=*NEW/*CONTINUE' or transform
the archive to a SEVERAL-SVIDS one.

## HSM0246

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0246 'PARTIAL-FILE-SAVE=LARGE-FILES/YES(...)' WITH SEVERAL-SVIDS BACKUP ARCHIVE NOT PERMITTED

### Meaning

Partial file saving when continuing a backup archive with a SAVE FILE
structure of type SEVERAL-SVIDS not permitted.

## HSM0247

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0247 ONLY THE LATEST SVID MAY BE COPIED WHEN COPYING INSIDE THE SAME ARCHIVE

### Meaning

When copying inside the same SEVERAL-SVID backup archive, only the latest
SVID in the archive may be copied.

### Response

Use for the operand 'SAVE-VERSION-DATE' the keyword '*LATEST-DATE' or
enter the exact date/time for specifying the latest SVID in the archive.

## HSM0248

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0248 ONLY ONE SAVE VERSION MAY BE ADDRESSED

### Meaning

When copying a SEVERAL-SVID archive to a medium which is not a S2 storage
level, only one SAVE VERSION may be specified.

## HSM0249

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0249 SAVE-VERSION-ID '(&00)' NOT LISTED IN ARCHIVE

### Meaning

No entry for the specified SAVE-VERSION could be found in the used
archive.

### Response

Check SAVE-VERSION-ID; reenter statement with other id or with other
archive.

## HSM025A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM025A ARCHIVE '(&00)' IN ENVIRONMENT '(&01)' IS NOT A SHADOW ARCHIVE

### Meaning

No shadow archive with the specified name for the specified environment
has been defined in HSMS.

### Response

Create shadow archive or re-enter statement with a different
archive name.

## HSM025B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM025B NOT ENOUGH SPACE WHEN OPENING OUTPUT FILE FOR REPORT OR PRINTER

### Response

Contact the system administrator.

## HSM025C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM025C THE VERSION BACKUP ARCHIVE '(&00)' IS ALREADY ASSIGNED AS A SYSTEM ARCHIVE TO PUBSET '(&01)'

### Meaning

A version backup archive can not be assigned to multiple pubsets as
a system archive.
&00: archive from current //MODIFY-PUBSET-PARAMETERS statement,
&01: pubset the archive is already assigned to.

## HSM025D

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM025D VERSION BACKUP ARCHIVE '(&00)' EXISTS BUT IS NOT ASSIGNED TO A PUBSET

### Meaning

It is not possible to mark files for deletion if the version backup
archive is not assigned to a pubset.

### Response

Assign the version backup archive to the respective pubset using
//MODIFY-PUBSET-PARAMETERS and reenter the statement. Hint: the
pubset must correspond to the catid in the pathname of the files
contained in the archive.

## HSM025E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM025E DIRECTORY '(&00)' LOCKED

### Meaning

&00: directory filename
Possible reasons:
1. The version backup directory is in use by a backup or
reorganization process.
2. The restored directory had been saved with
//REORGANIZE-VERSION-BACKUP SAVE-DIR=*YES,
during this save the directory is locked.
This lock needs to be removed. This is normal behavior.

### Response

1. Wait until the backup or reorganization process has finished.
2. Run //MODIFY-ARCHIVE ARCHIVE-NAME=<archive_name>,
DIRECTORY-LOCK=*UNLOCK-VERSION-DIR to get rid of the lock
or contact the administrator.

## HSM0250

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0250 OPTION 'DIALOG-FILE-SELECT=*YES' NOT PERMITTED

### Meaning

Only interactive tasks may select files interactively.

### Response

Modify statement in batch job procedure.

## HSM0251

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0251 INVALID ARCHIVE NAME '(&00)'

### Meaning

The internal structure of an archive name is subject to the following
restrictions:
- length of user ID no more than 8 characters.
- length of subsequent name part no more than 12 characters.
- usage of special characters as for BS2000 file names.

### Response

Re-enter statement with correct archive name.

## HSM0252

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0252 ARCHIVE NAME '(&00)' IN ENVIRONMENT '(&01)' NOT KNOWN BY HSMS

### Meaning

No archive with the specified name for the specified environment has been
defined in HSMS.
If the archive name is '$.*remote*' there is a remote access on a
shared pubset with no archive defined for the master host or
the backup server. In case of REPAIR-CATALOG-BY-RESTORE, this can
also refer to the SYSMIGRATE archive assigned to S0-PUBSET-ID.

### Response

Create archive(s) or re-enter statement with a different archive name.

## HSM0253

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0253 ARCHIVE NAME '(&00)' ALREADY DEFINED IN ENVIRONMENT '(&01)'

### Meaning

An archive with the given name for the given environment, but perhaps
a different usage type, has already been defined.
Archive names have to be unique during one HSMS session.

### Response

Create archive with a different name.

## HSM0254

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0254 ILLEGAL UTILIZATION OF ARCHIVE '(&00)' IN ENVIRONMENT '(&01)'

### Meaning

This access is not consistent with the archive's attributes.
Possible reasons:
- usage of a migration archive for archiving,
- write access to a protected archive,
- select JV names in an archive which is not a backup one,
- archive usage incompatible with environment.

## HSM0255

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0255 INVALID FORMAT FOR SAVE-FILE-ID '(&00)'

### Meaning

A save file ID has the format 'S.yymmdd.hhmmss'
(with yy=year, mm=month, dd=day, hh=hour, mm=minute, ss=second).
This time stamp represents the moment of creation of the save file.

### Response

Re-enter statement with correct save file ID.

## HSM0256

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0256 SAVE-FILE-ID '(&00)' NOT LISTED IN ARCHIVE

### Meaning

No entry for the specified save file could be found in the archive used.

### Response

Check save file ID; re-enter statement with other ID or with other
archive.

## HSM0257

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0257 INVALID 'FILE-EXPIRATION-DATE'. MAXIMUM RETENTION PERIOD: (&00)

### Meaning

The specified expiration date must lie within the maximum possible
retention period (specified in days).

### Response

Re-enter statement with valid expiration date.

## HSM0258

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0258 INVALID DEVICE TYPE '(&00)'

### Meaning

The specified device type is invalid or is not permitted in the
current context.

## HSM0259

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0259 PUBSET '(&00)' NOT AVAILABLE LOCALLY

### Meaning

Possible reasons:
- the specified pubset is assigned to storage level S0 or S1 in HSMS
but is not available in the current session (no IMPORT-PUBSET).
- the pubset is available but has not been assigned to any
storage level in HSMS.
- the pubset is available but shared with other hosts, and
the local host is not declared as master of that pubset.

### Response

Check input, if necessary contact the HSMS or system administrator.

## HSM026A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM026A IMPLICIT RECALL OF ENCRYPTED FILES NOT POSSIBLE

### Meaning

Imlicit recall of encrypted files only possible in BS2000/OSDV6.0
and higher.

### Response

Use explicit recall

## HSM026B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM026B THE PUBSET SPECIFIED IN THE TO-STORAGE OPERAND IS DIFFERENT FROM THE PUBSET THAT IS ASSIGNED TO THE STANDARD SAVE FILE IN THE ARCHIVE

## HSM026C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM026C THE PUBSET THAT IS ASSIGNED TO THE STANDARD SAVE FILE IN THE ARCHIVE IS NOT ALLOWED IN SPECIFIED SM PUBSET ENVIRONMENT

## HSM026D

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM026D VARIABLE FOR OPERAND 'STRUCTURE-OUTPUT' MUST BE A LIST OF TYPE 'STRUCTURE'

### Response

Declare variable with a correct type.

## HSM0260

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0260 VALUE OR NUMBER OF LIST ELEMENTS '(&00)' FOR OPERAND '(&01)' OUT OF ALLOWED RANGE (FROM '(&02)' TO '(&03)')

## HSM0261

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0261 SPECIFIED FILE NAME LIST AND/OR JV NAME LIST EMPTY

### Meaning

No files nor JVs found corresponding to the specified criteria.

## HSM0262

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0262 FILE OR JV LIST CONTAINS ERRORS

### Meaning

Check previous messages for more detailed information about different
objects.

## HSM0263

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0263 GIVEN VALUE FOR OPERAND 'ENVIRONMENT' IS INCONSISTENT WITH HIPLEX CAPABILITY SUPPORT FOR NODE OBJECTS (SITUATION '(&00)' DETECTED)

### Meaning

&00: number of the error:
1: Single-feature environment (*SF or *STD resolution) not accepted
when HIPLEX capability is requested.
2: System-managed environment (*SM or *STD resolution) not accepted
when HIPLEX capability is not supported.
3: Given SM-pubset catid not declared as node-environment and HIPLEX
capability is requested, thus it cannot be used for node management.
4: Given SM-pubset catid differs from the catid of the node environment
defined for the default host of the issuer.

### Response

Correct the environment and retry.

## HSM0264

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0264 ERROR '(&00)' WHEN CALLING CMD MACRO

### Meaning

The mapping of the HSMS statement to CMD macro has been rejected:
- 16: command terminated with error
(e.g. invalid version specified with START-HSMS),
- 20: command not valid for user
(e.g. START-HSMS statement not under TSOS).

### Response

For more detailed information see the BS2000 manual 'Executive Macros'.

## HSM0265

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0265 ERROR '(&00)' FOR OPERAND '(&01)'

### Meaning

An error was detected for the specified operand.

### Response

Correct the operand.

## HSM0266

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0266 ACCESS TO MIGRATED FILE '(&00)' NOT PERMITTED FOR THIS TASK TYPE. REQUEST REJECTED

### Meaning

Read access to migrated files causes HSMS recall requests.
Such requests are restricted to certain task types.

### Response

Contact the system administrator, send SYSOUT protocol and context
description for diagnosis.

## HSM0267

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0267 VSN LIST OVERFLOW

### Meaning

There were more volumes specified than could be processed for one
statement.

### Response

Re-enter the request, divided into several statements.

## HSM0268

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0268 CONTINUATION OF SAVE FILE '(&00)' NOT PERMITTED

### Meaning

Possible reasons:
- For backup and nodebackup archive, only the latest save file can be
continued.
- When copying a save file within an archive for archival, migration or
nodearchival, the input save file must not be the same as the continued
output file.
- When updating a save file within an archive for export, the input save
file must not be the same as the continued output save file.

### Response

Re-enter statement, but create a new output save file.

## HSM0269

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0269 SAVE FILE '(&00)' NOT ON S2 STORAGE

### Meaning

The specified save file was allocated to a volume type not permissible
for storage level S2 (usually S1 or private disk).

### Response

Correct the statement.

## HSM027A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM027A GIVEN VALUE FOR OPERAND 'REQUEST-DATA-ORIGIN' IS ONLY ACCEPTED IF THE LOCAL HOST SUPPORTS HIPLEX CAPABILITY

### Response

Correct the input and try again.

## HSM027B

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM027B INVALID ARCHIVE TYPE FOR 'SAVE-FILE-RETPD-UPDATE=*YES'

### Meaning

The retention period must not be changed for such an archive type.
Only long time archives (type = ARCHIVAL / NODEARCHIVAL) and their shadow
archives allow this period to be modified.

### Response

Issue the statement again, but without specifying a new retention period.

## HSM027C

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM027C ONLY SAVE FILES ON TAPES CAN BE CONTINUED, IF THE ARCHIVE DEFINITION ALLOWS 'SAVE-FILE-STRUCTURE=*SEVERAL-SVID'

## HSM027D

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM027D NO VALID ARCHIVE WITH DIRECTORY '(&00)' EXISTING

### Meaning

The OUTPUT-DIRECTORY used in the COPY-EXPORT-SAVE-FILES statement
does not refer to an archival archive in SF-pubset environment.

### Response

Use directory of an archival archive in SF-pubset environment.

## HSM027E

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM027E SYSTEM ARCHIVE FOR SM PUBSET '(&00)' IS DEFINED IN '(&01)' ENVIRONMENT BUT THE STATEMENT WAS STARTED IN '(&02)' ENVIRONMENT

### Meaning

Environment of system archive used does not correspond
to the statement environment entered.

### Response

Use the corresponding system archive environment.

## HSM027F

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM027F THE SPECIFICATION 'ARCHIVE-NAME=*BY-DIRECTORY-NAME' IS NOT PERMITTED FOR A DIRECTORY THAT IS ASSIGNED TO AN ARCHIVE

### Meaning

The operand 'BY-DIRECTORY-NAME' may only be used when the related
directory does not belong to any archive.

### Response

Give the archive name as ARCHIVE-NAME parameter.

## HSM0270

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0270 'DEVICE-TYPE' OPERAND NOT PERMITTED FOR SAVE-FILE-ID '(&00)'

### Meaning

The save file can only be continued with the same DEVICE-TYPE value
with which it was created.

### Response

Check device type using SHOW-ARCHIVE ...,SELECT=*SAVE-FILES and
re-enter statement with correct device type.

## HSM0271

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0271 'BACKUP-LEVEL' OPERAND NOT PERMITTED FOR SAVE-FILE-ID '(&00)'

### Meaning

The save file can only be continued with the same BACKUP-LEVEL value
with which it was created.

### Response

Check correct value using SHOW-ARCHIVE ...,SELECT=*SAVE-FILES and
re-enter statement.

## HSM0272

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0272 'SELECT-FILES' OPERAND NOT PERMITTED FOR SAVE-FILE-ID '(&00)'

### Meaning

The save file can only be continued with the same SELECT-FILES value
with which it was created.

### Response

Check correct value using SHOW-ARCHIVE ...,SELECT=*SAVE-FILES and
re-enter statement.

## HSM0273

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0273 COPYING OF SAVE FILE '(&00)' NOT PERMITTED

### Meaning

For backup archives: only the most recent save file may be copied.

## HSM0274

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0274 TO-STORAGE VALUE NOT COMPATIBLE WITH STORAGE OF SAVE FILE OR WITH SEVERAL-SVID STRUCTURE.

## HSM0275

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0275 ASSIGNMENT OF PUBSET '(&00)' T0 S0 STORAGE AND S1 STORAGE IS NOT ALLOWED

### Meaning

A pubset cannot be assigned to the storage levels S0 and S1
at the same time. The statement is not processed.

### Response

Assign different pubsets.

## HSM0276

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0276 ARCHIVE '(&00)' IN ENVIRONMENT '(&01)' IS NOT OF TYPE '(&02)'

### Meaning

The type of archive used does not correspond to the statement entered
e.g. assignment of an ARCHIVAL archive to the BACKUP-FILES statement.

### Response

Use archive of compatible type.

## HSM0277

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0277 INVALID VALUE OF OPERAND '(&00)' FOR ARCHIVE TYPE '(&01)'

## HSM0278

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0278 INVALID VALUE FOR 'VOLUMES' OPERAND

### Meaning

The number of volume groups must be the same as the number of
PARALLEL-RUNS when writing to the volumes and must not be greater than 16.

### Response

Re-enter corrected statement.

## HSM0279

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0279 INVALID COMBINATION OF OPERAND VALUES FOR '(&00)'

## HSM028A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM028A TARGET-LIBRAY '(&00)' NOT EXISTS OR IS NOT A LIBRARY

### Response

Create a TARGET-LIBRARY .

## HSM028B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM028B PLAM ERROR '(&00)' (INSERT: '(&01)') DURING '(&02)'-ACCESS TO LIBRARY '(&03)'. IN SYSTEM MODE: /HELP-MSG PLA(&00)

### Meaning

Library resp. element cannot be processed due to the specified error

### Response

For more detailed information about the PLAM error code enter /HELP-MSG in
system mode.

## HSM0280

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0280 HSMS CONTROL FILE DESTROYED

### Response

Delete control file and start HSMS again.

## HSM0281

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0281 HSMS REQUEST FILE DESTROYED

### Response

Contact the HSMS administrator: Request file has to be deleted in
DEFINE-SHOW mode.

## HSM0282

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0282 PUBSET '(&00)' DOES NOT EXIST. STATEMENT REJECTED

## HSM0283

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0283 THE USER IS NOT AUTHORIZED TO EXPORT FILES/JV OF OTHER USERS

### Meaning

The user is not authorized to export files/JV of other users.
Exception: if FILE-ATTRIBUTES=*RESET-TO-STD has been specified,
sharable files of other users may be exported.

## HSM0284

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0284 ERROR '(&00)' DURING SUBSYSTEM PART LOADING

### Meaning

The loading of a subsystem part reports the following error (SUBCODE1);
- '0008': HSMS/FHS subsystem/version not found.
- '0408': HSMS/FHS subsystem has not the right status.
- '0C08': HSMS/FHS subsystem is locked due to a previous error.
- '1008': subsystem part is not loaded, BLS has detected an error.

## HSM0285

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0285 ERROR IN FILE '(&00)' - '*FROM-FILE' OPERAND

### Meaning

The file (&00) contains records syntactically incorrect.

## HSM0286

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0286 NODE-S0-ID '(&00)' DOES NOT EXIST IN ENVIRONMENT '(&01)'

## HSM0287

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0287 UNIX FILE SYSTEM NOT REACHABLE

### Meaning

Possible reasons :
- See eventual previous message.
- BS2000/OSD V1 : subsystem NFS/POSRTS/TPRLIB not started.
- BS2000/OSD V2 : subsystem POSIX/POSRTS/POSPRRTS not started.

## HSM0288

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0288 SUBSYSTEM '(&00)' VERSION '(&01)' (&02)'

### Meaning

The subsystem (&00) with the version (&01)
and in the state (&02) is not available.

### Response

Contact the system administrator.

## HSM0289

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0289 '(&00)' NOT SUPPORTED WITH BS2000 VERSION '(&01)'

### Meaning

(&00) does not run with the BS2000 version (&01).

### Response

Reenter a correct statement or change the BS2000 version.

## HSM029A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM029A MIGRATION ARCHIVE NOT FOUND FOR FILES MIGRATED TO S1 PUBSET '(&01)'

### Meaning

-To migrate from S1, the S1 levels must be defined for S0 level of the
migrated data and the corresponding migration archive must be determined.
This is done via the global and the pubset-specific HSMS parameters.
However, the migration archive could not be determined because either
no S1 level is assigned to an S0 pubset or because no pubset-specific
migration archive has been defined for an S0 pubset, but no global
system migration archive has been defined.
- The name of the archive assigned to the symbolic archive
'(&00)' is not known to HSMS, e.g. because the archive was
deleted after it had been assigned as the system archive.

### Response

Contact the HSMS administrator for having the assignments
corrected or, in case of a deleted archive, for having it re-created.

## HSM029B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM029B FILES ONLY FROM ONE PUBSET ARE PROCESSED

### Meaning

A version backup archive can be assigned as a system archive
to one pubset only.
Only files that reside on this pubset could be
specified.

### Response

Specify only file names that reside on the respective pubset.

## HSM0290

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0290 WORKFILE '(&00)' FOR BACKUP WITH CONCURRENT COPY MUST BE EMPTY

### Response

Give another workfile.

## HSM0291

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0291 CATALOG FOR WORKFILE '(&00)' NOT ACCESSIBLE

### Response

Import catalog and re-enter statement.

## HSM0292

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0292 SM-PUBSET '(&00)' ALREADY KNOWN BY HSMS

## HSM0293

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0293 SM-PUBSET '(&00)' NOT DECLARED TO HSMS

### Meaning

A SM-pubset is not declared to HSMS when it is unknown in the HSMS pubset
table, i.e. either it is an unknown pubset, or it is unaccessible or its
parameters are not defined in HSMS (//CSP statement).

### Response

Try the command SHOW-MASTER-CATALOG-ENTRY and/or contact the system
administrator.

## HSM0294

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0294 FILES FROM DIFFERENT ENVIRONMENTS NOT PERMITTED

### Meaning

Some concerned files do not belong to the specified environment

## HSM0295

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0295 SM-PUBSET '(&00)' NOT READY

### Meaning

The specified SM-pubset is currently not ready.
(Processing of /IMPORT-PUBSET or /EXPORT-PUBSET currently running).

### Response

Wait and retry or contact the system administrator.

## HSM0296

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0296 INVALID DIRECTORY NAME

### Meaning

Possible reasons:
- A CATID must be given.
- The given CATID must be equal to the environment.

## HSM0297

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0297 'TO-STORAGE' RESTRICTED TO S1- AND S2-STORAGE-LEVEL IN SM-PUBSET MANAGEMENT

## HSM0298

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0298 INVALID EXPORT DIRECTORY

### Meaning

The EXPORT-FILES statement refers to an SM-pubset directory
or to a directory belonging to a version backup archive.

### Response

Correct statement and retry.

## HSM0299

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0299 USER IS NOT AUTHORIZED TO SPECIFY A VOLUME-SET-ID

### Meaning

User is not authorized to make physical allocation.

## HSM030A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM030A ERROR REPORTED BY CCOPY

### Response

For more detailed information about the error cause see the statement
preceding error message sent by CCOPY.

## HSM030B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM030B NAME OF FILE/JV '(&00)' IN //EXPORT-FILES OR //RECALL-MIGRATED-FILES STATEMENT IS WRONG

### Meaning

Non-privileged user are not allowed to specify wildcards in
the user ID part of a file/JV name in the //EXPORT-FILES
or //RECALL-MIGRATED-FILES statement.

### Response

Re-enter statement under user ID of the file/JV owner or specify user ID
in fully-qualified form.

## HSM030C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM030C NOT ALL FILES OR JOBVARIABLES TO BE SAVED ARE LOCATED ON THE SPECIFIED SNAPSET

### Meaning

Only files or jobvariables located on the snapset with the specified
pubset id could be saved.

### Response

Re-enter corrected statement.

## HSM0300

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0300 ERRORS DETECTED ON AT LEAST ONE FILE OR JV. CONCURRENT COPY BACKUP CANNOT BE PERFORMED

## HSM0301

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0301 ERROR DETECTED DURING WORKFILE '(&00)' HANDLING

## HSM0302

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0302 CONCURRENT COPY BACKUP AND SAVE-FILE=*CONTINUE IN A SINGLE SVID ARCHIVE NOT PERMITTED

## HSM0303

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0303 CONCURRENT COPY HANDLER REPORTED AN ERROR '(&00)'

### Meaning

'&00': Error indicator:
'1' or '1 / DMS RC = ....'
- file not cataloged
- file not accessible
- error during reading the catalog entry
- file on private volume
- error during reading ACL
- error during file lock request
- file opened in write mode
- file already included in another CC-session
- workfile included in another CC-session
- no file to save was given to Concurrent Copy Handler
'2' or '2 / DMS RC = ....'
- cat-id of specified workfile not found
- invalid user-id for specified workfile
- user-id of specified workfile not in the pubset
- specified workfile is a temporary file or a FGG
- specified workfile is not accessible
- shortage of disk space for CE of std workfile
- shortage of disk space for std workfile
- std workfile already exists
'3' : subsystem SRPMFACL not operating
'4' or '4 / DMS RC = ....' : internal error
'5' : invalid opcode detected by Concurrent Copy Handler
'6' : wrong session-id detected at CC-session delete
'7' : CC-session delete issued too early
'8' : CC-session delete already requested
'9' : CC-session has been cancelled (e.g. workfile could not be
extended due to disk space shortage)
'10' : connection error between slave and master
'11' : privilege necessary for MIRROR-CCOPY-SESSION missing
'12' : no mirror-volume installed for concerned volume(s)
'13' : mirror-volume(s) not synchronized
'14' : error after calling subsystem SHC-OSD
'15' : volume cannot be allocated/deallocated
'16' : Invalid request id
'17' : Invalid PVSID
'18' : Volume error
'19' or '19 / DMS RC = ....'
- file not cataloged
- file not accessible
- error during reading the catalog entry
- file on private volume
- error during reading ACL
- error during file lock request
- file opened in write mode
- file already included in another CC-session
- workfile included in another CC-session
- no file to save was given to Concurrent Copy Handler
'20' : Request id not unique
'21' : Missing privilege
'22' : Function or interface version not supported
'23' : Pubset also imported on slave
'24' : DAB-cache activated for the pubset
'25' : Pubset imported on master with BS2000 version lower V15.0B
'26' : One of the used pubsets is not accessible

### Response

'1' : a HSM0304 is sent for each file in error;
correct the files and try again
'3' : start the subsystem SRPMFACL and try again
'4', '5', '6', '7', '8':
a serslog entry has been written;
please contact the system administrator.
'1 / DMS RC = ....' or '2 / DMS RC = ....' or '4 / DMS RC = ....':
use given DMS-RC to know what to do to correct the problem.

## HSM0304

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0304 FILE '(&00)' CANNOT BE INCLUDED IN THE REQUESTED CONCURRENT COPY SESSION

## HSM0305

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0305 INVALID DIRECTORY USE

### Meaning

The used directory contains CATIDs from another environment.

### Response

Change directory and retry.

## HSM0306

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0306 CC-BACKUP IS NOT POSSIBLE DUE TO PROBLEM WITH SPVS

## HSM0307

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0307 INCONSISTENCY DETECTED DURING CONCURRENT COPY SESSION ON SPVS

## HSM0308

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0308 PROBLEM DURING CONTROL FILE CLEARING FOR SM-PUBSET '(&00)'. DMS RETURN CODE IS '(&01)'

### Meaning

&00: SM pubset id
&01: error code returned by DMS

## HSM0309

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0309 PUBSET '(&00)' NOT IN SPECIFIED ENVIRONMENT. PUBSET SKIPPED

### Meaning

Pubsets outside the environment specified by the statement are not
processed.

### Response

Use corresponding environment for rejected files.

## HSM031A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM031A FILE '(&00)' CANNOT BE INCLUDED IN THE REQUESTED CONCURRENT COPY SESSION. SERSLOG RECORD WITH ELSN = '(&01)' WRITTEN

### Meaning

&00: filename.
&01: record number in the SERSLOG file
(ELSN = Error Logging Sequence Number)

## HSM0310

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0310 USER IS NOT AUTHORIZED TO CALL THIS FUNCTION. CALL REJECTED

### Meaning

Only the system tasks are authorized.

## HSM0311

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0311 WARNING: THE GIVEN GUARD NAME '(&00)' IS NOT DEFINED

### Meaning

The guard name given in the structure PROTECTION is not defined, the
management class is nevertheless created.

## HSM0312

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0312 SUBSYSTEM '(&00)' IS NOT ACCESSIBLE

### Meaning

The subsystem (&00) is not loaded or not accessible.

### Response

Please contact the system administrator.

## HSM0313

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0313 CONCURRENT COPY BACKUP IS NOT POSSIBLE FOR FILE LOCATED ON PRIVATE VOLUME. FIRST FILE IN ERROR IS '(&00)'

### Meaning

'(&00)': name of the file which cannot be saved because it is located on a
private disk or on a tape.
The statement is aborted.

## HSM0314

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0314 ERROR WITH FGG '(&00)' GENERATION

### Meaning

'(&00)': name of the FGG of which some generation cannot be included in
the concurrent-copy session.

## HSM0315

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0315 FILE '(&00)' CANNOT BE INCLUDED IN THE REQUESTED CONCURRENT COPY SESSION. IT IS THE CONCURRENT COPY WORKFILE

## HSM0316

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0316 FILE '(&00)' CANNOT BE INCLUDED IN THE REQUESTED CONCURRENT COPY SESSION. DMS-RETURN-CODE IS '(&01)'

### Meaning

&00: filename
&01: error code returned by DMS

### Response

For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages'.

## HSM0317

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0317 INVALID DIRECTORY TYPE

### Meaning

Directory type must be NODE-NFS.

### Response

Change directory and retry.

## HSM0318

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0318 SAVE-FILE '(&00)' NOT FOUND. COPY ABORTED

## HSM0319

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0319 SAVE-FILE '(&00)' ALREADY EXISTS. COPY ABORTED

## HSM032A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM032A A VERSION BACKUP IS CURRENTLY NOT POSSIBLE, AS A REORGANIZATION RUN IS EXECUTED FOR THE SAME ARCHIVE.

### Meaning

Possible reasons:
- It is not possible to simultaneously perform reorganization
and version backup within the same archive.
- If you are using the recovered directory after //RVB with saving
directory processing, the lock flag was saved with the directory options.

### Response

- Wait for the processing completion and try again.
- If the lock exists even though no jobs are being processed for the
archive, unlock the archive directory using //MODIFY-ARCHIVE.

## HSM032B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM032B A REORGANIZATION RUN IS CURRENTLY NOT POSSIBLE, AS ANOTHER REQUEST IS EXECUTED FOR THE SAME ARCHIVE.

### Meaning

It is not possible to simultaneously perform reorganization
and version backup or another reorganization run within
the same archive.

### Response

Wait for the processing completion and try again.

## HSM032C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM032C DIRECTORY '(&00)' WAS NOT SAVED

### Meaning

During the reorganization process with
SAVE-DIRECTORY=*YES the directory was not saved due to errors.

## HSM0320

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0320 AUTOMATIC DUPLICATION IN SHADOW ARCHIVE '(&00)' STARTED

### Meaning

Save file copy to shadow archive started.

## HSM0321

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0321 AUTOMATIC DUPLICATION SKIPPED

### Meaning

Save file copy to shadow archive skipped.

## HSM0322

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0322 AUTOMATIC DUPLICATION ABORTED

### Meaning

Save file copy to shadow archive was not started because an error
had occurred.

## HSM0323

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0323 INCONSISTENT SAVE-VERSION SEQUENCE BETWEEN LINKED ARCHIVES

### Meaning

The save version sequence is different in the original archive and its
shadow one.

## HSM0324

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0324 SHADOW COPY-SAVE-FILE MUST LEAVE SAVE-VERSION UNCHANGED

### Meaning

When a Shadow Archive is used within a COPY-SAVE-FILE statement, the
following operands must not be used:
- SELECT-FILES, NEW-FILE-NAMES, EXCEPT-FILES,
- SELECT-JV, NEW-JV-NAMES, EXCEPT-JV

## HSM0325

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0325 SHADOW COPY-NODE-SAVE-FILE MUST LEAVE SAVE-VERSION UNCHANGED

### Meaning

When a Shadow Archive is used within a COPY-NODE-SAVE-FILE statement, the
following operands must not be used:
- SELECT-PATHS, EXCEPT-PATHS

## HSM0326

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0326 NEW SAVE FILE IN SHADOW ARCHIVE CREATED

### Meaning

New save file requested by the archiv attributes or after modification
of the attribute SHADOW-COPY from *ALLOWED-AND-NEW-SFID to *ALLOWED
no new save file was created in the original and in the shadow archive.

## HSM0327

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0327 DURING BACKUP FROM SNAPSET ONLY THE CATALOG ENTRIES OF MIGRATED FILES ARE SAVED

### Meaning

Against the attributes of the backup archive only the data
from files on S0 are saved during backup from snapset
with SAVE-DATA=*STD. For migrated files only the catalog entry
is saved.

## HSM0328

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0328 NET-STORAGE NOT SUPPORTED BY BS2000 VERSION ON MASTER HOST

### Meaning

Net-Storage is not supported by BS2000/OSD version lower than V9.0

### Response

Reenter a statement where files on Net-Storage are excluded.

## HSM0329

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0329 BACKUP SERVER OR PUBSET ON BACKUP SERVER NOT REACHABLE

### Meaning

Possible reasons:
- backup server not reachable or has wrong value in HSMS parameters;
- pubset to be saved not available on backup server, e.g. /IMPORT-PUBSET
missing.

### Response

Check backup server definition in HSMS parameters,
import pubset to be saved at the backup server.

## HSM040A

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM040A WARNING: NO JOB-VARIABLE AVAILABLE OR SELECTED FOR SEARCH STRING '(&00)'

### Meaning

No job-variable satisfying the appropriate selection criteria could be
found for the specified search string.

## HSM040B

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM040B ONLY BS2000 DIRECTORIES ARE ALLOWED IN THE PARAMETER 'ARCHIVE-NAME=*BY-DIRECTORY-NAME' OF THE '(&00)' STATEMENT

### Meaning

The operand 'BY-DIRECTORY-NAME' may only be used when the related
directory contains references to BS2000 files.

### Response

Give the archive name or the symbolic archive as ARCHIVE-NAME parameter.

## HSM040C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM040C SAVE FILE '(&00)' NOT FOUND

### Meaning

Requested SAVE FILE could not be found in the given directory.
(&00): save file (format 'S.YYMMDD.HHMMSS')

## HSM040D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM040D SAVE FILE '(&00)' GIVEN MORE THAN ONCE

### Meaning

Requested Save File occurs several times in the list.
(&00): save file (format 'S.YYMMDD.HHMMSS')

## HSM040E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM040E '(&00)' DOES NOT SUPPORT THE FUNCTIONALITY OF REQUEST '(&01)'. REQUEST NOT PROCESSED

### Meaning

The request contains a new functionality not supported by the HSMS version
that will process the request.
(&00) = 'CURRENT HSMS'
'HSMS ON MASTER <master_BCAM_name>'
'HSMS ON BACKUP SERVER <backup_server_BCAM_name>'
(&01) = request-name

## HSM040F

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM040F (&00) NOT ABLE TO RESTART REQUEST (&01) WHICH IS ONLY RESTARTABLE BY HSMS VERSION (&02)

### Meaning

A request can only be restarted by the HSMS version that
processed it initially.
&00: 'CURRENT HSMS'
'HSMS ON MASTER <master_BCAM_name>'
'HSMS ON BACKUP SERVER <backup_server_BCAM_name>'
&01: request name
&02: needed HSMS version

## HSM0400

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0400 WARNING: NO FILE AVAILABLE OR SELECTED FOR SEARCH STRING '(&00)'

### Meaning

No file satisfying the appropriate selection criteria could be found
for the specified search string.

## HSM0401

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0401 WARNING: MIGRATION NOT POSSIBLE FOR FILE '(&00)' (REASON '(&01)')

### Meaning

The specified file cannot be migrated due to an implicit restriction.
Possible reasons:
- (1) file is locked (already open)
- (2) file is empty (Last page pointer=0 or FCB type=*NONE)
- (3) file is on a private device
- (4) file is a file generation (FG) or a file generation group (FGG)
- (5) file is physically allocated in a SM-pubset (S0 migration inhibited)
- (6) file attribute 'AVAILABILITY=*HIGH' is set
- (7) file attribute 'WORK-FILE=*YES' is set
- (8) file attribute 'MIGRATE=*FORBIDDEN' is set

## HSM0402

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0402 WARNING: MIGRATION NOT PERMITTED FOR FILE '(&00)' (REASON '(&01)')

### Meaning

The specified file cannot be migrated due to an explicit migration lock:
Possible reasons:
- (1) file is protected against migration (INHIBIT).
- (2) file is protected by global exception list (EXCEPT-LIST).
- (3) file belongs to user ID SYSHSMS.

## HSM0403

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0403 WARNING : ERROR WHEN ACCESSING REQUEST FILE. REQUEST STATUS NOT UPDATED.

### Meaning

The REQUEST FILE can contain inconsistencies in the sense that the request
status cannot be updated due to REQUEST FILE access error.

## HSM0404

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0404 WARNING: NODE-ID '(&00)' SPECIFIED IN PATHNAME '(&01)' NOT UNDER HSMS CONTROL

### Meaning

Contact the HSMS administrator. The NODE must be placed under HSMS control
to be connected to HSMS server.

## HSM0405

Destination: USER-TASK Routing code: Weight: 00

Warranty : NO

HSM0405 ACCESS TO S2 STORAGE LEVEL FOR FILE '(&00)'. ACCEPT (Y/N)

### Meaning

The migrated file '(&00)' must be recalled from S2 storage level. You may
accept (Y) or refuse (N) the recall.
If you accept, the recall will start and no cancel will then be possible.
If you refuse, the recall is cancelled.
If the maximum wait time is reached, the recall will start automatically.
The wait time limit is fixed by the HSMS administrator.

## HSM0406

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0406 'VERIFY' STARTED FOR FILE '(&00)'

## HSM0407

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0407 WARNING: MIGRATION NOT YET ALLOWED FOR FILE '(&00)'

### Meaning

The specified file must not be migrated because it has not yet
been saved in a backup.

### Response

Try migration again later.

## HSM0408

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0408 WARNING '(&00)' IN MODULE '(&01)' WITH FUNCTION '(&02)' WHEN CALLED BY '(&03)'

### Meaning

A system error occurs when calling a not HSMS interface.

## HSM0409

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0409 DMS ERROR '(&00)' DURING ACCESS TO ARCHIVE DIRECTORY '(&01)'. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The directory file cannot be processed due to the specified error.

### Response

For more detailed information about the DMS error code, enter
/HELP-MSG in system mode or see the BS2000 manual 'System Messages'.

## HSM041A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM041A NO MORE PUBSPACE AVAILABLE FOR FILE '(&00)'

### Meaning

There is no more pubspace free for the given userid to recall file (&00).

### Response

Possibly migrate or delete some other files first, and try again, or
inform the system administrator.

## HSM041B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM041B REQUEST INTERRUPTED BY TSN '(&00)'

### Meaning

TSN (&00) has interrupted the request.
Possible reasons are:
(1) another user deleted the request by a //DELETE-REQUESTS statement
(2) the SM-pubset is under EXPORT (the EXPORT task TSN is displayed)
(3) the HSMS ServerTask encountered a serious error
(TSN 'HSMS' is displayed)

### Response

(1) The request is permanently deleted. No report is available.
Issue a new request if needed.
(2) The interruption is only temporary. An automatic rescheduling will
occur as soon as the SM-pubset is again available.
(3) For a request interrupted while in ACCEPTED state, an automatic
rescheduling will occur, so nothing should be done.
For a request interrupted while in STARTED state, the request is
switched to the INTERRUPTED state. Issue a //RESTART-REQUEST statement
to restart the request.

## HSM041C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM041C REQUEST NOT ADMITTED DUE TO A CLOSED TAPE SESSION ON ARCHIVE. STATEMENT REJECTED

### Meaning

A tape session defined on an archive is currently closed.
Synchronous or concurrent copy requests are not admitted.

### Response

Issue the request with WAIT-FOR-COMPLETION=*NO, or contact the HSMS
administrator to open the tape session.

## HSM041D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM041D ACCESS DENIED ON REQUEST, LOCKING HOST IS '(&00)'

### Meaning

The request is under processing by another host. It is not possible to
access it from any other host.

### Response

- Wait for the processing completion, the locking host will then unlock
the request.
- Issue the statement on the locking host.
- If the locking host is not available, contact the system administrator.

## HSM041E

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM041E DHSMBE5: FUNCTION '(&00)', ADDRESS = '(&01)', LENGTH = '(&02)', GROUP-ID = '(&03)', CALLED BY '(&04)'

### Meaning

Diagnose message for the HSMS support team.

## HSM041F

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM041F DHSBME5: NUMBER OF CLASS-5 PAGES = '(&00)' CALLED AT LOCATION '(&01)'

### Meaning

Diagnose message for the HSMS support team.

## HSM0410

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0410 WARNING: COMMON MEMORY AREA CANNOT BE DYNAMICALLY CHANGED

### Meaning

The virtual address space for the common HSMS memory area cannot be
dynamically changed during the current HSMS session.
For permanent changes (VALID-PERIOD=*PERMANENT) the new value
is stored in control file and will be activated during the next startup.

## HSM0411

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0411 DIRECTORY '(&00)' DOES NOT EXIST

## HSM0412

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0412 FILE '(&00)' DOES NOT EXIST

## HSM0413

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0413 CATALOG ID INVALID WITH 'CATALOG-ID-MODE=*NO' FOR FILE '(&00)'

### Meaning

No cat ID other than the default cat ID of the user ID may be specified in
this mode. In one statement, only files with the same default cat ID can
be processed.

### Response

Correct input.

## HSM0414

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0414 RENAME NOT ALLOWED: '(&00)' IS INVALID AS PART OF FILE OR JV NAME

### Meaning

Possible reasons:
1. A prefix or a new userid must not start with ':', '$', '#' or '@'.
2. The new userid must exist in the user catalog of the relevant pubset.

## HSM0415

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0415 A TEMPORARY FILE MUST BE CREATED FOR OPERAND '(&00)' BUT SYSTEM GENERATION DOES NOT SUPPORT THEIR CREATION

### Meaning

(&00): indicates which operand must be changed in order to avoid
the creation of a temporary file.

### Response

Give a file name in the input of the corresponding operand.
The generation of the system allowing the temporary files is possible.

## HSM0416

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0416 THE SPECIFIED '(&00)' PARAMETER OF THE '(&01)' STATEMENT DOES NOT CORRESPOND TO THE ARCHIVE TYPE

## HSM0417

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0417 ERROR REPORTED BY '(&00)' DURING '(&01)', RC = '(&02)'

### Meaning

&00: Identifier of the interface or HSMS processing step which returns
an unexpected return code.
&01: HSMS processing step.
&00: error code.

### Response

Contact the HSMS administrator.

## HSM0418

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0418 ERROR '(&00)' WHEN CALLING SYSTEM INTERFACE '(&01)'

### Meaning

The system interface (&01), called by HSMS, reported an error
i.e. returned the unexpected return code (&00).

### Response

Interpret the return code (&00) using the interface documentation.
If necessary contact system diagnosis.

## HSM0419

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0419 ERROR '(&00)' WHEN CALLING SYSTEM INTERFACE '(&01)' FOR FILE '(&02)'

### Meaning

The system interface (&01), called by HSMS for file (&02), reported an
error i.e. returned the unexpected return code (&00).

### Response

Interpret the return code (&00) using the interface documentation.
If necessary contact system diagnosis.
Example:
The error '00400005' means 'bad catid': the catid is either unknown, it is
not correctly given or is not supported in write mode from a slave shared
pubset. In all those cases, the file is recalled.

## HSM042A

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM042A DIRECTORY '(&00)' ALREADY EXISTS

### Meaning

The directory whose name is given in the statement is already cataloged.

### Response

Give another directory name.

## HSM042B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM042B TEMPORARY JV NAME '(&00)' NOT PERMITTED

### Meaning

The specified JV name refers to a temporary jobvariable and is
therefore not permitted.

## HSM042C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM042C WARNING : NO COMPRESSION REALIZED FOR NODE FILES

## HSM042D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM042D ARCHIVE '(&00)' IN ENVIRONMENT '(&01)' LOCKED BY TSN '(&02)' ON HOST '(&03)'

### Meaning

Current task will wait until the lock is released.
&00: name of the locked archive
&01: environment
&02: task having locked the archive
&03: host name

## HSM042E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM042E FILE '(&00)' NOT ACCESSIBLE

## HSM042F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM042F JOBVARIABLE '(&00)' NOT ACCESSIBLE

## HSM0420

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0420 FILE/JV NAME '(&00)' SYNTACTICALLY WRONG

## HSM0421

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0421 FILE NAME '(&00)' TOO LONG

## HSM0422

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0422 USER ID FOR FILE NAME '(&00)' DOES NOT EXIST

### Meaning

There is no JOIN entry for the user ID specified in the file name.

## HSM0423

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0423 TEMPORARY FILE NAME '(&00)' NOT PERMITTED

### Meaning

The specified file name refers to a temporary file and is
therefore not permitted.

## HSM0424

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0424 TEMPORARY FILE NOT SUPPORTED FOR 'OUTPUT=*SELECT-LIST'

### Response

Use a permanent file.

## HSM0425

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0425 OUTPUT INTO FILE '(&00)' NOT POSSIBLE

## HSM0426

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0426 FILE NAME LIST SHORTENED DUE TO MEMORY BOTTLENECK

### Response

Create file list, e.g. using SELECT-FILE-NAMES, and check it against the
statement report. Process the missing files in a subsequent statement.

## HSM0427

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0427 REQUEST FOR CLASS 5 MEMORY CANNOT BE HONORED

### Meaning

For more detailed information see the following message.

## HSM0428

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0428 FILE NAME ERROR LIST SHORTENED DUE TO MEMORY BOTTLENECK

### Meaning

The list of faulty or non-processed files is shortened. The amount of
files processed correctly is not affected.

### Response

See also information in the statement report, if created.

## HSM0429

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0429 TOO MANY ERRORS IN FILE NAME LIST. ERROR LIST SHORTENED

### Meaning

The specified list of file names contains more errors than can be output.

### Response

See also information in the statement report, if created.

## HSM043A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM043A DIRECTORY '(&00)' NOT FOUND IN THE CATALOG

## HSM043B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM043B ACCESS TO DIRECTORY '(&00)' NOT POSSIBLE AT THE MOMENT

### Meaning

Concurrent access on directory by another task.
&00: directory or repository name

### Response

Retry later again.

## HSM043C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM043C UNLOCK FAILED ON REPOSITORY '(&00)' (LOCKING TSN = '(&01)', LOCKING HOST = '(&02)')

### Meaning

An error occurs during unlock processing of the repository.
When happening before processing:
processing is aborted because an error occurs during recovery of
senseless lock
When happening after processing:
Lock got by current task on repository cannot be freed.
Further save operations from other hosts on the concerned repository are
no more possible without manual operation.

### Response

Use //MDA DIRECTORY-LOCK=*REMOVE to remove the lock.

## HSM043D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM043D ACCESS TO DIRECTORY '(&00)' NOT POSSIBLE AT THE MOMENT

### Meaning

Concurrent access on directory by another task.
&00: directory or repository name

## HSM043E

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM043E HSMS TRACE FILE '(&00)' ALREADY ACTIVE

### Meaning

(&00): file name.

## HSM043F

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM043F HSMS TRACE FILE NOT ACTIVE YET

## HSM0430

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0430 INVALID FORMAT FOR ARCHIVE DIRECTORY '(&00)'

### Meaning

There is already a file with the specified file name (&00), but it cannot
be used as an archive directory.
Possible reasons:
- FCB type not ISAM or wrong key position or key length.
- file is of type ISAM, but check-record is missing.
- file is a directory file, but created with an invalid CATALOG-ID mode.
- directory file for a several SVID archive can not be used as directory
file for a single SVID archive.
- A difference between the archive definition
and the directory was found during the
MODIFY-ARCHIVE-ATTRIBUTES statement.

### Response

Assign another file.

## HSM0431

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0431 DMS ERROR '(&00)' DURING '(&01)'-ACCESS TO ARCHIVE DIRECTORY '(&02)'. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The directory file cannot be processed due to the specified error.

### Response

For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages'.
If caller is //SHOW-ARCHIVE and DMS error code 'EXPECTED RECORD NOT FOUND'
repeat the statement.

## HSM0432

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0432 DMS ERROR '(&00)' DURING '(&01)'-ACCESS TO HSMS FILE '(&02)'. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The file cannot be processed due to the specified error.
If this message occurs during startup or at imcat of an SM-pubset and
indicates a non-existing HSMS file, the file will be created
automatically.

### Response

For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages'.

## HSM0433

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0433 DMS ERROR '(&00)' DURING '(&01)'-ACCESS TO FILE '(&02)'. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The file cannot be processed due to the specified error or the recalled
file cannot be unlocked.

### Response

For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages'.

## HSM0434

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0434 USER NOT AUTHORIZED TO ACCESS FILE/JV '(&00)'

### Meaning

A file/JV belonging to a foreign user cannot be processed due to missing
authorization. Also, non-privileged user are not allowed to specify
wildcards in the user ID and/or cat ID part of a file/JV name.

### Response

Re-enter statement under user ID of the file/JV owner or specify user ID
and/or cat ID in fully-qualified form.

## HSM0435

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0435 ACCESS ERROR '(&00)' FOR PUBSET CATALOG ENTRY '(&01)'

### Meaning

The catalog entry cannot be processed due to the specified error.
Possible reasons :
- (0020): Internal error
- (0040): Pubset in ACCESSIBLE state
- (0041): Specified volume-set does not exist
- (0043): System saturation
- (0044): Reconfiguration interrupted

## HSM0436

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0436 ERROR '(&00)' IN MODULE '(&01)' FOR FILE '(&02)'. FILE NOT PROCESSED

### Meaning

A module of the HSMS control program reports an internal error.

### Response

Pass statement report and SYSLST log for diagnosis.

## HSM0437

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0437 WARNING: SFID LIST OVERFLOW. STATEMENT PARTIALLY PROCESSED

### Meaning

Due to the SFID list overflow within HSMS not all of the selected
save files are processed.

### Response

Re-enter statement, select all non-processed SFIDs.

## HSM0438

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0438 SAVE-FILE-ID '(&00)' NOT FOUND

### Meaning

The save file with the specified save file ID
could not be found in the archive.

## HSM0439

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0439 WARNING: RETENTION PERIOD NOT EXPIRED. SAVE-FILE-ID '(&00)' NOT DELETED

### Meaning

The save file is protected for a fixed period, i.e. a physical protection
has been defined (RETENTION-PERIOD) or the save file contains save
versions with logical release date (FILE-EXPIRATION-DATE). At least one
of these protections is still active. The save file is not deleted.

### Response

If necessary delete save file using MODIFY-ARCHIVE ...,FORCED-DELETE=*YES.

## HSM044A

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM044A ANOTHER TRACE STMT IS CURRENTLY BEING TREATED

## HSM044B

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM044B ERROR '(&00)' WHEN TRYING TO LOCK REPOSITORY '(&01)'

### Meaning

The repository cannot be locked for processing.
Possible reasons:
- (0002): the repository is not in catalog
- (0003): the concerned file is not a repository
- (0004): the low key is invalid
- (0005): the low key is missing
- (0006): the high key is missing
- (0008): system memory saturation
- (0010): ARCHIVE internal error

### Response

For reason (0002) to (0006) restore a correct repository.
For reason (0008) and (0010) contact system administrator.

## HSM044C

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM044C HSMS LOGGING FILE '(&00)' OPENED

### Meaning

(&00): file name.

## HSM044D

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM044D HSMS LOGGING FILE '(&00)' CLOSED

### Meaning

(&00): file name.

## HSM044E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM044E SHADOW ARCHIVE '(&00)' IN ENVIRONMENT '(&01)' LOCKED BY TSN '(&02)' ON HOST '(&03)'. SHADOW PROCESSING ABORTED

### Meaning

Shadow archive is already in use when shadow processing is started.
Current shadow processing is aborted.
&00: name of the locked archive
&01: environment
&02: task having locked the archive
&03: host name

## HSM0440

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0440 WARNING: NO REQUEST FOUND

### Meaning

No request satisfying the specified criteria could be found in the
HSMS request file.

## HSM0441

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0441 ATTEMPT TO DELETE REQUEST '(&00)' IN ENVIRONMENT '(&01)' NOT SUCCESSFUL

## HSM0442

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0442 ATTEMPT TO RESTART REQUEST '(&00)' IN ENVIRONMENT '(&01)' NOT SUCCESSFUL

### Meaning

For more detailed information about the error cause see the statement
report.

## HSM0443

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0443 WARNING: NO ARCHIVE FOUND

### Meaning

No archive satisfying the specified criteria could be found in
the HSMS control file.

## HSM0444

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0444 WARNING: NO PUBSET FOUND

### Meaning

No pubset satisfying the specified criteria could be found in
the HSMS control file.

## HSM0445

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0445 WARNING: NO VOLUME FOUND

### Meaning

No volume satisfying the specified criteria could be found.

## HSM0446

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0446 WARNING: NO SAVE FILE FOUND

### Meaning

No SAVE FILE satisfying the specified criteria could be found, e.g.
- no obsolete save file is found,
- or the obsolete save file contains a file which is not yet obsolete.

## HSM0447

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0447 WARNING: NO FILE OR JOB VARIABLE FOUND

### Meaning

No file or JV satisfying the specified criteria could be found.

## HSM0448

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0448 WARNING: NO SAVE VERSION FOUND

### Meaning

No SAVE VERSION satisfying the specified criteria could be found.
This scenario also happens when meanwhile a save version has been deleted.
At S2 reorganization the standard save file is excluded.

## HSM0449

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0449 WARNING: SAVE FILE '(&00)' NOT DELETED

### Meaning

A (reorganized) copy of this save file has been created, but due to
an error which occurred during reorganization the original save file
is retained.

### Response

Check the statement report carefully, possibly delete the save file.

## HSM045A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM045A ERROR X'(&00)' DURING INITIALIZATION OF AN OPS STRUCTURE

### Response

Verify the second byte of the return-code. Most occurring cases are:
- 41: ask the system-administrator to start the subsystem SSTA.
- 03 followed by FFFF: a newer version of SSTA must be loaded.

## HSM045B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM045B ERROR X'(&00)' DURING DATA TRANSFER INTO AN OPS STRUCTURE. DATA NAME OR TYPE = '(&01)'

## HSM045C

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM045C LOCALIZATION INFORMATION OF FILE '(&00)' CANNOT BE REPAIRED. PROCESSING CONTINUES

### Meaning

Possible reasons:
- The pubset or SM-pubset is not declared to HSMS.
- The system archive *SYSMIGRATE for the corresponding pubset is not known
by HSMS.

### Response

Contact the system administrator.

## HSM045D

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM045D NO SYSINF-STREAM DEFINED.

### Meaning

If STRUCTURE-OUTPUT=*SYSINF, there has to be a definition
of a SYSINF-STREAM.

### Response

Define a SYSINF-STREAM.

## HSM045E

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM045E ERROR '(&00)' WHEN CALLING '(&01)' IN MODULE '(&02)'

### Meaning

The specified system interface reports the specified error to a module
of the HSMS control program.

### Response

Interpret the error code according to the interface documentation.
If necessary, pass statement report and SYSLST log for diagnosis.

## HSM045F

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM045F ERROR '(&00)' RESPECTIVELY '(&03)' WHEN CALLING '(&01)' IN MODULE '(&02)'

### Meaning

The specified system interface reports the specified error to a module
of the HSMS control program.
&00 : error is output in the form of hexadecimal constants.
&03 : error is output in the form of character constants, nonprinting
characters are output as smudge characters.

### Response

Interpret the error code according to the interface documentation.
If necessary, pass statement report and SYSLST log for diagnosis.

## HSM0450

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0450 ERROR '(&00)' WHEN CALLING '(&01)' IN MODULE '(&02)'

### Meaning

The specified system interface reports the specified error to a module
of the HSMS control program.

### Response

Interpret the error code according to the interface documentation.
If necessary, pass statement report and SYSLST log for diagnosis.

## HSM0451

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0451 INTERNAL ERROR '(&00)' IN MODULE '(&01)'. PROCESSING ABORTED

### Meaning

An internal error occurred in a module of the HSMS control program;
processing of the statement is aborted.

### Response

If necessary, pass statement report and SYSLST log for diagnosis.

## HSM0452

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0452 RECALL OF FILE '(&00)' NOT POSSIBLE

### Meaning

HSMS was not able to recall the data of the migrated file.
There is no localization information in the catalog entry of the file.

### Response

Use REPAIR-CATALOG-BY-EXCHANGE to write the localization information
in the catalog entry.

## HSM0453

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0453 INVALID RECORD '(&00)' IN DIRECTORY '(&01)'

### Meaning

During read access to the directory file an invalid (possibly destroyed)
record was detected. Process of the directory continues.

### Response

Do not modify the directory (!) and pass it for diagnosis together with
SYSLST log and statement report.

## HSM0454

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0454 NODE-S0-ID '(&00)' SYNTACTICALLY WRONG

## HSM0455

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0455 NODE-S0-ID '(&00)' TOO LONG

## HSM0456

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0456 ERROR REPORTED BY '(&00)' DURING '(&01)'

### Meaning

&00 : Identifier of the interface or HSMS processing step which returns
an unexpected return code.
&01 : HSMS processing step.
For more detailed information, see the following and/or preceding
messages.

## HSM0457

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0457 INTERNAL DATA LOCKED. STATEMENT PARTIALLY PROCESSED

### Meaning

TIME-OUT during COMMON MEMORY POOL or CONTROL FILE access.

### Response

Retry later or contact HSMS administrator.

## HSM0458

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0458 NODE-S0-ID NOT DEFINED

## HSM0459

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0459 ERROR '(&00)' IN MODULE '(&01)' WITH FUNCTION '(&02)' WHEN CALLED BY '(&03)'

### Meaning

A system error occurs when calling a not HSMS interface.

## HSM046A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM046A SHADOW ARCHIVE WITH DIRECTORY '(&00)' ALLOWS USAGE '(&01)', MAIN ARCHIVE '(&02)' ALLOWS USAGE '(&03)'

### Meaning

The usage definition of shadow archive and the usage definition of
main archive has to be the same

### Response

Correct the error cause and repeat the request.

## HSM046B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM046B RECONSTRUCTION OF AN ARCHIVE FROM THE DIRECTORY '(&00)' NOT POSSIBLE, BECAUSE THE DIRECTORY CONTAINS NO ARCHIVE DEFINITION

### Meaning

Possible reasons are:
- An archive with this directory was created/modified only in
an HSMS version lower V8.0.
- An error occured in a former CREATE-ARCHIVE run
during the creation of the archive definiton.

### Response

Call CREATE-ARCHIVE with RECONSTRUCT-ARCHIVE=*NO.

## HSM046C

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM046C WARNING: NO REDUCTION OF THE RETENTION PERIOD OF THE SAVE FILE WITH SAVE-FILE-ID '(&00)'

### Meaning

The expiration date of a save file must never be less
than the highest expiration date of the save versions.
In this case at least one save version exists with the
same expiration date like the save file.
(&00): save file (format 'S.YYMMDD.HHMMSS')

## HSM046D

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM046D WARNING: THE RETENTION PERIOD OF THE SAVE FILE WITH SAVE-FILE-ID '(&00)' IS ONLY REDUCED BY '(&01)' DAYS

### Meaning

The expiration date of a save file must never be less
than the highest expiration date of the save versions.
(&00): save file (format 'S.YYMMDD.HHMMSS')
(&01): number of days

## HSM046E

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM046E DMS ERROR '(&00)' WHEN CALLING '(&01)' IN MODULE '(&02)'. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The specified system interface reports the specified error
to the specified module of the HSMS control program.

### Response

For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages'.

## HSM046F

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM046F ARCHIVE ATTRIBUTES SAVED IN THE DIRECTORY '(&00)'

### Meaning

An archive with this directory
was created in HSMS version lower V8.0.
The directory did not contain archive attributes.
Now the directory is compatible with last HSMS versions.

## HSM0460

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0460 HSMS REQUEST RESTARTED

### Meaning

Processing of an interrupted request is restarted. The assigned
statement report will be extended.

## HSM0461

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0461 REQUEST STARTED BY COLLECTOR REQUEST. COLLECTOR REQUEST INTERRUPTED

### Meaning

The request remains STARTED. The collector request may be restarted
by the HSMS administrator only.

### Response

Check statement report, if necessary re-enter statement or contact
the HSMS administrator.

## HSM0462

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0462 ERROR WHEN ANALYZING '(&00)'. REPORT INCOMPLETE

### Meaning

An error occurred either during the creation of the ARCHIVE result file,
or during the copy of records from the ARCHIVE result file into the HSMS
report file.
Keep this file for diagnose purpose.

### Response

See previous errors and messages.

## HSM0463

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0463 DMS ERROR '(&00)' WHEN OPENING FILE FOR REPORT OUTPUT. OUTPUT REDIRECTED TO PRINTER

### Meaning

The assigned report file cannot be used.
Possible reasons:
- file is active, i.e. in use by another task.
- file protection prohibits write access.
- volume not accessible.
- file must have the SAM format.
- mail service problems.

### Response

Check report file or check mail service.

## HSM0464

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0464 REQUEST NOT FOUND IN REQUEST FILE. REQUEST STATUS NOT UPDATED

## HSM0465

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0465 WARNING: WRONG INPUT

## HSM0466

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0466 TAPE DEVICE FOR OUTPUT IS NOT AVAILABLE. REQUEST INTERRUPTED

### Meaning

The required tape devices cannot be reserved.

### Response

Use the HSMS statement RESTART-REQUESTS to restart the interrupted request
when the required output devices are available.

## HSM0467

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0467 REQUEST '(&00)' STARTED BY COLLECTOR REQUEST

### Meaning

The request named (&00) references a system archive and its standard
save file and was included in a collector request.
The collector request is assigned to the user ID of the HSMS
administrator.

## HSM0468

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0468 STORAGE BOTTLENECK FOR S1 PUBSET '(&00)'. PROCESSING ABORTED

### Meaning

No more files (i.e. no save files either) can be created on the specified
S1 pubset due to storage saturation.
Processing is aborted.

### Response

Erase not used files on the S1 pubset, then maybe reorganize archives
administrated by HSMS.

## HSM0469

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0469 MODIFICATION OF ARCHIVE DIRECTORY STARTED FOR '(&00)'

### Meaning

This message occurs only in the statement report of a MODIFY-ARCHIVE
statement and shows the subfunction executed.

## HSM047A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM047A '(&00)' PER CENT OF FILES IN SAVE FILE '(&01)' UNUSED. SAVE FILE NOT REORGANIZED

## HSM047B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM047B SNAPSET NOT AVAILABLE.

## HSM047C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM047C SAVE FILE COULD NOT BE CONTINUED. SNAPSET IS OLDER THAN AN EXISTING SAVE VERSION

## HSM047D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM047D SAVE FILE COULD NOT BE CREATED. SNAPSET IS OLDER THAN AN EXISTING SAVE VERSION IN THE BACKUP ARCHIVE

## HSM047E

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM047E SAVE FILE COULD NOT BE CONTINUED. SNAPSET HAS THE SAME TIMESTAMP AS AN EXISTING SAVE VERSION IN THE BACKUP ARCHIVE

### Meaning

The save versions inside the backup archive must be unique.

## HSM047F

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM047F SAVE FILE COULD NOT BE CREATED. SNAPSET HAS THE SAME TIMESTAMP AS AN EXISTING SAVE VERSION IN THE BACKUP ARCHIVE

### Meaning

The save versions inside the backup archive must be unique.

## HSM0470

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0470 WARNING: SAVE VERSION ATTRIBUTES NOT MODIFIED

## HSM0471

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0471 S1 STORAGE RESPECTIVELY S2 STORAGE HAS NOT BEEN REORGANIZED

### Meaning

Due to previously reported errors no reorganization took place.

### Response

See the previous messages HSM0450 / HSM045F or HSM0448.

## HSM0472

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0472 COPY '(&00)' OF SAVE FILE WILL BE DELETED

### Meaning

Due to a previously reported error the (possibly incomplete) copy of the
save file will be deleted.

### Response

Correct the error cause (see the previous message, normally HSM0449) and
restart reorganization.

## HSM0473

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0473 REORGANIZATION COMPLETED. '(&00)' PAGES ON S1 STORAGE RELEASED

### Meaning

The shown number of pages on the S1 Pubset are released by reorganization
of a HSMS archive.
The number shown is the difference in allocated pages before versus
after reorganization.

## HSM0474

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0474 SAVE FILE '(&00)' NOT REORGANIZED DUE TO S1 STORAGE BOTTLENECK

### Meaning

The message is output after all reducible save files have been
reorganized.
A (reduced) copy of the specified save file was not created due to
storage bottleneck on the S1 pubset.

### Response

Erase unused files on S1 pubset, if necessary repeat reorganization.

## HSM0475

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0475 SAVE FILE '(&00)' REORGANIZED INTO SAVE FILE '(&01)'

### Meaning

The contents of the old save file (&00) were copied into the new
save file (&01). The old save file was deleted.

## HSM0476

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0476 SAVE FILE '(&00)' DELETED DURING REORGANIZATION

### Meaning

The specified save file consists only of invalid files
and was thus deleted during reorganization of the archive.

## HSM0477

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0477 WARNING: NOT ALL S0 PUBSETS AVAILABLE

### Meaning

Some S0 pubsets to which the S1 pubset being processed is assigned
are not available (no IMCAT). All migrated files of this pubset are
treated as valid, i.e. the save files consist of 100% valid files.

### Response

Ask the system administrator to carry out a detailed
analysis and to issue an /IMPORT-PUBSET for these pubsets.

## HSM0478

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0478 HSMS ERROR '(&00)' FOR PUBSET '(&01)'

### Response

Get more information using /HELP-MSG-INFORMATION MSG-IDENTIFICATION=(&00).

## HSM0479

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0479 WARNING: MAXIMUM ALLOWED VALUE '(&00)' ASSUMED FOR 'FILE EXPIRATION DATE'

### Meaning

The date specified for FILE-EXPIRATION-DATE is too far in the future.
The date was restricted to (&00).

## HSM048A

Destination: CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM048A MASTER HOST NAME NOT AVAILABLE, REQUEST CANNOT BE SENT TO MASTER

### Meaning

The MSCF name of the master host is not given in MRSCAT entry.
Possible reason: MSCF subsystem not started.

## HSM048B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM048B VERSION BACKUP ARCHIVE HAS NOT BEEN REORGANIZED

### Meaning

Due to previously reported errors no reorganization took place.

### Response

See the previous message HSM0450 / HSM045F or HSM0451.

## HSM048C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM048C NO OBSOLETE FILE VERSIONS FOUND IN THE SPECIFIED SAVE FILES

### Meaning

NOTHING WAS REORGANIZED: there are no obsolete file versions within
the specified range of save files of the version backup archive.

## HSM0480

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0480 WARNING: PUBSET '(&00)' NOT AVAILABLE FOR MIGRATION STATUS EVALUATION

### Meaning

The catalog data of this pubset cannot be determined, e.g. because the
pubset is not available (missing /IMPORT-PUBSET).
The migration data cannot be checked.

## HSM0481

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0481 NOTE: NO MIGRATION INCONSISTENCY FOUND FOR PUBSET '(&00)'

### Meaning

Possible reasons:
- all migrated files on this pubset match (according to internal
CFID and version number) the entries in the assigned migration
archive (*SYSMIGRATE) and the corresponding save file on S1.
- no migrated files on this pubset.

## HSM0482

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0482 NO UNIQUE MASTER FOR REQUEST

### Meaning

A request applies to several shared pubsets with different masters.

### Response

Give separate requests for the pubsets.

## HSM0483

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0483 NO DATA FOR MIGRATED FILE '(&00)' IN BACKUP OR MIGRATION ARCHIVE. CATALOG ENTRY OF RESTORED FILE IS DELETED

### Meaning

The data of the file can be found neither in the backup archive nor in the
migration archive. The temporary restored catalog entry of this file is
deleted.

## HSM0484

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0484 NO FILES CAN BE FOUND TO PROCESS

### Meaning

- REPAIR-CATALOG-BY-EXCHANGE(RESTORE): no inconsistent files existing.
- REPLACE-SAVE-FILE-BY-EXCHANGE(RESTORE): the specified save file
contains no data of presently migrated files.
- REPAIR-CATALOG-BY-RESTORE and REPLACE-SAVE-FILE-BY-RESTORE:
the files to be restored are not in the backup or
version backup archive.

## HSM0485

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0485 FOR THE CATALOG ENTRY OF FILE '(&00)' THERE IS NO DATA IN THE BACKUP OR VERSION BACKUP ARCHIVE

### Meaning

REPAIR-CATALOG-BY-RESTORE like REPLACE-SAVE-FILE-BY-RESTORE can not
be executed for this file because there is no data of the file in
the backup or version backup archive.

## HSM0486

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0486 RESTORE ERROR FOR FILE '(&00)'. ERASE OF THE CATALOG ENTRY NOT SUCCESSFUL. NO DATA FOR THIS FILE EXISTING

### Meaning

The data of the file can be found neither in the backup archive
nor in the migration archive. The catalog entry of this file was
restored and could not be deleted.

## HSM0487

Destination: USER-TASK Routing code: Weight: 63

Warranty : NO

HSM0487 SAVE FILE '(&00)' IS NOT DELETED. IT CONTAINS THE DATA OF SOME PRESENTLY MIGRATED FILES

### Meaning

The save file is active i.e it contains the data
of some presently migrated files.

### Response

If these data are also in other save files, then the save file
can be made inactive by REPLACE-SAVE-FILE-BY-EXCHANGE.
If the data are in the backup or version backup archive, then the
save file can be made inactive by REPLACE-SAVE-FILE-BY-RESTORE.
The save file can always be deleted by FORCED-DELETE=*YES.

## HSM0488

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0488 WARNING: S1 PUBSET '(&00)' IMPORTED 'REMOTE' ONLY

### Meaning

Statement is processed. Access to the files of this pubset would not be
possible at this moment, especially no recall of files, which are
migrated to this pubset.

## HSM0489

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0489 S1 PUBSET '(&00)' NOT AVAILABLE. REQUEST INTERRUPTED

### Meaning

The S1 pubset is not available. Save files of the migration archive
on this pubset can not be checked. Request interrupted.

## HSM049A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM049A WARNING: SAVE FILE CONTAINS NOT OBSOLETE FILE VERSIONS. SAVE-FILE-ID '(&00)' NOT DELETED

### Meaning

The save file is protected, i.e. it contains the data of at least
one file version which is protected by the file attribute number
of backup versions. The save file is not deleted.

### Response

If necessary delete save file using MODIFY-ARCHIVE ...,FORCED-DELETE=*YES.

## HSM049B

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM049B MARK-FOR-DELETION SET FOR FILE '(&00)'

## HSM049C

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM049C MARK-FOR-DELETION RESET FOR FILE '(&00)'

## HSM0490

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0490 INTERNAL HSMS ERROR AT MASTER

### Meaning

An internal error was detected at the master.

### Response

Contact the HSMS administrator.

## HSM0491

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0491 NO EXCHANGE FOR FILE '(&00)' MADE

### Meaning

The file is in no (other) save file contained.

## HSM0492

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0492 ALL FILES OF PUBSET '(&00)', WHICH ARE STILL INCONSISTENT AFTER 'REPAIR-CATALOG-BY-EXCHANGE', ARE LISTED IN THE REPORT

## HSM0493

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0493 ONLY FILES, WHICH ARE PRESENTLY MIGRATED IN SAVE FILE '(&00)', ARE LISTED IN THE REPORT

## HSM0494

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0494 NO FILES TO BE PROCESSED COULD BE FOUND IN ARCHIVE '(&00)'

### Meaning

Possible reasons:
REPLACE-SAVE-FILE-BY-RESTORE: the files to be restored are not in the
backup or version backup archive.
MODIFY-ARCHIVE: files already marked / unmarked for deletion.

## HSM0495

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0495 ERROR '(&00)' DURING CATALOG ACCESS. PROCESSING ABORTED

### Response

Get more information using /HELP-MSG-INFORMATION MSG-IDENTIFICATION=(&00).

## HSM0496

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0496 NO MASTER COMPUTER COULD BE DETERMINED DURING REQUEST ASSIGNMENT. REQUEST INTERRUPTED

### Meaning

No master computer is accessible for the pubset processed in the
statement.
Possible reason: - the actual master is crashed.

### Response

Re-enter the statement later.

## HSM0497

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0497 ERROR '(&00)' DURING ARCHIVE SUBSYSTEM CALL. PROCESSING ABORTED

### Meaning

Possible reasons (&00):
04: Invalid directory for current run
08: No disc VSN specified
10: Invalid ASN or SVID
12: Invalid public disc specification
13: Invalid or missing VSN list
14: Invalid FROM save version
15: Other users files specified by not privileged user
18: Relative file generation number must not be used in current statement
21: Device type 'WORK' must not be used with DIRECTORY
24: Time specified in FROM operand is not coherent
25: One of the specified operand requires a directory
27: Continue specified without directory and without VSN(s)
30: FORCE=*YES requires fully qualified SVIDs
31: Error detecting by /SHOW-FILE-ATTRIBUTES on FGG index
35: Invalid rename at EXPORT
36: SAVE/RESTORE with CONTINUE or DIRSAVE not possible
with specified device type
37: TARGET-ARCHIVE-VERSION incompatible with other operands
38: LOCATION-RESET or ATTRIBUTE-RESET is not allowed
OTHERS: Internal HSMS error when building ARCHIVE parameter
list.

### Response

Contact the system administrator.

## HSM0498

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0498 ERROR '(&00)' DURING CONNECTION BETWEEN MASTER AND SLAVE COMPUTER.

### Meaning

Possible reasons (&00):
- '32' : internal error,
- '65' : Host unknown,
- '66' : Host not connected,
- '128' : Connection timeout,
- '129' : Connection overloaded.

## HSM0499

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0499 WARNING: THE CATALOG ID OF THE DIRECTORY HAS BEEN CHANGED

### Meaning

Notes on possible consequences:
- Changing the catalog ID of the directory causes
purge problems with MAREN.
- The specified archive may have a linked archive
(shadow archive or original archive).
The directory-catid is changed only for the specified archive.

### Response

- Adapt the directory name in the volume records in the MAREN catalog
with DIRCONV via UPDATE-VOLUME-CATALOG.
- If there is an archive linked to the specified archive, check
the directory path and adapt the catid of the directory if necessary.

## HSM050A

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM050A SM-PUBSET '(&00)' DOES NOT HAVE VOLUME SETS RESERVED FOR HSMS USAGE

## HSM050B

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM050B STORAGE BOTTLENECK FOR S1 VOLSET '(&00)'. PROCESSING ABORTED

### Meaning

No more files (i.e. no save files either) can be created on the specified
S1 volume set due to storage saturation.
Processing is aborted.

### Response

Erase not used files, release obsolete save files on the S1 volume set
and/or reorganize HSMS migration archives.

## HSM050C

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM050C STORAGE BOTTLENECK FOR S1 LEVEL OF SM-PUBSET '(&00)'. PROCESSING ABORTED

### Meaning

No more save files can be created on the specified S1 storage level
due to storage saturation. The S1 storage level consists of volume sets
with the usage HSMS-CONTROLLED.
Processing is aborted.

### Response

Erase not used files, release obsolete save files on S1 storage level
of the SM-pubset and/or reorganize HSMS migration archives.

## HSM050D

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM050D CURRENTLY S1-LEVEL SPECIFICATION '(&00)' FOR PUBSET '(&01)' IS NOT POSSIBLE

### Meaning

When taking an SM pubset under HSMS control the S1 level must be empty.
When removing the S1 level (S1-VOLUME-SET=*UNDEFINED) or changing from
*ALL-HSMS-CONTROLLED to a single volume set the S1 level of the SM pubset
must not contain save files.

### Response

Free S1 storage level by removing all the save files from it:
- Save files in migration archives can be reorganized to
S2 storage level with //MGF.
- Save files in backup archives can be moved to S2 level
by //MSF or //CSF and subsequent deletion from S1 level
with //MODIFY-ARCHIVE.
- Save files in archival archives can be copied to S2 by //CSF
and subsequent deletion from S1 level with //MODIFY-ARCHIVE.
- Removing obsolete save files with //MODIFY-ARCHIVE.

## HSM050E

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM050E NET-STORAGE VOLUME '(&00)' CANNOT BE USED.

### Meaning

Possible reasons:
- The specified Net-Storage volume is not assigned to a pubset.
A Net-Storage volume can be assigned to a pubset by
/ADD-NET-STORAGE-VOLUME.
- The specified volume is not a Net-Storage volume. Use the command
/SHOW-NET-STORAGE to view existing Net-Storage volumes on a system.

## HSM050F

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM050F PVS '(&00)' NOT ACCESSIBLE. STATEMENT ABORTED.

### Meaning

The Pubset (&00) is not in an accessible state.

### Response

Contact the system administrator.

## HSM0501

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0501 REMOTE NODE-S0 CANNOT BE PUT UNDER HSMS CONTROL BECAUSE HSMS-SV SUBSYSTEM IS NOT AVAILABLE

### Meaning

Without HSMS-SV, HSMS can only support DMS functions and *BS2000-UFS.
The subsystem HSMS-SV is not declared in the subsystem catalog.

### Response

Install HSMS-SV subsystem in the configuration.

## HSM0502

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0502 SM-PUBSET '(&00)' NOT DEFINED IN CATALOG

## HSM0503

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0503 IDENTIFIER '(&00)' IS NOT A SM-PUBSET-ID

## HSM0504

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0504 VOLUME-SET '(&00)' NOT DEFINED IN CATALOG

## HSM0505

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0505 IDENTIFIER '(&00)' NOT A VOLUME-SET

## HSM0506

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0506 SM-PUBSET '(&00)' ALREADY UNDER HSMS CONTROL

## HSM0507

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0507 VOLUME-SET '(&00)' NOT UNDER HSMS CONTROL

## HSM0508

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0508 VOLUME-SET '(&00)' NOT RESERVED FOR GIVEN SM-PUBSET

## HSM0509

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0509 ARCHIVE '(&00)' IN ENVIRONMENT '(&01)' MUST BE PUBLIC

## HSM0510

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0510 CATID '*STD' IS NOT A SYSTEM-MANAGED-PUBSET

### Meaning

The default pubset of the user is not a system-managed pubset. Hence, it
is not possible to display management classes on that pubset.

### Response

Issue the statement specifying the catalog-id of a system-managed pubset.

## HSM0511

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0511 MANAGEMENT-CLASS NOT DEFINED IN GENERIC CATALOG OF PUBSET '(&00)'

### Meaning

No management-class matching the selection criteria found in the generic
catalog.

## HSM0512

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0512 INVALID GUARD NAME '(&00)'

### Meaning

The GUARD name given in the structure PROTECTION is not accepted by GUARD,
or the given environment differs from the management class environment.

### Response

Create GUARD or correct the name.

## HSM0513

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0513 ACCESS TO OBJECT NOT AUTHORIZED

### Meaning

User tries to access an object protected by GUARD/ACL.

### Response

Contact the system administrator to restore access right.

## HSM0514

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0514 SUBSYSTEM GCF NOT AVAILABLE

### Meaning

Subsystem GCF not loaded or not accessible.

## HSM0515

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0515 ACCESS TO OBJECT LOCKED BY THE GCF SERVER

### Meaning

The object is locked by another task.

## HSM0516

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0516 OBJECT '(&00)' ALREADY DEFINED IN GENERIC CATALOG OF PUBSET '(&01)'

## HSM0517

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0517 SM-PUBSET '(&00)' CURRENTLY NOT ACCESSIBLE

### Response

Check the access status of the SM-Pubset.

## HSM0518

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0518 WARNING: DEFINITION '(&00)' REMOVED FROM '(&01)' TABLE (VALID PERIOD IS '(&02)')

### Meaning

HSMS detected a SM-pubset which has an alias entry as a SF-pubset. HSMS
deleted the SF-pubset entry. This may happen after a conversion of a
pubset from SF to SM while keeping the same catalog-id.
(&00): name of the entry
(&01): pubset: SF-pubset-table
(&02): session : the entry was only removed from memory
permanent: the entry was removed from the control-table

## HSM0519

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0519 WARNING: SYSTEM ARCHIVE '(&00)' COULD NOT BE CREATED OR SETUP CORRECTLY. PROCESSING CONTINUES

### Meaning

An error occurred while creating an archive specified in the
CREATE-SM-PUBSET-PARAMETERS statement.
(&00): *SYSBACKUP / *SYSMIGRATE / *SYSARCHIVE /
*SYSNODEBACKUP / *SYSNODEARCHIVE

### Response

After the completion of the statement, check the status of the system
archives of the SM-pubset.

## HSM052A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

HSM052A CMS ERROR '(&00)' ON PVS '(&01)'

### Meaning

The CMS error (&00) occurred during the MRSCAT entry access for PVS (&01).

## HSM0520

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0520 PUBSET '(&00)' NOT DEFINED IN CATALOG

## HSM0521

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0521 SM-PUBSET '(&00)' CANNOT BE GIVEN IN THIS STATEMENT

### Response

Use the statement MODIFY-SM-PUBSET-PARAMETERS for a SM-pubset.

## HSM0522

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0522 IDENTIFIER '(&00)' IS NOT A SF-PUBSET-ID

## HSM0523

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0523 ERROR '(&00)' DETECTED DURING '(&01)' PROCESSING

### Meaning

'&00': error indicator
'1' : given catid is neither SF-pubset nor SM-pubset
'2' : catid unknown or pubset not accessible
'3' : given catid is not a SM-pubset
'4' : given catid is already known in HSMS as SF-pubset
'5' : internal error
'6' : requested action already in process
'&01': IMPORT-CATALOG / EXPORT-CATALOG /
ADD-VOLUME-SET / REMOVE-VOLUME-SET

### Response

'1', '2' and '3': correct the catid and retry
'4': make first a MODIFY-PUBSET-PARAMETERS with all default values to
specify to HSMS that the catid is no more a SF-pubset; then retry
'5': please contact the system administrator
'6': none

## HSM0524

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0524 WORKSTATION '(&00)' ALREADY DEFINED IN ENVIRONMENT '(&01)'

### Meaning

A workstation must only be defined in one single environment.
&00: workstation name
&01: SF or SM with catid

### Response

Correct environment parameter or remove the workstation from HSMS control
for the old environment.
(MODIFY-NODE-PARAMETERS HSMS-CONTROL=*NO,ENVIRONMENT=&01)

## HSM0526

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

HSM0526 DURING '(&00)' AND 'SENDING EVENT TO SE MANAGER' MACRO '(&01)' REPORTS RC '(&02)'. PROCESSING CONTINUES

### Meaning

'&00': IMPORT-PUBSET / EXPORT-PUBSET / DELETE-REQUEST
START-SUBSYTEM / STOP-SUBSYSTEM / CHANGE-REQUEST-STATUS
'&01': name of the macro
'REWREQ' : REWAS macro
'REWS2J' : REWAS macro
'VAS.SSTAPUT' :
'&02': return code of the macro

### Response

Please, make SERSLOG file accessible to the service

## HSM0527

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0527 WARNING: SAVE FILE '(&00)' IS STILL BEING WRITTEN. SAVE FILE NOT REORGANIZED

### Response

Wait until migration to the save file is completed and repeat
the reorganization process. If there currently are no uncompleted
migrations, contact the service.

## HSM0530

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0530 NODES FROM DIFFERENT ENVIRONMENTS. USER DEFAULT ENVIRONMENT IS USED. PROCESSING CONTINUES

## HSM0531

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0531 ENVIRONMENT CHANGED FROM '*STD' TO '*NODE-STD'. PROCESSING CONTINUES

## HSM0550

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

HSM0550 WARNING: SOME FILES NOT MIGRATED (REASON '(&00)')

### Meaning

- (NOT-BACKUPED) : some files have not been saved yet in a backup
- (PROTECTED) : some files are protected against migration
(INHIBIT).
- (NET-STORAGE) : Some files are not allowed to be migrated
because they are net-storage files
- (MULTIPLE-REASON) : Any combination of reasons (1), (2) and (3).

## HSM0560

Destination: USER-TASK Routing code: Weight: 90

Warranty : NO

HSM0560 NET-STORAGE VOLUME '(&00)' NOT ASSIGNED TO A PUBSET. FILE '(&01)' CANNOT BE FOUND.

### Meaning

The Net-Storage volume storing the save file to be moved is not assigned
to a pubset. The save file cannot be moved.

### Response

Check status of the Net-Storage volume. A Net-Storage volume can be
assigned to a pubset by /ADD-NET-STORAGE-VOLUME.

## HSM0600

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0600 HSMS ERROR IN COMMUNICATION SUBTASK. STATEMENT DROPPED

## HSM0601

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0601 HSMS ERROR DURING STATEMENT PROCESSING. OUTPUT LOST. CONTACT HSMS ADMINISTRATOR

## HSM0602

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0602 HSMS ERROR IN SERVER TASK DURING REQUEST PROCESSING. REPORT LOST. CONTACT HSMS ADMINISTRATOR

## HSM0603

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0603 HSMS ERROR DETECTED IN CLIENT INPUT. REQUEST REJECTED

## HSM0604

Destination: USER-TASK, CONSOLE Routing code: U Weight: 50

Warranty : NO

HSM0604 HSMS CLIENT OR CALENDAR NODE BACKUP/ARCHIVE/RESTORE FUNCTIONALITY NOT SUPPORTED IN SIMULATION MODE. REQUEST REJECTED

## HSM0605

Destination: USER-TASK Routing code: Weight:

Warranty : NO

HSM0605 HSMS-API INTERFACE USAGE ERROR '(&00)' DETECTED AT STEP '(&01)'

### Meaning

Possible errors:
- MULTIPLE-CONNECTION : same task tries to open multiple connections
with HSMS-API.
- NO-CONNECTION : caller tries to access HSMS-API without
connection.
- INVALID-PARAMETER : invalid parameter value.
- PARAMETERS-COMBINATION: a wrong combination of parameters is detected.
- PARAMETERS-ACCESS : given area is not accessible.

### Response

Check parameter list available in the CONSLOG file.

## HSM0606

Destination: USER-TASK, CONSOLE Routing code: * (main console) Weight: 70

Warranty : NO

HSM0606 SENT REPORT IS NOT COMPLETE FOR REASON '(&00)'

### Meaning

&00 = 1: open error on report file
2: report file is empty
3: read error on first record
4: read error on one of the records
5: error on sending protocol tag
6: error on sending buffer

## HSM0607

Destination: USER-TASK Routing code: Weight: 50

Warranty : NO

HSM0607 CALENDAR NODE NOT DEFINED

## HSM0900

Destination: CONSOLE Routing code: U Weight: 98

Warranty : NO

HSM0900 INTERNAL HSMS ERROR '(&00)' IN MODULE '(&01)'. HSMS TERMINATES WITH DUMP

### Meaning

A system dump is generated. The subsystem HSMS is unloaded.

### Response

Pass the system dump, console logging and HSMS report for diagnosis.

## HSM0901

Destination: CONSOLE Routing code: U Weight: 98

Warranty : NO

HSM0901 INTERNAL HSMS ERROR '(&00)' IN MODULE '(&01)'. HSMS SERVER TASK TERMINATES WITH DUMP

### Meaning

An internal error was detected in the HSMS control program.
A system dump is taken, the HSMS server task terminates abnormally.

### Response

Pass the system dump, console log and HSMS report for diagnosis.

## HSM0902

Destination: CONSOLE Routing code: U Weight: 98

Warranty : NO

HSM0902 INTERNAL HSMS ERROR '(&00)' IN MODULE '(&01)'. STATEMENT PROCESSING TERMINATES WITH DUMP

### Meaning

An internal error was detected in the HSMS control program.
A system dump is taken, statement processing is aborted.

### Response

Pass the system dump, console log and HSMS report for diagnosis.

## HSM0903

Destination: CONSOLE Routing code: U Weight: 98

Warranty : NO

HSM0903 INTERNAL ERROR IN SUBSYSTEM HSMS. STATEMENT PROCESSING TERMINATES WITH DUMP

### Meaning

An internal error was detected in the HSMS control program.
A system dump is taken, statement processing is aborted.

### Response

Pass the system dump, console log and HSMS report for diagnosis.

©2024 Fujitsu | BS2000 System Messages