## DMS0AAA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AAA ISAM DATA LOCK. MACRO NOT PROCESSED

### Meaning

An ISAM macro could not be processed because a data lock imposed
by another user working with the same file was in force when the attempt
was made to process the macro, and this lock covers the required data.
The program is continued with the EXLST exit PGLOCK, if defined,
otherwise it is terminated.

### Response

Retry the ISAM action with the RETRY macro.

## DMS0AAB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AAB ISAM key sequence not allowed. Check program.

### Meaning

A PUT macro would result in a not allowed record sequence (at least
one record would have a key smaller than its predecessor).
Records whose sequence is invalid have not been inserted into the file.
The program is continued with the EXLST exit 'SEQCHK', if defined,
otherwise it is terminated.

## DMS0AAC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AAC SECONDARY ALLOCATION FOR ADDITIONAL DISK MEMORY REQUIREMENTS NOT POSSIBLE. MACRO NOT PROCESSED

### Meaning

During the processing of an ISAM macro additional disk memory is required.
However, the secondary allocation of disk memory for the file concerned
has the value '0'.
The program is continued with the EXLST exit NOSPACE, if defined,
otherwise it is terminated.

### Response

Change the value of the SPACE operand so as to enable secondary
allocation.

## DMS0AAD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AAD CURRENT RECORD SIZE LARGER THAN SPECIFIED IN 'RECSIZE' OPERAND

### Meaning

During an ISAM operation of the type GET, GETR, GETKY or GETFL a record
was found whose length is greater than that specified in the RECSIZE
operand (only in the case of RECFORM=V).
The record was copied in shortened form (i.e. with a length
corresponding to the value specified in the RECSIZE operand).
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Process the record in its shortened form or change the value of the
RECSIZE operand accordingly and retry the program.

## DMS0AAE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AAE END OF ISAM FILE REACHED. ONE RECORD WAS NOT READ

### Meaning

During processing of the ISAM macro GET, GETR or GETFL (with LIMIT=END)
either end-of-file or start-of-file has been reached, depending on
the processing direction.
The program is continued with the EXLST exit EOFADDR, if defined,
otherwise it is terminated.

## DMS0AAF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AAF MULTIPLE ISAM KEY. MACRO NOT PROCESSED

### Meaning

Using the PUT or INSRT macro an attempt was made to copy a record with
a key into the file. However, the file already contains a record with this
key, but the operand DUPEKY=YES is not set in the FCB.
The program is continued with the EXLST exit DUPEKY, if defined,
otherwise it is terminated.

### Response

Check the program; if necessary specify DUPEKY=YES and restart the macro
using the operand STORE instead of INSRT.

## DMS0AA1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA1 SYSTEM ERROR: INTERNAL INCONSISTENCY DURING ISAM PROCESSING. MACRO NOT PROCESSED

### Meaning

During the processing of an ISAM macro an internal system inconsistency
occurred or a system function called by ISAM reported an error
(e.g. rejection of a memory request due to shortage of memory space).
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Contact the system administrator.

## DMS0AA2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA2 SYSTEM ERROR: INCONSISTENCY DURING ISAM I/O OPERATION. MACRO NOT PROCESSED

### Meaning

During an I/O operation during the processing of an ISAM macro a
system-internal inconsistency occurred which was caused by something
other than a hardware error.
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Contact the system administrator.

## DMS0AA3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA3 PROGRAM ERROR: ILLEGAL USE OF OR VALUE FOR AN ISAM DMS ACTION MAKRO. MACRO NOT PROCESSED

### Meaning

An ISAM DMS macro was not correctly issued.
Possible reasons:
- Macro call incompatible with OPEN mode.
- Format of FCB not consistent with format of DMS macro
(e.g. FCB with PARMOD '24' and action macro with PARMOD '31').
- Length of a record not permitted for RECFORM=V
(record too small to accommodate key and perhaps flags,
record larger than specified in BLKSIZE operand in FCB).
- PUTX macro or ELIM macro (without key) without directly preceding
read call (with lock).
- PUTX macro for record with updated key.
- PUTX macro for update of record length in LOCATE mode.
- Inadvertent overwriting of information after PUT or PUTX in LOCATE
mode.
- GETFL macro for file for which no flags are defined.
- RETRY macro without previous PGLOCK condition.
The program is continued with the EXLST exit USERERR, if defined,
otherwise it is terminated.

### Response

If necessary take a dump. Check and correct the program.

## DMS0AA4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA4 SHORTAGE OF DISK MEMORY SPACE FOR ISAM DATA. MACRO NOT PROCESSED

### Meaning

Possible reasons:
- During the processing of an ISAM macro additional disk memory space
was required, but secondary allocation was not possible.
- A shortage of disk memory space may also occur if a file is to be
opened with BLKSIZE=(STD,n), 'N > 2', but no primary allocation or an
inadequate primary allocation was defined.
In such a case error message DMS0DA4 is issued.
- With shared pubset mode a malfunction in the MSCF connection is also
possible between slave and master.
- In FCB or ADD-FILE-LINK LARGE_FILE=*FORBIDDEN has been set,
but concerned file will exceed 32 gigabytes.
The program is continued with the EXLST exit NOSPACE, if defined,
otherwise it is terminated.

### Response

Supply enough disk memory space or modify the primary allocation
accordingly, or specify parameter LARGE_FILE=*ALLOWED in concerning
FCB resp. ADD-FILE-LINK.

## DMS0AA5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA5 SHORTAGE OF DISK MEMORY SPACE FOR ISAM INDEX AREAS. MACRO NOT PROCESSED

### Meaning

During the processing of an ISAM macro, additional disk memory space
was required for the index areas but secondary allocation was not
possible.
The program is continued with the EXLST exit ISPERR, if defined,
otherwise it is terminated.

### Response

Supply enough disk memory space or modify the primary allocation
accordingly.

## DMS0AA6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA6 INVALID FCB ADDRESS PASSED TO ISAM OR ISAM ACTION MACRO CALLED BEFORE 'OPEN' OR AFTER 'CLOSE'. CORRECT PROGRAM

### Meaning

The FCB address passed to ISAM for the processing of an ISAM macro
was invalid. The FCB has been completely or partially destroyed or an ISAM
action macro has been issued before opening or after closing the file.
When using SHARED=YES, also the FCB of another opened file may be invalid.

## DMS0AA7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA7 INCONSISTENCY IN ISAM FILE OR ILLEGAL USE OF ISAM ACTION MACRO 'PUTX' IN 'LOCATE' MODE. MACRO NOT PROCESSED

### Meaning

Either a block of an ISAM file read in during the processing of an ISAM
macro contained inconsistent block management information
(i.e. the file may be inconsistent) or a data block buffer was
inadvertently overwritten by the user during an ISAM action
macro PUTX in LOCATE mode.
The program is continued with the EXLST exit USERERR, if defined,
otherwise it is terminated.

### Response

Contact the system administrator, repair inconsistent file by
command REPAIR-DISK-FILE.

## DMS0AA8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA8 RECORD WITH SPECIFIED KEY NOT FOUND

### Meaning

During the processing of an ISAM macro GETKY or ELIM (with a key
specification) no record could be found with a key matching the one
specified in the field designated by the FCB operand KEYARG.
This record has not been read or deleted.
The program is continued with the EXLST exit NOFIND, if defined,
otherwise it is terminated.

### Response

If necessary check the value specified for the key input.

## DMS0AA9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AA9 HARDWARE ERROR. ISAM MACRO NOT PROCESSED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

## DMS0AFE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AFE BCAM CONNECTION ERROR

### Meaning

The user has attempted to execute an ISAM action macro on a remote host
identified by the catalog identifier field of the file name.
In the event of a BCAM connection error, error code 00FE is returned
by module RFADCSND/RFADRCV/RFADCLGF. The appropriate BCAM error message
is output at the operator console.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0AFF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0AFF BCAM CONNECTION INOP OR ABOUT TO BE SEVERED

### Meaning

The user has attempted to execute a DMS command or macro in a remote host
identified by the catalog identifier field of the file name.
Error code 00FF is returned by module RFADCSND /RFADRCV /RFADCLGF
due to a preceding error on the same communication line.

### Response

Clear down the connection by means of the /REMOVE-RFA-CONNECTION
command and then set it up again by means of a /SET-RFA-CONNECTION
command.
If the error persists, contact the system administrator.

## DMS0A0A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A0A ISAM INDEX BLOCK INCONSISTENT. PRESUMABLY ISAM FILE DEFECTIVE

### Meaning

During the processing of an ISAM macro an inconsistency was detected in
an index block.
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Check the file and repair it using /REPAIR-DISK-FILE if necessary.

## DMS0A0B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A0B ISAM FILE INCONSISTENT. PRESUMABLY ISAM FILE DEFECTIVE

### Meaning

During the processing of an ISAM macro an inconsistency was detected in
the control block, in an overflow block or in the index structure.
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Check the file and repair it using /REPAIR-DISK-FILE, if necessary.

## DMS0A0C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A0C IOAREA1 BUFFER INCONSISTENT. TAKE USER DUMP

### Meaning

During the processing of an ISAM PUT macro an inconsistency was detected
in the IOAREA1 buffer.
The buffer has presumably been overwritten by the program.
The program is continued with the EXLST exit USERERR, if defined,
otherwise it is terminated.

### Response

Analyze the dump.

## DMS0A0D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A0D FREE BLOCK OF ISAM FILE INCONSISTENT. PRESUMABLY ISAM FILE DEFECTIVE

### Meaning

During the processing of an ISAM macro an inconsistency was detected in a
free block.
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Check the file and repair it using /REPAIR-DISK-FILE, if necessary.

## DMS0A0E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A0E SYNTAX ERROR: OPERAND '(&00)' ILLEGAL. CORRECT COMMAND

## DMS0A01

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A01 ISAM LOCK EXISTS IN ANOTHER FILE. PROGRAM CONTINUED

### Meaning

An ISREQ macro with the operand ACTION=UNLOCK has been processed for an
ISAM file which has no ISAM lock.
However, there is a lock in another file which is being processed by this
task. The address of the FCB assigned to the file with the lock is
transferred in register 1.

### Response

Use ISREQ (1),ACTION=UNLOCK to unlock the other file, if necessary.

## DMS0A02

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A02 NO ISAM LOCK EXISTS. PROGRAM CONTINUED

### Meaning

An ISREQ macro with the operand ACTION=UNLOCK has been processed for an
ISAM file which has no ISAM lock.
Nor is there a lock in any other file which is being processed by this
task.

## DMS0A03

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A03 INVALID PARAMETER ADDRESS FOR ISAM POOL MACRO OR FOR MACRO TO PROCESS SECONDARY INDICES

### Meaning

An ISAM pool macro or a macro to process secondary indices has been
generated and the header of the parameter list is not accessible or the
address of the parameter list is not aligned on word boundary.

### Response

Correct the program and try again.

## DMS0A05

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A05 ALLOCATOR REPORTS TO ISAM: ERROR IN CONNECTION WITH REMOTE HOSTS DURING SECONDARY ALLOCATION

### Meaning

After a secondary allocation the return code '0305' is returned to ISAM.
The MRS connection is destroyed.

### Response

Contact the system administrator.

## DMS0A09

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A09 ISAM DATA BLOCK INCONSISTENT. PRESUMABLY ISAM FILE DEFECTIVE

### Meaning

During the processing of an ISAM macro an inconsistency was detected
in a data block.
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Check the file and repair it using /REPAIR-DISK-FILE, if necessary.

## DMS0A1A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A1A POOL LINKS TO SPECIFIED POOL STILL EXIST. COMMAND NOT PROCESSED

### Meaning

It is not possible to erase the specified ISAM pool because there still
exist pool links to this pool which have not been removed by means of
/REMOVE-ISAM-POOL-LINK, or the connection with the specified ISAM pool
cannot be cleared because at least one open file is still connected to
this pool.

### Response

Remove superfluous pool links by means of /REMOVE-ISAM-POOL-LINK or close
the file and reenter the command either at once or after an interval.

## DMS0A1B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A1B ISAM POOL LINK DOES NOT EXIST. COMMAND IGNORED

## DMS0A1C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A1C NK-ISAM NOT LOADED. PROCESSING OF ISAM POOL COMMANDS OR SECONDARY INDEX COMMANDS NOT POSSIBLE

### Meaning

The execution of an ISAM pool command or of a command to process
secondary indices is not possible if NK-ISAM is not loaded.

### Response

Contact the system administrator to have NK-ISAM loaded with the next
BS2000 startup.

## DMS0A1D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A1D LOCK FOR 'PUTX' OR 'PUT' CANCELLED

### Meaning

The file contained an invalid entry in a secondary index. The lock
was cancelled to enable the entry to be deleted, and was not restored
for subsequent PUT processing. The interrupted PUTX processing
must be repeated with the read operation.
An invalid entry in a secondary index can be caused by an unrecoverable
error (see messages DMS0AA1, DMS0AA4, DMS0AAC).
It is possible to enter /HELP-MSG for these messages.

### Response

Retry the task. The invalid entry has been deleted, but users
should remember that there may still be other invalid entries.

## DMS0A1E

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A1E AUTHORIZATION TO CREATE RESIDENT ISAM POOL IS MISSING

### Meaning

The command /CREATE-ISAM-POOL was not executed as the user is not
authorized to create ISAM pools with performance attribute RESIDENT=YES.

### Response

Correct the command ( create no resident ISAM pool ) and try again.

## DMS0A1F

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A1F INCONSISTENCY BETWEEN EXISTING ISAM POOL AND SPECIFIED VALUE 'RESIDENT'

### Meaning

This message occurs with CREATION-MODE=ANY if the specified ISAM pool
already exists and one of the following conditions applies:
1. The user has requested a resident ISAM pool and the existing ISAM
pool is pageable.
2. The user has requested a pageable ISAM pool and the existing ISAM
pool is resident.

### Response

Correct the command and try again.

## DMS0A10

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A10 COMMAND NOT SUPPORTED BY REMOTE SYSTEM. COMMAND NOT PROCESSED

### Meaning

The command is not available until BS2000 V9.5, but the remote BS2000
system referenced via the RFA connection belongs to an earlier version.

## DMS0A11

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A11 SPECIFIED CATALOG ID DOES NOT EXIST. COMMAND NOT PROCESSED

### Meaning

The specified catalog ID does not exist in the system, i.e. it is not
contained in the MRS catalog.

### Response

If the catalog ID specification was invalid, reenter the command with
a correct specification; otherwise have the MRS catalog extended
accordingly.

## DMS0A12

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A12 SPECIFIED CATALOG ID NOT AVAILABLE. COMMAND NOT PROCESSED

### Meaning

The specified catalog ID is known to the system but is not available.
Possible reason:
There is currently no RFA connection to the corresponding catalog of a
remote host.

### Response

Check the catalog ID; if necessary, set up the RFA connection and
retry the command.

## DMS0A13

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A13 SPECIFIED POOL NAME IS RESERVED OR SYNTACTICALLY INVALID. COMMAND NOT PROCESSED

### Meaning

The pool name specified in the POOL-NAME operand begins with '$'
(such names are reserved for use by the system); or the name does
not begin with a letter or one of the characters '#' or '@'; or
the rest of the name does not consist exclusively of letters,
digits or the characters '#', '@' and '$'.

### Response

Correct the value specified for the POOL-NAME operand and retry the
command.

## DMS0A14

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A14 SHORTAGE OF MEMORY SPACE FOR /CREATE-ISAM-POOL. COMMAND NOT PROCESSED

### Meaning

There is not enough address space to create an ISAM pool with the pool
size specified in the SIZE operand of the /CREATE-ISAM-POOL command.

### Response

Reduce the pool size and retry the command.

## DMS0A15

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A15 ISAM POOL ALREADY EXISTS. COMMAND NOT PROCESSED

### Meaning

Possible reasons:
1) The caller has already entered a /CREATE-ISAM-POOL command for the
specified ISAM pool.
2) Another user has already entered a /CREATE-ISAM-POOL command for the
ISAM pool specified through the values SCOPE=HOST-SYSTEM or
SCOPE=USER-ID and CREATION-MODE=NEW.

### Response

1) Specify another ISAM pool.
2) Enter the command again with operand CREATION-MODE=ANY.

## DMS0A16

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A16 'POOL-LINK-NAME' ALREADY ALLOCATED. COMMAND NOT PROCESSED

### Meaning

An attempt has been made to allocate a link name using the LINK-NAME
operand of the /ADD-ISAM-POOL-LINK command, but such an allocation has
already been made in a preceding /ADD-ISAM-POOL-LINK command and this
allocation is still valid.

### Response

Specify another link name or, if the existing allocation is no longer
required, cancel it using /REMOVE-ISAM-POOL-LINK and retry the command.

## DMS0A17

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A17 SYSTEM ERROR. COMMAND NOT PROCESSED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

During command processing an unexpected return code was issued when a
system function (e.g. $REQM or ENAMP) was called.

## DMS0A18

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A18 SIZE OF ISAM POOL INVALID. RETRY COMMAND WITH VALID 'SIZE' OPERAND VALUE

## DMS0A19

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A19 ISAM POOL DOES NOT EXIST. COMMAND NOT PROCESSED

### Meaning

The ISAM pool specified in the CAT-ID, POOL-NAME and SCOPE operands
does not exist.

### Response

If necessary, correct the ISAM pool specification and retry the command.

## DMS0A20

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A20 OPERAND OR OPERAND VALUE NOT SUPPORTED BY REMOTE BS2000 SYSTEM. COMMAND NOT PROCESSED

### Meaning

The operand or operand value specified in the command exists only as of
BS2000 V11.0, but RFA is connected with a remote BS2000 system with
a version less than BS2000 V11.0.

### Response

Try the command with an operand specification which corresponds to the
remote BS2000 system.

## DMS0A21

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A21 The contingent for ISAM pools is exceeded

### Meaning

During the execution of a command to process ISAM pools it was found
that the memory available to the caller is exhausted.
The command has not been processed.

### Response

Release memory, if possible, then repeat command.

## DMS0A22

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A22 No usergroup defined for command CREATE-ISAM-POOL. Command ignored.

### Meaning

On issue of the command CREATE-ISAM-POOL, the validity range
'SCOPE=USER-GROUP' was specified; however, the ID of the user
issuing the command does not belong to a user group.

### Response

Correct and retry.

## DMS0A23

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A23 FILE SIZE GREATER THAN 32 GIGABYTES IS NOT ALLOWED.

### Meaning

In FCB or ADD-FILE-LINK LARGE_FILE=*FORBIDDEN has been set,
but concerned file exceeds 32 gigabytes.

### Response

Correct program. If the error persists, contact system administrator.

## DMS0A3A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A3A NK-ISAM CONTROL BLOCK INCONSISTENT. COMMAND NOT PROCESSED

### Meaning

An inconsistency was detected in the NK-ISAM control block while
processing the command. The file is errored.

### Response

Check the file and repair it using /REPAIR-DISK-FILE, if necessary.

## DMS0A3B

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A3B RECORD TOO SMALL FOR SECONDARY KEY. COMMAND ABORTED

### Meaning

When creating a secondary key, a record was read that is too short to
accommodate the secondary key defined by KEYPOS and KEYLEN.

### Response

It must be possible to accommodate a secondary key in every record in the
file. Possible ways of ensuring this would be, for example, to extend
or delete records that are too short.

## DMS0A3C

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A3C MAXIMUM NUMBER OF SECONDARY INDICES ALREADY DEFINED. COMMAND IGNORED

### Meaning

The file already contains the maximum number (30) of secondary indices.

### Response

If necessary, a secondary index that is no longer required can be
deleted by means of /DELETE-ALTERNATE-INDEX.

## DMS0A3D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A3D FILE CONTAINS INCOMPLETE SECONDARY INDEX. COMMAND IGNORED

### Meaning

A file that contains an incomplete secondary index cannot be processed,
except in order to delete the incomplete index or to create a new,
complete one.

### Response

Either delete the incomplete secondary index or create a new, complete
one.

## DMS0A3E

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A3E ISAM POOL OVERLOADED. COMMAND IGNORED

### Meaning

The ISAM pool required to process the command is overloaded.

### Response

If necessary, try the command again later.

## DMS0A3F

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A3F SECONDARY INDEX ALREADY DEFINED WITH OTHER ATTRIBUTES. COMMAND IGNORED

### Meaning

The secondary index to be created already exists and is marked as
incomplete. However, the attributes defined for it are not the same
as those specified in the command. A secondary index with the same
name but different attributes cannot be created until the existing
one has been deleted.

### Response

Delete the secondary index or define identical attributes.

## DMS0A30

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A30 COMMAND NOT SUPPORTED BY REMOTE SYSTEM. COMMAND NOT PROCESSED

### Meaning

The command will not be introduced until BS2000 Version 10.0A, but the
remote BS2000 system accessed via the RFA connection belongs to an
earlier version.

## DMS0A31

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A31 SPECIFIED CATALOG DOES NOT EXIST. COMMAND NOT PROCESSED

### Meaning

The specified catalog is not known in the system, i.e. has not been
entered in the MRS catalog.

### Response

If the wrong catalog has been specified, retry the command with the
correct catalog specification. Otherwise request the extension of
the MRS catalog.

## DMS0A32

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A32 SPECIFIED CATALOG NOT AVAILABLE. COMMAND NOT PROCESSED

### Meaning

The specified catalog is known to the system but is not available, e.g.
because there is no RFA connection to the specified catalog on a
remote host at this time.

### Response

Check the catalog specification. If necessary, set up the RFA connection
and retry the command.

## DMS0A33

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A33 FILE CONTAINS DUPLICATE PRIMARY KEYS. COMMAND ABORTED

### Meaning

A secondary index can only be created for a file that contains no
duplicate keys.

### Response

Remove records containing duplicate keys.

## DMS0A34

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A34 SECONDARY INDEX ALREADY EXISTS. COMMAND IGNORED

### Meaning

The file already contains a secondary index with the same name as
specified under KEYNAME.

### Response

Select another name or delete the existing secondary index before
continuing processing.

## DMS0A35

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A35 SECONDARY INDEX DOES NOT EXIST. COMMAND IGNORED

### Meaning

The file contains no secondary index with the specified name.

### Response

Correct the specified name, if necessary.

## DMS0A36

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A36 FLAGS DEFINED FOR FILE. COMMAND IGNORED

### Meaning

No secondary indices are defined for files containing flags.

### Response

Make a logical copy of the file (e.g. using PERCON) without defining
flags for the target file.

## DMS0A37

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A37 SYSTEM ERROR. DMS ERROR CODE '(&00)'. COMMAND NOT PROCESSED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

During command processing an unexpected return code was issued
when calling a system function (e.g. $REQM, DISFIX).
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

### Response

Contact the system administrator.

## DMS0A38

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A38 ADDRESS SPACE TOO SMALL. COMMAND IGNORED

### Meaning

The privileged class 5 memory required to process the command is
not available.

## DMS0A39

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A39 ERROR IN 'KEYPOS' OPERAND. COMMAND IGNORED

### Meaning

A secondary index must fit into one record and must not extend into an
overflow block. The value of the KEYPOS operand, perhaps in conjunction
with the specified key length (KEYLEN), does not meet this requirement.

### Response

Correct the KEYPOS or KEYLEN value and retry the command.

## DMS0A4A

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A4A FILE HAS NO SECONDARY INDEX

### Meaning

/SHOW-INDEX-ATTRIBUTES has been issued for a file without a secondary
index.

## DMS0A4B

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

Warranty : NO

DMS0A4B DYNAMIC LOADING OF 'NK-ISAM' SUCCESSFUL

## DMS0A4C

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

Warranty : NO

DMS0A4C 'NK-ISAM' COULD NOT BE DYNAMICALLY LOADED

## DMS0A4D

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A4D FILE CONTAINS DUPLICATE SECONDARY KEYS. COMMAND ABORTED

### Meaning

The secondary index has a duplicate key, but DUPKEY=NO was
specified.

### Response

Remove records with duplicate keys.

## DMS0A4E

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A4E 'SHARUPD=YES' SPECIFIED FOR FILE

### Meaning

It is not permissible to create or delete a secondary index in SHARUPD
mode.

### Response

Modify the /SET-FILE-LINK command and try again.

## DMS0A4F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A4F RDTFT ERROR '(&00)'

### Meaning

An error has occurred while processing the link name with RDTFT. The
specified error code provides details of the error.

### Response

Take appropriate action in accordance with the error code. Check the
link name.

## DMS0A40

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A40 THE PRIMARY INDEX COUNT WAS NOT SUPPORTED FOR THIS FILE.

### Response

Switch on the PRIMARY-INDEX-COUNT with command
/REPAIR-DISK-FILES FILE-TYPE=*CLOSED(<filename 1..54>, -
INDEX-STATISTICS=*ON)

## DMS0A41

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A41 NO VALID PRIMARY-INDEX-COUNT AVAILABLE FOR THIS FILE.

### Meaning

Possible reasons:
1. Session or a task was abnormally terminated.
2. BS2000-GA with lower version than V21.0B opened
the file output or outin
3. Another system with BS2000-GA V21.0B has currently
opened the file output or outin

### Response

For case 1 or 2 reorganize the PRIMARY-INDEX-COUNT with the command
/REPAIR-DISK-FILES FILE-TYPE=*CLOSED(<filename 1..54>, -
INDEX-STATISTICS=*ON)
For case 3, use the command on the system, which has opened the file.

## DMS0A42

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A42 ERROR WHEN OPENING FILE. DMS ERROR CODE '(&00)'. COMMAND IGNORED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The attempt to open the file for command processing has been rejected.
The reason for this is given by DMS error code (&00).
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

## DMS0A43

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A43 ERROR WHEN CLOSING FILE. DMS ERROR CODE '(&00)'. COMMAND IGNORED. IM SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The attempt to close the file was rejected. The reason for this
is given by DMS error code (&00).
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

## DMS0A44

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A44 READ ERROR. DMS ERROR CODE '(&00)'. COMMAND IGNORED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

A read error has occurred when generating the secondary index. The
reason for this is given by DMS error code (&00).
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

## DMS0A45

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A45 WRITE ERROR. DMS ERROR CODE '(&00)'. COMMAND IGNORED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

A write error has occurred when generating the secondary index. The
reason for this is given by DMS error code (&00).
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

## DMS0A46

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A46 FILE IS NOT NK-ISAM FILE. COMMAND IGNORED

### Meaning

The file has not been created by NK-ISAM.

### Response

If necessary, convert the file into an NK-ISAM file.

## DMS0A47

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A47 DMS ERROR IN SORT PART OF NK-ISAM. DMS ERROR CODE '(&00)'. COMMAND ABORTED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

The sort part of ISAM has reported a DMS error. The specified DMS error
code gives details of the type of error involved.
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

## DMS0A48

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A48 INTERNAL ERROR IN SORT PART OF ISAM. ERROR CODE '(&00)'. COMMAND IGNORED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

An internal error has occurred in the sort part of ISAM.
(&00): error code for assistance in dealing with the error.

### Response

Contact the system administrator.

## DMS0A49

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS0A49 PROCESSING ABORTED BY USER

### Meaning

Processing of a command or macro has been aborted by caller due to
K2 key interrupt or due to entering /CANCEL-JOB

## DMS0A50

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A50 CAT ID SPECIFIED IN '/SHOW-ISAM-POOL-ATTRIBUTES' COMMAND DOES NOT EXIST. COMMAND REJECTED

### Meaning

The specified catalog ID is unknown in the system, i.e. not specified
in the MRS catalog.

### Response

Specify valid catalog ID in the command or ask the system administrator
to enlarge the MRS catalog by adding the required catalog ID.

## DMS0A51

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A51 ISAM POOL SPECIFIED IN '/SHOW-ISAM-POOL-ATTRIBUTES' COMMAND DOES NOT EXIST. COMMAND REJECTED

### Meaning

The ISAM pool specified by means of the operands CAT-ID, POOL-NAME and
SCOPE does not exist or cannot be found by means of the criterion
specified
in the SELECT operand.

### Response

If necessary correct the specification of the ISAM pool or the SELECT
operand and repeat the command.

## DMS0A52

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A52 SYSTEM ERROR OCCURRED DURING EXECUTION OF '/SHOW-ISAM-POOL-ATTRIBUTES' COMMAND. ERROR CODE '(&00)'. COMMAND REJECTED

### Meaning

Unexpected return code when calling a system function during
execution of the /SHOW-ISAM-POOL-ATTRIBUTES command.
Possible reasons:
(&00): 01 , error during privilege check (CHKRIV)
02 , error while determining LOGON-USERID or DEFAULT-CATID
(RDUIDI, DPSUSTA)
03 , error while determining a catalog ID location
(RFACINF, MRSCPI)
04-21, error during a request or release for class 5 memory space
for internal use.

### Response

Contact the system administrator.

## DMS0A53

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A53 INSUFFICIENT VIRTUAL MEMORY SPACE TO EXECUTE '/SHOW-ISAM-POOL-ATTRIBUTES' COMMAND. COMMAND NOT EXECUTED

### Meaning

No areas required internally could be generated.

### Response

Try again later.
If the error occurs again contact the system administrator.

## DMS0A54

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A54 PRIVILEGE FOR FUNCTION PROCESSING DOES NOT EXIST. COMMAND IGNORED

### Meaning

When entering command /SHOW-ISAM-POOL-ATTRIBUTES the operand SELECT=ALL
was specified but the caller does not have the required privilege
( TSOS or SW-MONITOR-ADMINISTRATION ).
The command has not been processed.

### Response

Enter the command again with operand SELECT=OWN.

## DMS0A55

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A55 NO ISAM POOL EXISTS

### Meaning

During execution the /SHOW-ISAM-POOL-ATTRIBUTES command with the
operand POOL-NAME=*ALL no ISAM pool could be found for the criterion
specified in the SELECT operand.

## DMS0A56

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A56 CATALOG ID SPECIFIED IN '/SHOW-ISAM-POOL-ATTRIBUTES' COMMAND NOT ACCESSIBLE. COMMAND REJECTED

### Meaning

The catalog ID specified in the command /SHOW-ISAM-POOL-ATTRIBUTES
exists in the system but is not accessible.
Possible reason:
There is no connection to the corresponding catalog on the remote
processor.

### Response

Check the catalog ID; if necessary generate the RFA connection and repeat
the command.

## DMS0A57

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A57 No usergroup defined for command SHOW-ISAM-POOL-ATTRIBUTES. Command ignored.

### Meaning

On issue of the command SHOW-ISAM-POOL-ATTRIBUTES, the validity range
'SCOPE=USER-GROUP' was specified for a ISAM pool; however, the ID of the
caller does not belong to a user group.

### Response

Correct and retry.

## DMS0A60

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A60 SPECIFIED ISAM-POOL-LINK-NAME DOES NOT EXIST. COMMAND REJECTED

### Meaning

Possible reasons:
- The ISAM-POOL-LINK-NAME specified in the /SHOW-ISAM-POOL-LINK command
does not exist.
- No corresponding ISAM pool link name exists for the specified pool name.

### Response

Correct the value for pool link name or pool name and repeat the
command.

## DMS0A61

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A61 NO ISAM POOL LINK NAME EXISTS. COMMAND REJECTED

### Meaning

No ISAM pool link name specified by the caller was found during
execution of the /SHOW-ISAM-POOL-LINK command.

## DMS0A62

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A62 SYSTEM ERROR OCCURRED WHILE EXECUTING '/SHOW-ISAM-POOL-LINK' COMMAND. ERROR CODE '(&00)'. COMMAND REJECTED

### Meaning

Unexpected return code when calling a system function during
execution of the /SHOW-ISAM-POOL-LINK command.
Possible reasons:
(&00): 01,02, error while determining the LOGON-USERID or DEFAULT-CATID
(RDUIDI, DPSUSTA)
03-11, error during a request or release for class 5 memory space
for internal use.

### Response

Contact the system administrator.

## DMS0A63

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0A63 INSUFFICIENT VIRTUAL MEMORY SPACE FOR EXECUTING '/SHOW-ISAM-POOL-LINK' COMMAND. COMMAND NOT PROCESSED

### Meaning

No areas required for internal use could be generated.

### Response

Try again later.
If the error occurs again contact the system administrator.

## DMS0A64

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A64 No usergroup defined for command SHOW-ISAM-POOL-LINK. Command ignored.

### Meaning

On issue of the command SHOW-ISAM-POOL-LINK, the validity range
'SCOPE=USER-GROUP' was specified for a ISAM pool; however, the ID
of the caller does not belong to a user group.

### Response

Correct and retry.

## DMS0A65

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A65 Required privilege is missing

### Meaning

For execution of command /SHOW-ISAM-CACHING or of command
/MODIFY-ISAM-CACHING the privilege TSOS is mandatory

### Response

None

## DMS0A66

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A66 Internal error during command execution

### Meaning

During execution of command /SHOW-ISAM-CACHING or of command
/MODIFY-ISAM-CACHING a system error has occurred. A SERSLOG entry
was created in order to facilitate error analysis

### Response

Please save SERSLOG file for error analysis

## DMS0A67

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A67 Extension or reduction of ISAM cache area is not possible

### Meaning

During execution of command /MODIFY-ISAM-CACHING for extending
or reducing the ISAM cache area the new maximum size specified
is invalid

### Response

By means of command /SHOW-ISAM-CACHING determine the current
size of the ISAM cache area and retry command specifying a modified
maximum size of ISAM cache area

## DMS0A68

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0A68 Reduction of ISAM cache area is currently not possible

### Meaning

Due to current use of the ISAM cache area reduction to a smaller
maximum size currently not possible

### Response

Retry command later

## DMS0BBA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BBA SAM HAS READ NON-PAM BLOCK

## DMS0BBB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BBB USER HAS USED INVALID RECORD LENGTH

## DMS0BBC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BBC EOT DETECTED BEFORE REACHING BLOCK LIMIT. PROGRAM TERMINATED ABNORMALLY

### Meaning

A BLOCK-LIMIT or BLIM operand has been specified but the tape is too small
to accommodate all the blocks.

### Response

Rerun the program with a BLOCK-LIMIT or BLIM value corresponding
to the tape size.

## DMS0BBD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BBD PROGRAM ERROR: INVALID ADDRESS FOR TRANSLATION TABLE

### Meaning

A user-own translation table was specified for the conversion of user
data.
An error was detected during validation of the specifications.

### Response

Correct the program.

## DMS0BBE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BBE User has specified an invalid IOAREA

### Response

Correct the program.

## DMS0BB0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB0 INVALID FCB ADDRESS. PROGRAM ABORTED

## DMS0BB1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB1 PROGRAM ERROR: END OF SAM FILE ENCOUNTERED AND 'EOFADDR' NOT DEFINED IN 'EXLST' MACRO

### Response

Correct the program and try again.

## DMS0BB2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB2 ADDITIONAL SPACE FOR USER FILE NOT AVAILABLE AND 'NOSPACE' OPERAND NOT DEFINED IN 'EXLST' MACRO. PROGRAM ABORTED

### Meaning

The allocator has rejected a request for additional memory space for the
user file.
Possible reasons:
- pubspace limit reached
- value for secondary allocation is '0'
- file has too many extents.
- file will exceed 32 gigabytes and
LARGE_FILE=*FORBIDDEN has been set.

### Response

Contact the system administrator.

## DMS0BB3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB3 PROGRAM ERROR: INCORRECT USE OF 'SETL' MACRO AND 'USERERR' NOT DEFINED IN 'EXLST' MACRO (SAM FILE)

### Meaning

Possible reasons:
1) The SETL macro with operand 'B' (position to beginning of file)
has been issued for an output file.
2) The SETL macro with operand 'R' does not contain any valid
positioning information from the retrieval address of the FCB.
The address is '0'.
3) The SETL macro with operand 'E' (position to end of file)
has been issued for an output file.

### Response

Correct the program and try again.

## DMS0BB4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB4 PROGRAM ERROR: BUFFER SPECIFICATION IN 'SETL' MACRO TOO LARGE AND 'USERERR' NOT DEFINED IN 'EXLST' MACRO

### Meaning

'SETL R' has been specified for a SAM file and the retrieval address in
the
FCB is greater than the current buffer address (OUTPUT) or the last
page (INPUT).

### Response

Correct the program and try again.

## DMS0BB5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB5 PROGRAM ERROR: RECORD DEFINED IN 'SETL' MACRO NOT PRESENT IN SPECIFIED BUFFER AND 'USERERR' NOT DEFINED IN 'EXLST' MACRO (SAM FILE)

### Response

Correct the program and try again.

## DMS0BB6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB6 PROGRAM ERROR: ACTION MACRO (GET, PUT OR PUTX) USED CLASHES WITH 'OPEN' MODE AND 'USERERR' NOT DEFINED IN 'EXLST' MACRO (SAM FILE)

### Meaning

This error can also occur if a SAM read or write call is issued
immediately after a preceding error (e.g. DMS0BB2, DMS0BB9, DMS0BD2).

### Response

Correct the program and try again.

## DMS0BB7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB7 PROGRAM ERROR: RECORD WITH INVALID LENGTH READ

### Meaning

Possible reasons:
- Inconsistent blocks were created when creating the file due to a
program error. The error was detected when reading the file.
- The file was created in NK-SAM format (BLKCTRL=DATA) in a later
BS2000 version.

### Response

Correct the program or convert the file by means of the conversion
program PAMCONV.

## DMS0BB8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB8 UNRECOVERABLE READ ERROR AND 'ERROPT' NOT DEFINED IN 'EXLST' MACRO (SAM FILE). HARDWARE ERROR POSSIBLE. CONTACT SYSTEM ADMINISTRATOR

## DMS0BB9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BB9 HALF-PAGE READ OR TO BE WRITTEN IN SAM FILE WITHOUT USING CF ID. 'USERERR' NOT DEFINED IN 'EXLST' MACRO

### Meaning

Input file : a logical block has been read without or with an incorrect
CF ID.
Output file: if NK SAM format (BLKCNTRL=DATA) the CF ID, which is at the
beginning of each logical block, is destroyed.
CF ID: coded file identification (internal file ID in the catalog).

### Response

Input file : contact the system administrator.
Output file: correct the program and try again.

## DMS0BD2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BD2 PROGRAM ERROR: 'RECFORM' AND 'RECSIZE' SPECIFICATIONS ARE INCOMPATIBLE

### Meaning

The record length '0' is illegal for fixed-length records.

### Response

Correct the program and try again.

## DMS0BD7

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0BD7 USER NOT AUTHORIZED TO ACCESS TAPE WITH VSN '(&00)' FOR FILE '(&01)' VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY)

### Meaning

The file cannot be opened or extended as the tape belongs to another
user and can therefore not be overwritten or because the file has not
been defined as shareable.

### Response

0: The program will be continued with the EXLST exit USERERR,
if defined, otherwise it will be terminated.
1: Retry the label check, using another tape if necessary.

## DMS0BFE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BFE BCAM CONNECTION ERROR

### Meaning

The user has attempted to execute a SAM action on the remote processor
identified by the catalog identifier (catalog ID field) of the file name.
Error code 00FE is returned by the RFADCSND/RFADCRCV/RFADCLGF module
due to a BCAM connection error. The specific BCAM error message
is output to the operator console.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0BFF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0BFF INVALID REQUEST FOR DEVICE DRIVER OR BCAM CONNECTION INOP OR ABOUT TO BE SEVERED

### Meaning

Possible reasons:
1. During the request for the device driver an invalid request was
reported.
2. The user has attempted to execute a SAM action on a remote processor
identified by the catalog identifier (catalog ID field) of the file
name. Error code 00FF is returned by the RFADCSND/RFADCRCV/RFADCLGF
module due to a preceding error on the same communication line.

### Response

1. Contact the system administrator.
2. Clear the connection by means of the command /REMOVE-RFA-CONNECTION and
then set it up again by means of the command /SET-RFA-CONNECTION.
If the error persists, contact the system administrator.

## DMS0B05

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B05 ALLOCATOR REPORTS TO SAM: ERROR IN CONNECTION WITH REMOTE HOSTS DURING SECONDARY ALLOCATION

### Meaning

After a secondary allocation the return code '0305' is returned to SAM.
The MRS connection is destroyed.

### Response

Contact the system administrator.

## DMS0B2C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B2C PPAM REPORTS TO SAM: INVALID EXTENT TABLE

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B2D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B2D PTAM REPORTS TO SAM: 'WAIT' AND 'CONTINGENCY' REQUESTED

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0B2E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B2E PPAM REPORTS TO SAM: DEVICE ACCESS AUTHORIZATION WITHDRAWN BY OPERATOR

## DMS0B2F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B2F PPAM REPORTS TO SAM: BOURSE ERROR

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B20

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B20 PPAM REPORTS TO SAM: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF DATA

### Meaning

Despite repeated attempts a write operation could not be performed.
The data in the magnetic tape cartridge buffer could not be written
to the cartridge in its entirety. Any data remaining in
this buffer has been lost.

## DMS0B21

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B21 PPAM REPORTS TO SAM: MEMORY SATURATION

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0B22

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B22 SAM HAS ATTEMPTED TO READ LOGICAL BLOCK WHICH IS NOT ALLOCATED TO THIS FILE

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B23

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B23 PPAM REPORTS TO SAM: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B24

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B24 PPAM REPORTS TO SAM: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B25

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B25 PPAM REPORTS TO SAM: ILLEGAL OPERATION

### Meaning

Possible reasons:
- the operation is not possible for the specified volume type on the
allocated device. E.g. no writing is possible if a device type C4 is
allocated on the specification of the volume type TAPE-C2 because no
compatible devices for writing in TAPE-C2 format are available.
- An attempt has been made to write to a shortened tape.

### Response

Case 1: select a volume type specification compatible with the device
installation.
Case 2: Use a tape with normal length.

## DMS0B26

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B26 PPAM REPORTS TO SAM: DEVICE TEMPORARILY LOCKED

### Meaning

The application is working with the function OPTION=NOWAIT (FCB operand).
The volume monitor has temporarily locked the device.

### Response

Try again.

## DMS0B27

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B27 PPAM REPORTS TO SAM: I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

### Response

Check the logical return code in the FCB.
Try again; if the problem persists, contact the system administrator.

## DMS0B28

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B28 PPAM REPORTS TO SAM: INCONSISTENCY BETWEEN DMS AND NDM TABLES

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B29

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B29 PPAM REPORTS TO SAM: INVALID SLOT ADDRESS

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B7A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B7A PTAM REPORTS TO SAM: BOURSE ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0B7B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B7B PTAM REPORTS TO SAM: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF ONE OR MORE BLOCKS

### Meaning

The data in the magnetic tape cartridge buffer has not been written
to the cartridge in its entirety. Since it was not possible to save this
buffer, this has resulted in one or more blocks being lost irretrievably.

## DMS0B7C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B7C PTAM REPORTS TO SAM: WRITE ERROR WITH BUFFERED OUTPUT

### Meaning

Despite repeated attempts a write operation could not be
performed. The data in the magnetic tape cartridge buffer has not
been written to the cartridge in its entirety. The position of the tape
is not defined.

## DMS0B71

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B71 PTAM REPORTS TO SAM: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0B72

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B72 PTAM REPORTS TO SAM: INCONSISTENCY BETWEEN DMS AND NDM TABLES

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0B73

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B73 PTAM REPORTS TO SAM: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B74

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B74 PTAM REPORTS TO SAM: SPECIFIED TAPE POSITION DOES NOT EXIST

## DMS0B75

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B75 PTAM REPORTS TO SAM: ILLEGAL OPERATION

### Meaning

Possible reasons:
- the operation is not possible for the specified volume type on the
allocated device. E.g. no writing is possible if a device type C4 is
allocated on the specification of the volume type TAPE-C2 because no
compatible devices for writing in TAPE-C2 format are available.
- An attempt has been made to write to a shortened tape.

### Response

Case 1: select a volume type specification compatible with the device
installation.
Case 2: Use a tape with normal length.

## DMS0B76

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B76 PTAM REPORTS TO SAM: DEVICE TEMPORARILY LOCKED

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0B77

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B77 PTAM REPORTS TO SAM: I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

### Response

Check the logical return code in the FCB.
Try again; if the problem persists, contact the system
administrator.

## DMS0B78

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B78 PTAM reports to SAM: Illegal PTAM call

### Response

Contact the system administrator.

## DMS0B79

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B79 PTAM REPORTS TO SAM: DEVICE ACCESS AUTHORIZATION WITHDRAWN BY OPERATOR

### Meaning

A given volume is no longer accessible. In the case of write operations
for magnetic tape cartridges, there may still be jobs in the
cartridge buffer.

## DMS0B90

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0B90 MACRO NOT ALLOWED FOR SAM NODE FILES IN PROCESSING MODE *T3

### Meaning

Possible reasons:
- An attempt was made to call a 'SETL E' or 'SETL R' macro
on a SAM node file in processing mode *T3
- An attempt was made to call a 'RELSE' macro on a SAM node
file in processing mode *T3

### Response

These macros are not supported for SAM node file in processing mode *T3

## DMS0CFE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0CFE BCAM CONNECTION ERROR

### Meaning

The user has attempted to execute a BTAM action on a remote host
identified by the catalog identifier (catalog ID field) of the file
name. Error code 00FE is returned by module RFADCSND/RFADRCV/RFADCLGF.
The appropriate BCAM error message is output at the operator console.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0CFF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0CFF INVALID REQUEST FOR DEVICE DRIVER OR BCAM CONNECTION INOP OR ABOUT TO BE SEVERED

### Meaning

Possible reasons:
1. During the request for the device driver an invalid request was
reported.
2. The user has attempted to execute a BTAM action on a remote host
identified by the catalog identifier (catalog ID field) of the
file name.
Error code '00FF' is returned by module RFADCSND/RFADCRCV/RFADCLGF
due to a preceding error on the same communication line.

### Response

1. Contact the system administrator.
2. Clear the connection by means of a /REMOVE-RFA-CONNECTION command and
then set it up again by means of a /SET-RFA-CONNECTION command.
If the error persists, contact the system administrator.

## DMS0C7A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C7A PTAM REPORTS TO BTAM: BOURSE ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0C7B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C7B PTAM REPORTS TO BTAM: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF ONE OR MORE BLOCKS

### Meaning

The data in the magnetic tape cartridge buffer has not been written
to the cartridge in its entirety. Since it was not possible to save this
buffer, this has resulted in one or more blocks being lost irretrievably.

## DMS0C7C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C7C PTAM REPORTS TO BTAM: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN SAVING OF ONE OR MORE BLOCKS

### Meaning

Despite repeated attempts a write operation could not be performed.
The data in the magnetic tape cartridge buffer has not been written
to the cartridge in its entirety. The tape is not in a defined position.
The blocks remaining in the buffer have been saved and can be
retrieved by the user.

### Response

With the aid of the RDBF instruction the user can read the contents of
the magnetic tape cartridge buffer which has not yet been written to
tape and process the corresponding data in his error recovery routine.
After the RDBF instruction, the tape position may be obtained by means of
the RBID instruction so that the tape can be repositioned before further
processing.
In this way it is possible to position the magnetic tape cartridge
behind the last correctly processed block and, if necessary,
to achieve error-free termination.

## DMS0C71

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C71 PTAM REPORTS TO BTAM: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary. May be the value of memory necessary for execution of the BTAM
order, which is the product of CHAINIO factor and blocksize is too high.

## DMS0C72

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C72 PTAM REPORTS TO BTAM: INCONSISTENCY BETWEEN DMS AND NDM TABLES

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0C73

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C73 PTAM REPORTS TO BTAM: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0C74

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C74 PTAM REPORTS TO BTAM: SPECIFIED TAPE POSITION DOES NOT EXIST

## DMS0C75

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C75 PTAM REPORTS TO BTAM: ILLEGAL OPERATION

### Meaning

Possible reasons:
- the operation is not possible for the specified volume type on the
allocated device. E.g. no writing is possible if a device type C4 is
allocated on the specification of the volume type TAPE-C2 because no
compatible devices for writing in TAPE-C2 format are available.
- An attempt has been made to write to a shortened tape.
- Some devices (e.g. tapes and MBK TAPE-C1/C2)
don't support an IO-length greater than 32K.

### Response

Case 1: select a volume type specification compatible with the device
installation.
Case 2: Use a tape with normal length.
Case 3: Check the program and the program environment

## DMS0C76

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C76 PTAM REPORTS TO BTAM: DEVICE TEMPORARILY LOCKED

### Meaning

Despite repeated attempts an I/O operation could not be performed.

### Response

Try again.

## DMS0C77

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C77 PTAM REPORTS TO BTAM: I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

### Response

Check the logical return code or the status bytes in the FCB.
Try again; if the problem persists, contact the system
administrator.

## DMS0C78

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C78 PTAM REPORTS TO BTAM: IMPERMISSIBLE PTAM CALL

### Meaning

Possible reasons:
- in MAV mode the WAIT sequence is invalid
- the chaining factor is >16.
- Wrong content of RECSIZE register.

## DMS0C79

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C79 PTAM REPORTS TO BTAM: DEVICE LOCKED AGAINST ACCESS BY OPERATOR

### Meaning

A given volume is no longer accessible. In the case of write operations
for magnetic tape cartridges, there may still be jobs in the
cartridge buffer.

## DMS0C9A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C9A PROGRAM ERROR: BTAM FILE NOT OPENED

## DMS0C9B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C9B READ ACCESS TO DUMMY BTAM FILE NOT POSSIBLE. CORRECT PROGRAM

## DMS0C9D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C9D WRITE ACCESS TO CURRENT TAPE POSITION NOT PERMITTED

## DMS0C90

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C90 PROGRAM ERROR DURING BTAM FILE PROCESSING: FCB INVALID OR MISSING

### Meaning

An action macro has been issued but it does not point to a valid FCB.

## DMS0C91

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C91 PROGRAM ERROR: WRITE ACCESS TO BTAM FILE NOT POSSIBLE IN CURRENT OPEN MODE

### Meaning

An attempt has been made to issue a BTAM action macro with an output or
RDBF operation for an input file.
If a file has been opened in INPUT or REVERSE mode, output (i.e. WRT,
WRTWT, ERG, WTM) and RDBF operations are not permitted.

## DMS0C92

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C92 PROGRAM ERROR: NO BUFFER ADDRESS SPECIFIED

### Meaning

The user has not specified a buffer address in action macro BTAM.
In addition, he/she has specified IOAREA1=NO in the FCB, which
automatically implies IOAREA2=NO.

## DMS0C93

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C93 PROGRAM ERROR: INVALID OR ILLEGAL BUFFER ADDRESS (BTAM FILE)

## DMS0C95

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C95 PROGRAM ERROR: INVALID OR ILLEGAL STATEMENT (BTAM FILE)

### Meaning

The RECSIZE register, length, request number, device type or order of
commands contains an error.

### Response

Correct the program.

## DMS0C96

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C96 PROGRAM ERROR: 'CHK' FUNCTION SET IN BTAM MACRO. NO CHECK ADDRESS GIVEN IN 'LOC' OPERAND

### Response

Specify a return address for the CHECK function in the LOC operand.
If the I/O operation is not completed correctly, control will be returned
to this address.

## DMS0C97

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0C97 PROGRAM ERROR: INVALID ADDRESS FOR TRANSLATION TABLE

### Meaning

A user-own translation table was specified for the conversion of user
data.
An error was detected during validation of the specifications.

### Response

Correct the program.

## DMS0DAA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DAA TAPE AT BOT MARKER. POSITIONING NECESSARY FOR 'OPEN=SINOUT'. CORRECT PROGRAM

### Meaning

A tape file is opened in SINOUT mode and the tape has been positioned
to the BOT marker.
Note:
Message DMS0DAA can also be an ISAM error 0AAA which
occurred during OPEN (see message DMS0AAA).

## DMS0DAB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DAB ERROR WHEN BRANCHING TO EXLST ROUTINE. ENTRY POINT ALREADY IN USE

### Meaning

The DZGOTO entry point is invalid for the current file since the register
save area is in use. EXRTN or LBRET must be specified for the exit
previously taken.

### Response

Correct the program and try again.

## DMS0DAC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DAC Invalid use of 'EXRTN' or 'LBRET' SVC.

### Meaning

The EXRTN/LBRET macro is invalid for the current file since
no user contingency exit was specified.

### Response

Correct the program and try again.

## DMS0DAD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DAD SYSTEM ERROR WHEN OPENING FILE. COMMAND NOT PROCESSED

### Meaning

A REL macro error has been detected.
Note: DMS0DAD can also be an ISAM error 0AAD which occurred during
OPEN; see DMS0AAD.

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0DAE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DAE ACCESS METHOD IN FCB INCONSISTENT WITH ACCESS METHOD IN CATALOG

### Meaning

SAM files must be cataloged as SAM files, and ISAM files must be cataloged
as ISAM files.
Note: DMS0DAE can also be an ISAM error 0AAE which
occurred during OPEN; see DMS0AAE.

### Response

Bring the entries in the FCB into line with the catalog entries.
Correct the program and try again.

## DMS0DAF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DAF Invalid open mode in FCB.

### Meaning

Specified open mode could not be identified.

### Response

Correct the program and try again.

## DMS0DA0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DA0 PROGRAM ERROR: ISAM FILE EMPTY. OPEN MODE 'INOUT' OR 'EXTEND' ILLEGAL

### Response

Correct the program and try again.

## DMS0DA1

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DA1 INVALID VSN FOR DEVICE '(&00)'. MOUNT VSN '(&01)' FOR FILE '(&02)', VSEQ '(&03)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

The VSN in the specified label does not have the expected value.
Note: DMS0DA1 can also be an ISAM error '0AA1' which occurred
during OPEN (see message DMS0AA1).
(&00): mnemonic device name
(&01): volume serial number
(&02): file name
(&03): file section number.

### Response

0: The program will be continued with the EXLST exit OPENER or
CLOSER, if defined, otherwise it will be terminated.
1: Retry the label checks with another volume.
2: Message DMS0DA4 will display the label.
I: If privilege TAPE-ACCESS=ALL, PRIVILEGED, BYPASS-LABEL or READ is
specified for the user ID , or if the user is $TSOS
or the message concerns the file owner, except in batch mode,
then label processing will be continued, regardless of the
results of the check.
Note: The response 'I' is not possible for ARCHIVE tasks.

## DMS0DA2

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DA2 NO VOL1/HDR ON DEVICE '(&00)'. MOUNT VSN '(&01)' FOR FILE '(&02)', VSEQ '(&03)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL)

### Meaning

Either the checked tape does not contain a standard label or its code
(OWN) does not match that of the file.
Note: DMS0DA2 can be also an ISAM error '0AA2' which occurred
during ISAM OPEN processing (see message DMS0AA2).
(&00): mnemonic device name.
(&01): VSN, if specified, otherwise 'SCRATCH'.
(&02): file name.
(&03): file section number.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label checks with another volume.
2: Message DMS0DA4 will be issued in order to display the label.

## DMS0DA3

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DA3 TAPE WRITE-PROTECTED: VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

An attempt has been made to overwrite a tape whose contents have been
defined as read-only or whose retention period has not yet expired.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label checks, using another tape if necessary.
2: Message DMS0DA4 will display the label.
I: If privilege TAPE-ACCESS=ALL or PRIVILEGED is specified for the
user ID, or if the user is $TSOS or the message
concerns the file owner, except in batch mode, the result of the
check will be ignored and label processing will be continued.
Note: The administrator or file owner may suppress this error in batch
mode by specifying PROTECTION-LEVEL or SECLEV=LOW.

## DMS0DA4

Destination: USER-TASK, CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DA4 LABEL: '(&00)'

### Meaning

This message is issued if '2' was entered in response to the previous
message to request display of a label and when TAPE-ACCESS=ALL or
PRIVILEGED is specified for the user ID, or if the user is $TSOS or
the message concerns the file owner.
Subsequently, the preceding message is issued again.
When opening an ISAM file, invalid values were found on the first page
of the file.
(&00): contents of the label.
Note : DMS0DA4 can also be an ISAM error '0AA4' (not enough space
for file) which occurred during OPEN (see DMS0AA4).

### Response

Check the file. If necessary, try to repair it by means of the command
/REPAIR-DISK-FILE.

## DMS0DA5

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DA5 INVALID FILE IDENTIFICATION: VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

On checking the file header labels HDR1 and HDR3 it was found that the
file name, the generation number or the file section number did not match
the expected value.
Note: DMS0DA5 can also be an ISAM error '0AA5' which occurred
during OPEN (see DMS0AA5).
(&00): VSN
(&01): file name.
(&02): file section number.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label checks, using another tape if necessary.
2: Message DMS0DA4 will display the label.
I: If privilege TAPE-ACCESS=ALL, PRIVILEGED, BYPASS-LABEL or READ is
specified for the user ID, or if the user is $TSOS or the message
concerns the file owner, except in batch mode, then label processing
will continue, regardless of any errors detected in the check.
Note: The system administrator or file owner may suppress
this error in batch mode by specifying PROTECTION-LEVEL
or SECLEV=LOW.

## DMS0DA6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DA6 SPECIFIED TAPE SEQUENCE INVALID. PROGRAM TERMINATED

### Meaning

A tape file is being opened and the list of volumes in the task file
table has been restructured by a START-POSITION or VSEQ specification,
but:
1) the file is a foreign file
and the LABEL operand is 'NO' or 'NON-STD'
2) the OPEN mode is 'OUTPUT' or 'OUTIN'
3) the START-POSITION or VSEQ specification contained a list and the
OPEN mode is 'EXTEND' or 'INOUT'.

### Response

Correct the program (FILE macro), or the /SET-FILE-LINK command where
the START-POSITION operand was specified, and try again.

## DMS0DA7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DA7 ISAM FILE INCONSISTENT. CONTACT SYSTEM ADMINISTRATOR

### Meaning

ISAM has passed return code '0AA7' to OPEN.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0DA8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DA8 REQUESTED VOLUME ALREADY BEING USED FOR ANOTHER FILE. PROGRAM TERMINATED

### Meaning

Access to a given file is not possible because the same program is already
processing another file on the same volume.

### Response

Correct the program and try again. Check which volumes are currently being
used by means of the /SHOW-FILE-LINK command.

## DMS0DA9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DA9 Volume cannot be mounted.

### Meaning

The request to mount a volume was rejected.
Possible reasons:
- As it was not possible to mount the volume, the operator answered
the preceding mount message with 'NO'.
- Access to the volume was denied by MAREN.
- Access to the volume is not allowed.
Note: DMS0DA9 can also be an ISAM error 0AA9 which
occurred during OPEN; see DMS0AA9.

### Response

Consult the operator or check the access authorization and availability
of the volumes in the MAREN catalog.

## DMS0DBA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DBA BLOCK SIZE SPECIFIED BY COMMAND OR MACRO IS DIFFERENT FROM CURRENT BLOCK SIZE OF ISAM FILE TO BE OPENED IN OPEN MODE 'INPUT'/'INOUT'/'EXTEND' OR ISAM FILE FORMAT INCONSISTENT

### Meaning

1. The value for the BLKSIZE operand specified by command or macro does
not match the catalog entry.
2. The format of the ISAM file does not match the corresponding BLKCTRL
indicator in the catalog entry. The catalog entry is BLKCTRL=PAMKEY,
but the actual file format is BLKCTRL=DATA.
3. The contents of the administrative block of an ISAM file with the
format BLKCTRL=PAMKEY have been destroyed.

### Response

Case 1: Correct the command or macro.
Case 2: Convert the file by means of the conversion program PAMCONV,
specifying the appropriate ISAM file format for the target file.
Case 3: Check the file and repair it, if necessary, by means of the
/REPAIR-DISK-FILE command.

## DMS0DBB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DBB INVALID VOLUME SEQUENCE NUMBER (VSN)

## DMS0DBC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DBC INVALID 'PAD' OPERAND. VALUE '>100' OR ILLEGAL WITH REGARD TO RELATION OF RECORD SIZE TO BUFFER LENGTH (BLKSIZE). CORRECT PROGRAM

### Meaning

The access method or the FCBTYPE is ISAM but the PAD value is not less
than 100 or the PAD value has reduced BUFFER-LENGTH or BLKSIZE so that
it is less than RECORD-SIZE or RECSIZE.

## DMS0DBE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DBE SYSTEM ERROR: ERROR IN 'OPEN' MACRO FOR ISAM FILE. COMMAND TERMINATED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The DOPEN module has detected an error in system processing.

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0DBF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DBF VSN IN LINK NAME INCONSISTENT WITH CATALOG ENTRY. RELEASE TFT ENTRY AND RETRY FILE ASSIGNMENT

### Meaning

Possible reasons:
1) The VSNs in the TFT associated with the link name in the FCB do not
match those in the catalog entry of the file that is to be opened.
2) The number of VSNs in the catalog entry is greater than the number of
VSNs in the TFT (task file table).

### Response

Enter a /REMOVE-FILE-LINK or /RELEASE command and retry the file
assignment.

## DMS0DB0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB0 Open mode in FCB is invalid for specified access method.

### Meaning

The DMS error code is 0BB0 or 0DB0; user program error. The open mode
specified in the FCB is invalid for the selected access method.

### Response

Correct the program and try again.

## DMS0DB1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB1 INVALID SPACE PARAMETER FOR SAM FILE

### Meaning

The primary allocation must be at least twice the block size. The
secondary allocation must be 0 or at least as large as the block size.

### Response

Modify the SPACE values in /MODIFY-FILE-ATTRIBUTES and start the program
again.

## DMS0DB2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB2 NOT ENOUGH SPACE FOR 'OUTPUT' OR 'EXTEND' FILE

### Response

Increase the secondary allocation or, if there
is no more public space, contact the system administrator.

## DMS0DB3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB3 LOGICAL ROUTINE FOR FCB DOES NOT EXIST

### Meaning

There is no matching logical routine for the values assigned to BLKSIZE,
RECFORM, RECSIZE, FCBTYPE, OPEN, DEVICE.

### Response

Correct the program and try again.

## DMS0DB4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB4 REVERSE INPUT FILE CANNOT BE PROCESSED

### Meaning

Either an empty file was opened with OPEN=REVERSE or the block size
(BLKSIZE) and the file size (LASTPG) are incompatible.

## DMS0DB5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB5 'BLKSIZE' NOT 'STD' FOR SAM FILE ON DISK. CORRECT PROGRAM

### Response

Correct the program and try again.

## DMS0DB6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB6 ACCESS METHOD IS ISAM BUT FILE RESIDES ON TAPE

### Meaning

ACCESS-METHOD or FCBTYPE=ISAM but the file resides on tape.

## DMS0DB7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB7 Record format in the FCB does not match the one in the catalog entry of the ISAM or SAM file.

### Meaning

Possible reasons:
1. ACCESS-METHOD or FCBTYPE=ISAM or SAM and RECORD-FORMAT or
RECFORM=U in the FCB.
2. RECORD-FORMAT or RECFORM=F and RECORD-SIZE or RECSIZE=0 in the FCB.
3. RECORD-FORMAT or RECFORM in the FCB is not the same as RECORD-FORMAT
or RECFORM in the catalog entry.
4. Value of RECSIZE in the FCB is not the same as in the catalog entry.
5. RECSIZE is longer than BLKSIZE in the FCB.

### Response

Correct the program and try again.

## DMS0DB8

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0DB8 ERROR WHEN OPENING A FILE

### Meaning

Possible reasons:
1) ISAM file : specified block size unequal to STD (standard).
2) ISAM file : block size too large for ISAM pool allocated to
the file.
3) SAM/BTAM file: block size too large.
4) BTAM file : chaining factor or request number exceeding the limit.

### Response

1) Specify the block size as STD (standard).
2) Allocate a larger ISAM pool to the file.
3) Correct the block size.
4) Correct the values.

## DMS0DB9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DB9 'RECSIZE' or 'IOREC' in the FCB contain invalid values.

### Meaning

Possible reasons:
1) The IOREG value is not between 2 and 12.
2) The VARBLD value is not between 2 and 12.
3) The RECSIZE value is not between 2 and 12 (if RECFORM=U).
4) IOREG=0 and OPEN=UPDATE.

### Response

Correct the program and try again.

## DMS0DCA

Destination: USER-TASK Routing code: Weight: 09

Warranty : NO

DMS0DCA Specified CODE operand is incompatible with either BLKSIZE or BLKCTRL parameter or the BLKSIZE parameter is higher than 32768.

### Meaning

The user has attempted to access a tape using SAM and a code other than
EBCDIC, i.e. IS07 or a user-specific code.
1) BUFFER-LENGTH or BLKSIZE=STD has been entered instead of
BUFFER-LENGTH or BLKSIZE=(absolute expression) or
2) BLKCTRL=DATA has been specified with CODE=ISO7.
Another error cause may be the user specified BLKSIZE greater than 32768
not for a file with RECFORM=V/U to be accessed with BTAM
or the user not being privileged.

### Response

Correct the program or the processing sequence and try again.

## DMS0DCB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DCB RECORD FORMAT OR RECORD LENGTH INVALID WITH REGARD TO 'CODE' OPERAND IN FCB FOR TAPE FILE. SPECIFY: RECORD FORMAT=V AND RECORD LENGTH <=9999

### Meaning

The user has attempted to access a tape using SAM and a code other than
EBCDIC, i.e. IS07 or a user-specific code, and has specified RECORD-FORMAT
or RECFORM=V. The specified RECORD-SIZE or RECSIZE was >9999 (maximum).

### Response

Correct the program or the processing sequence and try again.

## DMS0DCC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DCC RECORD FORMAT OR BLOCK SIZE INVALID WITH REGARD TO 'CODE' OPERAND IN FCB FOR TAPE FILE. SPECIFY: RECORD FORMAT=V AND BLOCK SIZE <=9999

### Meaning

The user has attempted to access a tape using SAM and a code other than
EBCDIC, i.e. IS07 or a user-specific code, and has specified RECORD-FORMAT
or RECFORM=V. The specified BUFFER-LENGTH or BLKSIZE was >9999 (maximum).

### Response

Correct the program or the processing sequence and try again.

## DMS0DCD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DCD PROGRAM ERROR: 'CODE=OWN' AND TRANSLATION TABLE ADDRESS NOT SPECIFIED IN FCB FOR TAPE FILE

### Meaning

The user has attempted to access a tape using his/her own translation
tables.

### Response

Correct the program and try again.

## DMS0DCE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DCE FILE CODE INCOMPATIBLE WITH TAPE CODE

### Meaning

A file has been opened, or continued on the tape requested, and the code
specified for this file does not correspond to the code in which the
tape is written (e.g. the tape has not been completely overwritten).

### Response

Modify the file code or use another tape, and try again.

## DMS0DCF

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DCF INVALID TAPE LABEL WITH VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

A field of a standard file label (HDR1, HDR2 or HDR3) does not
correspond to the defined format.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER, if
defined, otherwise it will be terminated.
1: Retry the label checks, using another tape if necessary.
2: Message DMS0DA4 will be issued in order to display the label.
I: If privilege TAPE-ACCESS=ALL, PRIVILEGED, BYPASS-LALEL or READ is
specified for the user ID, or if the user is $TSOS or the message
concerns the file owner, except in batch mode, then the results of
the check will be ignored and label processing will be continued.
The field remains undefined.

## DMS0DC0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC0 Key length, key position or flags in FCB invalid for ISAM file. Correct operands.

### Meaning

ACCESS-METHOD or FCBTYPE is ISAM but RECFORM-FORMAT or RECFORM
is 'F'.
The values specified for the operands KEY-POSITION or KEYPOS and
KEY-LENGTH or KEYLEN, and perhaps also for VALUE-LENGTH or VALLEN and
LOG-LENGTH or LOGLEN, are such that the current record length
(operand RECORD-SIZE or RECSIZE) is too small to accommodate
the key and perhaps the flags.

## DMS0DC1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC1 OPENING ISAM FILE PERMITTED WITH 'SHARUPD=YES/NO' BUT NOT WITH 'SHARUPD=WEAK'

## DMS0DC2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC2 EITHER VALUES FOR RECORD FORMAT AND RECORD LENGTH OR BLOCK SIZE ARE INCONSISTENT OR ATTEMPT WAS MADE TO OPEN SAM FILE IN 'SHARUPD=YES' MODE

### Meaning

In the case of fixed-length records, the value of RECORD-SIZE or RECSIZE
must not be greater than the value of BUFFER-LENGTH or BLKSIZE, and the
latter must not be zero.
With BLKCTRL=DATA the value of RECORD-SIZE+16 or RECSIZE+16 must be
smaller
than or equal to the value of BUFFER-LENGTH or BLKSIZE.
This error code will also be displayed if the operands ACCESS-METHOD or
FCBTYPE=SAM and SHARED-UPDATE or SHARUPD=YES are specified for a file at
the same time.

### Response

Make the necessary correction(s) and try again.

## DMS0DC3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC3 TOTAL VALUE OF KEY LENGTH, LENGTH OF VALUE FLAG AND LENGTH OF LOGICAL MARKING GREATER THAN 255

## DMS0DC4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC4 'BLKSIZE' or 'BLKCTRL' in catalog entry do not match specification in command or macro or value of 'BLKSIZE' is invalid.

### Meaning

Possible reasons:
- By the command or macro a specific value has been requested for
BLKSIZE and/or BLKCTRL, but this value is not the same
as the catalog entry, or
- the user tried to use UPAM to open a tape file with BLKCTRL=DATA or =NO
and a block size which is not a multiple of 2048.

## DMS0DC5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC5 SPECIFIED FCB OPERANDS (VALLEN, LOGLEN, VALPROP) NOT EQUAL TO CATALOG ENTRY OF ISAM FILE ON DISK

## DMS0DC6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC6 SPECIFIED COMBINATION OF 'BLKCTRL' AND 'BLKTYPE' NOT PERMITTED

### Meaning

Only the following combinations are permitted:
- BLKCTRL=PAMKEY and BLKTYPE=STD (=NSTD is not permitted)
- BLKCTRL=DATA/NO and BLKTYPE=NSTD (=STD is not permitted).

### Response

Correct the program or the command.

## DMS0DC7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC7 KEY LENGTH OR KEY POSITION IN FCB FOR ISAM FILE SMALLER THAN PERMITTED MINIMUM. CORRECT OPERAND

### Meaning

ACCESS-METHOD or FCBTYPE is ISAM.
The KEY-LENGTH or KEYLEN operand is <1 and/or the KEY-POSITION or
KEYPOS operand is either <1 with RECORD-FORMAT or RECFORM F, or <5 with
RECORD-FORMAT or RECFORM V.

## DMS0DC9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DC9 OPERAND 'CODE' IN FCB ONLY PERMITTED FOR TAPE FILES

### Meaning

The user has attempted to access a disk file using a code other than
EBCDIC, i.e. ISO7 or a user-specific code. This is not permitted.

### Response

Correct the program or the job sequence and try again.

## DMS0DDA

Destination: USER-TASK, CONSOLE Routing code: T Weight: 99

Warranty : NO

DMS0DDA INVALID PASSWORD FOR FILE GENERATION GROUP (FGG). PROGRAM ABORTED

### Meaning

A file generation is to be imported, but the password found
in the label is different from the password assigned to the
generation group.

### Response

Correct the program or the generation group definition
and try again.

## DMS0DDB

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DDB SPECIFIED FILE SEQUENCE NUMBER NOT FOUND ON TAPE. VSN '(&00)' FOR FILE '(&01)' VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY)

### Meaning

Possible reasons:
. The tape that has been mounted and initialized for reading is empty.
. A tape has been positioned according to the file sequence number but
the expected position has not been reached or there is no file at
this position.
. During the creation of a file with FSEQ=NEW on the tape a file was
found without trailer labels.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label checks, using another tape if necessary, after
checking the arrangement of the files on the tape and correcting the
value of the VSEQ operand in the FILE command or FILE/FCB macro, if
appropriate.

## DMS0DDC

Destination: USER-TASK, CONSOLE Routing code: T Weight: 99

Warranty : NO

DMS0DDC INVALID 'BYPASS' OPERAND. MOUNT VSN '(&00)' FOR FILE '(&01)'

### Meaning

The BYPASS operand in the /SET-FILE-LINK command is invalid.
The user is not privileged by means of TAPE-ACCESS=ALL or BYPASS-LABEL.
The program will be continued with the EXLST exit OPENER, if defined,
otherwise it will be terminated.
(&00): required volume serial number.
(&01): file name.

### Response

Modify the /SET-FILE-LINK command or change the user privilege via the
/MODIFY-USER command (system administrator) and then try /SET-FILE-LINK
again.

## DMS0DDD

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DDD UNEXPECTED TAPE MARK DETECTED FOR UNLABELED FILE. MOUNT VSN '(&00)' FOR FILE '(&01)'. REPLY (0=EXIT; 1=RETRY; C=CONTINUE)

### Meaning

An unlabeled file is to be opened on a tape which begins with a tape mark,
although this contradicts the operand specifications (operand TAPE-MARK
or TPMARK=YES not specified).

### Response

0: The program will be continued with the EXLST exit OPENER, if defined,
otherwise it will be terminated.
1: Retry the label checks, using another tape if necessary.
C: Ignore the error. The tape mark is bypassed and processing goes ahead.

## DMS0DDE

Destination: CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DDE MOUNT VSN '(&00)' ON DEVICE '(&01)' FOR FILE '(&02)' WITH WRITE-ENABLE RING '(&03)'

### Meaning

The next tape due to be processed can be mounted. The specified device
is simply a suggestion, i.e. it is not mandatory.
(&00): VSN of the tape.
(&01): mnemonic device name ('??' = use next free device).
(&02): file name.
(&03): write-enable ring option ('ON' or 'OFF').

## DMS0DDF

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DDF INVALID FILE SEQUENCE NUMBER. MOUNT VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

Error in the file sequence numbers:
FILE-SEQUENCE or FSEQ=NEW or >1 has been specified and the tape has
standard labels although LABEL=NON-STD or NO was specified.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label check, using another tape if necessary.
2: Message DMS0DA4 will display the label.
I: If privilege TAPE-ACCESS=ALL, PRIVILEGED, BYPASS-LABEL or READ is
specified for the user ID, or if the user is $TSOS or the message
concerns the file owner, except in batch mode, the results of
the check will be ignored and label processing will be continued.

## DMS0DD0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DD0 UNDEFINED FILE STATUS. FILE CANNOT BE OPENED

## DMS0DD1

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS0DD1 File not correctly closed. Continue open processing for tape file '(&00)'? Reply (0=Error exit; C=Continue)

### Meaning

The file has not been closed (the OPEN/CLOSE indicator is set in
its catalog entry).

### Response

For tape files:
0: The program continues with the EXLST exit OPENER, if defined;
otherwise it is terminated with DMS error code 0D9A.
C: Open processing continued. Since the file has not been closed
correctly, the user bears full responsibility for correct end-of-file
processing.
For disk files:
Use the /REPAIR-DISK-FILE command or the VERIF macro to repair the file.

## DMS0DD2

Destination: USER-TASK, CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DD2 INVALID OR ILLEGAL RESPONSE

### Meaning

The response to the preceding message is invalid or illegal.
The preceding message will be displayed again.

## DMS0DD3

Destination: CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DD3 FILE GENERATION NUMBER OR GENERATION GROUP ENTRY MISSING. OPEN NOT PROCESSED

### Meaning

The user has attempted to open a file generation group (FGG) for which
no generation number has been specified or for which no group entry
exists.

### Response

Enter a generation number or correct the file name and
retry the program. If there is no group entry, create one
using the /CREATE-FILE-GROUP or /CATALOG command.

## DMS0DD4

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DD4 ILLEGAL USE OF BTAM OR PAM IN OUTPUT-MODE. VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

Use of BTAM or PAM in output mode is not possible as the
DIN-REVISION-NUMBER of the standard label is greater than 1.

### Response

0: The program will be continued with the EXLST exit OPENER, if
defined, otherwise it will be terminated.
1: Retry the label check, using another tape if necessary.
2: Message DMS0DA4 will display the label.
I: If privilege TAPE-ACCESS=ALL, PRIVILEGED, BYPASS-LABEL or READ is
specified for the user ID, or if the user is $TSOS or the message
concerns the file owner, except in batch mode, the results of the
check will be ignored and label processing will continue.

## DMS0DD5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DD5 LABEL STANDARD VERSION OF FILE NOT COMPATIBLE WITH SPECIFIED RECORD FORMAT. PROGRAM ABORTED

### Meaning

One of the following situations was detected when opening a file:
1) the DIN-REVISION-NUMBER of the standard label is greater than 2 and
RECORD-FORMAT or RECFORM=V
2) the DIN-REVISION-NUMBER is greater than 1 and RECORD-FORMAT or
RECFORM=V with a BUFFER-LENGTH or BLKSIZE greater than 9999.

### Response

Correct the program and try again.

## DMS0DD6

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DD6 INVALID FILE SET IDENTIFIER ON VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; I=IGNORE)

### Meaning

The file set identifier of a file being opened or continued on the
requested tape does not match the specified value or the value from the
first file section.

### Response

0: The program will be continued with the EXLST exit OPENER, CLOSER or,
in the case of an automatic reel swap, EOFADDR, if defined,
otherwise it will be terminated.
1: Retry the label check, using another tape if necessary.
2: Message DMS0DA4 will display the label.
I: If privilege TAPE-ACCESS=ALL, PRIVILEGED, BYPASS-LABEL or READ is
specified for the user ID, or if the user is $TSOS or the message
concerns the file owner, except in batch mode, the results of the
check will be ignored and label processing will be continued.
Note: For input files this error can be suppressed in batch mode by
specifying PROTECTION-LEVEL or SECLEV=LOW.

## DMS0DD7

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DD7 ILLEGAL ACCESS BY FOREIGN USER. VSN '(&00)' FOR FILE '(&01)' VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY)

### Meaning

The file cannot be opened or extended as the tape belongs to another
user and can therefore not be overwritten or because the file has not
been defined as shareable.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label check, using another tape if necessary.

## DMS0DD8

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DD8 NO STANDARD LABELS FOUND ON VSN '(&00)' FOR FILE '(&01)' VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL)

### Meaning

No standard labels have been specified for the file in question.
It is not possible to open or extend the file if there are no labels
on it or if the tape was created with a code (OWN) other than the
one specified in the file declaration.

### Response

0: The program will be continued with the EXLST exit OPENER or CLOSER,
if is defined, otherwise it will be terminated.
1: Retry the label check, using another tape if necessary.
2: Message DMS0DA4 will be issued in order to display the label.

## DMS0DD9

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DD9 INVALID TAPE LABELS. MOUNTED VSN '(&00)' FOR FILE '(&01)' VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY)

### Meaning

During processing of a file for which LABEL=NON-STD has been specified
the user program has detected an error when checking the labels.
(&00): volume serial number.
(&01): file name.
(&02): file section number.

### Response

0: The program is continued with the EXLST exit OPENER or CLOSER,
if defined, otherwise it will be terminated.
1: Retry the label checks, using another tape if necessary.

## DMS0DEA

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DEA DATA BLOCK READ INSTEAD OF STANDARD LABEL EXPECTED FOR FILE '(&00)' ON VSN '(&01)'. REPLY (0=EXIT; C=CONTINUE)

### Meaning

On reaching the end of the tape, a data block has been encountered
instead of the expected end-of-volume or end-of-file label.

### Response

0: The program continues with the CLOSER exit, provided it has been
defined, otherwise it will be terminated.
C: The error is ignored and end-of-volume processing continued.

## DMS0DEB

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DEB DOUBLE TAPE MARK READ INSTEAD OF STANDARD LABEL EXPECTED FOR FILE '(&00)' ON VSN '(&01)'. REPLY (0=EXIT; C=CONTINUE)

### Meaning

On reaching the end of the tape, a double tape mark has been encountered
instead of the expected end-of-volume or end-of-file label.

### Response

0: The program is continued with the CLOSER exit, provided it has
been defined, otherwise it is terminated.
C: The error is ignored and end-of-volume processing continued.

## DMS0DEC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DEC BLOCK COUNT ERROR

### Meaning

When checking the block count during end-of-volume processing, a
discrepancy was detected. The operator or user program interprets this
discrepancy as an error. The program is terminated.

## DMS0DED

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DED I/O ERROR DURING RESTART ON DEVICE (&00) FOR FILE (&01). REPLY (R=RETRY; T=TERMINATE))

### Meaning

During restart on device (&00), an I/O error occurred when positioning
to file (&01).

### Response

R: retry.
T: terminate.

## DMS0DEE

Destination: CONSOLE Routing code: T Weight: 90

Warranty : NO

DMS0DEE RESTART ERROR: ON DEVICE '(&00)' VSN '(&01)' WAS EXPECTED. REPLY (R=RETRY; T=TERMINATE)

### Response

R: retry.
T: terminate.

## DMS0DEF

Destination: CONSOLE Routing code: T Weight: 90

Warranty : NO

DMS0DEF VOLUME WITH VSN '(&01)' EXPECTED ON DEVICE '(&00)'. REPLY (TSN.=VSN MOUNTED; TSN.T=TERMINATED)

### Response

TSN.: the volume has been mounted; processing continued.
TSN.T: the volume cannot be mounted as the VSN is not available;
processing
terminates.

## DMS0DE0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DE0 ILLEGAL USE OF SPECIFIED OPERAND(S)

### Meaning

The BLOCK-LIMIT (BLIM) or CHECKPOINT (CHKPT) operand has been specified
in the FCB but the file is not a SAM multivolume tape file with standard
labels.

### Response

Modify the FCB by specifying valid operands.

## DMS0DE2

Destination: USER-TASK, CONSOLE Routing code: T Weight: 99

Warranty : NO

DMS0DE2 EXPECTED 'EOF' LABELS NOT FOUND ON LAST TAPE. END OF FILE ASSUMED

### Meaning

On reaching the end of the last tape specified for a file, end-of-volume
labels have been encountered instead of the expected end-of-file labels.
It is assumed that EOF has been reached and processing continued.

## DMS0DE3

Destination: USER-TASK, CONSOLE Routing code: T Weight: 99

Warranty : NO

DMS0DE3 TAPE WITH VSN '(&00)' FOR FILE '(&01)' IS MOUNTED ON DEVICE '(&02)'

### Meaning

If the tape is unlabeled, (&00) stands for 'UNLABL'.

## DMS0DE4

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DE4 MOUNT VSN '(&00)' ON DEVICE '(&01)'. REPLY (0=VSN NOT MOUNTED; 1=VSN MOUNTED)

### Meaning

If the TFT contains the VSN, (&00) represents the next VSN in
the TFT. Otherwise it is 'SCRATCH' or '??????',
i.e. any free tape shall be mounted.

### Response

0: The operator cannot mount the volume. The program will be
continued with the EXLST-exit 'NODEV', if it has been
defined, otherwise it will be aborted.
1: The volume has been mounted on device (&01).

## DMS0DE5

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DE5 NEW VSN REQUESTED. MOUNTED VSN '(&00)' FOR FILE '(&01)' VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2'XXXXXX'=VSN)

### Meaning

If, when checking labels on output or foreign files, an error occurs
and the check is to be repeated, the user receives this message
prompting him to specify how processing is to continue. The tape
with which the label check is to be repeated can be specified.

### Response

0 : The program will be continued with the EXLST exit OPENER,
if it is defined, otherwise it will be terminated.
1 : Retry the label check.
2'XXXXXX': The user specifies the VSN 'XXXXXX'.

## DMS0DE6

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DE6 INVALID BLOCK COUNT FOR FILE (&00) ON VSN (&01). EOF/EOV BLOCK COUNT=(&02), BLOCKS READ=(&03). REPLY (0=EXIT; C=CONTINUE)

### Meaning

The block count in the EOV or EOF label clashes with the number of blocks
actually counted. The LABERR exit is not specified.
(&00): file name.
(&01): volume serial number.
(&02): block count in the EOV or EOF label.
(&03): number of blocks read.

### Response

0: The program will be continued with the EXLST exit CLOSER, if it is
defined, otherwise it will be terminated.
C: The block count value is assumed to be correct.
End-of-volume (EOV) processing continued.

## DMS0DE7

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

Warranty : NO

DMS0DE7 SAM FILE CLOSED: FILE NAME=(&00), LINK NAME=(&01), BLOCK COUNT=(&02)

### Meaning

The SAM file with file name (&00) and link name (&01) has been
closed. The block count (number of physical blocks) is (&02).

## DMS0DE8

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

Warranty : NO

DMS0DE8 END OF TAPE FOR FILE '(&00)' WITH LINK NAME '(&01)', BLOCK COUNT '(&02)' ON VOLUME WITH VSN '(&03)'

### Meaning

On reaching the end of the tape, the user is informed of the block count
for the file section that has just been completed.
End-of-volume processing continued.
(&00): file name.
(&01): link name.
(&02): block count.
(&03): volume serial number.

## DMS0DE9

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DE9 TAPE MARK READ INSTEAD OF STANDARD LABEL EXPECTED FOR FILE (&00) ON VSN (&01); REPLY (0=EXIT; C=CONTINUE)

### Meaning

During end-of-volume processing, a tape mark was read instead of the
expected EOV or EOF label.
(&00): file name.
(&01): volume serial number.

### Response

0: The program is continued with the CLOSER exit, if it has been
defined, otherwise it is terminated.
C: The error is ignored and end-of-volume processing continued.

## DMS0DFA

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DFA INVALID LABEL STANDARD VERSION USED. MOUNT VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL)

### Meaning

When opening the file, it was discovered that the label standard versions
of the tape and the file do not match.
(&00): volume serial number
(&01): file name
(&02): file section number.

### Response

0: The program continues with the EXLST exit OPENER or CLOSER, if it
has been defined, otherwise it is terminated.
1: Retry the label check, using another tape if necessary.
2: Message DMS0DA4 will be issued in order to display the label.

## DMS0DFB

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DFB ACKNOWLEDGE VSN '(&03)' ON DEVICE '(&00)' FOR FILE '(&01)', VSEQ '(&02)'. REPLY (0=EXIT; 1=RETRY; 2'XXXXXX'=NEW VSN; ETX=ACCEPT)

### Meaning

A file is to be opened or continued on a scratch tape. Once the
tape has been acknowledged, the VSN is checked to see whether
it is already among those assigned to the file.
(&00): mnemonic device name
(&01): file name
(&02): file section number
(&03): volume serial number or 'UNKNOWN'.

### Response

0: The program continues with EXLST exit OPENER or CLOSER, if
defined, otherwise it is terminated.
1: Retry the label check with another tape.
2'XXXXXX': The operator enters the VSN 'xxxxxx', which is to be used
instead of the specified VSN (&03).
: The operator accepts the already mounted tape.
Note: If the VSN is 'UNKNOWN', then ' ' is not permitted.

## DMS0DFC

Destination: USER-TASK, CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DFC SPECIFIED VSN CANNOT BE ACCEPTED

### Meaning

The volume serial number specified by the operator in response to
the previous message DMS0DFB is either illegal or already contained
in the catalog entry. Message DMS0DFB is displayed again, requesting
a different VSN. DMS0DFC will be issued also if a useless
scratch-vsn is passed over by MAREN. This can only be the case if
the appropriate MAREN-Function for tape-allocation is active.

## DMS0DFD

Destination: CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DFD 'BYPASS LABEL PROCESSING' OR 'LABEL=NON-STD/NO' AND STD LABEL TAPE ON DEVICE '(&00)'. MOUNT VSN '(&01)' FOR FILE '(&02)'

### Meaning

Either the bypassing of label processing has been specified for the
mounted tape or an attempt has been made to process a file with
standard labels using LABEL=NON-STD or LABEL=NO.
(&00): mnemonic device name
(&01): VSN
(&02): file name.

## DMS0DFE

Destination: CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DFE WRITE-PROTECTION ERROR WHEN CREATING CONTINUATION FILE

### Meaning

A second file is to be written following the first one, but overwrite
protection (OPR) has been specified and the first file is not so
securely protected as the one to be written.
Note: DMS0DFE can also be a BCAM error 0EFE, which occurred when
opening a remote file.

### Response

Correct the program or the program sequence and retry the job.
BCAM error: try again later. If the error persists, contact the system
administrator.

## DMS0DFF

Destination: CONSOLE Routing code: T Weight: 70

Warranty : NO

DMS0DFF ILLEGAL RESPONSE. USER HAS NO AUTHORIZATION FOR 'IGNORE' FUNCTION

### Meaning

In response to the previous message reporting an error during tape label
processing, the operator has entered 'tsn.', indicating that the error is
to be ignored. However, this response is rejected as the user task is
not authorized to ignore the error. The previous message is then
repeated.
Note: DMS0DFF can also be a BCAM error 0EFF, which occurred when
opening a remote file.

### Response

In the case of a BCAM error: clear the connection by means of the
/REMOVE-RFA-CONNECTION command, and then restore it by
means of a /SET-RFA-CONNECTION command.
If the error persists, contact the system administrator.

## DMS0DF0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF0 PROGRAM ERROR: 'PAMREQS' OPERAND IN FCB INVALID

### Meaning

The user has specified too many I/O operations in his FCB without
waiting for termination. The maximum number of I/O operations
for disk files is 100, for tape files 1 only.

### Response

Correct the program and try again.

## DMS0DF1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF1 NOT ENOUGH CLASS 4 OR 5 MEMORY AVAILABLE

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0DF2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF2 Internal lock could not be requested

### Response

Try again or contact the system administrator.

## DMS0DF3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF3 ILLEGAL ATTEMPT TO OPEN NON-PAM FILE FOR PAM SHARED UPDATE

### Response

Correct the program and try again.

## DMS0DF4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF4 ILLEGAL ATTEMPT TO OPEN TAPE FILE FOR PAM SHARED UPDATE

### Response

Correct the program and try again.

## DMS0DF5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF5 FILE TO BE OPENED IS NOT ACCESSIBLE

### Meaning

This message is issued by the system routine DOPEN.
1. An attempt was made to open a file residing on a remote pubset, but it
is only possible to access files residing on private volumes or local
pubsets.
2. An attempt was made to open a file and the referenced pubset and its
catalog are not available, either because the catalog ID is not in
MRSCAT or because the pubset has not yet been imported.
3. An attempt was made to open a file located on a volumeset that
currently is in the state in hold.

### Response

Correct the program and retry it or contact the system administrator.

## DMS0DF6

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DF6 INPUT TAPE WITH VSN '(&00)' HAS STD LABELS, BUT ATTEMPT WAS MADE TO PROCESS IT WITH 'NON-STD' OR 'NO'. REPLY (0=EXIT; C=CONTINUE)

### Meaning

An input tape with STD labels is to be treated as NON-STD or NO.

### Response

0: The program continues with the EXLST exit OPENER, if defined;
otherwise it is terminated.
C: Tape processing continues if privilege TAPE-ACCESS=ALL or
BYPASS-LABEL is specified for the user ID, or if the user is $TSOS or
the message concerns the file owner, except in batch mode.

## DMS0DF7

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DF7 OUTPUT TAPE WITH VSN '(&01)' ON DEVICE '(&00)' HAS STD LABELS BUT IS TO BE PROCESSED WITH 'NON-STD' OR 'NO'. REPLY (0=EXIT; ETX=ACCEPT)

### Meaning

Output tape has STD labels, but is treated as NON-STD or NO.
(&00): mnemonic device name
(&01): VSN.

### Response

0: the tape request is rejected.
: the mounted tape is overwritten.

## DMS0DF8

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS0DF8 EXPECTED VSN '(&01)' FOR FILE '(&02)', VSEQ '(&03)' NOT MOUNTED ON DEVICE '(&00)'. VSN '(&04)' FOUND INSTEAD. REPLY (0=EXIT; 1=RETRY; 2=DISPLAY LABEL; ETX=ACCEPT)

### Meaning

A volume has been mounted on device (&00) corresponding to the
file name (&02), section number (&03). Its VSN should be (&01), but
the VSN (&04) has been found.
(&00): mnemonic device name
(&01): expected volume serial number
(&02): file name
(&03): file section number
(&04): volume serial number found.

### Response

0: error exit processing
1: retry after mounting the correct tape
2: display the label of the mounted tape
: accept the new VSN and update the catalog entry.

## DMS0DF9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0DF9 OPERAND 'BLOCK-OFFSET' OR 'BUFOFF' CONTAINS ILLEGAL VALUE. PROGRAM TERMINATED

### Meaning

The BLOCK-OFFSET or BUFOFF operand has been specified and does not
match BLOCK-CONTROL-INFO=PAMKEY or DATA or the access method
is not SAM or the operand is greater than 99.
The program will be continued with the EXLST exit OPENER, if
defined, otherwise it will be aborted.

### Response

Correct the program or the command /SET-FILE-LINK and try again.

## DMS0D00

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D00 SYSTEM ERROR WHEN OPENING FILE

### Meaning

During OPEN processing, a system error occurred in a DMS component.

### Response

Contact the system administrator so that any diagnostic material that
is required can be produced.

## DMS0D01

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D01 REQUESTED CATALOG ENTRY NOT ACCESSIBLE. COMMAND IS REJECTED.

### Meaning

One of the specified path names contains the catalog ID of a catalog which
is not accessible.
The class 2 option BMTNUM=0 is set for private disks.
The file is encrypted. Processing of encrypted file is not supported
in BS2000/OSD releases older than V6.0.

### Response

Contact your system administrator to have the class2 option
changed to a value not equal to zero.

## DMS0D02

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS0D02 Requested catalog in QUIET or HOLD state. Waiting time is over. Command not processed

### Meaning

The catalog containing the file to be opened is currently not accessible.

## DMS0D05

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

Warranty : NO

DMS0D05 ERROR IN CONNECTION WITH REMOTE HOST

### Meaning

An error has occurred in the MSCF communication facility when accessing
a non-local system. The remote system is currently not available or a
Net-Storage volume is not accessible on the master system.

### Response

Request the system administrator to check the connection with the remote
host. At the best it will only be a temporary fault and a repeated
attempt to execute the job will be successful.

## DMS0D06

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D06 ATTEMPT TO OPEN TAPE FILE REJECTED BY 'MAREN' SUBSYSTEM

### Meaning

Possible reasons:
- Missing or invalid volume password.
- The volume belongs to a foreign user ID and is not shareable.
- The volume belongs to a foreign user ID and is only shareable for
read-access, but the user wants to write to it.
- The volume has been lent out.
- Data is to be written to the volume but the file expiration date has not
yet been reached.
- The volume has an invalid status in its archive entry (e.g. 'defective'
or 'free').
- The volume is reserved for ARCHIVE applications, but this is not an
ARCHIVE subtask.
- The volume is currently locked by another task on the same host.
- The volume is still locked by another task on another host.
- The VSN has not been saved in the MAREN catalog.
- The volume is not locally available.
- The request was rejected by the MAREN administrator by means of
a MAREN-specific computer center exit.

## DMS0D07

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D07 FILE CANNOT BE OPENED OWING TO MASTER CHANGE. TRY AGAIN

### Meaning

The catalog entry for the file cannot be written to TSOSCAT, because
a master change is still in progress.

## DMS0D08

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D08 Catalog index destroyed

### Meaning

The specified catalog cannot be accessed because the catalog index
was destroyed by a system error. A reconstruction will be carried out
at the next import of the pubset at the latest.

### Response

Repeat the job. Inform the system administrator if the problem persists.

## DMS0D09

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D09 LBP_REQUIRED IN THE FCB IS NOT ALLOWED FOR THE SPECIFIED FILE

### Meaning

Possible reasons:
The last byte pointer for a PAM file was requested on OPEN
with LBP_REQUIRED. That is not allowed for
- files on private disk or tape
- encrypted files
- OPEN with SHARUPD=YES

## DMS0D1A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D1A Wrong values for a NODE-FILE in P1FCB or TFT

### Meaning

- The value of FCBTYPE can only be PAM or SAM.
- On each OPEN with FCBTYPE=SAM, SAM_NODE_FILE_ENABLE must
be set in P1FCB.
- On a write UPAM access to SAM files, SAM_NODE_FILE_ENABLE
must be set in P1FCB.
- For SAM files only BLKCTRL=DATA and RECSIZE=V allowed.
- For PAM files only BLKCTRL=NO allowed.
- DIV and FASTPAM are not allowed.

### Response

Correct values in P1FCB or TFT.

## DMS0D1B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D1B NET CLIENT REPORTS PERMISSION DENIED TO FILE ON NET-STORAGE.

### Meaning

Possible reason:
- POSIX user number and/or POSIX group number for specified userID
on the specified pubset do not match UID and/or GID for the
corresponding userID on the net server.

### Response

Call system administrator.

## DMS0D1C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D1C Specified value for PROCESSING_MODE in the P1FCB wrong or not supported

### Meaning

- The specified PROCESSING_MODE in the P1FCB is wrong or
not supported in the current BS2000 version.

### Response

Correct value in P1FCB.

## DMS0D1D

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D1D ONETSTOR reports invalid NET-CODED-CHAR-SET or CODED-CHARACTER-SET of a SAM node file

### Meaning

- On open of a SAM node file the subsystem ONETSTOR could not
find any conversion table for the NET-CODED-CHAR-SET
or the CODED-CHARACTER-SET of the specified file.

### Response

Correct the properties NET-CODED-CHAR-SET or CODED-CHARACTER-SET
respectively, of the file.

## DMS0D1E

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D1E ONETSTOR reports NET-CODED-CHAR-SET and CODED-CHARACTER-SET incompatible

### Meaning

- On open of a SAM node file the subsystem ONETSTOR has detected
that the file attributes NET-CODED-CHAR-SET and
CODED-CHARACTER-SET are incompatible.

### Response

Correct the attributes NET-CODED-CHAR-SET and CODED-CHARACTER-SET
respectively, of the file.

## DMS0D1F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D1F DATA IN CACHE BUFFER

### Meaning

cache buffer still contains data for this file which cannot be
accessed. Cache Manager is not available or cached data
are in the cache buffer of another host or the data are inconsistent
due to a previous system crash.

### Response

- In the case of data inconsistency delete the file
- The file can be accessed without restrictions by issuing the command
/REMOVE-FILE-ALLOCATION-LOCKS....,OPEN-ALLOWED=*YES. This should be
done only when there are no data belonging the file in the cache buffer
or if you can guarantee that the cache buffer is not rewritten while
the file is accessed. The privilege TSOS is required for this action.

## DMS0D10

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D10 System administrator has restricted the use of OPEN macro.

### Meaning

The activated system exit routine has rejected the OPEN.
The program is continued with the EXLST exit OPENER, if defined,
otherwise it is aborted.
Note: 'DMS0D10' can also be a CMS-error '0310'.

### Response

Ask the system administrator why the command or macro was rejected.

## DMS0D11

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D11 FCB ADDRESS NOT ALIGNED ON WORD BOUNDARY

## DMS0D12

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D12 ERROR CODE '(&00)' DURING CHECKPOINT PROCESSING. ABNORMAL PROGRAM TERMINATION

### Meaning

An error with error code (&00) has occurred during processing of a
checkpoint written automatically by the system at the end of the tape
when the BLIM or CHKPT operand is used.

## DMS0D13

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D13 PRIVATE DISK POOL INCONSISTENCY DETECTED DURING OPEN PROCESSING. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The pool information on the system volume label (SVL) of a private disk
clashes with the catalog entry.

### Response

The system administrator must check all the private disks in the pool
with the aid of the PDPOOLS utility routine.

## DMS0D14

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D14 File is to be processed using encryption and OpenCrypt is inoperable.

### Meaning

When OpenCrypt is inoperable, Processing of files using encryption is
aborted.

### Response

Action
- Contact your system administrator

## DMS0D15

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

Warranty : NO

DMS0D15 Calling base mechanism of system exit '(&00)' results in error code '(&01)'

### Meaning

(&00): exit number.
(&01): error code of $SYSX interface.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0D17

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D17 'OPEN VOLUME' FUNCTION ILLEGAL

### Meaning

Possible reason:
the user ID is not $TSOS.

## DMS0D18

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D18 INVALID OPERAND IN 'OPEN VOLUME' FUNCTION

### Meaning

Possible reasons:
- no /SET-FILE-LINK command or FILE macro specified
- file name not *DUMMY
- DEVICE not disk
- more than one VSN in /SET-FILE-LINK command or FILE macro.

## DMS0D19

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D19 Error at the OPEN of the file on the Net-Storage volume

### Meaning

An error occurred during the call of the
OPEN function of ONETSTOR.
Possible reasons:
Access to Net-Storage denied
File on Net-Storage is in use
File on Net-Storage does not exist

### Response

For further diagnosis contact system administrator

## DMS0D2C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D2C PPAM REPORTS TO OPEN: INVALID EXTENT TABLE

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D2D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D2D PTAM REPORTS TO OPEN: 'WAIT' AND 'CONTINGENCY' REQUESTED

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D2E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D2E PPAM REPORTS TO OPEN: DEVICE ACCESS AUTHORIZATION WITHDRAWN BY OPERATOR

## DMS0D2F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D2F PPAM REPORTS TO OPEN: BOURSE ERROR

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D20

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D20 PPAM REPORTS TO OPEN: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF DATA

### Meaning

Some of the data in the buffer has been lost.

## DMS0D21

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D21 PPAM REPORTS TO OPEN: MEMORY SATURATION

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D22

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D22 PPAM REPORTS TO OPEN: REQUESTED LOGICAL HALF-PAGE NOT CONTAINED IN FILE

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D23

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D23 PPAM REPORTS TO OPEN: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D24

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D24 PPAM REPORTS TO OPEN: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0D25

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D25 An internal error occurred while the file was being opened.

### Meaning

-

### Response

Contact your system engineer.

## DMS0D26

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D26 PTAM REPORTS TO OPEN: DEVICE LOCKED FOR A SHORT TIME

### Meaning

The application uses the function OPTION=NOWAIT (FCB operand).
The volume monitor has locked the device for a short time.

### Response

Try again; if the problem persists, contact the system administrator.

## DMS0D27

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D27 'PPAM' reports to 'OPEN': I/O operation terminated due to hardware error.

### Response

Try again; if the problem persists, contact the system administrator.

## DMS0D28

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D28 PPAM REPORTS TO OPEN: INCONSISTENCY BETWEEN DMS AND NDM TABLES

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D29

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D29 PPAM REPORTS TO OPEN: INVALID SLOT ADDRESS

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D3A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D3A SYSTEM ERROR OR ERROR WHEN UPDATING FORMAT 1 LABEL

### Meaning

Possible reasons:
1) The private volume contains too many files.
2) The file cannot be located on the private volume.
3) One of the following system errors has occurred:
a) $WTCT was requested for a file on a private volume
and a PAM I/O error occurred.
b) There is no space on the F1 label.
c) An F1 label entry cannot be found.
d) The inode of a node file on Net-Storage could not be read.

### Response

Try to reorganize the volume. If the problem persists,
contact the system administrator.

## DMS0D3B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D3B SYSTEM ERROR WHEN OPENING FILE

### Meaning

The UPDATE-TSOSCAT or CLEAR-TSOSCAT function or the F1 label function
returned internal error code '033B'.
Possible reasons:
- On a pubset which is not locally allocatable a catalog entry for a
normal pubset file (non-shared PVS) was to be deleted or modified.
- A catalog entry is to be written back with obsolete contents.
- A catalog entry was read that is not supported in this BS2000 version.
- A catalog function from slave not supported.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0D3D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D3D TSOSCAT OR F1 LABEL BLOCK DESTROYED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

If this error occurs in connection with a system error, the length of
a catalog or F1 entry is 0.
If '033D' is returned internally to the caller, this means that the
F1 entry cannot be found or that one or more duplicate entries exist.

### Response

Contact the system administrator and request diagnostic
material, if necessary.

## DMS0D31

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D31 FILE NAME INVALID OR ILLEGAL

### Meaning

The user file name violates BS2000 conventions.
Possible reasons:
1) $USERID invalid, or the user is not authorized to access the
specified pubset.
2) The requested function does not permit partially qualified file names.
Message DMS0331 lists other possible error causes.

### Response

Correct the program and try again.

## DMS0D32

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D32 FILE LOCKED

### Meaning

The file is locked by another task (for instance by a pending
print request).

### Response

Try again later.

## DMS0D33

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D33 Specified file not cataloged.

### Meaning

The requested file has not been cataloged in the system.
For the file no catalog entry could be found.

### Response

Correct the error and try again.

## DMS0D34

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D34 Internal error in the Catalog Management System

### Meaning

An internal error has occurred in the Catalog Management System.
A SERSLOG entry or a system dump has been generated to
facilitate diagnosis.

### Response

Contact the system administrator.

## DMS0D35

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

Warranty : NO

DMS0D35 THE CATALOG ENTRY OF THE SPECIFIED FILE IS NOT ACCESSIBLE AS FILE PROTECTION IS ACTIVE. OPEN REJECTED

### Meaning

The user tried to open a catalog entry of a file which he/she is not
authorized to access owing to its protection attributes.
One of the following protection mechanisms can be active:
- standard file protection
- simple access control (Basic ACL)
- profile protection (GUARDS).

### Response

Contact the owner to change the access right if necessary.

## DMS0D36

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D36 SYSTEM ERROR WHEN OPENING FILE. IN SYSTEM MODE: /HELP-MSG DMS0336

### Meaning

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

### Response

Contact the system administrator.

## DMS0D37

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D37 SYSTEM ERROR WHEN OPENING FILE. IN SYSTEM MODE: /HELP-MSG DMS0337

### Meaning

$FRCT was requested for a catalog block which was
not locked by the requesting task.
For more detailed information about the DMS error code enter
/HELP-MSG DMS0337 in system mode or see the BS2000 manual 'System
Messages'
or one of the BS2000 DMS manuals.

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0D40

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D40 Net client reports SAM node file is too big

### Meaning

On open of a SAM node file the net client has detected,
that the file size on the Net-Storage is too big.

## DMS0D41

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D41 A record of the SAM Node file to be opened is too long

### Meaning

When opening a SAM node file, it was detected that the
length of a record of the file exeeds the block limit.

## DMS0D42

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D42 Timeout on OPEN of a file on Net-Storage.

### Meaning

Possible reasons:
A SAM node file could not be read completely in the given time.

## DMS0D43

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D43 REQUESTED FUNCTION NOT SUPPORTED BY NET CLIENT

### Meaning

Possible reasons:
- The currently installed net client supports generally no node files
or particular SAM node files are not supported.

### Response

Ask system administrator for installation of latest net client.

## DMS0D44

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0D44 OPEN MODE INVALID FOR SAM NODE FILES IN PROCESSING MODE *T3

### Meaning

Possible reasons:
- An attempt was made to open a SAM node file in processing mode *T3
with 'open reverse'
- An attempt was made to open a SAM node file in processing mode *T3
with 'open update'

### Response

These OPEN modes are not supported by SAM node file in processing mode *T3

## DMS0D45

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D45 ERROR WHEN OPENING PAM NODE FILE. NO VALID VALUE FOR 'BLKSIZE' IN THE CE

### Meaning

When opening a PAM node file, no valid value for 'BLKSIZE'
is specified in the catalog entry.

### Response

Import PAM node file again with the /IMPORT-NODE-FILE ...,REPLACE=*YES
command.

## DMS0D7A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D7A PTAM REPORTS TO OPEN: BOURSE ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D7B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D7B PTAM REPORTS TO OPEN: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF ONE OR MORE BLOCKS

### Meaning

The data in the magnetic tape cartridge buffer has not been written
to the cartridge in its entirety. Since it was not possible to save this
buffer, this has resulted in one or more blocks being lost irretrievably.

## DMS0D7C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D7C FILE MIGRATED BY HSMS. PROCESSING WITH HSMS NOT POSSIBLE AT THIS TIME

### Meaning

Possible reasons:
- Illegal access from HSMS task to a file migrated (e.g. multi migration).
- File does not exist in the migration archive.
- Look for other reasons into the HSMS report, which will be displayed
to the printer in this case.
HSMS: hierarchical storage management system.

### Response

By means of the explicit HSMS RECALL statement the restore of the data
can be initiated and a statement report will be produced.

## DMS0D7D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D7D FILE HAS BEEN MIGRATED ('MIGRATE' OPERAND) AND CANNOT BE RECALLED WITHOUT DELAY

### Meaning

The volume containing the data to be recalled is not available online
at present. Either no waiting time has been specified, or the one
specified cannot be adhered to.
HSMS: hierarchical storage management system.

### Response

Call the HSMS subsystem and initiate the asynchronous recall.
Once the recall operation has been completed, retry the task.

## DMS0D7E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D7E FILE HAS BEEN MIGRATED ('MIGRATE' OPERAND) AND 'HSMS' NOT AVAILABLE. TASK ABORTED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The task cannot be processed without the HSMS subsystem, but it is
currently not available.
HSMS: hierarchical storage management system.

## DMS0D7F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D7F SYSTEM ERROR WHEN OPENING FILE. CONTACT SYSTEM ADMINISTRATOR

### Meaning

During OPEN processing an error occurred while calling a BASIS function.

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D71

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D71 PTAM REPORTS TO OPEN: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D72

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D72 PTAM REPORTS TO OPEN: INCONSISTENCY BETWEEN DMS AND NDM TABLES

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D73

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D73 PTAM REPORTS TO OPEN: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D74

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D74 PTAM REPORTS TO OPEN: SPECIFIED TAPE POSITION DOES NOT EXIST

## DMS0D75

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D75 PTAM REPORTS TO OPEN: ILLEGAL OPERATION

### Meaning

Possible reasons:
- the operation is not possible for the specified volume type on the
allocated device. The allocated device type may differ from the
from the specified one - e.g. because no devices of the
specified type are available.
- An attempt has been made to write to a tape with a reduced length.
- the operation is not possible for the used volume on the
allocated device.

### Response

Case 1: select a volume type specification compatible with the installed
device.
Case 2: Use a tape with standard length.
Case 3: Use a volume with matching type

## DMS0D76

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D76 PTAM REPORTS TO OPEN: DEVICE TEMPORARILY LOCKED

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0D77

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D77 PTAM REPORTS TO OPEN: I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

### Response

Try again; if the problem persists, contact the system administrator.

## DMS0D79

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D79 PTAM REPORTS TO OPEN: DEVICE ACCESS AUTHORIZATION WITHDRAWN BY OPERATOR

## DMS0D8A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D8A DIV REPORTS ERROR WHEN OPENING A FILE

### Meaning

This is an internal system message.
A DIV-specific error code will be displayed on the user level.

## DMS0D8B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D8B FASTPAM REPORTS ERROR WHEN OPENING A FILE

### Meaning

This is an internal system message.
A FASTPAM error code will be displayed on the user level.
Exception: If DSSM reports an error during the FASTPAM call, the program
will be aborted with this error message.

### Response

If the program is terminated with this message, contact the system
diagnostics staff.

## DMS0D8C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D8C ERROR WHEN OPENING A DIV OR FASTPAM FILE

### Meaning

The file to be opened is a remote file.
An OPEN for a remote file is not possible with the DIV or FASTPAM access
method.

## DMS0D8D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D8D An encrypted file is to be opened for a transfer application using one of the access methods SAM or ISAM.

### Meaning

For an encrypted file to be accessed at the record level encryption and/or
decryption of its blocks is mandatory.

### Response

Correct your programme.

## DMS0D8E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D8E FILE IS COMPRESSED

### Meaning

Compressed files can be opened only by BS2000/OSD V8 or later versions.

## DMS0D80

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D80 Allocated disk space does not match with the requested file format.

### Meaning

Possible reasons:
1) The physical and logical attributes of the allocated disk in the
SM pubset conflict with the requested file attributes.
A reallocation of the file during OPEN is not possible for one
of the following reasons:
- there is no appropriate volumeset in the SM pubset
- the file is marked with S0 migration inhibited.
2) File attribute 'BLKCTRL' or 'BLKSIZE' not compatible with
referenced disk volume (SF pubset or private disk).
- BLKSIZE=(STD,n) with 'n' odd is incompatible with
disk format NK4,
- BLKCTRL=PAMKEY is not compatible with disk format NK2 and NK4.
3) Specification of BLKCTRL is not compatible with specification
of BLKSIZE; e.g. BLKCTRL=DATA4K and BLKSIZE=(STD,1).

### Response

Choose appropriate file attributes or remove the S0 migration lock.

## DMS0D81

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D81 NK-ISAM NOT LOADED

### Meaning

OPEN on a NK-ISAM file is only possible if NK-ISAM is loaded.

### Response

Contact the system administrator and request him/her to load NK-ISAM
on BS2000 startup.

## DMS0D82

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D82 FILE CANNOT BE ASSIGNED TO ISAM POOL. CORRECT COMMAND

### Meaning

For the ISAM pool referenced during OPEN processing contradictory
specifications have been detected in preceding commands.
Possible reasons:
1) The specified pool link does not exist.
2) The file is already being processed in a pool other than the specified
one.
3) The processing characteristics of the file and the ISAM pool are
incompatible, e.g. SHARUPD=YES or SCOPE=TASK.

### Response

Correct the specifications in the /SET-FILE-LINK or the /CREATE-ISAM-POOL
or the /ADD-ISAM-POOL-LINK command or define POOL-LINK correctly.

## DMS0D83

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D83 FILE HAS CONTROL BLOCK THAT CANNOT BE PROCESSED

### Meaning

The NK-ISAM control block in the file either has a version that cannot
be processed by the loaded NK-ISAM or is inconsistent.

### Response

Try to repair the file using /REPAIR-DISK-FILES.

## DMS0D84

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D84 FILE CONTAINS INCOMPLETE SECONDARY INDEX

### Meaning

The file could not be opened because one of the secondary indices
has been marked as incomplete.

### Response

Identify the incomplete secondary index with the aid of the
/SHOW-INDEX-ATTRIBUTES command or the SHOWAIX macro. Then either
create an alternate index using the /CREATE-ALTERNATE-INDEX command
or the CREAIX macro, or delete it using the /DELETE-ALTERNATE-INDEX
command or the DELAIX macro.

## DMS0D85

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D85 FILE CONTAINS CONTROL BLOCK WITH INVALID TIME STAMP

### Meaning

The global time of day stored in the NK-ISAM control block when the file
was last closed is greater than the current global time.

### Response

Try to process the file at a later point in time or restore the file by
means of the command /REPAIR-DISK-FILES.

## DMS0D86

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D86 FILE WITH SECONDARY INDEX CANNOT BE PROCESSED WITH 24-BIT FCB

### Meaning

A file with a secondary index can only be processed with a 31-bit
file control block.

### Response

Modify the program accordingly.

## DMS0D87

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D87 MULTIPLE PRIMARY KEYS NOT PERMITTED FOR FILE

### Meaning

A file with a secondary index must not be processed with the specification
DUPKEY=YES. This specification is also prohibited for the commands
/CREATE-ALTERNATE-INDEX and /DELETE-ALTERNATE-INDEX.

### Response

Specify DUPKEY=NO.

## DMS0D88

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D88 Error during device processing

### Meaning

A call for a state modification during device processing could
not be terminated successfully.

### Response

Try again (with another device, if necessary).
If the error persists, contact the system administrator.

## DMS0D89

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0D89 ISAM pool designated for processing NKISAM file to be opened is overloaded.

### Meaning

Trying to open a NKISAM file, the ISAM pool designated for processing
the file is found to contain no more resources.
Open for specified NKISAM file has been refused.

### Response

Increase size of ISAM pool or assign greater ISAM pool, try
again to open specified NKISAM file.

## DMS0D9A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D9A FILE TO BE OPENED NEITHER 'OUTPUT' NOR 'OUTIN' AND FILE DOES NOT EXIST. CORRECT PROGRAM

### Meaning

A file is not considered by the operating system to exist until it has
been opened and closed.
Open mode: TYPE=INPUT, REVERSE, INOUT, UPDATE, EXTEND or SINOUT and the
file has not been previously opened and closed in output mode.

### Response

Correct the program and try again.

## DMS0D9B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D9B Lack of system memory or system error

### Meaning

A system component called during open processing cannot
perform a memory request properly, or a system component provides an
unexpected return code.
Possible reasons:
- class 4 memory or class 5 memory saturation
- call of task lock manager provides unexpected return code

### Response

In the case of class 5 memory saturation, extend the address space or
reduce the memory pools.
In all other cases contact the system administrator in order
to obtain diagnostic material, if necessary or to interpret
serslog entry with record identification DIS2901 resp. DIS6201.

## DMS0D9C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D9C OPERAND 'TVSN' OR 'VSEQ' ILLEGAL FOR SPECIFIED FILE

### Meaning

A tape file is to be opened and the list of tapes in the task file table
(TFT) has been modified by a VOLUME-LIST/TVSN or a START-POSITION/VSEQ
specification. However, the file to be opened is no tape input file.
The program will be continued with the EXLST exit OPENER, if it is
defined, otherwise it will be terminated.

### Response

Correct the program, or the /SET-FILE-LINK command containing
the VOLUME-LIST/TVSN or START-POSITION/VSEQ operand, and try again.

## DMS0D9D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D9D ERROR WHEN OPENING DISK FILE. NO MEMORY SPACE ALLOCATED

### Meaning

Possible reasons:
- In the catalog entry no Volume- or SPACE specification is defined
(primary allocation).
- In the catalog entry for the file to be opened the value of the
secondary allocation is smaller than the block size.
- The file is larger than 32 GB. Opening with LARGE-FILE=FORBIDDEN
(Default) is not allowed.

### Response

Allocate the memory space by means of the command /MODIFY-FILE-ATTRIBUTES
or for a file larger than 32 GB set LARGE-FILE=ALLOWED in the FCB
or set EXCEED-32GB=ALLOWED in /ADD-FILE-LINK after having made sure
that the programme in question is able to process files >= 32 GB.

## DMS0D9E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D9E ERROR WHEN OPENING FILE. SPECIFY CORRECT DEVICE TYPE IN /ADD-FILE-LINK COMMAND

### Meaning

An /ADD-FILE-LINK command or FILE macro was issued without a DEVICE
operand or with an invalid DEVICE operand, thus making it impossible
for the system to open the file.
The program continues with the EXLST exit OPENER, if defined;
otherwise it is aborted.

### Response

Extend the /ADD-FILE-LINK command or FILE macro to include the
correct device type, then try again.
When using a magnetic tape cartridge, a continuation file must have the
same device type specification as the first file on the volume.

## DMS0D9F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D9F FCB memory address is invalid or another file was already opened with the same FCB address.

### Meaning

Possible reasons:
- the FCB memory address has not been allocated or
- the contents of FCB are invalid or
- another file has already been opened with
the same FCB address or the same LINK name.

### Response

Ensure that a valid FCB was specified and that its contents
are correct.

## DMS0D90

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D90 Error when opening file. Specified link name already used for another opened file. Correct program

### Meaning

The user has attempted to open a file with a link name
identical to one used for an already opened file.
Possible reasons:
1) The FCB defined in the OPEN macro is already associated with an
opened file.
2) The TFT with the same link name as in the FCB is currently associated
with an already opened file.
The program will be continued with the EXLST exit OPENER, if defined;
otherwise it will be aborted.

### Response

Correct the link name in the FCB macro or the FCB specification in the
OPEN macro, and try again.

## DMS0D91

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D91 File to be opened is protected by a password or by encryption.

### Meaning

Either an invalid password or encryption password was specified
for a protected file or no password or encryption password was
specified.

### Response

Enter the correct password or crypto password with the command
/ADD-PASSWORD or /ADD-CRYPTO-PASSWORD as applicable.

## DMS0D92

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D92 Open mode other than 'INPUT' or 'REVERSE' and expiration date has not been reached.

### Meaning

File can only be opened in read mode.

### Response

Check whether it is possible to overwrite the file; if so, update
the retention period in the catalog.

## DMS0D93

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D93 Private volume could not be mounted.

### Meaning

- The first private volume of a random access file has not been mounted
(it is necessary to read the F1 label) or
- the operator could not mount the requested tape.

### Response

Mount the private volume and try again.

## DMS0D94

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D94 Specified operands can only be used for new files.

### Meaning

A tape file is to be opened and the TSET option or FILE-SEQUENCE/FSEQ=NEW
has been specified, but:
1) the OPEN mode is not 'OUTPUT' or 'OUTIN', or
2) the file has already been created.
The program will be continued with the EXLST exit OPENER, if defined;
otherwise it will be aborted.

### Response

Correct the program and try again.

## DMS0D95

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D95 I/O area addresses invalid or not compatible with the values in the FCB.

### Meaning

One of the following I/O address errors has been detected:
1) IOAREA1=NO, IOAREA2=NO and FCBTYPE is SAM or ISAM.
2) IOAREA1=NO and IOAREA2 is not equal to NO.
3) BUFFER-LENGTH or BLKSIZE NSTD and >4096.
4) BUFFER-LENGTH or BLKSIZE <=4096 and IOAREA is not aligned on a word
boundary or crosses a page boundary.
5) BUFFER-LENGTH or BLKSIZE >4096 and IOAREA does not start on a
page boundary or crosses a segment boundary.
6) IOAREA1 specified and IOAREA2=NO entered for access method ISAM.
7) IOAREA1 specified by the user and OPEN processing requires IOAREA2.
8) OPEN processing requires IOAREAS and
BUFFER-LENGTH or BLKSIZE=O.
9) OPEN processing requires IOAREA1 and IOAREA2 was specified by
the user.
10) BUFFER-LENGTH or BLKSIZE > 32768 with IO-areas to be provided
by OPEN processing.

### Response

Correct the program and try again.

## DMS0D96

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D96 'FOREIGN' tape file must not be opened as 'OUTPUT' or 'OUTIN'.

### Response

Correct the program and try again.

## DMS0D97

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D97 Requested volume could not be mounted

### Meaning

Possible reasons:
- An attempt was made to open a file stored on a private volume or
on a Net-Storage volume, although this volume is already reserved
for another task or the corresponding request to mount the volume
was rejected from the operator.
- Allocation of Net-Storage volume failed.

### Response

Contact the system administrator.

## DMS0D98

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D98 ERROR WHEN OPENING TAPE FILE. 'TYPE=SINOUT' INVALID FOR CURRENT OPEN

### Meaning

Possible reasons:
1) The specified OPEN type is SINOUT and the file is not a tape file.
2) ACCESS-METHOD or FCBTYPE is not BTAM.
3) The file is a foreign file.
The program will be continued with the EXLST exit OPENER, if defined;
otherwise it will be aborted.

### Response

Correct the OPEN operand in the /SET-FILE-LINK command or FILE macro or
FCB macro, or the OPEN mode in the OPEN macro, and try again.

## DMS0D99

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0D99 File write protected or already in use

### Meaning

Possible reasons:
1) Attempt to open a locked file.
2) Attempt to open a read-only file in a mode other than INPUT or REVERSE.
3) Attempt to open an ISAM or PAM file in SHARED UPDATE mode when it
has already been opened as non-shareable by another user.
4) Attempt to open an ISAM or PAM file in an OPEN mode intended to
prohibit opening of the file when one or more users have already
opened it.
5) Attempt to open an ISAM file with LOCKENV=XCS.
6) File is used by a C-COPY session.

### Response

Correct and try again later.

## DMS0EAF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EAF Multiple ISAM key. Last macro not processed

### Meaning

ISAM has passed returncode '0AAF' to CLOSE.

## DMS0EA2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EA2 SYSTEM ERROR: INCONSISTENCY FOR ISAM I/O OPERATION DURING CLOSE. MACRO NOT PROCESSED

### Meaning

During an I/O operation during the processing of an ISAM CLOSE macro
a system-internal inconsistency occurred which was caused by something
other than a hardware error.
The program is continued with the EXLST exit ERRADR, if defined,
otherwise it is terminated.

### Response

Contact the system administrator.

## DMS0EA4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EA4 SHORTAGE OF DISK MEMORY SPACE FOR ISAM-FILE DURING CLOSE. MACRO NOT PROCESSED

### Meaning

During close processing of an ISAM file additional disk memory space
was required, but secondary allocation was not possible (ISAM has
passed returncode '0AA4' to CLOSE)

### Response

Supply enough disk memory space or modify the primary allocation
accordingly.

## DMS0EA7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EA7 ISAM FILE INCONSISTENT. CONTACT SYSTEM ADMINISTRATOR

### Meaning

ISAM has passed return code '0AA7' to CLOSE.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0EB2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EB2 ADDITIONAL SPACE FOR USER FILE NOT AVAILABLE DURING CLOSE, AND 'NOSPACE' OPERAND NOT DEFINED IN 'EXLST' MACRO. PROGRAM ABORTED

### Meaning

The allocator has rejected a request for additional memory space for the
user file during CLOSE processing.
Possible reasons:
- pubspace limit reached
- value for secondary allocation is '0'
- file has too many extents.
- file will exceed 32 gigabytes and
LARGE_FILE=*FORBIDDEN has been set.

### Response

Contact the system administrator.

## DMS0ECD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0ECD PROGRAM ERROR: 'CODE=OWN' AND TRANSLATION TABLE ADDRESS NOT SPECIFIED IN FCB FOR TAPE FILE OR INVALID

### Meaning

The user has attempted to access a tape using his/her own translation
tables.

### Response

Correct the program and try again.

## DMS0EEE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EEE ERROR WHEN CLOSING ISAM FILE

## DMS0EE0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EE0 END OF FILE FOUND DURING FEOV HANDLING

### Meaning

The end of the file has been encountered during FEOV processing.

## DMS0EE2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EE2 TAPE SWAPPING ERROR: NEXT TAPE CANNOT BE MOUNTED

### Meaning

The tape required for tape swapping cannot be mounted or the tape swap
would result in more than 255 VSN entries within the catalog/TFT entry.

## DMS0EFE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EFE BCAM CONNECTION ERROR

### Meaning

The user has attempted to execute OPEN, CLOSE or FEOV on a remote host
identified by the catalog ID of the file name. Error code 00FE is
returned from the RFADCSND/RFADCRCV/RFADCLGF module due to a BCAM
connection error. The BCAM error is described in an error message
sent to the operator console.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0EFF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0EFF BCAM CONNECTION INOP OR ABOUT TO BE CLEARED

### Meaning

The user has attempted to execute OPEN, CLOSE or FEOV on a remote host
identified by the catalog ID of the file name. Error code 00FF is
returned from the RFADCSND/RFADCRV/RFADCLGF module due to an earlier
error in the same connection.

### Response

Clear the connection by means of a /REMOVE-RFA-CONNECTION command
and then set it up again by means of a /SET-RFA-CONNECTION command.
If the error persists, contact the system administrator.

## DMS0E01

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E01 ACCESS TO REQUESTED CATALOG NOT POSSIBLE

### Meaning

One of the specified path names contains the catalog ID of a catalog which
is not accessible.

## DMS0E02

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS0E02 Requested catalog in QUIET or HOLD state. Waiting time is over. Command not processed

### Meaning

The catalog containing the file to be closed is currently not accessible.

## DMS0E05

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

Warranty : NO

DMS0E05 ERROR IN MRS COMMUNICATION FACILITY

### Meaning

An error has occurred in the MSCF communication facility when accessing
a non-local system. The remote system is currently not available or a
Net-Storage volume is not accessible on the master system.

### Response

Request the system administrator to check the connection with the remote
host. At the best it will only be a temporary fault and a repeated
attempt to execute the job will be successful.

## DMS0E07

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E07 FILE CANNOT BE CLOSED OWING TO MASTER CHANGE

### Meaning

The catalog entry for the file cannot be written because a master change
took place.

## DMS0E09

Destination: CONSOLE Routing code: T Weight: 99

Warranty : NO

DMS0E09 'MAREN' SUBTASK RESTRICTS VOLUME SWITCHING WITH ERROR '(&00)'

### Meaning

(&00): error code, the following will be possible:
01: missing or invalid volume password
02: the volume belongs to a foreign user ID and it is not shareable
03: the volume belongs to a foreign user ID, it is only read-access and
the user wants to write
04: the volume is borrowed
05: the volume shall be written to although the file expiration date is
not yet reached
06: the volume has an invalid state in its archive entry (e.g. defective
or free)
07: the volume is reserved for ARCHIVE applications, but it is no ARCHIVE
subtask
08: the volume is being locked by another task on the same host
09: the volume is still locked by another task of another host
0A: the VSN is not saved in the MAREN catalog
0B: the volume is not locally available
0C: the request was rejected by a special MAREN RZ exit by the MAREN
administrator.

## DMS0E10

Destination: CONSOLE Routing code: T Weight: 99

Warranty : NO

DMS0E10 System administrator restricts volume swapping

### Meaning

The activated system exit routine has rejected the volume swapping
request.
Note: 'DMS0E10' can also be a CMS-error '0310'.

### Response

The system administrator is responsible for the system exit routines.
Contact him for further details about the reason for rejection.

## DMS0E15

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

Warranty : NO

DMS0E15 Calling base mechanism of system exit '(&00)' results in error code '(&01)'

### Meaning

(&00): exit number.
(&01): error code of $SYSX interface.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0E19

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0E19 Error at the CLOSE of the file on the Net-Storage volume

### Meaning

An error occurred during the call of the CLOSE function
of ONETSTOR.
Possible reasons:
- Access to Net-Storage denied
- File on Net-Storage does not exist
- invalid file descriptor,
i.e. after UMOUNT-NET-STORAGE with FORCE=*YES

### Response

For further diagnosis contact system administrator

## DMS0E2C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E2C PPAM REPORTS TO CLOSE: INVALID EXTENT TABLE

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0E2E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E2E PPAM reports 'CLOSE': Device access authorization withdrawn by operator

## DMS0E26

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E26 PTAM REPORTS TO OPEN: DEVICE LOCKED FOR A SHORT TIME

### Meaning

The application uses the function OPTION=NOWAIT (FCB operand).
The volume monitor has locked the device for a short time.

### Response

Try again; if the problem persists, contact the system administrator.

## DMS0E27

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E27 ERROR WHEN CLOSING FILE. I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

## DMS0E28

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E28 PPAM REPORTS TO SAM OR UPAM: INCONSISTENCY BETWEEN DMS AND NDM TABLES DURING CLOSE

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0E3B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E3B SYSTEM ERROR WHEN CLOSING FILE

### Meaning

The UPDATE-TSOSCAT or CLEAR-TSOSCAT function or the F1 label function
returned internal error code '033B'.
Possible reasons:
- On a pubset which is not locally allocatable a catalog entry for a
normal pubset file (non-shared PVS) was to be deleted or modified.
- A catalog entry is to be written back with obsolete contents.
- A catalog entry was read that is not supported in this BS2000 version.
- A catalog function from slave not supported.

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0E31

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E31 FILE NAME INVALID OR ILLEGAL

### Meaning

The user file name violates BS2000 conventions.
Possible reasons:
1) $USERID invalid, or the user is not authorized to access the
specified pubset.
2) The requested function does not permit partially qualified file names.
Message DMS0331 lists other possible error causes.

### Response

Correct the program and try again.

## DMS0E33

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E33 SPECIFIED FILE NO LONGER AVAILABLE AT CLOSE TIME

### Meaning

Possible reasons:
- The requested file is no longer cataloged in the system.
- The catalog entry was deleted by the system administrator after the
file was opened.

## DMS0E34

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E34 Internal error in the Catalog Management System

### Meaning

An internal error has occurred in the Catalog Management System.
A SERSLOG entry or a system dump has been generated to
facilitate diagnosis.

### Response

Contact the system administrator.

## DMS0E49

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0E49 UPAM: INVALID ALLOCATOR REQUEST DURING CLOSE.

### Response

Contact system administration.

## DMS0E5B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E5B Internal error during the CONCURRENT COPY session

### Response

Abort the session.

## DMS0E5C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E5C A CANCEL was given for the CONCURRENT COPY session

### Response

Abort the session.

## DMS0E5D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E5D During the CONCURRENT COPY session the MSCF connection to a slave host was interrupted.

### Response

Abort the session.

## DMS0E7A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E7A PTAM REPORTS TO CLOSE: BOURSE ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0E7B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E7B PTAM REPORTS TO CLOSE: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF ONE OR MORE BLOCKS

### Meaning

The data in the magnetic tape cartridge buffer has not been written
to the cartridge in its entirety. Since it was not possible to save this
buffer, this has resulted in one or more blocks being lost irretrievably.

## DMS0E7C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E7C PTAM REPORTS TO CLOSE: WRITE ERROR IN CONJUNCTION WITH BUFFERED OUTPUT

### Meaning

Not all of the data in the MB cartridge buffer was written completely to
the cartridge, as a write operation could not be performed in spite of
repeated attempts.
The tape has no defined position.

## DMS0E7F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E7F SYSTEM ERROR WHEN CLOSING FILE. CONTACT SYSTEM ADMINISTRATOR

### Meaning

During CLOSE processing an error occurred while calling a BASIS
function.

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0E71

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E71 PTAM REPORTS TO CLOSE: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0E72

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E72 PTAM REPORTS TO CLOSE: INCONSISTENCY BETWEEN DMS AND NDM TABLES

## DMS0E73

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E73 PTAM REPORTS TO CLOSE: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0E75

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E75 PTAM REPORTS TO CLOSE: ILLEGAL OPERATION

### Meaning

Possible reasons:
- the operation is not possible for the specified volume type on the
allocated device. E.g. no writing is possible if a device type C4 is
allocated on the specification of the volume type TAPE-C2 because no
compatible devices for writing in TAPE-C2 format are available.
- An attempt has been made to write to a shortened tape.

### Response

Case 1: select a volume type specification compatible with the device
installation.
Case 2: Use a tape with normal length.

## DMS0E76

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E76 PTAM REPORTS TO CLOSE: DEVICE TEMPORARILY LOCKED

### Response

Contact the system administrator and request diagnostic material, if
necessary.

## DMS0E77

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E77 PTAM REPORTS TO CLOSE: I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

### Response

Try again; if the problem persists, contact the system administrator.

## DMS0E78

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E78 PTAM REPORTS: ILLEGAL PTAM CALL

### Meaning

Possible reason:
In MAV mode essential WAIT's before the FEOV or CLOSE call are missing.

### Response

Correct the user program.

## DMS0E79

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E79 PTAM REPORTS TO CLOSE: DEVICE ACCESS AUTHORIZATION WITHDRAWN BY OPERATOR

## DMS0E88

Destination: USER-TASK Routing code: Weight: 70

Warranty : NO

DMS0E88 ERROR DURING DEVICE PROCESSING

### Meaning

A call for a device state modification during tape processing could
not be terminated successfully.

### Response

Try again (with another device, if necessary).
If the error persists, contact the system administrator.

## DMS0E9A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E9A ERROR WHEN RELEASING MEMORY SPACE

## DMS0E9B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E9B Error during a request or a release of system memory.

### Meaning

A system component called during close processing cannot
perform a request or a release properly.

## DMS0E9C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E9C RELM ERROR '0C'

### Meaning

Error in attempt to release memory space.

## DMS0E9F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E9F $REQM ERROR WHEN CLOSING FILE. MACRO NOT PROCESSED

### Response

Contact the system administrator, produce a system error message
and forward it for diagnosis.

## DMS0E90

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E90 INACTIVE FCB

## DMS0E91

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E91 ERROR WHEN CLOSING FILE. CATALOG ENTRY MAY BE IN UNDEFINED STATE. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The error occurred while bringing the catalog up to date during CLOSE
processing. The file was not closed.

## DMS0E92

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E92 ERROR (&00) WHEN CLOSING FILE (&01)

### Meaning

While processing a CLOSE ALL instigated by the user, DMS has reported
error (&00) for file (&01). Processing of CLOSE ALL continued. The
status of file (&01) may remain inconsistent (e.g. tape labels not
written, catalog not updated).
(&00): DMS error code (see IDEMS macro).
(&01): file name.

### Response

Depending on the error code and the OPEN type, it may be necessary
to reconstruct or repair the file.

## DMS0E93

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E93 ERROR WHEN CLOSING FILE. FIRST VOLUME CONTAINED IN CATALOG NOT MOUNTED

### Meaning

The CLOSE routine has tried to access the first volume of a file, but it
wasn't mounted.

## DMS0E94

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E94 SYSTEM ERROR: WRONG PAGES SPECIFIED IN RELM. RELM ERROR CODE '04'

## DMS0E95

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E95 I/O ERROR(S). CHECK THE LAST PAGE(S) WRITTEN IN THE FILE

### Meaning

Privileged PAM reports a physical I/O error while waiting for an I/O
operation without waiting for termination.

## DMS0E96

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E96 Current tape position does not permit EOV labels for file '(&00)' to be written

### Meaning

For the BTAM file (&00), which was opened in INOUT or OUTIN mode, EOV
labels are to be written during CLOSE processing. However, the current
tape position prohibits this as it would cause foreign files on the tape
to be destroyed.

## DMS0E97

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E97 FILE (&00) CANNOT BE CLOSED

### Meaning

When processing a CLOSE ALL instigated by the user, file (&00)
could not be closed due to one of the following errors:
1) The FCB memory space has been deallocated.
2) The link from P1FCB to P2FCB has been modified.
No CLOSE processing was performed. The file is unlocked and
set as inactive in the TFT. The catalog entry has not been updated.
Memory areas (buffers, P2FCB, etc.) are not released. The status
of the file remains inconsistent (e.g. tape labels not written).

### Response

Depending on the OPEN type, it may be necessary to reconstruct
or repair the file.

## DMS0E98

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E98 ERROR DURING PSEUDO-CLOSE PROCESSING

### Meaning

Possible reasons:
- FCBTYP not SAM,
- OPEN mode not OUTPUT or EXTEND,
- file name is *DUMMY,
- volume is a tape.

### Response

Correct the program.

## DMS0E99

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0E99 INVALID FCB ADDRESS IN CLOSE MACRO

### Meaning

FCB is invalid and cannot be processed by the system.
Possibly it was overwritten by the user program.

### Response

Correct program.

## DMS03AA

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

Warranty : NO

DMS03AA TIMEOUT FOR CMS BUFFER ALLOCATION BOURSE

### Meaning

While waiting for a found CMS buffer to be released the task received a
timeout on the bourse used for serializing the tasks on a buffer.
The timeout error may be due to there having been too few buffers
allocated or to problems relating to disk I/O operations.

### Response

If not enough CMS buffers have been allocated (from 6 to 256 are
possible),
increase the number of buffers with the next import.
If the error is due to an I/O problem, contact the system administrator.

## DMS03AB

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

Warranty : NO

DMS03AB SYSTEM CATALOG FOR USER INVALID. TASK ABORTED

### Meaning

Call by DKCMAIN using $TERM.
The primary catalog block of a user could not be written back. The
task is aborted.

### Response

The system administrator has to repair the system catalog.

## DMS03AD

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

Warranty : NO

DMS03AD RELM ERROR. ABNORMAL TASK TERMINATION

### Meaning

Call by DKCMSE, DKCMSPL, DKCMPN and CMSCTOP using $TERM.

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03AE

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

Warranty : NO

DMS03AE DEVICE COULD NOT BE RELEASED. ABNORMAL TASK TERMINATION

### Meaning

Call by DKCMSPL or DKTSKU using $TERM.
Error in the DRSRL call for the release of a private disk device.

## DMS03A1

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

Warranty : NO

DMS03A1 CMS LOCK ERROR. ABNORMAL TASK TERMINATION

### Meaning

Call by DKCMAIN and DCALOCK using $TERM.
An error related to a CMS lock has occurred.

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03A2

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

Warranty : NO

DMS03A2 INTERNAL CMS ERROR. ABNORMAL TASK TERMINATION

### Meaning

Call by DKCMAIN, DKTSKU and DCAWER using $TERM.
An internal CMS error has occurred, causing task termination.

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03A3

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

Warranty : NO

DMS03A3 REQM ERROR IN CMS. ABNORMAL TASK TERMINATION

### Meaning

Call by DKCMSPL and DKCMAIN using $TERM.
A REQM macro for CMS was not successful. The task is terminated.

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03A5

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

Warranty : NO

DMS03A5 Pubset (&00): Catalog block '(&01)' of user '(&03)' in catalog '(&02)' destroyed. PHP '(&04)' on VSN '(&05)' and PHP '(&06)' on VSN '(&07)' are concerned. Abnormal task termination. Take dump.

### Meaning

Either a catalog block is inconsistent or the disk being processed has not
been initialized.
(&00): Pubset ID (c'*F1*' for private disk)
(&01): logical halfpage number of the catalog block concerned.
(&02): name of catalog file (c'F1LABEL' for private disk)
(&03): name of block owner (c'********' for private disk or block of
PBN-Table)
(&04): physical half page number of first part of destroyed block
(&05): VSN, where physical half page of first part of block is allocated
(&06): physical half page number of second part of destroyed block
(&07): VSN, where physical half page of second part of block is allocated

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03A6

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

Warranty : NO

DMS03A6 JOB VARIABLE RETURNED ON REQUEST FOR CATALOG ENTRY FOR FILE, OR VICE VERSA

### Meaning

Call by DKCMAIN using $TERM.
In response to a request for a catalog entry for a file a job variable
was returned, or vice versa.

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03A7

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

Warranty : NO

DMS03A7 PROBLEMS WITH CATALOG STRUCTURE. ABNORMAL TASK TERMINATION

### Meaning

Call by DKCMAIN using $TERM.
Problems with the catalog structure:
there are inconsistencies in the catalog block chaining.

### Response

Take a dump and send it to the system administrator for further diagnosis.

## DMS03A8

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

Warranty : NO

DMS03A8 Connection to pubset (&00) interrupted. Timeout. Do you want to wait for connection? Reply (Y=Yes, N=No).

### Meaning

For at least 10 minutes a batch task has been waiting for a communication
to the system that has imported the pubset (&00) exclusively or as
master. The message is issued by the catalog management, the allocator
and the storage class management.
(&00): Identifier of the pubset.

### Response

If you want to wait for the re-establishment of the connection, you
should query the status of the pubset by /SHOW-MASTER-CATALOG-ENTRY
(&00). In this case you should answer the message DMS03A8 with Y only
when the pubset is no longer QUIET.
Y: The task continues to wait.
N: The task ceases to wait. The command which is being processed is
aborted.

## DMS03A9

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

Warranty : NO

DMS03A9 Internal error in the MSCF/DMS communication function. Task continued

### Meaning

In the MSCF/DMS communication function, an error has occurred on calling
an external function. A SERSLOG entry has been written, but the
task has continued.

## DMS03BA

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

Warranty : NO

DMS03BA (&00) ENTRIES WRITTEN TO SERSLOG FILE

### Meaning

(&00): number of SERSLOG entries.

### Response

Evaluate the SERSLOG file.

## DMS03BB

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03BB Write error on shared pubset with pubset id '(&00)' recovered

### Meaning

This message is displayed if a permanent error on the shared public
volume has been recovered.
If this host is a slave sharer, monitoring by the master sharer will be
performed again through the vital-sign messages.
If this host is a master sharer, monitoring by the slave sharers will be
performed again through the vital-sign messages.
Shared pubset operation will continue normally.

## DMS03BC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03BC NO ACL ENTRY FOR FILE

### Meaning

This message serves simply to provide the internal information that
a SERSLOG entry is being created. No system dump is taken and the
message itself is not displayed. Contrary to expectations, a catalog entry
does not contain an ACL entry. Consequently, a SERSLOG entry with
the path name is created for diagnostic purposes.

## DMS03BD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03BD /SET-PUBSET-ATTRIBUTES OR /SHOW-PUBSET-ATTRIBUTES NOT PROCESSED CORRECTLY. ERROR TYPE '(&00)'

### Meaning

(&00): '01', the public residence with the specified pubset ID could not
be released.
'02', the SVL of the public residence with the specified pubset ID
could not be released.
'03', the MRSCAT entry with the specified pubset ID could not be
released.
'04', error when releasing class 5 memory.
'05', a pubset allocation could not be cancelled.
SVL: standard volume label.

## DMS03BE

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS03BE /SET-PUBSET-ATTRIBUTES or /SHOW-PUBSET-ATTRIBUTES not processed. Error code '(&00)', return information '(&01)'

### Meaning

(&00): '01', the user is not authorized to use the command; /SET-P-A
is restricted to the system administrator, /SHOW-P-A is
restricted to the system administrator or to console
'02', error when reading the multiprocessor catalog entry
'03', op DEVICE-TYPE missing and device type not in mrscat
'04', the disk request has been rejected
'05', error when reading the time stamp of the disk label
'06', error when reading or writing the disk label (SVL)
'07', invalid call of the $CNVSYSI interface; internal error
'08', error in the terminal or console display
'09', the pubset is being exported, retry later
'10': error during allocation of the pubset
'11', internal privilege-check error
'12', OPS internal error
'13', OPS operational error
'14', OPS subsystem error
'15', wrong mrscat entry type
'16', mrscat entry not defined
'17', incompatible pvs record in SVL
'18', ID of the control volumeset not specified
'19', internal error
(&01): return info of a system function, '%' otherwise

## DMS03BF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03BF Operand error in /SET-PUBSET-ATTRIBUTES or /SHOW-PUBSET-ATTRIBUTES. Error type '(&00)'

### Meaning

(&00): '01', impermissible operand value for DEVICE-TYPE
'02', impermissible operand value for SYSID
'03', impermissible operand value for MASTER
'04', impermissible operand value for BACKUP-MASTER

## DMS03B0

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B0 PUBSET SHARER WITH SYSTEM ID '(&00)' ON PUBSET WITH PUBSET ID '(&01)' FAILED

### Meaning

This message will be displayed on the master sharer Host if a slave
sharer crash has taken place, and on the slave sharer if the master has
failed.
(&00): system identification.
(&01): catalog identifier.

### Response

Restart the sharer that has crashed.

## DMS03B1

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B1 NO MORE VITAL-SIGN MESSAGES CAN BE WRITTEN ON PUBSET WITH PUBSET ID '(&00)'. PUBSET FORCIBLY EXPORTED

### Meaning

If a slave sharer is no longer able to write vital-sign messages, it tries
to have its vital-sign monitoring deactivated via the master. If it
succeeds, shared pubset operation will be continued normally. If it
fails, this message will be displayed and the pubset forcibly exported.
(&00): catalog identifier.

## DMS03B2

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B2 WARNING: FUNCTIONAL INTEGRITY OF PUBSET WITH PUBSET ID '(&00)' WILL NO LONGER BE MONITORED

### Meaning

This message is displayed if the vital-sign messages of a shared pubset
cannot be read (e.g. due to a read error). Shared pubset operation
continues normally.

## DMS03B3

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B3 WATCHDOG function '(&00)' failed

### Meaning

(&00): function identifier, i.e.:
CONNECT: a pubset in shared mode cannot be imported to this
host until all imported shared pubsets have been
exported.
DISCONNECT: the watchdog function cannot be deactivated until
the next session.
CHECK-SHARER: monitoring of pubset sharers is not possible again
until all imported shared pubsets have been exported.
ACK-EXCAT: the exportation of a shared pubset on the master cannot
be reported to the host at the moment.

## DMS03B4

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B4 ALIGNMENT ERROR DURING SHARED PUBSET FUNCTION CALL

### Meaning

One of the functions for shared pubset management, the watchdog mechanism
or the remote shared pubset functions was called with a parameter list
which has not been aligned on a word boundary.

### Response

The caller task is aborted.

## DMS03B5

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B5 UNRECOVERABLE INTERNAL ERROR DURING SHARED PUBSET FUNCTION

### Meaning

An unrecoverable error has occurred in one of the functions for
shared pubset management, the watchdog mechanism or the remote
shared pubset functions.

### Response

The caller task is aborted.

## DMS03B6

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B6 WARNING: INTERNAL ERROR IN SHARED PUBSET FUNCTION. TASK CONTINUED

### Meaning

In one of the functions for shared pubset management, the watchdog
mechanism or the remote shared pubset functions an error has
occurred; this error has not caused the task to be aborted,
but led simply to an error logging call.

## DMS03B7

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B7 WATCHDOG MECHANISM FAILED. SHARED PUBSET OPERATION NOT MONITORED

### Meaning

An error has occurred in connection with the watchdog mechanism,
further monitoring of shared pubset operation is impossible at the moment.
If shared pubset monitoring can be recovered by MSCF, the message MCS4132
will be issued.

### Response

If monitoring of shared pubset operation cannot be resumed
automatically, all shared pubsets must be exported.
They can subsequently be imported again.

## DMS03B8

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B8 WARNING: SHARED PUBSET MONITORING FOR PUBSET ID '(&00)' WILL BE RESUMED

### Meaning

This message is displayed after a DMS03B2 message.
It means that the watchdog mechanism has successful rectified an
intermittent read error.
Monitoring of the vital-sign messages and of shared pubset
operation will continue normally.

## DMS03B9

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS03B9 WRITE ERROR ON SHARED PUBSET WITH PUBSET ID '(&00)'. VITAL-SIGN MESSAGES NO LONGER WRITTEN BY THIS HOST

### Meaning

This message is displayed if a permanent error on the shared public
volume set occurs when writing vital-sign messages.
If this host is a slave sharer, the vital-sign message monitoring by
the master sharer will be performed only through the communication line.
If this host is a master sharer, the monitoring by the slave sharer
will be performed only through the network.
An error logging entry has been written.
Shared pubset operation will continue normally.

### Response

Check error logging entries, if necessary HEL file entries, too.

## DMS03CA

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

Warranty : NO

DMS03CA Error when updating the CE limit.

### Meaning

The number of accounted catalog entries of files or job variables could
not be updated for a certain user in one of the following situations:
- during F5-label reconstruction when importing a pubset;
- when creating or deleting a file or job variable.

### Response

Contact the system administrator and request diagnostic information
(SERSLOG file).

## DMS03CB

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

Warranty : NO

DMS03CB Migration for SM pubset (&00) not possible as file '(&02)' exists on the SF pubset (&01).

### Meaning

The CMS migration for the SM pubset (&00) cannot be performed because
the name of the catalog file (&02) that is to be created during CMS
migration is occupied on the SF pubset (&01).

### Response

Erase or rename the file and restart SMPGEN.

## DMS03CD

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

Warranty : NO

DMS03CD PVS: (&00), CATALOG CONVERSION TO V10. NEW INFORMATION WILL BE LOST (E.G. GUARDS PROFILES). ABORT CONVERSION ? (Y=YES; N=NO)

### Meaning

During conversion from V11 to V10 format information will be lost.
The user has to decide if conversion continue or be aborted.

### Response

Y: abort conversion.
N: continue conversion.

## DMS03CE

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

Warranty : NO

DMS03CE PVS: (&00), CATALOG NOT RECONVERTIBLE BECAUSE CACHE OF PUBSET STILL ACTIVE. CONTINUE DESPITE POSSIBLE DATA LOSS? REPLY (Y=YES; N=NO)

### Meaning

Because the cache of the pubset is still active for some files
(whose pages are still in the cache) data is lost if the catalog of
the pubset is reconverted. Reconstruction of the files concerned is
only possible with the next /IMCAT in versions V10.0A or >=V11.0A.
Reverting to older versions means the information as to which files
are affected will be lost in the catalog entries.
(&00): catalog ID.

### Response

Import the pubset again in >=V11.0A.
Y: data loss permitted
N: data loss not permitted.

## DMS03CF

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

Warranty : NO

DMS03CF PVS: (&00), CONVERSION TO OLD CATALOG FORMAT (&01)

### Meaning

The desired reconversion of the V11.0 catalog to the old format was
processed successfully or failed.
The reason for failure may be tasks busy in the CMS during exportation
which prevented final reconversion of the catalog.
(&00): catalog ID
(&01): "SUCCESSFULLY DONE" or "FAILED".

### Response

Convert the catalog offline with the aid of SIROS or retry the import in
V11.0 and then export again.

## DMS03C0

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

Warranty : NO

DMS03C0 Pubset: (&00), catalog (&01), reconstruction of CMS PBN table '(&02)'

### Meaning

The PBN table of the CMS in the TSOSCAT is destroyed and has to be
reconstructed with the aid of the TSOSCAT blocks which are assigned to
the different users of the JOIN file.
The message reports if the attempt was successful or not.
(&00): pubset ID
(&01): name of catalog
(&02): FAILED or SUCCESSFULLY DONE.

### Response

If the attempt was not successful use DPAGE to dump the catalog because
pubset reconstruction is not possible without manual repair.

## DMS03C1

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

Warranty : NO

DMS03C1 PVS: (&00), FILE OR JV ENTRIES EXIST ALREADY IN CATALOG FOR NEWLY CREATED USER ID '(&01)'. COPY ENTRIES ? REPLY (Y=YES; N=NO, DELETE; T=ABORT OPERATION)

### Meaning

During the creation of a PBN in the catalog by means of addition of a
user ID in the JOIN file it was detected that the new user ID which is to
be created has already file or JV entries in the catalog.
(&00): PVS ID
(&01): User ID.

### Response

The operator has to decide if the entries should be taken over or deleted
or if the PBN allocation has to be aborted.

## DMS03C2

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

Warranty : NO

DMS03C2 Pubset: (&00), no PBN in catalog '(&01)' corresponds to user ID '(&02)'.

### Meaning

When reading the PBN table in the catalog during IMPORT-PUBSET
no PBN was found for the current user ID.
(&00): pubset ID
(&01): name of catalog file
(&02): user ID

## DMS03C3

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

Warranty : NO

DMS03C3 PVS: (&00), INVALID CATALOG ID

### Meaning

The TSOSCAT of the current pubset is useless.
There have probably been problems when converting from BS2000 V10 to
BS2000 V11 or vice versa.

### Response

Import the most recent backup copy into the system or generate the pubset
again.

## DMS03C4

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

Warranty : NO

DMS03C4 HOME PVS: (&00), CATALOG NOT IN V10 FORMAT

### Meaning

The pubset was used in a BS2000 version >= V11, with the result that its
catalog has the new format.

### Response

The catalog of the current pubset must be converted offline with the aid
of SIR if the pubset is to be used as a home pubset.
If, in BS2000 V10, the pubset is to be used as a normal pubset and not
as a home pubset, the catalog is converted automatically during IMCAT
processing.

## DMS03C5

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

Warranty : NO

DMS03C5 PVS: (&00), CATALOG CONVERTER COULD NOT BE LOADED

### Meaning

Dynamic loading of the catalog converter was unsuccessful. The TSOSCAT of
the pubset could not be converted from BS2000 V11 format to BS2000 V10
format.

### Response

Try again or convert the catalog of the pubset offline with the aid of
SIR.

## DMS03C6

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

Warranty : NO

DMS03C6 PVS: (&00), CATALOG CONVERSION TO (&01) FORMAT NOT CORRECT

### Meaning

When converting the catalog into BS2 V11 or BS2 V10 format the
catalog structure has been destroyed.

### Response

Insert (&01)='V10': restore the save data from the pubsets concerned.
Insert (&01)='V11': CMS restored the old catalog state (V10).
The pubset continues to be useable in version <V10.

## DMS03C7

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

Warranty : NO

DMS03C7 Pubset (&00), error when converting catalog. Reason: '(&01)'

### Meaning

An error occurred when converting the old catalog into the new BS2 V11
format or the new catalog into the old BS2 V10 format.
(&00): catalog ID
(&01): reason of the error (decimal value)
(&01): 01, the file CONVCAT does not exist
02, the file CONVCAT is too small
03, error when handling the JOIN file
04, I/O error
05, error when handling the SVL
06, internal error during conversion
07, interface error
08, file CONVCAT not on pubres (with first extent)
09, catalog destroyed
10, first PHP of CONVCAT too high
PHP: Physical Half Page
11, invalid catalog pointer in SVL
12, ACQUIRE or DALL error when calling $NKACALL
13, allocation unit on the pubset not equal to 6K.
The pubset is not convertible to versions <V11.0
because the allocation unit is unknown there.
14, the cache of the pubset is still active.
The pubset cannot be used in versions <V11.0
because the pubset cache is still active.
This may lead to data inconsistency.
15, conversion cancelled by operator.
Message DMS03CD was answered with "YES".
Conversion of the catalog from V11 to V10 format therefore is
aborted.
16, the pubset contains volumes with a capacity > 32 GB.
The pubset is not convertible to versions < V11.0, as
such objects are not supported there.
17, the pubset contains an extra large catalog.
That's why the pubset is not convertible to versions
< V11.0.

### Response

Analyze the error.
If 08: if possible import again in V11.0 and reinitialize file
CONVCAT so that the first extent resides on the pubres.
If 09: create diagnostic information (DPAGE dump of TSOSCAT)
If 10: same as '08'; CONVCAT must be located in front so that
the first PHP can be accommodated in a half-word.
If 11: create diagnostic information (take dump of SVL)
If 12: check if all disks of the pubset exist
If 13: none
If 14: import the pubset once more in V11.0 and then try again
or
convert the pubset offline with the aid of SIROS; in this case
message DMS03CE will be displayed and can be answered positively
for conversion, but data inconsistency may occur.
If 15: If conversion is imperative, retry and answer message DMS03CD
with "NO".
Attention: If the reply is "NO" the new (V11) information in the
catalog entries will be lost.
If 16: none
If 17: none

## DMS03C8

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

Warranty : NO

DMS03C8 CE LIMIT REACHED. CMS OPERATION ABORTED

### Meaning

This message will be displayed if during recataloging of a file or
job variable the CE limit entered in the JOIN file is exceeded.

### Response

Delete the files or job variables which are no longer in use.

## DMS03C9

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

Warranty : NO

DMS03C9 Pubset: (&00), catalog (&01), read error on catalog block(s) during reconstruction of PBN table. Continue reconstruction? Reply (Y=yes; N=no)

### Meaning

During the reconstruction of the PBN table with the aid of the TSOSCAT
blocks which are assigned to different users of the JOIN file, one or more
block(s) could not be read.
(&00): pubset Id
(&01): name of catalog

### Response

Y: the reconstruction will be continued, but files of some users might be
lost.
N: the reconstruction will be aborted.
A DPAGE dump should be taken to make a manual repair if necessary.

## DMS03DF

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

Warranty : NO

DMS03DF DCADITO CRASH IN CONNECTION WITH A SPECIAL RETURN CODE

## DMS03D1

Destination: CONSOLE Routing code: R Weight: 70

Warranty : NO

DMS03D1 MRSCAT CANNOT BE READ. REASON: (&00)

### Meaning

This message is issued by DCASTRM. During startup MRSCAT could not be
read.
DCAINIT returned error code (&00).

### Response

If error code 04, 12 or 20 is returned, the volumes must be
regenerated.
In all other cases, notify system maintenance.

## DMS03D2

Destination: CONSOLE Routing code: R Weight: 70

Warranty : NO

DMS03D2 MRSCAT COULD NOT BE WRITTEN. REASON: (&00)

### Meaning

This message is issued by DCASTRM. During startup MRSCAT could not be
written.
DCAINIT returned error code (&00).

### Response

If error code 04, 12 or 20 is returned, the volumes must be regenerated.
In all other cases, notify system maintenance.

## DMS03D3

Destination: CONSOLE Routing code: R Weight: 70

Warranty : NO

DMS03D3 BOURSE CANNOT BE CREATED. REASON: (&00)

### Meaning

This message is issued by DCASTRM. During system initialization an error
occurred when creating the bourse. The bourse error code is (&00).

### Response

Contact system maintenance.

## DMS03EE

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

Warranty : NO

DMS03EE SPEEDCAT START ABORTED FOR CATALOG WITH CAT ID '(&00)' DUE TO ERROR TYPE '(&01)'

### Meaning

Due to the error type (&01) the start of SPEEDCAT is aborted for catalog
with catalog Id (&01).

### Response

Analyze the user dump, if necessary.

## DMS03EF

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

Warranty : NO

DMS03EF Pubset: (&00), catalog block '(&01)' in catalog '(&02)' destroyed. Invalid user ID '(&03)' for file or JV name '(&04)' in catalog entry of user '(&05)'. Reply (R=Repair, E=Erase, D=Dump)

### Meaning

When upgrading from a BS2000 version < V9.5 to a version >= V9.5, a
catalog entry with an invalid user ID has been found in a catalog block.
The operator has to decide whether to erase or repair the catalog entry in
question or, as is customary in CMS, to take a system dump with message
DMS03A5.

### Response

R: try to repair the catalog entry.
E: first ensure that the file is no longer needed and then erase
the catalog entry.
D: take a system dump.

## DMS03E0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03E0 SCA (SPEEDCAT) VERSION (&00) RUNNING FOR CATALOG ID '(&01)'

### Meaning

This message is issued by SPEEDCAT.
SCA has been loaded and initialized.
(&00): version number of SCA (Vnn.nn).

## DMS03E1

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

DMS03E1 SCA RUNNING FOR CATALOG ID '(&00)'. STATUS OF CATALOG: (&01) FILE ENTRIES AND (&02) JOB VARIABLES IN (&03) CATALOG BLOCKS

### Meaning

(&00): <catalog ID>.
(&01): <number of catalog entries for files = nnnnnnnn>.
(&02): <number of job variables = nnnnnnnn>.
(&03): <number of used catalog blocks = nnnnnnnn>.
During initialization the entries listed in the message were
contained in the catalog.

## DMS03E2

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

Warranty : NO

DMS03E2 NORMAL TERMINATION OF SCA (CATALOG ID '(&00)')

### Meaning

This message is issued by the P1 program SPEEDSTP.

## DMS03E3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03E3 TERMINATION OF SCA PROGRAM INITIATED (CATALOG ID '(&00)')

### Meaning

This message is issued by the P1 program SPEEDSTP.

## DMS03E4

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

Warranty : NO

DMS03E4 SCA START INITIATED. CATALOG ID ? REPLY (<N>=CATALOG ID)

### Meaning

This message is issued by the P1 program SPEED.

### Response

<N>: enter the catalog ID (4 bytes maximal).

## DMS03E5

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

Warranty : NO

DMS03E5 SCA START INITIATED (CATALOG ID '(&00)')

### Meaning

This message is issued by the P1 program SPEED.

## DMS03E6

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

Warranty : NO

DMS03E6 SCA TERMINATION INITIATED. CATALOG ID ? REPLY (<N>=CATALOG ID)

### Meaning

This message is issued by the P1 program SPEEDSTP.

### Response

N: enter the catalog ID.

## DMS03E7

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

Warranty : NO

DMS03E7 SPEEDCAT is stopped because pubset '(&00)' is migrated to an SM pubset.

### Meaning

SCA is stopped and no restart is possible because there is no SPEEDCAT
for an SM pubset.

## DMS03E8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03E8 SCA CANNOT BE STARTED, BECAUSE SNAP-ID '(&01)' DOES NOT EXIST FOR PUBSET '(&01)'.

### Meaning

(&00): PUBSET-ID;
(&01): SNAP-ID;

## DMS03E9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03E9 SCA CANNOT BE STARTED, BECAUSE SNAP-ID '(&01)' DOES NOT EXIST FOR PUBSET '(&00)'.

### Meaning

(&00): PUBSET-ID;
(&01): ID of SNAP-PUBSET;

## DMS03FA

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

Warranty : NO

DMS03FA SCA CANNOT BE TERMINATED FOR CATALOG WITH CATALOG ID '(&00)' BECAUSE IT IS NOT LOCALLY ACCESSIBLE OR THE SYSTEM IS NOT MASTER OF SHARED PUBSET

### Meaning

SCA cannot support the management of this catalog.
The attempt to terminate SCA was aborted.

### Response

If there has been an input error, repeat the attempt to terminate SCA for
the catalog for which it is active.

## DMS03FB

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

Warranty : NO

DMS03FB TERMINATION OF SCA TASK ABORTED BECAUSE OF ERROR (CATALOG ID (&00))

### Meaning

(&00): <catalog ID>.
This message is issued by the DKCSPEED module.
Depending on the type of error involved, additional information on the
error can be obtained either via an entry in the SERSLOG file or by
means of a system dump.

### Response

Evaluate the system dump or the error logging file.

## DMS03FC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS03FC SPEED TABLE COULD NOT BE RECONSTRUCTED DUE TO '(&00)' ERROR

### Meaning

This message is issued by the DKCSPEED module.
An unrecoverable $REQM error (&00) has made it impossible to reconstruct
the SPEED table.

## DMS03FD

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

Warranty : NO

DMS03FD SCA NOT STARTED FOR CATALOG WITH CATALOG ID '(&00)' BECAUSE 'DKCSPEED' NOT LOADED

### Meaning

Problems occurred during the dynamic loading of DKCSPEED, resulting in
abortion of the SCA start operation.

### Response

Contact the system administrator.

## DMS03FE

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

Warranty : NO

DMS03FE PROCESSING MODE OF SPEEDCAT. WITHOUT TASK CHANGING ? REPLY (Y=YES; N=WITH TASK CHANGING)

### Response

Reply according with the processing mode.

## DMS03FF

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

Warranty : NO

DMS03FF SPEEDCAT TERMINATED DUE TO SHORTAGE OF CLASS 4 MEMORY SPACE

### Meaning

Not enough class 4 memory space is available.

### Response

Try to avoid the problem by use of 'SPEEDCAT with task changing'.

## DMS03F0

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

Warranty : NO

DMS03F0 SCA CANNOT BE STARTED BECAUSE OF INTERNAL PROBLEMS IN MANAGEMENT OF CATALOG '(&00)'

### Meaning

(&00): <catalog ID>.
Problems have occurred in the management of catalog (&00), making it
impossible to start SCA.

### Response

Contact the system administrator.
If (&00) is the TSOSCAT of the home or a paging pubset, terminate the
session and restart the system; otherwise export the pubset concerned
and import it again. After performing these actions, start SCA again.

## DMS03F1

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

Warranty : NO

DMS03F1 SCA STARTUP OR TERMINATION ALREADY IN PROGRESS FOR CATALOG (&00)

### Meaning

(&00): <catalog ID>.
User error, e.g. the SCA start procedure was initiated twice in succession
or the stop procedure was started before SCA startup had been
completed.

### Response

Wait until the current SCA startup or termination operation has been
completed and then perhaps retry the original SCA procedure.

## DMS03F2

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

Warranty : NO

DMS03F2 SCA ALREADY ACTIVE FOR CATALOG WITH CATALOG ID '(&00)'

### Meaning

This message is issued by the DKCSPEED module.
SCA is already active for the catalog with the catalog identifier (&00),
thus causing a repeated start attempt to be rejected.

## DMS03F3

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

Warranty : NO

DMS03F3 SCA cannot be started because catalog with catalog ID '(&00)' has status '(&01)'

### Meaning

(&01): <status of catalog>.
(&01): '0'; inaccessible
'1'; quiet
'2'; remote
'3'; being exported
'4'; exported
'5'; slave in shared pubset
'6'; system managed pubset
'7'; migrated to SM pubset

### Response

If there has been an input error, repeat the attempt to start SCA for the
locally available catalog.

## DMS03F4

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

Warranty : NO

DMS03F4 SCA TERMINATES AFTER HARDWARE ERROR IN CATALOG WITH CATALOG ID '(&00)'. CONTACT SYSTEM ADMINISTRATOR

### Meaning

This message is issued by the DKCSPEED module.
After an input/output error in the catalog and the subsequent error
recovery actions, the SCA tables and the catalog do not match, so
SCA terminates.

## DMS03F5

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

Warranty : NO

DMS03F5 SCA ABNORMALLY TERMINATED FOR CATALOG WITH CATALOG ID '(&00)'

### Response

Contact the system administrator and evaluate the error logging file.

## DMS03F6

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

Warranty : NO

DMS03F6 INVALID SCA VERSION

### Meaning

This message is issued by the DKCSPEED module.
The SCA version is not compatible with the BS2000 version.

### Response

Terminate the system and restart it with the correct SCA version.

## DMS03F7

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

Warranty : NO

DMS03F7 SCA IS NOT RUNNING FOR CATALOG ID '(&00)'. SCA STOP REJECTED

### Meaning

This message is issued by the DKCSPEED module.

## DMS03F8

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS03F8 $REQM ERROR DURING CREATION OF SPEED TABLE. RETRY ? REPLY (Y=YES, N=NO)

### Meaning

The message is issued by the DKCSPEED module.
When creating a 4-Kb page in the SPEED table a $REQM error has occurred,
caused by a lack of class 4 memory space.

### Response

Y: DKCSPEED will retry the $REQM after class 4 memory space has been
made available.
N: DKCSPEED will not retry the $REQM.

## DMS03F9

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

Warranty : NO

DMS03F9 INPUT ERROR. CATALOG ID '(&00)' UNKNOWN TO SYSTEM

### Meaning

This message is issued by the P1 programs SPEED and SPEEDSTP.

### Response

Repeat the attempt to initiate or terminate the SCA task after specifying
a valid catalog ID.

## DMS03SE

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

Warranty : NO

DMS03SE SCANET-START ABORTED FOR NET-STORAGE VOLUME '(&00)' DUE TO ERROR '(&01)'.

### Meaning

Due to the error (&01) the start of SCANET is aborted for NET-STORAGE
VOLUME (&01).
(&00): Net-Storage Volume
(&01): Error description (xxxxxxxx)
xxxxxxxx optional further information for your support.
error descriptions:
LOCK ERROR The lock for synchronisation of
SCANET-calls can't be created.
DATA SPACE Data Space not created.
DATA SPACE ACCESS Access to Data Space is not
possible.
NOT ENOUGH MEMORY IN DATA SPACE Memory is exhausted.
MEMORY IN DATA SPACE NOT RELEASED Memory is not completely
releasable.
NOT ENOUGH MEMORY Class 4 memory is exhausted.
MEMORY NOT RELEASED Memory is not completely releasable
INPUT/OUTPUT ERROR ON DEVICE Ein/Ausgabe-Fehler auf den
Net-Storage.

### Response

Analyze the user dump, if necessary.

## DMS03SX

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

Warranty : NO

DMS03SX SCANET-SESSION ABORTED FOR NET-STORAGE VOLUME '(&00)' DUE TO ERROR '(&01)'.

### Meaning

Due to the error (&01) the start of SCANET-SESSION is aborted for
NET-STORAGE VOLUME (&01). The NET-STORAGE VOLUME is without SCANET
accessible.
(&00): Net-Storage Volume
(&01): Error description (xxxxxxxx)
xxxxxxxx optional further information for your support.
error descriptions:
LOCK ERROR The lock for synchronisation of
SCANET-calls can't be created.
DATA SPACE Data Space not created.
DATA SPACE ACCESS Access to Data Space is not
possible.
NOT ENOUGH MEMORY IN DATA SPACE Memory is exhausted.
MEMORY IN DATA SPACE NOT RELEASED Memory is not completely
releasable.
NOT ENOUGH MEMORY Class 4 memory is exhausted.
MEMORY NOT RELEASED Memory is not completely releasable
INPUT/OUTPUT ERROR ON DEVICE Ein/Ausgabe-Fehler auf den
Net-Storage.

### Response

Inform the service and deliver the created systemdump.

## DMS03S0

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

Warranty : NO

DMS03S0 SCANET START INITIATED FOR NET-STORAGE-VOLUME '(&00)'.

### Meaning

SCANET start initiated for Net-Storage volume &00 .
&00 vsn of Net-Storage-Volume

## DMS03S1

Destination: USER-TASK Routing code: Weight: 30

Warranty : NO

DMS03S1 SCANET RUNNING FOR NET-STORAGE VOLUME '(&00)' WITH '(&01)' FILE ENTRIES.

### Meaning

(&00): vsn of Net-Storage Volume
(&01): <number of catalog entries for files = nnnnnnnn>.
During initialization the entries listed in the message were
contained in the catalog.

## DMS03S6

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

Warranty : NO

DMS03S6 SCANET STOPPED FOR NET-STORAGE-VOLUME '(&00)'.

### Meaning

SCANET stopped for Net-Storage volume &00 .
&00 vsn of Net-Storage-Volume

## DMS030A

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

Warranty : NO

DMS030A PUBSET ID: (&00), ERROR IN CATALOG MANAGEMENT. CMS STARTUP ABORTED. CONTACT SYSTEM ADMINISTRATOR

## DMS030B

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

Warranty : NO

DMS030B PUBSET ID: (&00), CMS BOURSE PROBLEM. CMS STARTUP ABORTED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

An error has occurred when creating the CMS bourses.

## DMS030C

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

Warranty : NO

DMS030C PUBSET ID: (&00), INTERNAL ERROR IN CMS STARTUP. CMS STARTUP ABORTED. CONTACT SYSTEM ADMINISTRATOR

## DMS030D

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

Warranty : NO

DMS030D PUBSET ID: (&00), ERROR IN PARAMETER LIST FOR CMS STARTUP. CMS STARTUP ABORTED. CONTACT SYSTEM ADMINISTRATOR

## DMS030E

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

Warranty : NO

DMS030E PUBSET ID: (&00), ERROR IN CMS STARTUP CALL SEQUENCE. CONTACT SYSTEM ADMINISTRATOR

### Meaning

CMS startup was called for pubset ID (&00) before the CMS-global data
was made available by another CMS startup function.

## DMS030F

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

Warranty : NO

DMS030F PUBSET ID: (&00), CMS STARTUP ABORTED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The reason for CMS abortion is specified in a separate message.

## DMS0300

Destination: CONSOLE Routing code: R Weight: 99

Warranty : NO

DMS0300 Pubset: (&00), write error in system catalog '(&01)'. Abnormal task termination.

### Meaning

The first PAM page (catalog control block) of the catalog (&01) could not
be written back. It is no longer possible to add or remove catalog blocks.

## DMS0301

Destination: CONSOLE Routing code: R Weight: 99

Warranty : NO

DMS0301 CATALOG NOT ACCESSIBLE

### Meaning

In the case of a private disk file, the unavailability of the catalog
might be due to the fact that the CMS environment for supporting private
disks was not created during startup.
For private disks the class 2 option BMTNUM > 0 is mandatory.
If the files are not on private disks, the catalog was not imported
(in this case the class 2 option BMTNUM = 0 is permitted).

### Response

When processing private disk files, restart the system with the class 2
option BMTNUM > 0 and repeat the job.
In all other cases request the system administrator to import the
catalog and then repeat the job.

## DMS0302

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS0302 Connection to pubset (&00) interrupted. Timeout in catalog operation.

### Meaning

The MSCF connection to the system that has imported the pubset
exclusively or as master is interrupted. A catalog operation was waiting
for the pubset to become available again. The wait time as specified in
the master catalog entry has expired. The operation has been aborted.
(&00): CATID of the pubset involved.

### Response

Repeat the command when the MSCF connection to the pubset (&00) is
restored. The pubset will then no longer appear as QUIET in the output of
/SHOW-MASTER-CATALOG-ENTRY (&00).

## DMS0304

Destination: CONSOLE Routing code: R Weight: 99

Warranty : NO

DMS0304 Pubset: (&00), read or write error when accessing catalog '(&01)'. User task '(&02)' aborted.

### Meaning

Call by DCAWER.
An unrecoverable read or write error has made it impossible for a block to
be added to the catalog block chain for the user with the ID (&02)
in catalog (&01). The user's catalog data is thus invalid.

### Response

The system administrator has to repair the system catalog.

## DMS0305

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

Warranty : NO

DMS0305 ERROR IN CONNECTION WITH REMOTE HOST

### Meaning

An error has occurred in the MSCF communication facility when accessing
a non-local system. The remote system is currently not available or a
Net-Storage volume is not accessible on the master system.

### Response

Request the system administrator to check the connection with the remote
host. At the best it will only be a temporary fault and a repeated
attempt to execute the job will be successful.

## DMS0306

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0306 CMS OPERATION ABORTED DUE TO USER REQUEST

### Meaning

The CMS was called at the moment when a master change was in progress.
The user did not want to wait with execution of the operation until
termination of the master change.

### Response

Release any existing locks. Try again later if necessary.

## DMS0307

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0307 CMS WRITE OPERATION NOT PROCESSED

### Meaning

The process of writing a catalog entry to the TSOSCAT has not been
executed because a master change was being processed.

### Response

If necessary repeat the aborted operation, including all previous
operations connected to it.

## DMS0308

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

Warranty : NO

DMS0308 Pubset: (&00), catalog (&01) destroyed

### Meaning

Call by DCAINIT (= CMS startup).
The internal structure of the catalog (&01) of pubset (&00) is destroyed.
CMS - Startup is aborted.
(&00) : pubset ID
(&01) : name of catalog

### Response

Contact the system administrator. The catalog has to be repaired.

## DMS0309

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

Warranty : NO

DMS0309 PUBSET ID: (&00), RELM ERROR AT 'IMCAT' OR CMS STARTUP

### Meaning

Call by DCAINIT (IMCAT or CMS startup).
An attempt to release memory space was not successful.
The IMCAT or the CMS startup is aborted.

### Response

System error; contact the system administrator.

## DMS031F

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

Warranty : NO

DMS031F PVS: (&00), ABNORMAL TASK TERMINATION WITH DMS ERROR CODE '(&01)' SUPPRESSED IN MODULE '(&02) + (&03)' (DECIMAL). CATALOG OPERATION NOT PROCESSED

### Meaning

During a catalog operation an unrecoverable error occurred in CMS, which
normally terminates the task abnormally. Because the task concerned is the
JOIN task (TSN=RP01 or RP02) instead of the task the catalog operation
is aborted with this message and the DMS return code (RC X'031F').
(&00): catalog ID
(&01): DMS03xy (DMS-Errorcode)
(&02): DKCMAIN or DKCMSPL
(&03): the distance in the module, where the error reason occurred.

## DMS0310

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0310 A FUNCTION INTERNALLY USED BY CATALOG MANAGEMENT REPORTS ERROR. PROCESSING ABORTED

### Meaning

Possible reasons:
- conversion between the old and the new catalog format could not be
processed.
- for a file on Net-Storage an error occured during the access to the
catalog entry on the Net-Storage volume.
- error during processing of the TASKLIST on the slave host in the
shared pubset network.
- error during processing of a Net-Storage volume on master host in the
shared pubset network.
- error during processing of internal tables in MSCF processing.
- error during check of access rights by SRPM.

### Response

Try function again. If the error occurs again contact the system
administrator.

## DMS0312

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0312 REQUESTED MRSCAT ENTRY IS UNKNOWN TO SYSTEM

### Meaning

The existing MRSCAT entries can be checked by means of
/SHOW-MASTER-CATALOG-ENTRY.

### Response

The system administrator can specify the missing MRSCAT entries
by means of the command /ADD-MASTER-CATALOG-ENTRY.

## DMS0315

Destination: CONSOLE Routing code: V Weight: 99

Warranty : NO

DMS0315 ERROR DURING ACCESS TO CLASS 2 OPTIONS

### Response

Take a dump and diagnose the error.

## DMS0316

Destination: CONSOLE Routing code: V Weight: 99

Warranty : NO

DMS0316 CMS-GLOBAL DATA COULD NOT BE CREATED

### Response

Take a dump and diagnose the error.

## DMS0318

Destination: CONSOLE Routing code: V Weight: 99

Warranty : NO

DMS0318 DMS STARTUP ERROR

### Response

Take a dump and diagnose the error.

## DMS0319

Destination: CONSOLE Routing code: V Weight: 99

Warranty : NO

DMS0319 SATURATION LEVELS NOT DEFINED IN DESCENDING ORDER. DEFAULT VALUES ASSUMED

### Meaning

The saturation levels of the PVS-specific global disk storage management
system have not been defined correctly.

## DMS032A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS032A PUBSET-ID: (&00); INCONSISTENCY IN CATALOG. EXPORT AND IMPORT PUBSET AND TRY HSMS-COMMAND AGAIN. (&00): Pubset ID

### Meaning

There exists an inconsistency in catalog, which can only be repaired
by a new IMPORT of the pubset.

## DMS032B

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS032B Pubset: (&00), volumeset (&01), the file TSOSCAT has a wrong name.

### Meaning

During IMCAT of SM pubset (&00) the catalog of volumeset (&01)
doesn't have the right name 'TSOSCAT.<volumeset ID>' but the wrong
name 'TSOSCAT'.
(&00): pubset ID
(&01): volumeset ID

### Response

Call system administrator. Catalog has to be repaired.

## DMS032C

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

Warranty : NO

DMS032C Pubset (&00) cannot be extended by (&02) (&01), which possesses an extra-large catalog.

### Meaning

For reasons of compatibility (Pubset not useable in BS2000-OSD-versions
lower V6.0B) a SM-pubset with normal or
large catalogs cannot be extended
by pubsets/volume sets with extra large catalog.
(&00): CAT ID
(&01): volume set ID or pubset ID
(&02): string 'pubset' or 'volume set'

### Response

Export the SM-pubset and start next import with catalog conversion
to extra-large format.
Then pubsets/volumesets with extra large catalog may be added.

## DMS032D

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

Warranty : NO

DMS032D PUBSET ID: (&00), CONVERSION TO EXTRA-LARGE CATALOG WITHDRAWN

### Meaning

Call by DCAINIT (CMS startup).
The operator has answered the message DMS032F with 'no'.
(&00): CAT-ID

### Response

none

## DMS032E

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

Warranty : NO

DMS032E PUBSET ID: (&00), REQM ERROR AT CMS STARTUP

### Meaning

Call by DCAINIT (CMS startup).
A memory request was not successful. CMS startup is aborted.

### Response

Repeat the command for the allocation of the pubset.
If the retry is not successful, contact the system administrator.

## DMS032F

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

Warranty : NO

DMS032F Pubset (&00), after conversion to extra large catalog pubset is only useable in versions > BS2000/OSD-BC V6.0A. continue? (Y=yes, N=no)

### Meaning

The transformation of the catalog in the extra large format causes an
incompatibility, which makes it impossible for older BS2000-versions
to understand the layout of the catalog file.
(&00): CAT ID

### Response

Answer 'Y', if there is no need of the pubset in versions
<= BS2000/OSD-BC V6.0A. Otherwise the reply has to be 'N'.

## DMS0320

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

Warranty : NO

DMS0320 Pubset: (&00), catalog (&01), warning: Some blocks used may have been lost

### Meaning

Call by DCAINIT (= CMS startup).
According to the information in the catalog control table the catalog is
too small. Startup continues.
(&00): pubset ID
(&01): name of catalog

### Response

Contact the system administrator. It is likely that a
/MODIFY-FILE-ATTRIBUTES command with SPACE=RELEASE was specified for
TSOSCAT in the last session.

## DMS0321

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

Warranty : NO

DMS0321 Pubset: (&00), catalog (&01), warning: Catalog block with a LBN higher than the highest possible for the catalog in use.

### Meaning

According to the information in the catalog control table a block with
an excessive logical block number (LBN) is being used.
This is probably due to a system error.
CMS startup continues.
(&00): pubset ID
(&01): name of catalog

### Response

Contact the system administrator.

## DMS0323

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

Warranty : NO

DMS0323 PUBSET ID: (&00), WARNING: BOURSE COULD NOT BE DESTROYED DURING CMS STARTUP

### Meaning

Call by DCAINIT (= CMS startup).
When aborting a CMS startup, a CMS bourse could not be destroyed.

### Response

Contact the system administrator.

## DMS0325

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

Warranty : NO

DMS0325 Pubset: (&00), some filenames (volsetid is new catid) exceed the length limit. Shall they be renamed? Reply (Y=yes; N=no)

### Meaning

Call by DCAINIT (= CMS startup). The filenames, that are too long,
will be renamed in S.RENAME.<date>.N.<number>. The pairs (new name,
old name> will be stored into an ISAM-file on home pubset, by the
name TSOSCAT.CONV.<catid>.<date>. After reconstruction of the
SM-Pubset this ISAM-File may be used, to rename the new names into
the old ones. After renaming the ISAM-file should be erased
immediately, as a new reconstruction after a new crash of the same
SM-Pubset will use an existing file (the existing pairs will remain
in the file).

### Response

Y: The filenames, that are too long, will be renamed, the renamed
pairs are written in an ISAM-file on home pubset.
N: Imcat is terminated with error. A conversion of the volset to a
SF-Pubset, and the reconstruction of the SM-Pubset by SMPGEN is not
possible

## DMS0326

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

Warranty : NO

DMS0326 Pubset: (&00), some filenames (volsetid is new catid) exceed the length limit. No renaming possible. Wait and retry.

### Meaning

Call by DCAINIT (= CMS startup). The filenames, that are too long,
could not be renamed, as no date was found, to make the beginning
of the filename substitution unique under filenames in catalog.
After a little waiting the imcat of the pubset may be tried again
with a good chance of success.

## DMS0327

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

Warranty : NO

DMS0327 Pubset (&00), error during conversion to extra large catalog format. Reason is: '(&01)'

### Meaning

An error occurred when converting the catalog to extra large format.
(&00): catalog ID
(&01): reason of the error (decimal value)
01, the import of a non-control-volset was started with the
parameter 'convert to extra large catalog' or the volset
possesses an extra large catalog. However the associated
SM-pubset is one with normal or large catalogs.
02, one or more of the files TSOSCAT.#M00, TSOSCAT.#P00 and
TSOSCAT.#J00 are already existing in the SM-Pubset
03, there exists no free block in the catalog. However a free
block is needed for removing the static mrscat from page 1
04, the mrscat-block could not be chained to block 1
05, the special catalog files could not be renamed in catalog index
06, the size of the bitmap(s) could not be updated in the
CMS-structures
07, page 1 could not be written after setting the sign
'conversion to extra large catalog finished'

### Response

Analyze the error.
If 01: Convert SM-pubset to extra large catalog format.
If 02: Import pubset without conversion, clear the existing
'catalog files' and retry the import with conversion.
If 03: Import pubset without conversion, enlarge catalog or
remove some users or files from catalog and retry
the import without conversion.
If 04: none
If 05: none
If 06: none
If 07: none

## DMS0328

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

Warranty : NO

DMS0328 Pubset: (&00), in file '(&01)' page (&03) could not be (&02) due to an error. Retry? Reply (Y=yes; N=no)

### Meaning

Call by DCAINIT (= CMS startup).
The page (&03) of the file ((&01)=name of file) of the pubset
with catalog ID (&00) could not be read or written back
((&02)=READ/WRITTEN).

### Response

Y: attempt to read/write will be retried
N: the read/write operation will not be repeated. In this case
the CMS startup will be aborted. The system administrator has to
repair the catalog.

## DMS0329

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

Warranty : NO

DMS0329 Pubset: (&00) does not have a valid catalog (&01)

### Meaning

Call by DCAINIT (= CMS startup).
The pubset (&00) does not contain a valid catalog (&01).
CMS Startup is aborted.
(&00) : pubset ID
(&01) : name of catalog file

### Response

Contact the system administrator. The catalog has to be repaired.

## DMS033A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS033A SYSTEM ERROR OR FORMAT 1 LABEL UPDATE ERROR

### Meaning

Possible reasons:
1) The private volume contains too many files.
2) The file cannot be located on the private volume.
3) One of the following system errors has occurred:
a) WRITE-NEW call for a private disk declared as PPD
b) There is no space on the F1 label.
c) An F1 label entry cannot be found.
d) The inode of a node file on Net-Storage could not be read.

### Response

Try to reorganize the volume. If the problem persists,
contact the system administrator.

## DMS033B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS033B ILLEGAL REMOTE ACCESS OR LOGGING ERROR

### Meaning

Possible reasons:
- On a pubset which is not locally allocatable a catalog entry for a
normal pubset file (non-shared PVS) was to be deleted or modified.
- A catalog entry is to be written back with obsolete contents.
- A catalog entry was read that is not supported in this BS2000 version.
- A catalog function from slave not supported.

### Response

Create a dump for error localization.

## DMS033C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS033C CATALOG BLOCK REQUEST WAS NOT SUCCESSFUL

## DMS033D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS033D TSOSCAT OR F1 LABEL BLOCK DESTROYED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

If '033D' occurs with a system error, the length of a catalog or F1
entry is '0'.
If '033D' is returned internally to the caller, this means that the
F1 entry cannot be found or that one or more duplicate entries exist.

### Response

Contact the system administrator and request diagnostic
material, if necessary.

## DMS033E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS033E NEW FILE TO BE CREATED ON PRIVATE VOLUME ALREADY EXISTS IN F1 LABEL AREA

## DMS033F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS033F FILE LOCKED BY ANOTHER TASK

### Meaning

The file is locked by another task by means of a
SECURE-RESOURCE-ALLOCATION
or /SECURE command.

## DMS0330

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

Warranty : NO

DMS0330 REQM ERROR

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0331

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0331 OPERAND ERROR

### Meaning

Either the operand values defined for the $DCACALL interface are invalid
or
there was an internal CMS error condition.
Secondary return code (hexadecimal):
04: A lock request was not successful or a CMS operation
on a Net-Storage timed out.
08: An invalid operation code was defined.
0C: The caller has violated the rules governing CMS protocols.
10: There are various possible reasons for the error:
- the operand <catid> is either missing or invalid
- the requested catalog is not accessible
- user table access returns the error code 'BAD CAT ID'.
14: The JOIN file contains no entry for the user ID specified in the
operation.
1C: The operand <pathname> does not conform to the syntax rules
(e.g. file name exceeds maximum length).
20: There are various possible reasons for the error:
- the catalog entry is invalid, e.g. shorter than the minimum length
or longer than the maximum length
- a required catalog entry has not been supplied.
24: There are various possible reasons for the error:
- the operand <userid f1> has not been specified
- the F1 operation code is invalid
- the DEVICE operand is either missing or invalid
- the DEVICE operand and the device type in the catalog entry are
not identical
- the requested private disk is not available.
28: CMS tried to read the LOGON environment of the caller. This attempt
was rejected with an error code (only possible in conjunction with
remote CMS operation).
2C: The attempt to access a user table was rejected with an error code.
30: A dynamic request for class 4 or class 5 memory was rejected with an
error code.
34: An error was detected in the password validation for the calling
remote host and the requested host:
- the LOGON passwords are different
- the encryption methods are different.
38: The specified LBN exceeds the number of catalog blocks.
3C: The specified path name is partially-qualified, but the operation
requires a fully-qualified path name.
58: The calling user has no entry in the JOIN file of the requested
catalog.
5C: A task has attempted to initiate another read operation although it
has already locked the file or JV name (check the CLEXCL operand)
68: In the DCACALL call the operand ACL is invalid.
74: An operation for a SM pubset has not been correctly restricted to a
subcatalog.

### Response

The above secondary return codes provide information on the errored
operand
and suggest remedial action. If a different error occurs, contact the
system administrator.

## DMS0332

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0332 FILE LOCKED

### Meaning

The file is locked by another task.

### Response

With SPD: locked catalog entries must be unlocked by the system operator
by means of /UNLOCK-DISK,*UNKNOWN.

## DMS0333

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0333 REQUESTED FILE NOT CATALOGED

### Meaning

The requested file has not been cataloged in the pubset.
For the file or job variable (JV) no catalog entry could be found.

### Response

Correct the error and try again.

## DMS0334

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0334 Internal error in the Catalog Management System

### Meaning

An internal error has occurred in the Catalog Management System.
A SERSLOG entry or a system dump has been generated to
facilitate diagnosis.

### Response

Contact the system administrator.

## DMS0335

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

Warranty : NO

DMS0335 THE CATALOG ENTRY OF THE SPECIFIED FILE IS NOT ACCESSIBLE AS FILE PROTECTION IS ACTIVE. COMMAND REJECTED

### Meaning

The user tried to access a catalog entry of a file which he/she is not
authorized to access owing to its protection attributes.
One of the following protection mechanisms can be active:
- standard file protection
- simple access control (Basic ACL)
- profile protection (GUARDS).

### Response

Contact the owner to change the access right if necessary.

## DMS0336

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0336 DEADLOCK WARNING

### Meaning

This return code is set if a file could not be locked after waiting about
ten minutes and the task has already locked another file.

### Response

Determine who has locked the file and take care that the lock will be
removed.

## DMS0337

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0337 SYNCHRONIZATION ERROR IN CATALOG MANAGEMENT

### Meaning

When creating a new catalog entry or extending an existing one, a new
catalog block is required but none is available.
The system administrator has already received message DMS0339.

### Response

Contact the system administrator.

## DMS0338

Destination: CONSOLE Routing code: R Weight: 99

Warranty : NO

DMS0338 Warning: Pubset '(&00)' has only (&01) free blocks in catalog file '(&02)'. Number of blocks allocated = (&03).

### Meaning

This message is issued if there are only 4 to 7 catalog blocks still
available in the catalog (&02).

### Response

The system administrator has to increase the size of the catalog by means
of the command /MODIFY-FILE-ATTRIBUTES.
The new size takes effect immediately.

## DMS0339

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

Warranty : NO

DMS0339 Pubset: (&00), insufficient catalog space available. (&01) block(s) used. Extend or restructure the catalog file '(&02)'! System administrator informed? Reply (Y=Yes).

### Meaning

This message is issued by CMS if no free block can be assigned in the
catalog (&02) on pubset (&00).
(&01): number of blocks reserved in the catalog.

### Response

Request the system administrator to extend the catalog file by means
of the command /MODIFY-FILE-ATTRIBUTES.
The command does take effect immediately.
If an extension of the catalog is not possible it has to be restructured.
This may be done by deleting files or users in the pubset. The pubset
may also be restructured by HSMS (backup / init pubset / restore), which
will heighten the filling degree of the catalog blocks, so that some
catalog blocks will get free for newly created files.
Y: the system administrator has been informed and has extended or
restructured the file.

## DMS035A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS035A IMPORT-PUBSET task for pubset/volumeset '(&00)' could not be created. Import processing aborted with error code X'(&01)'.

### Meaning

(&00): Id of pubset/volumeset
(&01): Errorcode:
01 Interface error at task creation.
02 The maximum number of jobs in the system has
already been reached.

### Response

Contact the system administrator and request diagnostic material,
or try again later.

## DMS035B

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

Warranty : YES

DMS035B IMPORT PUBSET TASK WITH TSN '(&00)' FOR PUBSET WITH PUBSET ID '(&01)' HAS BEEN CREATED AND STARTED

## DMS035C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS035C EXPORT-PUBSET task for pubset/volumeset '(&00)' could not be created. Export processing aborted with error code X'(&01)'.

### Meaning

(&00): Id of pubset/volumeset
(&01): Errorcode:
01 Interface error at task creation.
02 The maximum number of jobs in the system has
already been reached.

### Response

Contact the system administrator and request diagnostic material,
or try again later.

## DMS035D

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

Warranty : YES

DMS035D EXPORT-PUBSET TASK WITH TSN '(&00)' FOR PUBSET WITH PUBSET ID '(&01)' HAS BEEN CREATED AND STARTED

## DMS035E

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS035E Cache buffer cannot be created or connected on import of pubset/volumeset '(&00)'. Error Code '(&01)'

### Meaning

'(&01)': Error Code (hexadecimal):
04 the subsystem to serve the cache medium is not available.
08 the definition of the cache configuration in the MRSCAT entry is
not allowed:
- one of the volumes of the pubset/volumeset is a fastdisk (SSD)
or a GS volume
- the requested cache medium is defective (defective ES/GS partition
or IO error of cache control) or the control device is not
attached.
- defined cache medium in the MRSCAT is not available
- Single buffering not allowed: A cache buffer in the GS in
single buffering mode must not be added to a pubset/volumeset
in the DRV mode.
- the required cache size is not defined
0C no cache buffer reserved for shared pubset: a cache buffer in
a different cache medium or with a different security resp.
with a different GS-UNIT number is already assigned to the
pubset on another host.
10 double buffering not possible: the specified cache medium is suitable
only for single buffering.
14 single buffering is not allowed: when pubset/volumeset is running
with GS in DRV mode. A cache buffer with single buffering must
not created.
DRV: Dual Recording by Volume.
18 lack of system memory.
1C system memory saturation during cache buffering.
20 The last pubset session was terminated abnormally without saving
the write buffer cache contents to disk.
It is no longer possible to connect this cache.
Possible reasons:
- the cache buffer has been deleted with /FORCE-DESTROY-CACHE
and doesn't exist no longer.
- the cache buffer has been created in GS and the GS is not
available or not connected
- 'FORCE-IMPORT=BY-OPERATOR' is set in MRSCAT and the operator
answered message DMS1350 with 'N' (No) or
- 'FORCE-IMPORT=NO' is set in MRSCAT.
24 a cache buffer is already connected to the pubset/volumeset or
to individual disks via the ADM-PFA interfaces of PCA or DAB.
28 For pubset/volumeset (&00) a cache buffer is still defined in
the specified cache medium. It is therefore not possible to
create a new cache buffer.
2C DPSIMPO calls DPSCMGR (cache-manager) with invalid params
30 DPSIMPO calls DPSCMGR with invalid functioncode
34 MRSCAT of SF pubset/volumeset (&00) doesn't exist
38 MRSCAT of SM pubset belonging to volumeset (&00) doesn't exist
3C a cache manager for the SF pubset/volumeset (&00) is already
referenced in the MRSCAT
40 function REPAIR_TSOSCAT cannot be executed for a slave
44 the SF pubset imported by SMPGEN still has an old cache buffer
48 internal error, serslog entry written by cache management
4C A cache buffer in a DAB medium is still assigned to the pubset.
The cache buffer cannot be connected, because
- it was created in version < OSDV4 and is actually imported in
a version >= OSDV4
- it was created in version >= OSDV4 for an exclusively imported
pubset and the pubset is actually imported as shared pubset or
vice versa

### Response

Response:
'(&01)': Error Code (hexadecimal):
04 load subsystem and try again.
08 - delete cache configuration: fastdisks and GS volumes are high
performant without caching
- attach the control device;
in case of a HW error message inform the system engineer;
perhaps repeat with SIZE-TOLERANCE=YES
- make the cache medium available
- set GS-UNIT=DUAL for the cache buffer in the MRSCAT entry
(requirement: two GS units).
- update cache size with /MODIFY-CACHE-ATTRIBUTES
10 correct and try again.
14 set GS-UNIT=DUAL for this cache buffer in the MRSCAT
(requirement: two GS units)
18 check the cache medium; if still space available in the
cache medium but not as much as requested
reduce the cache size or set SIZE-TOLERANCE=YES
20 - repeat with FORCE-IMPORT=BY-OPERATOR
- make GS available and try /IMPORT-PUBSET again
24 disconnect the cache buffer via the ADM-PFA interface of PCA or
DAB and try /IMPORT-PUBSET again.
28 delete the old cache buffer with /FORCE-DESTROY-CACHE
(PFA) or /STOP-DAB resp. /FORCE-STOP-DAB or /STOP-CONTROLLER-CACHING
resp. /FORCE-CONTROLLER-CACHING-STOP (ADM-PFA) and try
/IMPORT-PUBSET again.
2C,30 internal error (serslogentry DMS13C6)
34,38 internal error
3C delete MRSCAT
40 internal error
44 import the SF pubset and export it again
48 internal error
4C Connect the cache buffer by importing the pubset in the old
environment (BS version resp. shared modus), export the pubset
and import it again in the actual environment.

## DMS035F

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

Warranty : NO

DMS035F HOME PUBSET WITH PUBSET ID '(&00)' CONTAINING ALL IMPORTANT FILES FOR SYSTEM COULD NOT BE IMPORTED. STARTUP ABORTED

### Meaning

During startup an error has occurred when attempting to import the home
pubset with pubset ID (&00).
Since this home pubset contains all the files which are important for the
system, startup was aborted.

### Response

Contact the system administrator and request diagnostic material.

## DMS0350

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0350 ILLEGAL ATTEMPT TO IMPORT ALREADY ACCESSIBLE PUBSET WITH PUBSET ID '(&00)'. COMMAND TERMINATED

### Response

Check the status of the pubset with the specified pubset ID and
change it, if possible; then try again.

## DMS0351

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : YES

DMS0351 '(&00)' processing for pubset '(&01)' not processed because of error with error code '(&02)'

### Meaning

(&00): 'IMPORT-PUBSET' or 'EXPORT-PUBSET'
(&01): pubset id
(&02): error code with &00 = IMPORT-PUBSET
'01': import pubset in process
'02': export pubset in process
'03': Pubres/Volres used by PVSREN
error code with &00 = EXPORT-PUBSET
'03': import pubset in process
'04': pubset is imported by SMPGEN
'05': SM pubset is imported internally
'06': master change in process
'07': watchdog does not allow export pubset
'08': explicit volumeset export is not allowed
'09': Export of Control Volume Set is not allowed as the
entire SM pubset is imported.

### Response

measures on error code '(&02)':
'01'-'06': wait for import/export end
'03' : IMPORT processing: if the pubset is being
renamed by PVSREN or being restored by means
of command /RESTORE-PUBSET-FORM-SNAPSET wait
for processing to be completed; otherwise check
if renaming of pubset by PVSREN
or restoration of pubset by means of
command /RESTORE-PUBSET-FROM-SNAPSET needs to be
restarted.

## DMS0352

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0352 PUBSET WITH PUBSET ID '(&00)' CANNOT BE IMPORTED BECAUSE OF INTERNAL ERROR '(&01)'.

### Meaning

(&00): Pubset Id
(&01): Error code:
01: Error on MRSCAT access
02: Previous EXPORT terminated with errors

### Response

Contact the system administrator.

## DMS0354

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0354 Command EXPORT-PUBSET for pubset '(&00)' cannot be processed, because snapsets belonging to the pubset are being imported.

### Meaning

(&00): catalog id

### Response

Retry command later.

## DMS0355

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0355 Same request was already issued for pubset '(&00)'. Command not processed

### Meaning

The same command for the pubset with pubset ID (&00) was already
issued:
- /EXPORT-PUBSET ...,TERMINATE-JOBS=NO or =YES,
- /FORCE-PUBSET-EXPORT,
- /CANCEL-PUBSET-EXPORT.

### Response

Wait until the pubset has been exported or enter allowed command.
If an error occurred during exportation, enter an /EXPORT-PUBSET
...,TERMINATE-JOBS=YES command, followed by a /FORCE-PUBSET-EXPORT
command.

## DMS0356

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0356 REQM ERROR DURING STARTUP WHEN IMPORTING PUBSET WITH PUBSET ID '(&00)'

### Response

Contact the system administrator and request diagnostic material.

## DMS0357

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS0357 ADDITIONAL VOLUME '(&00)' DOES NOT HAVE HIGH-AVAILABILITY. EXTEND PUBSET WITH ID '(&01)'? REPLY (Y=YES; N=NO)

### Meaning

This message is issued if, during IMPORT-PUBSET processing, adding a new
volume would remove the pubset attribute "homogeneous high-availability".

### Response

Y: the pubset is extended to include the additional volume.
N: the IMPORT-PUBSET processing is aborted.

## DMS0358

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0358 '/EXPORT-PUBSET TERMINATE-JOBS=YES' TASK RECEIVED. ALL TASKS USING PUBSET WITH PUBSET ID '(&00)' WILL BE TERMINATED

### Meaning

The termination of all tasks using this pubset is initiated by the
TERMINATE-JOBS=YES operand of the /EXPORT-PUBSET command. In the case
of shared pubsets this may also affect tasks working with other hosts.
(&00): pubset ID.

## DMS0359

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0359 WARNING: SYSTEM ERROR WHEN RELEASING CLASS (&00) MEMORY BUT TASK CONTINUED

### Meaning

The attempt to release superfluous class 4 or class 5 memory failed due
to a system error. Class 4 memory will be released at shutdown,
class 5 memory will be released at the end of the job.
(&00): 4 or 5.

### Response

Contact the system administrator and request diagnostic material.

## DMS036A

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

Warranty : NO

DMS036A PUBSET WITH PUBSET ID '(&00)' CANNOT BE EXPORTED. SHUTDOWN CONTINUED

### Meaning

During shutdown all locally available pubsets are exported.
During exportation of the pubset with pubset ID (&00) an error was
detected, with the result that this pubset cannot be exported,
however, shutdown continued.
For the pubset which cannot be exported this means simply that the system
may have to reconstruct the F5 label when this pubset is next imported.

## DMS036B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS036B Import-pubset processing for pubset '(&00)' aborted with error '(&01)' due to missing or improperly declared mrscat entry

### Meaning

The pubset with pubset ID (&00) cannot be imported. Either there is
no MRSCAT entry or the device type in the MRSCAT entry or the MRSCAT
entry itself does not match the task.
(&00): Pubset ID
(&01): cause of error
01, missing MRSCAT entry
02, MRSCAT entry of a volumeset
03, no devicecode specified
04, control volumeset not specified
05, pubset type does not match task
06, MRSCAT entry not of type volumeset
07, volumeset MRSCAT entry with wrong SM pubsetid
08, import with conversion to a SF pubset for a control
volset, import with conversion to a SF pubset for a
SM pubset, or import without conversion for a not yet
fully converted volumeset

### Response

Create MRSCAT entry and supply device type in the MRSCAT entry for
the pubset affected or define the MRSCAT type correctly and reenter
the /IMPORT-PUBSET command correctly.

## DMS036C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS036C THERE IS NO EXPORT PUBSET PROCESSING ACTIVE FOR PUBSET WITH PUBSET ID '(&00)' THAT CAN BE CANCELLED USING /CANCEL-EXPORT-PUBSET COMMAND. COMMAND NOT PROCESSED

## DMS036D

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS036D ERROR TYPE '(&00)'. COMMAND FOR PUBSET WITH PUBSET ID '(&01)' IS ILLEGAL AT THIS TIME AS PUBSET IS BEING EXPORTED. PROCESSING ABORTED

### Meaning

For the pubset with pubset ID (&01) an EXPORT-PUBSET processing
is active. The command is illegal at this time, because
it was entered in one of the following possible situation:
Error type (&00):
1) '/EXPORT-PUBSET ...,TERMINATE-JOBS=NO' after
'/EXPORT-PUBSET ...,TERMINATE-JOBS=YES' or
/FORCE-PUBSET-EXPORT or /CANCEL-PUBSET-EXPORT
2) '/EXPORT-PUBSET ...,TERMINATE-JOBS=YES' after
/FORCE-PUBSET-EXPORT or /CANCEL-PUBSET-EXPORT
3) /FORCE-PUBSET-EXPORT after /CANCEL-PUBSET-EXPORT
or without prior '/EXPORT-PUBSET ...,TERMINATE-JOBS=YES'.

### Response

Wait until the pubset has been exported or enter allowed command at this
time. If an error occurred during exportation,
enter an '/EXPORT-PUBSET ...,TERMINATE-JOBS=YES' command,

## DMS036E

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS036E '/FORCE-PUBSET-EXPORT' only permitted after '/EXPORT-PUBSET ..., TERMINATE-JOBS=YES' for Pubset '(&00)'. Command terminated.

### Meaning

/FORCE-PUBSET-EXPORT causes the immediate exportation of this pubset
without waiting for the termination of all its applications. For
this reason this command should be used only if the EXPORT-PUBSET
is in a permanent wait state due to an error.

### Response

Enter '/EXPORT-PUBSET ...,TERMINATE-JOBS=YES' followed by
'/FORCE-PUBSET-EXPORT', if still necessary.

## DMS036F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS036F DURING STARTUP IMPORT-PUBSET TASK WITH TASK ID '(&00)' FOR HOME PUBSET WAS ABNORMALLY TERMINATED. STARTUP ABORTED. TAKE DUMP

### Meaning

(&00): task identifier of the IMPORT PUBSET task.

### Response

Generate diagnostic material and determine the cause of the error.

## DMS0360

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0360 USE OF COMMAND RESTRICTED TO OPERATOR OR SYSTEM ADMINISTRATOR

### Meaning

This message is issued by /EXPORT-PUBSET or /IMPORT-PUBSET command
processing if a non-privileged user has entered one of these commands.

## DMS0361

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0361 INVALID OPERAND(S). CORRECT COMMAND

## DMS0362

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0362 REQM ERROR DURING '(&00)' PROCESSING. COMMAND TERMINATED

### Meaning

(&00): /IMPORT-PUBSET or /EXPORT-PUBSET

### Response

Contact the system administrator to request diagnostic material
or retry command later.

## DMS0363

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0363 Pubset '(&00)' cannot be exported because of internal error with error code '(&01)'

### Meaning

(&00): pubset id
(&01): error code
'01': A system error has occurred when accessing MRSCAT
'02': A previous EXPORT was terminated with errors
'03': watchdog error on export with masterchange
'04': watchdog error on 'Export Allowed'

### Response

Contact the system administrator and request diagnostic material

## DMS0364

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0364 ILLEGAL ATTEMPT TO EXPORT INACCESSIBLE PUBSET WITH PUBSET ID '(&00)'. COMMAND TERMINATED

### Meaning

Either the specified pubset has not been imported or it has already
been exported or there is no mrscat-entry.

## DMS0365

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0365 ERROR '(&00)' DURING PVS RECORD ACCESS ON PUBRES OF PUBSET WITH PUBSET ID '(&01)'. ERROR CODE '(&02)'. PROCESSING ABORTED

### Meaning

During PVS record access on PUBRES of pubset with pubset ID (&01)
an internal error occurred.

### Response

Contact the system administrator and request diagnostic material.

## DMS0366

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0366 Export of HOME pubset not allowed

### Meaning

An attempt was made to export the home pubset
during the current system session.

## DMS0367

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

Warranty : NO

DMS0367 NO LOCALLY AVAILABLE PUBSET CAN BE EXPORTED, DUE TO ERROR '(&00)' DURING MRSCAT OPERATION

### Meaning

Due to an error when accessing MRSCAT the locally available pubsets could
not be found. As a result, shutdown continued without any locally
available pubsets being exported. If these pubsets are subsequently
imported, the F5 labels are reconstructed.

### Response

Contact the system administrator and request diagnostic material.

## DMS0368

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

Warranty : NO

DMS0368 HOME PUBSET WITH PUBSET ID '(&00)' COULD NOT BE EXPORTED. SHUTDOWN CONTINUED

### Meaning

When importing this pubset to another system or during the next system
startup from this pubset, the system performs F5 label reconstruction.

## DMS0369

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

Warranty : NO

DMS0369 PUBSET WITH PUBSET ID '(&00)' CANNOT BE EXPORTED BECAUSE OF REQM ERROR BUT SHUTDOWN CONTINUED

### Meaning

A REQM error has occurred during shutdown processing when exporting
the pubset with pubset ID (&00).
The prevent shutdown processing will be continued.
When importing this pubset to another system or during the next system
startup from this pubset, the system performs F5 label reconstruction.

## DMS037A

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS037A WARNING: ERROR '(&00)' IN OPERATOR COMMAND SERVER PROCESSING, BUT PROCESSING CONTINUED

### Meaning

During the transfer of an operator command processing to or from an
IMPORT-PUBSET or EXPORT-PUBSET task an error occurred.
Therefore command final result may be incorrect.

### Response

Contact the system administrator and request diagnostic material.

## DMS037B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS037B Shared pubset '(&00)' not imported (errorcode '(&01)')

### Meaning

(&00): pubset ID
(&01): error code:
'01': the pubset is still being used by a slave system
'02': the pubset has already been correctly imported in master mode
by another system
'03': it is not possible to switch from slave mode to master mode
'04': the home pubset is to be imported in shared mode
'05': contradictory specifications in connection with the
shareability of the pubset between label (SVL) or MRSCAT
entry or import job
'06': no MSCF connection of type 'Closely Coupled System' (CCS)
with the specified sharer.
'07': temporarily or permanent MSCF connection error or MSCF
connection for sysid locking the pubres is down
'08': during simultaneous slave import and master export, in the
meantime the pubset is no longer imported in master mode.
'09': pubset is defined ACCESS-CONTROLLED and must be imported
in exclusive mode.
'10': pubset status inhibits pubset-import with masterchange
'11': changeover from slave to master not possible when one of the
slaves is running in a version < V11.2.
'12': subsystem MSCF is not created.
'13': subsystem MSCF is not connected, is in delete-hold or is
temporarily not available.
'14': watchdog inhibits masterchange
'15': CCOPY BCV Session has been started on the master.

## DMS037C

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS037C IMPORTATION OF SHARED PUBSET WITH PUBSET ID '(&00)' IN SLAVE MODE, INTERRUPTED. CONNECTION SETUP TO MASTER HOST CURRENTLY NOT POSSIBLE

### Meaning

Possible reasons:
1. Importation of the pubset in master mode has not been completed or has
not yet been requested.
2. The MSCF connection to the other shared MPVS users has not yet been
set up.
3. The subsystem MSCF is not available.
IMPORT-PUBSET processing of pubset (&00) is interrupted until an MSCF
connection to the master host of the pubset has been set up and the pubset
has been successfully imported.
(&00): pubset ID.

### Response

The wait state can be terminated by an /EXPORT-PUBSET command. In this
case
the pubset remains in the 'not available' state.

## DMS037D

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS037D '/EXPORT-PUBSET' ISSUED FOR PUBSET WITH PUBSET ID '(&00)'. IMPORT SLAVE PUBSET PROCESSING FOR THIS PUBSET ABORTED

### Meaning

An IMPORT-PUBSET task which is waiting for the connection to the master
host was aborted by an /EXPORT-PUBSET command.
IMPORT-SLAVE-PUBSET processing for pubset (&00) is aborted.
The pubset remains in the 'not available' state.
(&00): pubset ID.

## DMS037E

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS037E Format of volume '(&02)' inconsistent with pubset/volumeset '(&00)'. Import pubset task aborted with errorcode '(&01)'.

### Meaning

(&00): id of SF pubset or volumeset
(&01): format error
'01': PAM key volumes and NON-PAM key volumes exists. SF pubsets
or volumesets may only consist of volumes with the same PAM
key type.
'02': volumes with different minimal I/O-transfer units exist.
SF pubsets or volumesets may only consist of volumes with
the same minimal I/O unit.
'03': volumes with different minimal allocation units exist.
SF pubsets or volumesets may only consists of volumes with
the same minimal allocation unit.
'04': a volume is larger than 32 GB, but the pubset doesn't have
the attribute for large volumes.
(&02): vsn of current volume

### Response

Check volume identity, maybe initialize some volumes and try
import again.

## DMS037F

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS037F EXPORT-PUBSET PROCESSING COMPLETED (&00) FOR PUBSET '(&01)'

### Meaning

This message indicates that an EXPORT-PUBSET processing has been
completed.
If no error has occurred, the pubset is exported after this message has
been displayed. All resources (devices, memory, bourses, etc.)
have been released and may be reallocated. The pubset itself may
be imported again.
(&00): ' ' , if termination was successful or
''WITH ERRORS'', if terminated abnormally.
(&01): Pubset Id

## DMS0370

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0370 WAIT STATE TERMINATED BECAUSE /FORCE-EXPORT-PUBSET HAS BEEN RECEIVED

### Meaning

The exportation of the pubset begins immediately, without waiting
until the file lock table (FLT) contains no more entries relevant
to this pubset. That means the exportation is started even though
some of the files on this pubset are still in use.
This message is an acknowledgment for a previous /FORCE-EXPORT-PUBSET
command. No response is necessary. /FORCE-EXPORT-PUBSET is only permitted
in exceptional situations. A pubset that was exported by means of
/FORCE-EXPORT-PUBSET should never be imported again during the same
session.

## DMS0371

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0371 EXPORT-PUBSET processing of pubset '(&01)' aborted because of '(&00)'

### Meaning

(&00): cause of abortion
'01': aborted by /CANCEL-EXPORT-PUBSET command
'02': POSIX subsystem occupies pubset
'03': timeout (after 20 min) on waiting for end of
current reconfiguration
'04': POSIX task occupies pubset
'05': POSIX linkage error and occupation by POSIX
'06': POSIX temporarily unable to reduce occupations
(&01): pubsetid

### Response

The pubset is still imported and can be exported later.
For all POSIX error codes ('02','04','05','06') a call for
export pubset with terminate option will not be aborted, user
tasks are cancelled, the POSIX call is repeated internally if
necessary.
(&00): '02': stop POSIX
'03': Wait for end of current reconfiguration
'04': end all POSIX pubset occupations and
call umount for the POSIX-file-system
'06': call export pubset later

## DMS0372

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0372 Export function '(&01)' for pubset/volumeset X'(&03)' ended with error code '(&02)' in code step '(&00)'

### Meaning

(&00): unique internal error identifier
(&01): called interface with format: <include name>:<opcode>
(&02): standard returncode of called interface (hex)
(&03): id of pubset/volumeset causing the error
On calling a function while exporting a pubset/volumeset an error
occurred. The corresponding pubset export will continue. It should be
noted that calling export functions for a volumeset are possible
in ending an unsuccessful SM-pubset import.
The message is often used to give a unique report of the error
situation (interface, returncode and code step) in cases where
the most common errors of a function call are logged by
more specialized messages. But to understand the message a knowledge
of the interface together with its returncode is useful. The code
step number uniquely localizes the called function.
It remains objective to log often occurring errors in special
error messages.

### Response

As the pubset export is continued after a successful export start,
despite occurring errors, the error messages should specify which
hardware or software function caused the error.

## DMS0373

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0373 ERROR CODE: X'(&02)' DURING MODIFY OR SET JV '(&00)', WITH C'(&01)'

### Meaning

This message is issued by EXPORT-PUBSET processing.
An error (&02) has occurred when the monitoring job variable (&00)
is modified or set to a new value C'(&01).
The error will be ignored for the further processing, that means the
export pubset processing will be continued.

### Response

If the system administrator is able to eradicate the source of the error,
it is possible to set the job variable to the required value.

## DMS0374

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0374 ERROR CODE X'(&02)' DURING '(&00)' ON VOLUME '(&01)'

### Meaning

A device-specific error has occurred during EXPORT-PUBSET processing.
The message contains more detailed information
on the required action, the volume affected and the error
code received. As a rule, the pubset is no longer accessible after
display of this message.
This message does not require an immediate response.
The error code specified in the message identifies the source of the
error and implies appropriate remedial action. The F5 label will be
reconstructed when the pubset is next subjected to IMPORT-PUBSET
processing.
(&00): 'WRITE SVL AND RELEASE LABELS' or
'RESERVE LABEL AND READ SVL'
(&01): VSN of the volume.

## DMS0377

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0377 NO MEMORY FOR '(&00)'

### Meaning

A request for class 4 memory could not be satisfied.
The message contains an insert specifying the name of the required memory
area.
This message does not require a particular response or remedial action.
The EXPORT-PUBSET processing simply requests class 4 memory, i.e. the
message is only issued when there is a high degree of system address space
saturation. If the pubset is subsequently imported, the F5 labels may
have to be reconstructed.

## DMS0379

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0379 COMMAND /FORCE-PUBSET-EXPORT HAS BEEN PROCESSED

### Meaning

The message informs about the fact, that /FORCE-PUBSET-EXPORT
has been processed.

## DMS038A

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS038A JOIN FILE COULD NOT BE OPENED

### Meaning

This message is issued by IMPORT-PUBSET processing.
An error has occurred when opening the JOIN file.

### Response

The exact nature of the error was given in the previous message. This
message serves simply to confirm the abortion of IMPORT-PUBSET processing.
If importation of the pubset is still desired, the error must be
eliminated
and a new /IMPORT-PUBSET command issued. It may be possible to eliminate
the error with the aid of the 'ACTUAL-JOIN=FIRST' operand of the
/IMPORT-PUBSET command.

## DMS038B

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

Warranty : NO

DMS038B VALUE OF TIME OF LAST SESSION '(&00)' FOR PUBSET WITH PUBSET ID '(&01)' GREATER THAN CURRENT TIME OF DAY '(&02)'. CONTINUE TASK ? REPLY (Y=YES; N=NO)

### Meaning

Pubset (&01) was last used in a session which was loaded at a later
time (&00) than the currently set time (&02).
Possible reasons:
- error in time-of-day specification, or
- time reset intentionally, or
- time stamp overwritten due to system error.

### Response

Y: the IMPORT-PUBSET task is continued; the current date is entered in the
SVL (Standard Volume Label).
N: the IMPORT-PUBSET task is aborted.
Possible responses in the case of task abortion:
During startup:
1. Shutdown.
2. Set the correct time of day.
3. Retry startup.
After SYSTEM READY or an unsuccessful startup:
Request the system administrator to set an earlier date for the time
stamp in the standard volume label of the public residence by means
of DPAGE.

## DMS038C

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

Warranty : NO

DMS038C Pubset/volumeset '(&00)' imported by another system or last session terminated abnormally. Continue IMPORT-PUBSET processing ? Reply (Y=YES; N=NO)

### Meaning

The shutdown bit in the SVL (standard volume label) of the public
residence of pubset/volumeset (&00) has been set.
It is not possible to work with this pubset at the moment.
The JOIN file or the catalog may be destroyed.
Possible reasons:
- the pubset/volumeset has not been correctly exported, or
- another host is working with this pubset/volumeset, or
- one or more volumes of the pubset have been extended by means
of the command /ADAPT-PUBSET-SIZE.

### Response

Check whether another host is already working with this pubset.
Y: IMPORT-PUBSET processing will be continued.
N: IMPORT-PUBSET processing will be aborted.

## DMS038D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS038D Pubset/volumeset '(&00)' is currently locked

### Meaning

(&00): id of pubset/volumeset causing the error
During import processing, an error occured when accessing
a pubset/volumeset because the pubset/volumeset is currently
locked by another Task.

### Response

Repeat the /IMPORT-PUBSET command later.

## DMS038E

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS038E Additional volume '(&00)' available. Extend pubset/volumeset '(&01)' ? Reply (Y=yes; N=no)

### Meaning

This message is issued if, during IMPORT-PUBSET processing, a new
volume with the same ID as the imported sf pubset or volumeset is
available but does not yet belong to this pubset.

### Response

Y: the imported sf pubset or volumeset is extended to include the
additional volume.
N: the additional volume is not added to the imported SF pubset or
volumeset by IMPORT-PUBSET.

## DMS038F

Destination: CONSOLE Routing code: E Weight: 30

Warranty : NO

DMS038F IMPORT PUBSET PROCESSING COMPLETED (&00) PUBSET WITH PUBSET ID '(&01)' IN '(&02)' STATE

### Meaning

This message marks the end of IMPORT-PUBSET processing for the pubset with
pubset ID (&01).
(&00): '.' in the case of successful termination.
'WITH ERRORS.' if terminated abnormally.
(&01): pubset ID.
(&02): 'HOME-IMPORTED' the pubset is the home pubset for this host;
the data is accessible exclusively.
'LOCAL-IMPORTED' all data on the pubset is accessible exclusively
to this host.
'LOCAL-IMPORTED, SHARED, MASTER'
the data on the pubset is available. Other
hosts have access to this pubset if they
are participating in shared pubset operation.
The home computer assumes the master function for
this pubset.
'LOCAL-IMPORTED, SHARED'
the data on the pubset is available. The host
is involved in shared pubset operation as a
slave.
'REMOTE-IMPORTED' the data on the pubset is not available. There is
an MSCF connection to another host which imported
the pubset locally.
'REMOTE-IMPORTED, QUIET'
the data on the pubset is not available. The MSCF
connection to another host has been interrupted.
'INACCESSIBLE' the pubset is not available.

## DMS0380

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0380 LABEL (SVL) OF VSN '(&00)' COULD NOT BE PROCESSED IN (&02) MODE DUE TO ERROR X'(&01)'

### Meaning

This message is issued by the /IMPORT-PUBSET processing. An error has
occurred while reading or writing the standard volume label (SVL).
The message contains inserts specifying the error code and the
volume (disk) whose label (SVL) could not be read or written.
(&00): volume serial number (VSN)
(&01): error code
01, label is locked by another task or system
02, permanent I/O error
03, resource bottleneck
04, volume or exclusive access right for the disk no longer
available.
Possible reason:
an /UNLOCK-DISK command has been entered.
05, label locked by device monitoring
'xxxxxxxx' internal error: the error code of the access method is
displayed
for diagnostic purposes.

### Response

If importation of the pubset is still desired, the source of the error
has to be eliminated and then a new /IMPORT-PUBSET command issued.
Upon an internal error 'xxxxxxxx', contact the system administrator.

## DMS0381

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0381 Request for volume '(&00)' not honoured (error code '(&01)')

### Meaning

This message is issued by IMPORT-PUBSET processing. The requested
volume '&00' could not be made available. Look at code '(&01)' for
further information.
(&00): vsn of volume
(&01): error code
'01': volume &00 is acquired exclusively
'02': a drv volume cannot be sharable acquired
'03': device not available
'XXXXXXX': if the error code is a message number, you should
gain further information with '/HELP XXXXXXX'.

### Response

A pubset cannot be imported unless all the volumes it comprises are
available. The volume (&00) has to be mounted and must correspond
to the requested device type. The device type of the pubres
volume is taken from the pubset MRSCAT, that of all other volumes
is taken from the volume catalog in the SVL (there is a volume
catalog for every volumeset assigned to a SM Pubset).
The device type in the MRSCAT entry can be modified with
the /MODIFY-MASTER-CATALOG-ENTRY command.

## DMS0382

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0382 Import function '(&01)' for pubset/volumeset '(&03)' ended with error code '(&02)' in code step '(&00)'

### Meaning

(&00): unique internal error identifier
(&01): called interface with format: <include name>:<opcode>
(&02): standard returncode of called interface (hex)
(&03): id of pubset/volumeset causing the error
On calling a function while importing a pubset/volumeset an error
occurred. The pubset import will be aborted.
The message is often used to give a unique report of the error
situation (interface, returncode and code step) in cases where
the most common errors of a function call are loggod by
more specialized messages. But to understand the message a knowledge
of the interface together with its returncode is useful. The code
step number uniquely localizes the called function.
It remains objective to log often occurring errors in special
error messages.

### Response

The error can be analysed by inspecting the returncode in the
specified include, for the developer further information is available
by inspecting the step number.

## DMS0383

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0383 ERROR: X'(&02)' DURING MODIFY OR SET JV '(&00)', WITH C'(&01)'

### Meaning

This message is issued by IMPORT-PUBSET processing.
An error (&02) has occurred when the monitoring job variable (&00)
is modified or set to a new value C'(&01).

### Response

If the system administrator is able to eradicate the source of the error,
it is possible to set the job variable to the required value.

## DMS0384

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0384 CATALOG MANAGEMENT COULD NOT BE INITIALIZED

### Meaning

During initialization of catalog management for a particular pubset
a negative return code was supplied, i.e. catalog management could
not be initialized for this pubset.
The exact nature of this error is described in earlier (catalog
management) messages. This message serves simply to confirm abortion
of IMPORT-PUBSET processing.

### Response

If importation of the pubset is still desired, the source of the error
must be eliminated and a new /IMPORT-PUBSET command issued.

## DMS0385

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS0385 DIFFERENT TIME STAMPS ON PUBRES WITH VSN '(&00)' (STAMP=(&02)) AND VSN '(&01)' (STAMP=(&03)). CONTINUE ? REPLY (Y=YES; N=NO)

### Meaning

Each volume of a pubset contains a time stamp in its standard volume
label (SVL). The time stamp of each volume of this pubset is
compared with the time stamp of the public residence of this pubset.
This message is issued whenever a non-matching time stamp is detected.
One possible reason for non-matching time stamps is different pubsets,
i.e. the two volumes belong to different pubsets with the same catalog ID
(e.g. the online pubset and a backup pubset).
(&00): VSN of the public residence.
(&01): VSN of the volume being used.
(&02): time stamp of the public residence.
(&03): time stamp of the volume being used.

### Response

Y: the system administrator may enter 'Y' only if it is ensured that both
volumes belong to the same pubset. In this case the conflicting time
stamps are ignored and IMPORT-PUBSET processing continued.
N: IMPORT-PUBSET processing is aborted.

## DMS0386

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0386 Resource '(02)' not available on '(&00)' of pubset '(&01)'

### Meaning

(&00): import or export
(&01): pubset id
(&02): resource:
'01': allocating memory for error recovery
'02': allocating memory for svl
'03': allocating memory for speedcat
'04': allocating memory for user table
'05': allocating memory for message buffer
'06': allocating memory for volume list
'99': unknown resource

### Response

If the missing resource inhibits the pubset import, you should try
to import the pubset later

## DMS0387

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS0387 ERROR CODE X'(&01)' WHEN SETTING NEW TIME STAMP ON VOLUME '(&00)'. CONTINUE ? REPLY (R=RETRY AFTER CORRECTION; T=TERMINATE; I=IGNORE)

### Meaning

A new time stamp is written to the standard volume label (SVL)
of each volume in this pubset during /IMPORT-PUBSET processing.
This message is issued if the SVL could not be written.
(&00): Volume Serial Number (VSN)
(&01): error code
01, label is locked by another task or system
02, permanent I/O error
03, resource bottleneck
04, volume or exclusive access right for the disk no longer
available.
Possible reason:
an /UNLOCK-DISK command has been entered.
05, label locked by device monitoring
'xxxxxxxx' internal error: the error code of the access method is
displayed
for diagnostic purposes.

### Response

If importation of the pubset is still desired, the source of the error
has to be eliminated.
R: eliminate the error, then repeat the write operation
T: /IMPORT-PUBSET processing will be aborted
I: the error will be ignored and /IMPORT-PUBSET processing continued;
however, this inevitably leads to different time stamps in the SVL of
the volume concerned (see message DMS0385).
Upon an internal error 'xxxxxxxx', contact the system administrator
and abort processing.

## DMS0388

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0388 ERROR WHEN DEALLOCATING DEVICE '(&00)'

### Meaning

This message is issued by IMPORT-PUBSET processing and does not force an
action. It will only be issued if the IMPORT PUBSET processing is aborted
due to a previous error.
The message is a note that the allocation of a device could not be
deallocated.

## DMS0389

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0389 ERROR CODE X'(&01)' WHEN READING F5 LABEL OF VOLUME '(&00)'

### Meaning

When setting up the tables for the disk storage management routines,
the F5 labels of the volumes of the pubset must be read in. This
message is issued if an error has occurred during this read operation.
It contains inserts specifying the error code and the name of the
volume affected.

### Response

If importation of the pubset is still desired, the cause of the error
must be eliminated and a new /IMPORT-PUBSET command issued.

## DMS039A

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

Warranty : NO

DMS039A PUBSET ID: (&00), LAST /IMPORT-PUBSET WITH OPERAND 'ACTUAL-JOIN=FIRST' NOT PROCESSED. /IMPORT-PUBSET IS NOW RESTRICTED TO THIS OPERAND

### Meaning

The last import for the specified pubset, with the operand
ACTUAL-JOIN=FIRST, was terminated abnormally between the creation of the
bit map and the resetting of the PBN table in the catalog.
To avoid inconsistency in the catalog, the /IMPORT-PUBSET command can only
be entered again with the same operand.

### Response

Retry the /IMPORT-PUBSET command with the ACTUAL-JOIN=FIRST operand.
It may be necessary to determine the precise cause of the error before
it can be eliminated.

## DMS039B

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS039B Occupations of pubset '(&02)' on host with system id '(&00)' not yet released. Number of occupying tasks: '(&01)'

### Meaning

EXPORT-PUBSET processing will not export a pubset until all the
occupations on this pubset have been withdrawn.
(&00): host system id
(&01): number of tasks working with the pubset
(&02): pubset id

### Response

The TSNs of all tasks working with the pubset can be determined by
means of /SHOW-PUBSET-PARAMETERS ...,INFO=*PUBSET-OCCUPATION.

## DMS039C

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS039C '/EXPORT-PUBSET TERMINATE-JOBS=YES' TASK RECEIVED. ALL TASKS USING PUBSET WITH PUBSET ID '(&00)' WILL BE TERMINATED

### Meaning

The termination of all tasks using this pubset is initiated by the
TERMINATE-JOBS=YES operand of the /EXPORT-PUBSET command. In the case
of shared pubsets this may also affect tasks working with other hosts.
(&00): pubset ID.

## DMS039D

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS039D TASK '(&00)' IS USING PUBSET WITH PUBSET ID '(&01)'

### Meaning

The task with TSN (&00) still has references to the pubset with
PUBSET ID (&01), e.g. the file is open or the TFT entry still exists.
EXPORT-PUBSET processing will be delayed until this task has released
its references.

## DMS039E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS039E STOP CONDITION MET FOR CMS TRACER

### Meaning

This message is issued by the CMS diagnostic tool.
The STOP condition for the trace routine has been met.
The diagnostic information is available in the CMS trace table.

### Response

The trace may be reactivated with the aid of DCADITO function
RESTART TRACER.

## DMS039F

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

Warranty : NO

DMS039F SESSION TERMINATED BY SYSTEM ERROR. DURING STARTUP NO MEMORY WAS AVAILABLE FOR CREATING FILE LOCK TABLE

### Meaning

$CRASH call by DKLOCK.
The file lock table could not be created during system startup due to
memory saturation. As the file lock table only takes up two 4-Kb pages
at first, the class 4 memory space must have been used up by a system
error during system startup.

### Response

Send a tape copy of the SLED dump to maintenance. If you have
performed your own SODA analysis, the operands
BASE MINI=Y, TASK TID=ALL, UVM=Y and MEMORY CL4=Y must be specified.

## DMS0390

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

Warranty : NO

DMS0390 DKLOCK TABLES HAD TO BE RECONSTRUCTED. SERSLOG ENTRY WAS WRITTEN

### Meaning

This message is issued by the DKLOCK module. An inconsistency in internal
tables caused the recovery mechanism to be called. Further details can be
found in the SYS.SERSLOG.NNNNN file.

### Response

Evaluate the SERSLOG file and contact maintenance, if necessary.

## DMS0391

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

Warranty : NO

DMS0391 DKLOCK was called with invalid operation code

### Response

Contact system administration.

## DMS0399

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS0399 UNABLE TO LOAD PLAM. ERROR CODE '(&00)'. STARTUP ABORTED

### Meaning

During startup when attempting to import the home pubset with the
pubset ID (&00) an error occurred when loading PLAM.
Since PLAM provide access functions necessary in a running system,
startup was aborted.

### Response

Contact the system administrator and request diagnostic material.

## DMS040A

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

Warranty : NO

DMS040A LOCKED CATALOG ENTRY COULD NOT BE RELEASED

### Meaning

A DKLOCK call to unlock a locked catalog entry produced a return
code. The task had to be terminated to avoid a deadlock.

## DMS040B

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

Warranty : NO

DMS040B PUBLIC VOLUME SPACE TABLE OR F5 LABEL DESTROYED

## DMS040D

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

Warranty : NO

DMS040D ERROR WHEN WRITING USER TABLE ENTRY

## DMS040E

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

Warranty : NO

DMS040E ERROR WHEN RELEASING USER TABLE ENTRY

### Meaning

The error occurred when processing a non-temporary file.

## DMS040F

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

Warranty : NO

DMS040F ERROR WHEN RELEASING USER TABLE ENTRY

### Meaning

The error occurred when processing a temporary file.

## DMS0400

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

Warranty : NO

DMS0400 INVALID SEQUENCE OF LOGICAL HALF-PAGE NUMBERS IN CATALOG ENTRY

## DMS0401

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

Warranty : NO

DMS0401 PHYSICAL UNIT NUMBER IS NOT POSITIVE

## DMS0402

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

Warranty : NO

DMS0402 NUMBER OF UNITS IN EXTENT OF ALLOCATOR EXTENT LIST IS 0

## DMS0403

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

Warranty : NO

DMS0403 SYSTEM ERROR: INCONSISTENCY IN INTERNAL ALLOCATOR WORK AREA. SYSTEM DUMP PRODUCED

### Response

Send the system dump to maintenance.

## DMS0404

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

Warranty : NO

DMS0404 MEMORY AREA FOR PSEUDO-PVST OF PRIVATE DISK IS TOO SMALL

### Meaning

PVST: public volume space table.

## DMS0406

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

Warranty : NO

DMS0406 ERROR WHEN WRITING F5 LABEL

### Meaning

When allocating or deallocating memory space for a private disk, an
error occurred when writing back the F5 label; this may have caused
the F5 label to be destroyed.

### Response

If the F5 label on the disk has been destroyed, subsequent attempts to
allocate or deallocate memory space lead to message EXC0446 and the disk
has to be reconstructed.

## DMS0407

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

Warranty : NO

DMS0407 F5 LABEL OF PRIVATE DISK COULD NOT BE RELEASED

### Meaning

A DRSRL call requesting release of a disk returned error code 0882
(permanent I/O error). The task is aborted so that the release request
can be repeated and a potential deadlock avoided. In a few exceptional
cases the F5 label will be destroyed.

## DMS0408

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

Warranty : NO

DMS0408 F5 LABEL OF PRIVATE DISK COULD NOT BE RELEASED

### Meaning

A DRSRL call requesting release of a disk resulted in a return code.
The task is aborted so that the release request can be repeated and
a potential deadlock avoided.

## DMS0409

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

Warranty : NO

DMS0409 LOCKED CATALOG ENTRY COULD NOT BE RELEASED

### Meaning

This message is issued by DC2ALLO. A DKLOCK call requesting release of
a locked catalog entry returned error code 0334 (device inoperable).
The task must be aborted in order to avoid a deadlock.

## DMS041A

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

Warranty : NO

DMS041A ERROR IN INITIALIZATION OR OVERWRITING OF F5 LABEL

### Response

A system dump is only practical if the error did not happen during disk
initialization.
If necessary the disk has to be initialized again.

## DMS041B

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

Warranty : NO

DMS041B SYSTEM ERROR WHEN RECORDING AMOUNT OF ALLOCATED DISK SPACE OF USER DURING A SPACE ALLOCATION OPERATION

## DMS041C

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

Warranty : NO

DMS041C SYSTEM ERROR WHEN RECORDING AMOUNT OF ALLOCATED DISK SPACE OF USER DURING A SPACE RELEASE OPERATION

## DMS041E

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

Warranty : NO

DMS041E ALLOCATOR RECOVERY COULD NOT BE PERFORMED DUE TO ERROR WHEN ACCESSING MRSCAT

### Meaning

An $SNCT call resulted in a return code.

## DMS0410

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

Warranty : NO

DMS0410 ALLOCATOR REQUEST COUNTER IS NOT POSITIVE. SYSTEM TERMINATED WITH DUMP

### Meaning

The counter shows the value '0' or a negative value, even though it has
been incremented by this task. System error in SPACEMGMT.

### Response

Send the dump off for diagnosis.

## DMS0411

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

Warranty : NO

DMS0411 SYSTEM ERROR DURING DISK SPACE ALLOCATION OR DEALLOCATION

### Meaning

This system exit is activated in the following 3 cases:
1) A $RELM call issued for a work area when processing a file on private
space contained an error.
2) An attempt was made to release a PVST (Public Volume Space Table)
which was locked by another task.
3) More memory space was allocated than requested by the caller.
4) A $RELM call for a work area when processing a remote job for a public
file contained an error.

## DMS0412

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

Warranty : NO

DMS0412 ALLOCATOR REQUEST COUNTER IS NOT POSITIVE. SYSTEM ERROR AT TASK TERMINATION

### Meaning

The counter does not show a positive value, even though it has been
incremented by this task.

## DMS0413

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

Warranty : NO

DMS0413 ALLOCATOR REQUEST COUNTER IS NOT POSITIVE. SYSTEM ERROR IN ALLOCATOR SERVICES CALL

### Meaning

The counter does not show a positive value, even though it has been
incremented by this task.

## DMS0414

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

Warranty : NO

DMS0414 ALLOCATOR EXTENT BUILDER ROUTINE CALLED WITH 0 EXTENTS

### Meaning

The segment table of the F5 labels which have just been processed is
probably not consistent with the associated package table.

## DMS0415

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

Warranty : NO

DMS0415 System error during disk space allocation or deallocation for requests from slave sharers of a pubset

### Response

Take a dump and diagnose the error.

## DMS0416

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

Warranty : NO

DMS0416 ILLOGICAL CONDITION IN ALLOCATOR VOLUME SELECTION ROUTINE. SYSTEM ERROR

## DMS0417

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

Warranty : NO

DMS0417 ALLOCATOR VOLUME SELECTION ROUTINE IS LOCKED BY INVALID TID. DEFINED PVST HAS BEEN REFERENCED

### Meaning

The lock could not be released after executing the routine.
The desired PVST was referenced without problems.
TID = task identifier.
PVST = public volume space table.

## DMS0418

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

Warranty : NO

DMS0418 ALLOCATOR VOLUME SELECTION ROUTINE IS LOCKED BY INVALID TID. DEFINED PVST NOT REFERENCED

### Meaning

The lock could not be released after executing the routine.
The desired PVST was not referenced. Another attempt to reference
it should be made later.
TID = task identifier.
PVST = public volume space table.

## DMS0419

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

Warranty : NO

DMS0419 ALLOCATOR VOLUME SELECTION ROUTINE IS LOCKED BY INVALID TID. DEFINED PVST DOES NOT EXIST

### Meaning

The lock could not be released after executing the routine.
The desired PVST does not exist and could therefore not be referenced.
TID = task identifier.
PVST = public volume space table.

## DMS044A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS044A NOT ENOUGH MEMORY SPACE. PARTIAL ALLOCATION ONLY

## DMS044B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS044B CATALOG ID NOT FOUND OR SPECIFIED PUBSET NOT ACCESSIBLE

## DMS044C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS044C USER ID NOT FOUND IN JOIN FILE. COMMAND REJECTED

### Meaning

The allocator could not read or find the specified
user ID in the JOIN file.

## DMS044D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS044D NO ADDITIONAL MEMORY SPACE POSSIBLE ON SPECIFIED PUBSET. ERASE SUPERFLUOUS FILES. RETRY COMMAND

## DMS044E

Destination: CONSOLE Routing code: A Weight: 50

Warranty : NO

DMS044E INTERNAL ERROR WHEN RELEASING MEMORY SPACE OF FILE

### Meaning

Possible reasons:
- The allocator was transferred a file with length '0' for deallocation.
- The allocator inadvertently attempted to release space which was not
assigned to the file.

## DMS0441

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0441 NO DISK SPACE ALLOCATED AS NONE AVAILABLE

## DMS0442

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0442 DEVICE UNKNOWN OR NOT AVAILABLE OR DISK MUST BE RESERVED EXCLUSIVELY. COMMAND REJECTED

### Response

Correct the device type specification, or try again later, or
reserve the disk for exclusive use.

## DMS0443

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0443 OPERAND ERROR WHEN CALLING ALLOCATOR

## DMS0444

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0444 SYSTEM ERROR: (DE)ALLOCATION NOT PERFORMED DUE TO INCORRECTLY FORMATTED CATALOG ENTRY IN PARAMETER LIST

## DMS0445

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0445 PUBLIC VOLUME NOT ONLINE OR INVALID DEVICE TYPE SPECIFIED

## DMS0446

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0446 CATALOG ENTRY FULL

## DMS0447

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0447 OPERATOR CANNOT MOUNT VOLUME. $AQIR ERROR '14'

## DMS0448

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0448 INSUFFICIENT MEMORY SPACE. $REQM ERROR '04'

## DMS0449

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0449 ALLOCATOR PASSED INVALID OPERAND TO 'REQM' OR 'AQIR'

## DMS0460

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

Warranty : NO

DMS0460 CATALOG ENTRY FOR FILE '(&00)' LOCKED DUE TO ERROR

### Meaning

During reconstruction of the F5 labels an invalid device type or VSN
was found in the catalog entry for file (&00).
This message may appear several times for the same file if a number
of consecutive catalog scans are performed during startup.

### Response

The invalid entry must be analyzed, and corrected or deleted as need be.

## DMS0461

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

Warranty : NO

DMS0461 WARNING: OVERLAPPING FILES ON DISK WITH VSN '(&00)'

### Meaning

The files in question are listed in the subsequently issued
message DMS0462.

### Response

Identify the files in question and take appropriate corrective measures.

## DMS0462

Destination: USER-TASK Routing code: Weight: 09

Warranty : NO

DMS0462 File '(&00)' overlaps from PHP (&01) to PHP (&02)

### Meaning

The specified file overlaps on the disk specified in the preceding
message DMS0461.
PHP = physical half page number

### Response

Analyze the file in question and take appropriate corrective measures.

## DMS0463

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

Warranty : NO

DMS0463 OVERLAPPING FILES ON PUBSET '(&00)'. DETAILS CANNOT BE ISSUED DUE TO SHORTAGE OF CLASS 5 MEMORY

### Response

Extend main memory and restart the pubset.

## DMS0464

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

Warranty : NO

DMS0464 Disk space request on disk '(&00)' for file '(&01)' results in disk type inconsistency. Request not processed

### Meaning

The specified file starts on a private disk whose type is not
consistent with the type of disk '(&00)'.
Possible reasons:
- the PAM key type of the disks is not the same
- one disk is a GS volume and the other is not

### Response

Contact the system administrator.

## DMS0465

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

Warranty : NO

DMS0465 F5 LABEL RECONSTRUCTION FOR PVS '(&00)' COMPLETED

## DMS05AA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05AA INVALID OPERAND. COMMAND FOR DELETION NOT PROCESSED

## DMS05AB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05AB INVALID AREA ADDRESS OR INVALID LENGTH FIELD IN DMS MACRO. CORRECT PROGRAM

### Meaning

An invalid area address or an invalid length field has been specified
in the parameter list.

## DMS05AC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05AC INVALID SECOND OPERAND. COMMAND FOR DELETION NOT PROCESSED

### Meaning

The user has issued an invalid command for file deletion.

### Response

The second operand must be a valid keyword or it must be omitted.
Reenter the command with the correct operand.

## DMS05AD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05AD The file attributes were updated but the rename could not be executed. Processing terminated

### Meaning

The user attempted to rename a file in a system-managed pubset and
simultaneously to assign attributes to it that were not compatible
with the previous location (volumeset).
The file was successfully reallocated to a suitable volumeset and the
new file attributes were entered in the catalog entry. The renaming
of the file could no longer be executed, however, due to a system error
that occurred in the meantime.

### Response

Repeat the file rename operation. Inform the system administrator
if the problem persists.

## DMS05AF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05AF ONLY SYSTEM ADMINISTRATOR CAN REQUEST PASSWORDS

### Meaning

The user is not authorized to request file passwords. This message
is only displayed to non-privileged users.
The file name was fully qualified and the PASSWORD operand was
specified, but the caller is not the system administrator.

### Response

Contact the system administrator.

## DMS05A0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A0 The requested catalog entry modification is not possible while there is file data in the write-back cache

### Meaning

There is still file data in the write-back cache (for example
because the file was not closed correctly or because it was
closed with option KEEP-DATA-IN-CACHE). In this case certain
modifications of the file attributes are not allowed.
This may for example concern the following modifications:
- Modifications of performance attributes (explicitly by
IO-PERFORMANCE, IO-USAGE, DISK-WRITE or implicitly by
STORAGE-CLASS)
- Renaming
- Allocation or deallocation of disk space
- modifications that require a S0-Migration of the file

### Response

Open and close the file again in order to write all data from the cache
to the volume. Inform the system administrator if the problem persists.

## DMS05A1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A1 INVALID '(&00)' OPERAND. COMMAND NOT PROCESSED

### Response

Reissue the command in the correct format.

## DMS05A3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A3 INVALID INPUT FOR SPACE ALLOCATION. COMMAND NOT PROCESSED

### Meaning

An invalid value has been specified for the space allocation.
Possible reasons:
- A value for space allocation is not in the permissible range.
- A space allocation was specified for a tape file.
- A non-positive primary allocation and a volume was specified for a file
which does not yet have an allocation.
- A negative primary allocation was specified for a new file.
- A non-positive primary allocation was specified for the data part of
a file which does not yet have an allocation.

### Response

Reenter the command in the correct format.

## DMS05A4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A4 ILLEGAL USE OF OPERANDS 'DATA-DEVICE-TYPE', 'DATA-VOLUME' OR 'DATA-SPACE'. CORRECT COMMAND

## DMS05A5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A5 Invalid change of space contingents

### Meaning

Possible reasons:
1: An attempt was made to rename an existing permanent file with
the AVAILABILITY=*HIGH attribute into a temporary file.
The simultaneous modification of the permanent/temporary and
AVAILABILITY contingents is not possible.
2: An attempt was made to rename an existing work file (WORK-FILE=*YES
attribute) into a temporary file.

### Response

Depending on the cause:
1: First change the AVAILABILITY file attribute to *STD and then
repeat the job.
2: If necessary copy the work file as a temporary file.

## DMS05A6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A6 INVALID SECOND OPERAND. /CHANGE-FILE-LINK NOT PROCESSED

### Meaning

The second operand must be either a symbolic device name or a new
link name.

### Response

Reenter the /CHANGE-FILE-LINK command with a valid second operand.

## DMS05A7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A7 FIRST FILE NAME INVALID. COMMAND FOR COPY IGNORED

### Meaning

Possible reasons:
- The specified file name is incorrect (e.g. the user ID does not exist).
- The specified file name does not match the corresponding TFT entry
(LINK=DMCOPY11).
- The specified file generation group is empty.
- Subsystem ACS reported an error after conversion of the file name.

### Response

Reenter the command with the correct file name or
delete the corresponding TFT entry.

## DMS05A8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A8 DEVICE NOT GENERATED OR SPECIFICATION INVALID. FILE ASSIGNMENT REJECTED

### Meaning

An error has occurred during mount processing.
The requested device type does not exist in the system.

### Response

Ask the system administrator what device types have been generated
for this system.

## DMS05A9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05A9 SECOND FILE NAME IN COMMAND FOR COPY INVALID OR DOES NOT EXIST. CORRECT COMMAND

### Meaning

Possible reasons:
- The user has attempted to issue a copy command containing an invalid
second operand (filename2).
- The specified second file name does not match the corresponding TFT
entry (LINK=DMCOPY22).
- Subsystem ACS reported a syntactical error after
conversion of the second file name.

### Response

Reenter the /COPY command with a correct second file name or delete
the corresponding TFT entry.

## DMS05BD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05BD Invalid combination of file attributes and volumeset attributes

### Meaning

An attempt was made to fix a file to a volumeset by means of
physical allocation or the specification of S0-MIGRATION=*FORBIDDEN.
Due to the volumeset attributes, file attributes that are relevant
to the allocation of contingents of space had to be lifted and one
of the affected contingents of space was exhausted or unavailable.

### Response

Select a suitable volumeset or leave the volumeset selection to
the system.

## DMS05BE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05BE FILE CANNOT BE ASSIGNED TO TEMP SPACE

## DMS05BF

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS05BF FILE PASSWORD-PROTECTED. FIRST ENTER CORRECT PASSWORD VIA APPROPRIATE COMMAND, THEN REENTER COMMAND FOR DELETION

### Meaning

The command for deletion was not preceded by an /ADD-PASSWORD
command containing the correct password for the file to be deleted.

### Response

The password for the file to be deleted must be made known to the system
by means of an /ADD-PASSWORD command before deletion.

## DMS05B0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B0 NO DEVICE OF DESIRED TYPE CURRENTLY AVAILABLE. COMMAND NOT PROCESSED

### Meaning

Possible reasons:
- A device request has been rejected by the device management because
no device is currently available which corresponds to the desired
conditions (e.g. desired device type or entries in the MAREN catalog).
- A Net-Storage volume was requested, that is not available on the
specified pubset.

### Response

Contact the system administrator for a suitable device or a Net-Storage
volume and retry the command.

## DMS05B1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B1 FILE LOCKED BECAUSE CURRENTLY IN USE. RETRY COMMAND LATER

### Meaning

Possible reasons:
- The file is currently open.
- The file is involved in a concurrent copy session.

## DMS05B3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B3 ONLY SYSTEM ADMINISTRATOR IS AUTHORIZED TO DELETE FILE UNDER FOREIGN USER ID

### Meaning

Only the system administrator or the owner of a file may delete the file.
In case of TSOS restriction this is not allowed for the system
administrator.

### Response

Contact the owner or system administrator.

## DMS05B4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B4 Volume cannot be mounted.

### Meaning

The request to mount a volume was rejected.
Possible reasons:
- As it was not possible to mount the volume, the operator answered
the preceding mount message with 'NO'.
- Access to the volume was denied by MAREN.
- Access to the volume is not allowed.

### Response

Consult the operator or check the protection attributes and
availability of the volume in the MAREN catalog.

## DMS05B5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B5 Guard not available

### Meaning

A required guard does not exist or is not accessible.
Possible reasons:
- Rule container for default protection is not accessible.
- Default protection rule uses a Guard that does not exist
or is not accessible.

## DMS05B6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B6 INCORRECT TIME CONVERSION FROM UTC TO LT. PROCESSING CONTINUED

### Meaning

This message is issued if the GTIME macro for converting the time from
UTC time to LT is terminated incorrectly when output of a catalog entry
is initiated by a /SHOW-FILE-ATTRIBUTES command.
The date/time specifications converted incorrectly are indicated with
????-??-?? or ??:??:??.

### Response

Have the startup parameter file checked by the system administrator and
corrected if necessary.

## DMS05B7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B7 INVALID PATH NAME IN /SHOW-FILE-ATTRIBUTES. COMMAND NOT PROCESSED

### Meaning

Possible reasons:
- The format of the path name contains an error.
- Subsystem ACS reported an error after conversion of the file name.

### Response

Reenter the command in the correct format.

## DMS05B8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B8 SPECIFIED OPERANDS FOR CONTROLLING OUTPUT FORMAT ARE INCOMPATIBLE WITH SPECIFIED OUTPUT MEDIUM. COMMAND REJECTED

## DMS05B9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05B9 INVALID POSITIONAL OPERAND. /SHOW-FILE-ATTRIBUTES NOT PROCESSED

### Response

Reenter the command in the correct format.

## DMS05CA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05CA INTERNAL ERROR WHEN CHANGING COUNTER FOR CE CONTINGENTS. COMMAND REJECTED

### Meaning

Due to an internal error the file could not be created.

### Response

Contact the system administrator.

## DMS05CB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05CB Invalid first file name or foreign user ID specified

### Meaning

Possible reasons:
1) The first file name contains illegal characters.
2) Subsystem ACS reported an error after conversion of the file name.
3) The first file name does not exist.
4) The first file name contains a foreign user ID.

## DMS05CC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05CC FILE NAME ALREADY CATALOGED OR INVALID OPERAND. COMMAND NOT PROCESSED

## DMS05CD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05CD INVALID SECOND FILE NAME, FOREIGN USER ID IN COMMAND OR ILLEGAL ACS REPLACEMENT. CORRECT COMMAND

## DMS05CE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05CE FIRST FILE NAME NOT CATALOGED

### Meaning

The user has attempted to update the catalog entry for an uncataloged
file.

### Response

Enter the file in the catalog.

## DMS05CF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05CF FILE PROTECTED BY (CRYPTO)PASSWORD. ADD REQUIRED (CRYPTO)PASSWORD AND REENTER COMMAND

### Meaning

The user tried to modify the catalog entry of a file that is
protected by a (crypto)password, but the required (crypto)password
has not yet been added to the (crypto)password table of the task.

### Response

Add (crypto)password to the (crypto)password table
(command ADD-(CRYPTO-)PASSWORD) and reenter command.

## DMS05C0

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

Warranty : NO

DMS05C0 ERROR WHEN RELEASING DEVICE. COMMAND PROCESSED

### Meaning

An error has occurred when releasing a device. Command processing
continued after generation of a SERSLOG entry.

## DMS05C1

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

Warranty : NO

DMS05C1 UNEXPECTED ERROR DURING RELEASE OF MEMORY SPACE. COMMAND PROCESSING CONTINUED

### Meaning

A SERSLOG entry was created and the command processing continued.

## DMS05C2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05C2 FILE LINK NAME CONTAINS BINARY ZEROS. COMMAND IGNORED

### Meaning

The entry of the file link name in the operand list contains
impermissible binary zeros.

### Response

Correct the entry of the file link name and retry the command.

## DMS05C3

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS05C3 FILE TO BE DELETED IS IN USE. RETRY COMMAND LATER

### Meaning

Possible reason:
- The file is currently open.

### Response

Try again later.

## DMS05C4

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

Warranty : NO

DMS05C4 I/O ERROR DURING MESSAGE OUTPUT. COMMAND NOT PROCESSED

### Meaning

An I/O error has occurred when requesting the operator to enter the VSNs
for the file.

### Response

Reenter the command and contact the system administrator, if necessary.

## DMS05C5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05C5 'SPACE' OPTION NOT PERMITTED IN CONNECTION WITH FILES ON PRIVATE DISKS. CORRECT COMMAND

## DMS05C6

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS05C6 EXPIRATION DATE PROHIBITS DELETION OF FILE. COMMAND REJECTED

### Meaning

The expiration date is later than the current date, thus preventing
the file from being deleted.

### Response

If deletion of the file is desired, modify the expiration date
accordingly, using /MODIFY-FILE-ATTRIBUTES, or specify the IGNORE
operand when using the delete command.

## DMS05C7

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

Warranty : NO

DMS05C7 UNEXPECTED INTERNAL ERROR IN DMS

### Meaning

An internal error has occurred when processing a DMS function.
A SERSLOG entry has been written.
If possible, the function will be continued.

### Response

Evaluate the SERSLOG entry.

## DMS05C8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05C8 CE LIMIT REACHED. COMMAND REJECTED

### Meaning

This message is issued if the current CE counter exceeds the CE contingent
during creation of a catalog entry in the TSOSCAT for the user.

### Response

Delete no longer required files or ask the system administrator to
increase
the CE contingent for the user's files.

## DMS05C9

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS05C9 File not exported. Correct command

### Meaning

Only files on private volumes or files on Net-Storage volume
of the NETSTOR type can be exported. For files on Net-Storage volume
specify the Net-Storage volume and/or the storage type in addition.
Files on Net-Storage volume of the NETVOL type cannot be exported.

## DMS05DA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05DA Disk space deallocation not permitted for files with foreign user identification

### Meaning

The user can only deallocate space for files that he/she owns.
Only the system administrator may deallocate space for files on foreign
user identifications.

### Response

Correct the command and try again.

## DMS05DB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05DB THIRD OPERAND ILLEGAL OR INVALID. COMMAND FOR COPY NOT PROCESSED

### Response

Reenter the command with a valid operand.

## DMS05DC

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

Warranty : NO

DMS05DC ERROR WHEN REQUESTING MEMORY. COMMAND TERMINATED ABNORMALLY WITH DUMP

### Response

Send the dump to the system administrator.

## DMS05DD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05DD SECOND LINK NAME ALREADY EXISTS. /CHANGE-FILE-LINK IGNORED

### Meaning

The user has attempted to change a link name to one that is already
active.
A TFT entry with the new link name exists already.

### Response

Try again with a different link name.

## DMS05DE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05DE FILE NAME MISSING OR ILLEGAL. COMMAND IGNORED

### Meaning

Possible reasons:
- The file name contains illegal characters
- Subsystem ACS reported an error after conversion of the file name.

### Response

Reenter the command with a valid file name.

## DMS05DF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05DF Specification of block limit or checkpoint invalid in this environment

### Meaning

A specification of block limit or checkpoint was rejected.
Possible reasons:
- The file concerned is not a tape file.
- A volume type that is not a tape was specified.
- A file sequence number not equal to 1 was specified.
- A label type not equal to standard was specified.
- An access method not equal to SAM was specified.
- Checkpoint at block limit was specified without specifying
a block limit.

### Response

Try again with correct operands.

## DMS05D0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D0 FILE IS IN USE. RETRY COMMAND LATER

### Meaning

The specified file is locked or the modification of a file generation
group requires deletion of a locked file generation.
Possible reasons:
- The file (generation) has been opened.
- The file (generation) is involved in a concurrent copy session.

### Response

Try again later.

## DMS05D1

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

Warranty : NO

DMS05D1 ERROR WHEN REQUESTING DEVICE. COMMAND TERMINATED ABNORMALLY

## DMS05D2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D2 RETENTION PERIOD INVALID. COMMAND NOT PROCESSED

### Meaning

The retention period is rejected as invalid if no creation date is
specified in the catalog entry.

## DMS05D3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D3 INVALID GUARD NAME SPECIFIED

### Meaning

An invalid GUARD name has been detected during the syntax check.

## DMS05D4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D4 The specified file must not be protected by GUARDS

## DMS05D5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D5 SPECIFIED LINK NAME OF FILE INVALID OR MISSING. COMMAND TERMINATED

### Meaning

The link name has not been defined. There is no TFT entry with the
specified link name.

### Response

Verify the link name and try again.

## DMS05D6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D6 FILE WITH SPECIFIED LINK NAME IS CURRENTLY OPENED. COMMAND IGNORED

### Meaning

The located TFT entry is currently linked with an open file.

### Response

Close the file and retry the command.

## DMS05D8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D8 FILE PASSWORD-PROTECTED. ENTER REQUIRED PASSWORD AND REPEAT COMMAND

### Meaning

The user has attempted to modify the catalog entry of
a password-protected file whose password is not contained
in the password table. The password for the cataloged file has not
been made known to the system by means of the password command.

### Response

Specify the password of the file by means of /ADD-PASSWORD
and then repeat the command.

## DMS05D9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05D9 SPECIFIED SYSTEM FILE DOES NOT HAVE ITS PRIMARY ALLOCATION

### Meaning

The /DELETE-SYSTEM-FILE command is rejected because the
system file to be deleted no longer has its primary allocation.

### Response

Enter a /SHOW-SYSTEM-FILE-ASSIGNMENTS command in order to
ascertain the status of the system file.

## DMS05EA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05EA OPERAND 'VTOC=YES' ILLEGAL IN CONJUNCTION WITH PARTIALLY QUALIFIED FILE NAME OR FILE GENERATION GROUP. COMMAND NOT PROCESSED

### Response

Reenter the command with valid operands.

## DMS05EC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05EC INTERNAL ERROR WHEN PROCESSING A CRYPTO PASSWORD

### Meaning

Possible reasons:
- An unexpected error occurred when transforming a crypto password.
- An unexpected error occurred when adding a crypto password
to the crypto password table.

### Response

Contact the system administrator.

## DMS05ED

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05ED UNRECOVERABLE I/O ERROR. COMMAND NOT PROCESSED

### Meaning

Probably a hardware error.

## DMS05EE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05EE CATALOG ENTRY CANNOT BE SET UP. CATALOG ID AND/OR USER ID TOO LONG

### Meaning

After being extended to include the catalog ID and/or the user ID, the
total length of the path name exceeds the maximum permissible value of
54 characters.

### Response

Shorten the file name so that it does not violate the maximum length
or select another catalog or user ID.

## DMS05EF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05EF Invalid protection attribute for a file on a private volume

### Meaning

The GUARDS and FREE-FOR-DELETION attributes cannot be assigned
to files on private volumes.
In addition, BASIC-ACL cannot be assigned to tape files.
An encrypted file must not be on a private disk
and must not have a tape device type.

## DMS05E0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E0 SYSTEM ERROR. FILE NOT ACCESSIBLE DUE TO SPACE PROBLEM. COMMAND IGNORED. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The catalog entry is locked because an earlier attempt to allocate or
deallocate memory space was not successful.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS05E1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E1 TASK FILE TABLE (TFT) NOT AVAILABLE OR SPECIFIED FILE NOT IN 'TFT'. OPERATION NOT PROCESSED

### Meaning

One of the following situations has arisen during task processing:
- no TFT (Task File Table) was created, or
- all TFTs were released, or
- none of the available TFTs contains the file or link name specified
in the command or macro.
Processing of the command or macro is aborted.

## DMS05E2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E2 INVALID FILE NAME. COMMAND NOT PROCESSED

### Meaning

The specified file name is invalid because:
- its generation number is not absolute, or
- the specified user ID has not been entered in the home pubset, or
- the file name contains a syntax error.
- subsystem ACS reported a syntactical error after
conversion of the file name.

### Response

Correct the file name and reenter the command, or request the system
administrator to enter the user ID.

## DMS05E3

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

Warranty : NO

DMS05E3 INCONSISTENCY IN TFT (TASK FILE TABLE)

### Meaning

An unexpected error has occurred while reading the TFT entry.
A SERSLOG entry has been created.

## DMS05E5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E5 UNRECOVERABLE I/O ERROR. COMMAND ABORTED

### Meaning

Probably a hardware error.

## DMS05E7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E7 SPECIFIED OPERAND RESERVED FOR SYSTEM ADMINISTRATOR

### Meaning

Only the system administrator is authorized to enter the operand for
changing the user ID.

### Response

Correct the command and try again.

## DMS05E8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E8 INVALID NAME FOR DISK FILE

### Meaning

The file name specified by the user in the form 'file(ABC)' (group
syntax) is illegal for disk files.

### Response

Use a correct file name, i.e. one that observes the DMS naming
conventions.

## DMS05E9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05E9 ERROR IN SCREEN OUTPUT. COMMAND ABORTED

## DMS05FA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05FA REQUESTED FILE ON PUBSET '(&00)' NOT ACCESSIBLE

### Meaning

It is only possible to access files on private volumes or on the home
or an imported public volume set.

### Response

Contact the system administrator.

## DMS05FB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05FB ONLY SYSTEM ADMINISTRATOR MAY SPECIFY FOREIGN USER ID IN FILE NAME

### Meaning

Only the system administrator may import a file into a foreign user ID.

## DMS05FC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05FC SPECIFIED USER ID DOES NOT EXIST IN HOME PUBSET. COMMAND TERMINATED

### Meaning

No default pubset ID could be found.

### Response

Reenter the command with the correct pubset ID or request the system
administrator to join the user ID to the pubset.

## DMS05FD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05FD File is Protected against write access or by retention period. Command rejected

### Meaning

The user tried to modify the catalog entry of a file which is protected
by means of the retention period or with a write protection.

## DMS05FE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05FE REQUESTED FILE(S) NOT FOUND

### Meaning

The files specified in the command are not on the volume to be imported.

## DMS05F0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F0 UNCATALOGED SECOND FILE NAME BEGINS WITH FOREIGN USER ID

### Meaning

If the target file has not yet been cataloged, its file name must not
begin with a foreign user ID.

### Response

Reenter the command once the second file has been cataloged.

## DMS05F1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F1 SECOND FILE CANNOT BE USED AS OUTPUT FILE. CHECK SPECIFIED CATALOG ENTRY OF OUTPUT FILE

### Meaning

The second specified file cannot be used as an output file because:
- it does not have enough memory space and the secondary allocation is 0
- it is a generation and the first specified file must be deleted in order
to create this generation
- both it and the first specified file are tape files.

### Response

Correct the command or macro and try again.

## DMS05F2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F2 ILLEGAL REQUEST FOR COPY OF *DUMMY FILE

### Meaning

*DUMMY files are empty files, i.e. there is nothing to be copied.
The command is rejected.

## DMS05F3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F3 REQUIRED (CRYPTO)PASSWORD IS NOT IN (CRYPTO)PASSWORD TABLE. ENTER (CRYPTO)PASSWORD AND RETRY COMMAND

### Meaning

Possible reasons:
- The user did not enter an /ADD-PASSWORD command prior to entering a
copy command for a file protected by a password.
- The user entered a copy command requiring decryption of a file
without having entered the required /ADD-CRYPTO-PASSWORD command.

### Response

Enter the password and then retry the copy command.

## DMS05F4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F4 FIRST FILE NAME IDENTICAL TO SECOND FILE NAME. COMMAND IGNORED

### Meaning

The first file name must not be the same as the second file name.

### Response

Give the second file a name other than that of the first file
and retry the command.

## DMS05F5

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS05F5 Some blocks of the source file could not be copied

### Meaning

When trying to copy a file marked as defective, some blocks could not be
copied because of a read error.
Copy file may be incomplete.

## DMS05F6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F6 FILE CANNOT BE COPIED. INPUT FILE CONSISTS OF NON-STANDARD BLOCKS OR ISAM INDEX SECTION AND DATA SECTION OF INPUT OR OUTPUT FILE ARE ON DIFFERENT PRIVATE DISKS. COMMAND IGNORED

## DMS05F7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F7 FILE GENERATION DOES NOT EXIST BUT GROUP ENTRY IS UPDATED. PROCESSING CONTINUES

### Meaning

A specific generation of an FGG has probably been physically destroyed
prior to processing (/DELETE-FILE-GENERATION with the VOLUME
operand). However, its index still exists.
The message is simply a reminder that the pointer to the deleted
generation still exists.

### Response

Continue normal processing.

## DMS05F8

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS05F8 DMS ERROR CODE '(&00)'. COMMAND PROCESSING ABORTED. IN SYSTEM MODE: /HELP-MSG DMS(&00)

### Meaning

DMS has detected an error during command processing.
For more detailed information about the DMS error code enter /HELP-MSG in
system mode or see the BS2000 manual 'System Messages' or one of the
BS2000 DMS manuals.

## DMS05F9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS05F9 FILE ATTRIBUTES OF SOURCE AND TARGET FILES INCOMPATIBLE. COMMAND NOT PROCESSED

### Meaning

The source file and the target file must have the same BLKCTRL attribute
or File-Type and FCBTYPE are not suitable.
In addition, the type of the file and the block size must be identical
when
files with the attribute BLKCTRL=DATA are copied.

## DMS0501

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0501 Requested catalog not available or wildcards in user identification

### Meaning

Possible reasons:
Case 1: The class 2 option BMTNUM=0 is set for private disks.
Case 2: When accessing files with the aid of a MSCF connection,
wildcards were used in the user identification.
Case 3: The required catalog is not imported.
Case 4: The identification of a volume set from a pubset was
specified in the pathname.
Case 5: The required volume set is not available.

### Response

Case 1: Request the system administrator to make the catalog
available. Reset the class 2 option BMTNUM to a value other
than zero.
Case 2: Repeat the call without wildcards.
Case 3: Request the system administrator to import the required catalog.
Case 4: Specify the identification of the relevant pubset.
Case 5: Ask the system administrator to make the required
volume set available.

## DMS0502

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0502 REQUESTED CATALOG IN QUIET OR HOLD STATE. WAITING TIME IS OVER. COMMAND NOT PROCESSED

### Meaning

One of the specified path names contains the pubset ID of a catalog
which is currently in the quiet or hold state. This state was not changed
during the scheduled waiting time.

## DMS0503

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0503 MRSCAT CONTAINS INCORRECT INFORMATION. COMMAND TERMINATED

### Meaning

A specific catalog ID is marked in MRSCAT as being available on a remote
processor, whereas in fact it is not.

### Response

Contact the system administrator, and request him/her to prepare
material for diagnosis.

## DMS0504

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0504 CATALOG MANAGEMENT SYSTEM ERROR. COMMAND TERMINATED

### Meaning

One of the specified path names contains the catalog ID of a remote
catalog which is currently in the quiet state. As the task is unable
to wait, the requested catalog is not available.

### Response

Contact the system administrator and request him/her to prepare
material for diagnosis.

## DMS0505

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0505 CMS RETURNED ERROR IN MRS COMMUNICATION FACILITY TO COMMAND PROCESSING

### Meaning

An error has occurred in the MSCF communication facility when accessing
a non-local system. The remote system is currently not available or a
Net-Storage volume is not accessible on the master system.

### Response

Request the system administrator to check the connection with the remote
host. At the best it will only be a temporary fault and a repeated
attempt to execute the job will be successful.

## DMS0506

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0506 DUE TO MASTER CHANGE OPERATION NOT EXECUTED

### Response

Try the command or the macro again.

## DMS0508

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

Warranty : NO

DMS0508 CHANGED SYSTEM PARAMETER '(&00)' FROM VALUE '(&01)' TO VALUE '(&02)'.

## DMS051A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS051A FILE '(&00)' ALREADY EXISTS. COPY COMMAND NOT PROCESSED

### Meaning

The specified command option precludes overwriting of the file.

## DMS051B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS051B REQUESTED USER ID NOT IN PUBSET (&00)

### Meaning

This message is issued by DMS commands. The requested user ID is not
contained in the specified pubset.

## DMS051C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS051C USER NOT AUTHORIZED TO ACCESS PUBSET '(&00)'

### Meaning

This message is issued by DMS commands. The user has tried to access a
pubset for which he has no access right.

### Response

Request the system administrator to authorize you to access this pubset.

## DMS051D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS051D LOGON PASSWORD DIFFERENT FROM LOGON PASSWORD IN PUBSET '(&00)'

### Meaning

This message is issued by DMS commands. The LOGON password in the
requested pubset is not the same as the one in the home pubset.

### Response

Request the system administrator to match up the passwords.

## DMS051E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS051E INCONSISTENCY IN PRIVATE DISK POOL OR OPERAND ERROR DETECTED. REQUEST PARTIALLY SATISFIED

### Response

In the case of an operand error, correct the error and reenter the
command; in the case of a pool error, contact the system
administrator.

## DMS0510

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0510 A FUNCTION USED INTERNALLY BY THE CATALOG MANAGEMENT REPORTS ERROR. PROCESSING ABORTED

### Meaning

Possible reasons:
- conversion between the old and the new catalog format could not be
processed.
- error during processing of the TASKLIST on the slave host in the
shared pubset network.
- error during processing of a Net-Storage volume on master host in the
shared pubset network.
- error during processing of internal tables in MSCF processing.
- error during check of access rights by SRPM.

### Response

Try function again. If the error occurs again contact the system
administrator.

## DMS0511

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0511 INCONSISTENCY IN PRIVATE DISK POOL OR OPERAND ERROR DETECTED. ALLOCATION REJECTED

### Response

In the case of an operand error, correct the error and reenter the
command; in the case of a pool error, contact the system administrator.

## DMS0512

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0512 REQUESTED CATALOG CANNOT BE FOUND. COMMAND TERMINATED

### Meaning

One of the specified path names contains the catalog ID of a catalog
that has not been entered in MRSCAT.

### Response

Either check the contents of MRSCAT and repeat the command, or request
the system administrator to add the requested catalog ID to MRSCAT.

## DMS0513

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0513 Use of specified Command or 'CATAL' macro restricted by system administrator. Command or macro rejected

### Meaning

The activated system exit routine has rejected the command or macro.

### Response

Further details of the reason for rejection can be obtained from the
system administrator, who is responsible for the system exit routines.

## DMS0514

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0514 USE OF SPECIFIED COMMAND OR 'ERASE' MACRO RESTRICTED BY SYSTEM ADMINISTRATOR. COMMAND OR MACRO REJECTED

### Meaning

The activated system exit routine has rejected the command or macro.

### Response

Further details of the reason for rejection can be obtained from the
system
administrator, who is responsible for the system exit routines.

## DMS0515

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0515 USE OF SPECIFIED COMMAND OR 'FILE' MACRO RESTRICTED BY SYSTEM ADMINISTRATOR. COMMAND OR MACRO REJECTED

### Meaning

The activated system exit routine (e.g. MAREN) has rejected the command
or macro.

### Response

Further details of the reason for rejection can be obtained from the
system
administrator, as he/she is responsible for the system exit routines.

## DMS0516

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS0516 DELETE FILE(S) '(&00)' ? REPLY (Y=YES; N=NO; T=TERMINATE COMMAND; ?=EXPLAIN ADDITIONAL OPTIONS)

### Meaning

The user can decide, in interactive mode, whether or not to execute the
specified delete task.
(&00): partially qualified file name, or name of a file, a file generation
or a file generation group.
Y: the file, file generation or file generation group will be deleted.
N: the displayed file, file generation or file generation group will
not be deleted.
T: processing of the entered delete command will be terminated.
?: explanations of the additional options will be displayed, followed
by renewed display of the task.
The meanings of the operands of the possible additional options are
analogous to those of the corresponding operands in the command and
may be looked up in the 'Control System Command Language' manual.
The following additional options may be added, separated by a comma,
to the response ('Y' or 'N' or 'T'):
,CHECK: update the current dialog form:
,CHECK=NO or =PVS or =MULTIPLE or =SINGLE or =ERROR.
,IGNORE: redefine the protection attribute before processing the delete
task:
,IGNORE=ACCESS or =EXDATE or ,IGNORE=(ACCESS,EXDATE).
,PASSWORD: reassign the passwords before processing the delete task.
A maximum of 3 (hexadecimal or numeric) passwords are
permitted.
,PASSWORD=password or =(password,...).

### Response

Enter the appropriate reply for the explanation in the 'Meaning' text.
If the reply is invalid or if an empty string is entered, the task
will not be processed.

## DMS0517

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0517 DELETE FUNCTION WITHDRAWN BY CALLER

### Meaning

'N' or 'T' was entered in response to message DMS0516. The last
task displayed has not been processed.

## DMS0518

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS0518 FILE '(&00)' ALREADY EXISTS. OVERWRITE? REPLY (Y=YES; N=NO)

### Meaning

The user can now decide, in interactive mode, whether or not the file is
to
be overwritten.

## DMS0519

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0519 COPY COMMAND WITHDRAWN BY CALLER

### Meaning

'NO' was entered in response to message DMS0518.
The command for copying was not processed.

## DMS052C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS052C UNEXPECTED TERMINATION OF DISK ACCESS FUNCTION

### Response

Contact the system administrator.

## DMS052E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS052E VOLUME LOST

### Meaning

The access right for the volume is permanently locked.

### Response

Contact the system administrator.

## DMS052F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS052F BOURSE ERROR DURING CATALOG ACCESS

### Meaning

The disk access function has returned a bourse error to catalog
management.

### Response

Contact the system administrator.

## DMS0521

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0521 ERROR DURING FILE PROCESSING. NO I/O SLOTS AVAILABLE. REENTER COMMAND LATER

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0522

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0522 SYSTEM ERROR: REQUESTED LOGICAL HALF-PAGE NOT IN FILE. CONTACT SYSTEM ADMINISTRATOR

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0523

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0523 PPAM reports error when defining pages

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0524

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0524 SYSTEM ADDRESS SPACE EXHAUSTED. RETRY COMMAND LATER

### Meaning

The routine for disk access informs the catalog processing
that there is currently not enough address space in the main memory.

## DMS0525

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0525 SYSTEM ERROR DURING CATALOG ACCESS DUE TO ILLEGAL PPAM CALL

### Meaning

The disk access function was called by catalog management with an
illegal operation.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0526

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0526 VOLUME LOCKED FOR A SHORT TIME, CATALOG NOT ACCESSIBLE. TRY AGAIN

### Meaning

The volume monitor has locked the device for a short time.

### Response

Try again. If this attempt also fails, contact the system administrator.

## DMS0527

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0527 I/O ERROR DURING CATALOG ACCESS. COMMAND NOT PROCESSED

### Meaning

The routine for disk access detected an I/O error while performing the
requested function.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0528

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0528 SYSTEM ERROR DURING CATALOG ACCESS DUE TO INVALID DEVICE ACCESS AUTHORIZATION

### Meaning

The routine for disk access detected that the disk access function has
been
called by the catalog management with an invalid device access
authorization.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0529

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0529 SYSTEM ERROR DURING CATALOG ACCESS DUE TO INVALID SLOT ADDRESS. COMMAND NOT PROCESSED

### Meaning

The routine for disk access detected an invalid slot address for the
desired disk access function.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS053A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS053A ERROR WHEN DELETING OR UPDATING F1 LABEL ON PRIVATE VOLUME

### Meaning

Either there is no more room in the F1 label area to accommodate a new F1
entry, or an operating system error has occurred.

### Response

Either delete some of the files on the private volume or reinitialize the
disk with an increased VTOC capacity.
(VTOC: Volume Table Of Contents.)
If the error persists, write an appropriate error message.

## DMS053B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS053B SYSTEM ERROR DURING FILE PROCESSING. ERROR IN DMS FUNCTION. COMMAND NOT PROCESSED

### Meaning

The routine for the catalog access returned the error code '033B'.
Reason: - error in the lock mechanism for the catalog or in the F1 label
entries.
- A catalog entry was read that is not supported in this BS2000
version.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS053C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS053C NO MORE SPACE AVAILABLE FOR CATALOG FILE ON PUBSET WITH PUBSET ID '(&00)'. COMMAND TERMINATED

### Meaning

This message is issued by DMS commands. The requested catalog has reached
its maximum size and no additional extension is possible.

### Response

Request the system administrator to allocate additional space for the
catalog file.

## DMS053D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS053D CATALOG BLOCK OR F1 LABEL BLOCK DESTROYED

## DMS053E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS053E Catalog entry already exists on private disk, Net-Storage volume or in the catalog

### Meaning

Creation of a new catalog entry was rejected, because the catalog entry
already exists in the table of contents of the private disk, in the table
of contents of the Net-Storage volume or in the catalog.
Possible reasons:
- A file was specified that is already cataloged in the table of
contents of the private disk or of the Net-Storage volume,
but not in the catalog.
- A file generation was specified, which is new according to the
file generation group entry, but its catalog entry exists.

### Response

- Take another filename.
- Take another private disk or another Net-Storage volume.
- Import the catalog entry from the private disk or from
the Net-Storage volume and delete the file as necessary.
- Create a correct file generation group entry.

## DMS053F

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS053F SPECIFIED FILE ALREADY RESERVED BY ANOTHER TASK

### Meaning

The file that the user wants to work with has already been reserved
by another user with the aid of a SECURE function.

### Response

Reenter the command later.

## DMS0530

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

Warranty : NO

DMS0530 REQM ERROR

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0531

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0531 Internal error during catalog access

### Meaning

Possible reasons:
- invalid call of catalog management system.
- general error in catalog management system.
A SERSLOG entry has been written.

### Response

Contact the system administrator.
For more detailed information see messages DMS0331 and DMS1331 (/HELP-MSG
DMS0331 and /HELP-MSG DMS1331).

## DMS0532

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0532 FILE CURRENTLY IN USE. TRY COMMAND FOR RESERVATION LATER AGAIN

### Meaning

The specified file is locked or the modification of a file generation
group requires deletion of a locked file generation.
Possible reasons:
- The file (generation) has been opened.
- The file (generation) is involved in a concurrent copy session.

### Response

Try again later.

## DMS0533

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0533 REQUESTED FILE NOT CATALOGED IN PUBSET '(&00)'. COMMAND TERMINATED

### Meaning

This message is issued by DMS commands. The requested file is not
cataloged in the requested pubset.

## DMS0534

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0534 PRIVATE DEVICE OR VOLUME CANNOT BE ALLOCATED

### Response

Reenter the command once the device or volume is available.

## DMS0535

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0535 CATALOG ENTRY OF SPECIFIED FILE NOT ACCESSIBLE DUE TO ACTIVE FILE PROTECTION. COMMAND REJECTED

### Meaning

The user attempted to access a file whose catalog entry is inaccessible
due to the current protection attributes.
One of the following protection mechanisms can be active:
- standard file protection
- basic access control (BASIC-ACL)
- profile protection (GUARDS).

## DMS0536

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0536 SYSTEM ERROR: ERROR IN DMS FUNCTION. RETRY COMMAND LATER

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS0537

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0537 NO CATALOG BLOCK AVAILABLE

### Meaning

When creating a new catalog entry or extending an existing one, a new
catalog block is required but none is available.
The system administrator has already received message DMS0339.

### Response

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

## DMS054A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS054A Requested disk space only partially allocated.

### Meaning

Possible reasons:
- not enough space was available on the disk.
- a disk was not accessible.
- the maximum possible file size in the catalog entry would be
exceeded if the memory space request was satisfied fully.
- a PAM key inconsistency was detected.

### Response

Delete the files which are no longer in use and try again or ask the
operator for the missing disk or contact the system administrator.

## DMS054B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS054B Pubset or volume set not available

### Meaning

Possible reasons:
- The pubset identification could not be found.
- The pubset is not accessible.
- The volume set is not accessible due to its processing state.

## DMS054C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS054C USER ID NOT FOUND IN USER TABLE

### Meaning

The specified user ID could not be found or read in the user table.

## DMS054D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS054D User-specific disk space contingent used up for associated file type on pubset

### Meaning

A space request has been rejected because the space restriction
defined by the system administrator was exceeded for the
associated file type on the pubset. In case of files on Net-Storage
the user has no Net-Storage usage right.

### Response

Delete files of the associated file type which are no longer needed
and repeat command or contact the system administrator. In case of
files on Net-Storage the administrator should grant the Net-Storage
usage right.

## DMS054F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS054F UNEXPECTED ERROR WHEN ACCESSING JOIN FILE. COMMAND TERMINATED

### Response

Try again.
If the error persists, contact the system administrator.

## DMS0540

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0540 The file location does not support the desired file attributes.

### Meaning

The physical or logical attributes of the desired file location
are inconsistent with the desired file attributes.
If it is a system-managed pubset,
- there is no suitable volumeset available within it or
- an S0 migration lock (S0-MIGRATION=*FORBIDDEN) is preventing the
reallocation of the file or
- an unsuitable volume or volumeset was specified.

### Response

Choose a suitable file location or cancel the S0 migration lock.

## DMS0541

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0541 Requested disk space could not be allocated

### Meaning

Possible reasons:
- Lack of space.
- An absolute allocation was requested, and the specified
space area is not completely free.
- SM-Pubset does not contain a volume set which is compatible
to the requested file attributes.
- Allocations are forbidden on specified volume set.
- Allocations are forbidden on all specified volumes.
- The file size has already reached the maximum possible value in
the catalog entry.
- An inconsistency concerning the PAM key type of the volumes
was detected.

### Response

Delete files of the concerning file type which are no more needed
and repeat command or correct specifications.

## DMS0542

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0542 DEVICE UNKNOWN OR NOT AVAILABLE OR VOLUME IN EXCLUSIVE USE

### Meaning

This message is issued by DMS modules.
Possible reasons:
- no free device, or
- requested device type not known, or
- volume only available for exclusive use.

### Response

Try again later, or
specify another (valid) device type, or
secure the volume for exclusive use.

## DMS0543

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0543 (DE)ALLOCATION FAILURE OR WRITE-PROTECTED BY PPD. COMMAND TERMINATED

### Meaning

During the processing of the allocation or deallocation function an
invalid
parameter list has been detected, or the required disk is
write-protected by PPD (Protected Private Disk).

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0544

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0544 SYSTEM ERROR: (DE)ALLOCATION NOT PERFORMED DUE TO INCORRECTLY FORMATTED CATALOG ENTRY IN PARAMETER LIST

### Meaning

The routine has attempted to perform an allocation function
and the allocator has detected an incorrectly formatted catalog entry
within its parameter list.

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0545

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0545 Specifications concerning volumes cannot be fulfilled

### Meaning

Possible reasons:
- Pubset does not contain specified volume.
- Pubset does not contain specified volume set.
- Device type does not match with volume.

### Response

Correct specifications.

## DMS0546

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0546 CATALOG ENTRY FOR SPECIFIED FILE HAS REACHED MAXIMUM SIZE. REQUEST POSSIBLY NOT COMPLETELY SATISFIED. REORGANIZE FILE BY COPYING AND RETRY COMMAND

### Meaning

In all likelihood the file has been split over too many volumes.
An attempt was made to perform an allocation function, but the catalog
entry for the specified file has already reached its maximum size.

### Response

Either reorganize the file by having it copied, or mount another
private volume and copy the file to it.

## DMS0547

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0547 OPERATOR CANNOT MOUNT REQUIRED VOLUME. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The required volume cannot be mounted.
It was tried to perform an allocation function but the operator could
not mount the required volume.

## DMS0548

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0548 SYSTEM ERROR: INSUFFICIENT MEMORY AVAILABLE. RETRY COMMAND LATER

### Meaning

It was tried to perform an allocation function but
there was not enough memory space.

### Response

If the error persists, contact the system administrator.

## DMS0549

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0549 SYSTEM ERROR: (DE)ALLOCATION FAILURE. COMMAND REJECTED

### Meaning

An attempt was made to perform an allocation function, but the
allocator presented an invalid operand list.

### Response

Contact the system administrator and request
diagnostic material, if necessary.

## DMS055A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS055A DEVICES CURRENTLY OCCUPIED. RETRY COMMAND LATER

### Meaning

A device request has been rejected by the device management because
no device according to the requirements specified is available
(e.g. device type specified or specification from MAREN-catalog).

## DMS055C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS055C CATALOG ENTRY NOT FOUND ON PRIVATE DISK OR NET-STORAGE VOLUME. COMMAND NOT PROCESSED

### Meaning

Possible reasons:
- the file specified with STATE=FOREIGN doesn't exist on
the specified volume (private disk or Net-Storage volume).
- the catalog entry of the file points to a volume (private disk or
Net-Storage volume) where the file doesn't exist.

## DMS055D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS055D There is no authorization assigned to the user ID for the physical reservation of storage on public volumes

### Meaning

Possible reasons:
- The user tried to define the location of the file on a public
volume by specifying the VOLUME or VOLUME-SET operands.
- The user tried to prevent the reallocation or migration of the file
by setting a migration lock (S0-MIGRATION=*FORBIDDEN or
MIGRATION=*FORBIDDEN).

### Response

Repeat the job without operands for the physical reservation of
disk storage or ask the system administrator to assign the relevant
authorization.

## DMS055E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS055E FOREIGN USER ID IN SPECIFIED COMMAND ONLY PERMITTED FOR CATALOGED FILES

### Meaning

Only the system administrator and the coowner may specify a file name
starting with a foreign user ID in conjunction with an uncataloged file.

## DMS055F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS055F VOLUME COULD NOT BE ALLOCATED. COMMAND REJECTED

### Meaning

Possible reasons:
1. The required volume is already used by another task.
2. The specified device type is invalid.
3. The user's own task requests another density by means of a reservation
command.
4. The operator or the system has made the tape unavailable to the user.
5. The specified volume is unknown to the system.
6. The specified volume is a Net-Storage volume
and the concerned pubset is not assigned to this
Net-Storage volume.
7. Specification of a private disk is expected
and the specified volume is not a private disk.

### Response

Case 1: None.
Case 2: Define the correct device type.
Case 3: Specify another recording density.
Case 4: Release the volume allocation and repeat the use of the volume,
if necessary.
Case 5: Specify a valid volume.
Case 6: Ask the system administrator to assign
the concerned pubset to the Net-Storage volume
or specify a Net-Storage volume
to which the concerned pubset is already assigned.
Case 7: Specify a private disk.

## DMS0550

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0550 FILE IS CURRENTLY OPEN. COMMAND TERMINATED

### Meaning

The user has attempted to enter commands in an open file.
The TFT entry in question belongs to an open file.

### Response

The file must be closed before the commands can be accepted.

## DMS0551

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0551 VSN FOR TAPE FILE ASSIGNED MORE THAN ONCE. COMMAND REJECTED

### Meaning

The erroneously repeated VSN already exists for the file in the catalog
entry or in the parameter list.

### Response

Reenter the command in the correct format.

## DMS0553

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0553 ABSOLUTE ALLOCATION REQUEST ILLEGAL. COMMAND REJECTED

### Meaning

Only the system administrator is authorized to issue an absolute
allocation request on public volumes.
Another possibility is that the VOLUME operand has not been
specified.

### Response

Either reenter the command in the correct format or request the system
administrator to allocate space.

## DMS0554

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0554 FILE NAME INVALID OR MISSING. COMMAND IGNORED

### Meaning

Possible reasons:
- The file name has an illegal format.
- If a catalog entry is to be created for a file on a private volume,
a file name must be specified.
- Subsystem ACS reported an error after conversion of the file name.

## DMS0555

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0555 SPECIFIED FILE NAME ALREADY CATALOGED

### Meaning

During the import this file must not already be cataloged in the system.

### Response

Either modify or delete the existing catalog entry and retry the command,
or use the existing catalog entry.

## DMS0556

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0556 'DEVICE' OPERAND MISSING OR INVALID. CORRECT COMMAND

### Meaning

In connection with the import of a file the device operand has either been
omitted or specified incorrectly.

## DMS0557

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0557 Invalid volume specification

### Meaning

Possible reasons:
- illegal character in the VOLUME operand
- same VSN specified both as index VSN and as data VSN
- DEVICE option specified without the VOLUME operand for a disk file
- specification of the VSN of a public volume
without the right of physical allocation on the pubset
- specification of the VSN of a public volume
together with a specification that is only allowed
for files on private volumes
- specification of the VSN of a private volume
together with a specification that is only allowed
for files on public volumes
- the number of VSNs in the catalog entry exceeds 255
- for files on Single Feature pubsets:
the catalog IDs of the VSN and the file name do not match.
- the VSN specified for a file on Net-Storage doesn't match
with the VSN of the catalog entry
- a VSN of the Net-Storage volume was specified for a file,
with a catalog entry which contains already another VSN

### Response

Correct VSN specification

## DMS0558

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0558 PUBLIC VOLUME SPECIFICATION IN 'VOLUME' OPERAND IS ILLEGAL. RETRY COMMAND WITH VALID 'VOLUME' OPERAND

### Meaning

An illegal VSN has been specified in connection with a tape file or during
an import of a file.

## DMS0559

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0559 ILLEGAL OPTION FOR VOLUME SEQUENCE NUMBERS

### Meaning

Possible reasons:
1) a volume sequence number has been specified for a file on public
volume.
2) the specified list of tape sequence numbers is not compatible with
the sequence in which the file sections are to be processed.
3) at least one of the specified tape sequence numbers is higher than
the number of entries in the VSN list of the file.

## DMS057A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS057A Invalid combination of file attributes and storage class

### Meaning

A storage class was assigned to a file (explicitly or by user
default storage class or for file generations by default storage
class of the file generation group), and the attributes in the
storage class cannot be combined with the file attributes.

### Response

Assign storage class with different attributes or suppress
assignment of storage class (STORAGE-CLASS=*NONE).

## DMS057B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS057B Invalid operand for migrated file

### Meaning

Possible reasons:
- An attempt was made to specify a volume for a migrated file
- An absolute allocation was attempted for a migrated file.
- An attempt was made to assign the attribute AVAILABILITY=*HIGH
to a migrated file, possibly implicitly by the specification
of a storage class.
- An attempt was made to set a migration lock (S0-MIGRATION=*FORBIDDEN
or MIGRATE=*FORBIDDEN) for a migrated file.

## DMS057C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS057C FILE MIGRATED BY HSMS. PROCESSING WITH HSMS NOT POSSIBLE TO THIS MOMENT

### Meaning

Possible reasons:
- Illegal access from HSMS task to a file migrated (e.g. multi migration).
- File does not exist in the migration archive.
- Look for other reasons into the HSMS report, which will be displayed
to the printer in this case.
HSMS: hierarchical storage management system.

### Response

By means of the explicit HSMS RECALL statement the restore of the data
can be initiated and a statement report will be produced.

## DMS057D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS057D FILE HAS BEEN MIGRATED ('MIGRATE' OPERAND) AND CANNOT BE RECALLED WITHOUT DELAY

### Meaning

The volume containing the data to be recalled is not available online
at present. Either the caller has not specified a waiting time or the
specified waiting time cannot be observed.
HSMS: hierarchical storage management system.

### Response

Call the HSMS subsystem and initiate the asynchronous recall operation.
On completion of the recall operation, retry the task.

## DMS057E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS057E HSMS subsystem unavailable

### Meaning

Possible reasons:
- The HSMS subsystem is required to execute the job, however,
it is not available at the moment.
- The MANAGEMENT-CLASS operand was specified for a file in a pubset
that is not administered by HSMS.
HSMS: Hierarchical storage management system.

### Response

Contact the system administrator.

## DMS057F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS057F RENAMING OF MIGRATED FILE NOT PERMITTED. COMMAND REJECTED

## DMS0570

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0570 ERASE OF *SYSOUT ILLEGAL IN INTERACTIVE MODE

### Meaning

/ERASE *SYSOUT is only permitted, for example, in an ENTER task.

## DMS0571

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0571 SYSTEM FILE DEFINED AS '*DUMMY'. ERASE CANNOT BE PROCESSED

## DMS0572

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0572 SYSTEM FILE NOT ALLOCATED TO DMS FILE. COMMAND REJECTED

### Meaning

A system file either has its primary allocation or is allocated
to another system file.

## DMS0573

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0573 SYSTEM FILE IS EMPTY. COMMAND IGNORED

### Meaning

A command for deletion has been entered for a system file which is
currently empty.

## DMS0574

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0574 DMS ERROR CODE '(&00)' OCCURRED WHEN DELETING SYSTEM FILE. COMMAND NOT PROCESSED

### Response

Analyze the DMS error code and retry the command.

## DMS0575

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0575 SPECIFIED COMMAND ACTIVE FOR SYSTEM FILE. COMMAND IGNORED

### Meaning

A /DELETE-FILE command has been entered for a system file for which an
earlier /PRINT-FILE is still active.

### Response

Suppress the earlier /PRINT-FILE by means of the operand
START-SPOOL=NO and reenter the /DELETE-FILE command.

## DMS0576

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0576 INCORRECT OPERAND VALUE OR INVALID OPERAND COMBINATION

### Meaning

Possible reasons:
- The given operand value or operand combination is not valid
within the current version of the operating system.
- Files greater or equal 32GB are among the files selected by FSTAT
(VERSION=710/800).

## DMS0577

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

Warranty : NO

DMS0577 UNRECOVERABLE ERROR DURING ACCESS TO TASK ENVIRONMENT. COMMAND OR MACRO PROCESSING ABORTED

### Meaning

The access routines used in the internal run for interrogating the task
environment report either an operand error or a configuration error.

### Response

Prepare diagnostic material and send it to the system administrator.

## DMS0578

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0578 INTERNAL ERROR WHEN CHECKING FILE SECURITY. COMMAND OR MACRO PROCESSING ABORTED

### Meaning

While checking file security an unexpected error has occurred.
The file cannot be processed.
Possible reason:
- Internal error. A SERSLOG entry has been written for diagnostic
purposes.

### Response

Contact the system administrator.

## DMS0579

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0579 Invalid operand for temporary file or work file

### Meaning

One of the specified operands is not permitted for temporary files
or work files.

### Response

Reenter the command without invalid operands.

## DMS0582

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0582 FILE CURRENTLY LOCKED OR IN USE AND NOT PROCESSABLE. COMMAND PROCESSING ABORTED

## DMS0583

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0583 ERROR OCCURRED DURING FILE RECOVERY. RECOVERY NOT PROCESSED

## DMS0584

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0584 A STATE WAS REPORTED DURING PROCESSING WHICH DOES NOT ADMIT THE FUNCTION. COMMAND PROCESSING ABORTED

## DMS0585

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0585 ERROR OCCURRED DURING CATALOG OR MRS PROCESSING. COMMAND PROCESSING ABORTED

### Meaning

Possible reasons:
- required catalog not accessible
- communication medium of MRS reports error
- memory bottleneck
- internal communication or I/O error.

## DMS0586

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0586 ACCESS OR ALLOCATION OF VOLUME CURRENTLY NOT POSSIBLE. COMMAND PROCESSING ABORTED

### Meaning

Possible reasons:
- volume not available or used by another task
- volume request rejected (e.g. by the system administrator or by the
MAREN subsystem).

## DMS0587

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0587 USE OF COMMAND ENTERED RESTRICTED BY SYSTEM ADMINISTRATOR. COMMAND REJECTED

## DMS0588

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0588 DISK ALLOCATION NOT PROCESSED. COMMAND PROCESSING ABORTED

### Meaning

Possible reasons:
- not enough disk storage
- volume not available
- memory bottleneck.

## DMS059A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS059A SPECIFIED FILE LINK NAME NOT FOUND. COMMAND IGNORED

### Meaning

Possible reasons:
- the actual link name was not defined
- there is no TFT entry with the specified link name.

### Response

Reenter the command with a valid link name.

## DMS059B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS059B FILE WITH SPECIFIED LINK NAME IS STILL IN USE. COMMAND IGNORED

### Meaning

The user has attempted to release a TFT (Task File Table) entry, but
the entry in question is currently linked with an open file.

### Response

Close the file in question and try the command again.

## DMS059C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS059C The TASK FILE TABLE entry with the link name '(&00)' could not be removed

### Meaning

Removal of task file table entries was demanded by a wildcard selection,
and the link name was selected. However, the corresponding task file
table entry cannot be removed.

## DMS059D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS059D INVALID FILE LINK NAME IN SPECIFIED COMMAND. COMMAND TERMINATED

### Meaning

The user has attempted to enter a command with an invalid link name.

### Response

Reenter the command with a valid link name.

## DMS059E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS059E INVALID SECOND OPERAND. TFT ENTRY NOT RELEASED

### Response

Reenter the command with a valid second operand.

## DMS059F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS059F SPECIFIED VALUE FOR NUMBER OF BACKUP VERSIONS INVALID

### Meaning

Possible reasons:
- Value for the number of backup versions is not in the allowed range.
- HSMS version backup is not allowed for files on private disk.
- HSMS version backup is not allowed for file generation groups (FGGs).

## DMS0590

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0590 SPECIFICATION OF DEVICE TYPE MISSING

### Meaning

An attempt was made to establish a catalog entry for a tape file or
a file on private disk respectively on a Net-Storage volume.
The device type needed therefore was not specified
nor can it be determined.
Possible reasons:
- No volume was specified, thus no device type can be determined.
- MAREN device substitution was not possible.
- The file is to be created on public disk,
but a Net-Storage volume was specified.

### Response

Complete specifications
or ask system administrator to make MAREN available
or ask system administrator to add volume to MAREN catalog respectively.

## DMS0591

Destination: CONSOLE Routing code: D Weight: 98

Warranty : NO

DMS0591 ENTER (&00) VSN(S) FOR (&01) PRIVATE (&02) VOLUME(S) (DEV=(&03)) FOR FILE '(&04)'. REPLY (<VSN>,<VSN>,...; *C=ABORTION)

### Meaning

This message is issued during file processing.
The operator is requested to supply the volume serial number of one or
more private volumes for the specified file.
(&00): DATA (private disk for ISAM data part)
(&01): number of VSNs
(&02): TAPE or DISK
(&03): device type
(&04): file name.

### Response

Specify VSN(s) or abort with '*C'.

## DMS0592

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

Warranty : NO

DMS0592 INVALID 'VOLUME' OPERAND

### Meaning

The VOLUME operand either contains an illegal character or does
not specify a private volume (e.g. the VSN is not alphanumeric).

### Response

Specify valid volume serial number(s) for the private volume(s)
and try the command again.

## DMS0593

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0593 NUMBER OF REQUESTED HALF PAGES ILLEGAL

### Meaning

In the event of absolute allocation a number of half pages was specified
which is not a multiple of the size of an allocation unit.

## DMS0594

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0594 NOT ENOUGH VIRTUAL MEMORY AVAILABLE. COMMAND ABORTED

### Meaning

There is not enough space in virtual memory to permit execution of the
command.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0595

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0595 PUBLIC AND PRIVATE VOLUMES MUST NOT BE MIXED. CHECK VSN AND CATALOG ENTRY. CORRECT COMMAND

### Meaning

The operand list contains both public and private volume serial numbers
(VSN's). A file may reside on either public or private volumes, but
not on both at the same time.

## DMS0596

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0596 SPECIFIED DEVICE TYPE DOES NOT MATCH CATALOG ENTRY FOR FILE. COMMAND IGNORED

### Meaning

The device type in the file operand list does not match the device type
in the catalog entry for this previously cataloged file.

### Response

Enter a /SHOW-FILE-ATTRIBUTES command and then retry the original
command with the correct device type.

## DMS0597

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0597 Illegal absolute space request: First page not on unit boundary

### Meaning

The specified number of the first page divided by the size of the
allocation unit must leave a remainder of 1.

### Response

Enter the command with a page allocation which begins on a unit boundary.

## DMS0598

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0598 TOO MANY OR INVALID POSITIONAL OPERANDS. COMMAND NOT PROCESSED

### Response

Refer to the appropriate DMS manual for the correct format and then retry
the command.

## DMS0599

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0599 OPERAND NOT SUPPORTED IN REQUESTED OPERATING SYSTEM VERSION

## DMS06A0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06A0 COMMAND NOT PROCESSED ON REMOTE HOST (&00). PROCESSING CONTINUED

### Meaning

(&00): catalog identifier of a remote host.
A BCAM communication error has occurred when executing the /ADD-PASSWORD
command on the specified remote host. The appropriate BCAM
error code is displayed on the operator console.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS06A6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06A6 'AUDIT' OPERAND ILLEGAL FOR THIS USER ID. COMMAND REJECTED

## DMS06A9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06A9 SOME GENERATIONS OF THIS FILE GENERATION GROUP ARE MISSING. COMMAND PROCESSING WILL BE CONTINUED WITH THE SPECIFIED GENERATIONS

### Meaning

During the processing, it becomes clear that not all generations of the
file generation group have been entered in the catalog.
Processing continued for each cataloged generation.

## DMS06B4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06B4 USER ERROR. NO GENERATION TO BE DELETED BEFORE OR AFTER SPECIFIED ONE. COMMAND TERMINATED

### Meaning

Possible reasons:
Either the generation specified in the command is
- the current one and FILE=GENERATIONS-AFTER or POS=AFTER has been
specified
- the first one and FILE=GENERATIONS-BEFORE or POS=BEFORE has been
specified
- or no generation has been specified at all.

## DMS06B5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06B5 FILE ALREADY OPEN OR CATALOG ENTRY NOT UPDATED AFTER SYSTEM ERROR

### Meaning

The file was not correctly closed when last processed.

### Response

Enter /REPAIR-DISK-FILE.

## DMS06B6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06B6 The file attributes do not match with the file generation group

### Meaning

Possible reasons:
- An attempt was made to copy or rename a file into a file generation that
does not have the same CODED-CHARACTER-SET as the file generation group.
- An attempt was made to rename a file into a file generation whose
WORK-FILE attribute does not match with the file generation group.

## DMS06B8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06B8 INVALID '(&00)' OPERAND. COMMAND NOT PROCESSED

### Meaning

An invalid (&00) operand was detected during the syntax check.

### Response

Reenter the command in the correct format.

## DMS06B9

Destination: CONSOLE Routing code: A Weight: 99

Warranty : NO

DMS06B9 The exit routine that is connected to system exit (&00) returned unexpected error code (&01)

### Meaning

Possible reason:
- The exit routine is incorrect.

### Response

Contact the system administrator so that the exit routine can be
deactivated or corrected.

## DMS06CA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06CA Invalid BASE-NUMBER specification. Processing continued regardless of the MAXIMUM, OVERFLOW-OPTION, and BASE-NUMBER operands

### Meaning

The specified base value does not denote an existing file generation.

## DMS06CB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06CB LENGTH SPECIFICATION TOO SMALL FOR ENTRY. CORRECT PROGRAM

### Meaning

The output area is too small for the required information.
Output area may be the OUTAREA and/or STOUTAR.

### Response

Check the length of the TFT entry in the RDTFT macro or of the
catalog entry in the FSTAT macro.
The caller may use a REQM to increase the memory space and a new FSTAT
call
to force output of the complete information.
Correct and recompile the program.

## DMS06CC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06CC NO FILE CORRESPONDING TO SPECIFIED OPERANDS

## DMS06CD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06CD Specified file generation group is write protected

### Meaning

A new generation can be created only if write access to the file
generation group is possible.

### Response

If possible, change protection attributes.

## DMS06CE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06CE Expiration date or deletion date specified incorrectly.

### Meaning

An invalid value was specified for at least one of the EXPIRATION-DATE,
RETENTION-PERIOD, and FREE-FOR-DELETION attributes.

## DMS06CF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06CF SPECIFICATION OF FILE GENERATION GROUP NOT PERMITTED

### Meaning

The command/macro cannot process a file generation group.

## DMS06C1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C1 NUMBER OF GENERATIONS GREATER THAN 255 OR DOES NOT MATCH 'FIRST' OR 'BASE' VALUE. COMMAND NOT PROCESSED

### Response

Correct the operands and try the command again.

## DMS06C2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C2 FILE LOCKED BY ANOTHER TASK

### Meaning

The file is currently locked by another task.

### Response

Try again later.

## DMS06C3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C3 ILLEGAL FILE GENERATION GROUP NAME. COMMAND TERMINATED

### Meaning

The user has attempted to catalog a group name which contains brackets.

### Response

Reenter the command with a valid group name.

## DMS06C4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C4 FILE GENERATION GROUP NOT YET CATALOGED. COMMAND REJECTED

### Meaning

The file generation group (FGG) has not been defined by a
/CREATE-FILE-GROUP command or by a /CATAL macro.

### Response

Enter a /CREATE-FILE-GROUP command for the FGG, then try the command
for this generation again.

## DMS06C5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C5 NAME OF FILE GENERATION GROUP TOO LONG. COMMAND NOT PROCESSED

### Meaning

The length of an FGG name must not exceed 34 characters as this would
cause
the length of an associated generation to be greater than 41 characters.

### Response

Reenter the /CREATE-FILE-GROUP command with a valid FGG name.

## DMS06C6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C6 NAME OR ATTRIBUTE OF TAPE FILE CANNOT BE UPDATED

### Meaning

The catalog entry or file name of a tape file is to be updated,
but the file already exists (it has been opened and closed normally
at least once).
Command processing is aborted.

## DMS06C7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C7 INVALID GENERATION NUMBER IN COMMAND. NUMBERS MUST BE IN UNBROKEN ASCENDING ORDER. COMMAND NOT PROCESSED

### Meaning

Generation files must be cataloged with generation numbers arranged
in unbroken ascending order.

## DMS06C8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C8 The specified file attribute can either be defined for the whole file generation group or is not permitted for file generations

## DMS06C9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06C9 Specified operands invalid for file generation group or in the wrong context

### Meaning

Possible reasons:
- An invalid value was specified for one of the BASE-NUMBER,
FIRST-GENERATION, or LAST-GENERATION operands.
- The specified values for the BASE-NUMBER, FIRST-GENERATION, or
LAST-GENERATION operands do not match semantically.
- Operands were specified for a file generation group, but the specified
file is not a file generation group.
- Operands were specified that are invalid for file generation groups.

## DMS06DA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06DA ILLEGAL COMBINATION OF PRIVATE AND PUBLIC VOLUMES FOR FILE GENERATION GROUP IN SPECIFIED COMMAND

### Meaning

The user has attempted either to create a generation on a private disk
and the file generation group resides on a public volume, or to create
a generation on a public volume or a tape and the file generation
group resides on a private disk.

### Response

If the file generation group resides on a private disk, the generation
must be created on this disk; if it resides on a public volume, it
must reside on a public volume or on a tape.

## DMS06DB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06DB The specification of a private disk is missing or in the wrong context

### Meaning

Possible reasons:
- A file generation group is to be imported from a private disk, but
the volume (VOLUME operand) or the device type (DEVICE-TYPE operand)
was not specified or specified incorrectly.
- Invalid operands or attributes were specified when creating up a
file generation group on a private disk.

### Response

Correct the command.

## DMS06DC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06DC SPECIFIED (CRYPTO)PASSWORD(S) NOT IN PASSWORD TABLE

### Meaning

The user has attempted to release one or more (crypto)passwords
that are not contained in the password table.

## DMS06DD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06DD SPECIFIED TAPE SET NAME DOES NOT EXIST. COMMAND NOT EXECUTED

### Meaning

The tape set table does not contain an entry with the specified
file link name.

### Response

Try the command again with the name of an existing tape set.
If necessary create a tape set first.

## DMS06DE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06DE FILE OR FILE GENERATION CANNOT BE COPIED INTO FILE GENERATION GROUP

### Meaning

A file generation group cannot be used as an output file in this
context.

## DMS06DF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06DF SPECIFIED OPERAND VALUES ILLEGAL OR CONTRADICTORY

### Meaning

The specification of a volume sequence number, file sequence number or
tape set is inconsistent with other specifications or with the
current file attributes.

### Response

Correct the operands and try again.

## DMS06D0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D0 SPECIFIED FILE GENERATION DOES NOT EXIST

### Meaning

An /IMPORT-FILE with SUPPORT=DISK(TYP-OF-FILE=ANY(GENERATIONS=YES)) or
a FILE macro with STATE=FOREIGN has been specified for a
non-existent generation.

## DMS06D1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D1 FILE GENERATION GROUP IS SECURED BY ANOTHER TASK

### Meaning

The file generation group is currently being used by another task.

### Response

Try again later.

## DMS06D3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D3 SPECIFICATION OF FILE GENERATION GROUP INVALID

### Meaning

The user has attempted to open a file generation group.

### Response

Correct the program and try again.

## DMS06D4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D4 ILLEGAL GENERATION SPECIFICATION OR ERASE DEFINITION FOR FILE GENERATIONS MISSING. ERASE COMMAND IGNORED

### Meaning

The user has attempted to erase a special generation of a group.

### Response

Reenter the command, defining the file generations
(younger or older) to be deleted.

## DMS06D5

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS06D5 FILE IS READ-ONLY. CHECK FILE. MODIFY ACCESS TYPE AND REENTER COMMAND

### Meaning

Read-only files cannot be deleted.

### Response

Change the catalog entry for this file to write access and try again.

## DMS06D6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D6 ERROR WHEN ERASING CERTAIN FILES. 'ERASE' NOT COMPLETELY PROCESSED

### Meaning

A partially qualified file name has been specified in the ERASE command
resp. macro.

## DMS06D7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D7 FGG COPY ERROR. COMMAND TERMINATED

### Meaning

The user has attempted to copy a file generation group into a generation
of this group.

## DMS06D8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06D8 GENERATIONS OF SPECIFIED GROUP HAVE DIFFERENT FILE ATTRIBUTES. COMMAND IGNORED

### Meaning

The user has attempted to copy a file generation group into a file, but
not all generations of the group have the same file attributes
(RECORD-SIZE, RECORD-FORMAT, BUFFER-LENGTH, ACCESS-METHOD=SAM,
BLOCK-CONTROL-INFO, CODED-CHARACTER-SET).
The /COPY-FILE command was not processed.

## DMS06EA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06EA FILE SPECIFIED IN COMMAND CANNOT BE PROCESSED. RECONSTRUCTION NOT POSSIBLE. COMMAND NOT PROCESSED

### Meaning

The file to be repaired could not be opened or read, thus making
reconstruction impossible.

## DMS06EB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06EB INCONSISTENT DATA BLOCKS STORED IN SCRATCH FILE 'S.<FILENAME-1>.REPAIR' DURING FILE RECONSTRUCTION

### Meaning

While repairing an ISAM file, inconsistent data blocks were found.
These blocks are written into a PAM file S.<FILENAME-1>.REPAIR,
the first file name being truncated to the right if necessary.

### Response

The file can be viewed and corrected with the aid of DPAGE, so that any
records that are still needed can be added to the reconstructed file.

## DMS06EC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06EC ERROR WHEN GENERATING OUTPUT FILE. RECONSTRUCTION NOT PERFORMED. COMMAND NOT PROCESSED

### Meaning

It was not possible to write all the records to the ISAM output file.

### Response

If the output file is still cataloged, check whether the space it has
been allocated is sufficient.

## DMS06ED

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06ED ERROR WHEN WRITING UNRECOVERABLE DATA BLOCKS TO SCRATCH FILE 'S. <FILENAME-1>.REPAIR'. RECONSTRUCTION CONTINUED

### Meaning

When repairing an ISAM file, the scratch file could not be processed
normally. The errored blocks due to be written to this file are ignored.

## DMS06EE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06EE FILE REPAIRED ON FILE 'REPAIR.<TSN>.<HHMMSS>'

### Meaning

The ISAM file has been repaired on file REPAIR.<tsn>.<hhmmss>.
tsn: task sequence number of the user.
hhmmss: time at which the file was accessed.
On completion of file reconstruction it was not possible to recatalog
the file or copy it into the original file.

### Response

Enter the /SHOW-FILE-ATTRIBUTES REPAIR. command in order to determine the
exact file name. Try to use this file, or to rename or copy it.

## DMS06EF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06EF Error when creating scratch file or specified destination file. Reconstruction not possible.

### Meaning

ISAM files cannot be repaired without a scratch file or a second file name
(destination file) specified in the command/macro. An error has occurred
when creating such a file. Reconstruction is not possible without
this file.

### Response

Check whether enough memory space is available or whether the
authorization of the user has changed since creation of the
source file.
Try the command or macro again, if necessary.

## DMS06E0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E0 INVALID '(&00)' OPERAND IN COMMAND

### Meaning

Possible reasons:
- The file names must be different and they must both be either
fully-qualified or partially-qualified.
- Subsystem ACS reported an error after conversion of the file name.
- An invalid user ID has been specified.
- An invalid REPAIR or SUPPORT operand has been specified.

## DMS06E1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E1 SPECIFICATION OF PARTIALLY QUALIFIED FILE NAMES IS ILLEGAL

## DMS06E2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E2 FILE CANNOT BE MADE ACCESSIBLE. FILE LOCKED

### Meaning

This message is issued by /REPAIR-DISK-FILE.

### Response

Contact the system administrator to force unlocking of the file,
if possible.

## DMS06E3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E3 NO FILE TO UNLOCK OR REPAIR

### Meaning

None of the specified files needs to be unlocked or repaired.
This message is displayed following use of the command
/REPAIR-DISK-FILES or /REMOVE-FILE-ALLOCATION-LOCKS.

## DMS06E4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E4 FILE DESTROYED

### Meaning

During the consistency check of the file it became clear either that the
data blocks have been destroyed or that a secondary key has not been
completely initialized or has been deleted.

### Response

Repair the file by means of /REPAIR-DISK-FILE.

## DMS06E5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E5 CONSISTENCY CHECK NOT POSSIBLE FOR SPECIFIED FILE

### Meaning

The specified file is not an ISAM file of the type
BLOCK-CONTROL-INFO=WITHIN-DATA-BLOCK.

### Response

Repair the file by means of /REPAIR-DISK-FILE, if possible.

## DMS06E6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E6 FILE SPECIFIED IN COMMAND IS EMPTY

### Meaning

The file which is to be reconstructed is empty, i.e. none of its pages
contains any data.

## DMS06E7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E7 RECONSTRUCTION OF SPECIFIED FILE NOT POSSIBLE WITH SPECIFIED COMMAND

### Meaning

The specified file cannot be repaired (see the section on the restrictions
on file recovery in the DMS manuals).

### Response

Check the restrictions on file recovery as given in the description of
the /REPAIR-DISK-FILE command.

## DMS06E8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E8 FOR RECONSTRUCTION OF ISAM FILE ON PRIVATE VOLUME WITH SEPARATE INDEX AND DATA BLOCKS SECOND FILE NAME MUST BE SPECIFIED

### Meaning

The scratch file for reconstruction is created on a public volume, thus
destroying the possibility of separate index and data blocks.

### Response

Create the destination file with the requested attributes and with enough
memory space. Try the command or macro again with the destination file
name
as the second file name.

## DMS06E9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06E9 NO VALID RECORD FOUND DURING RECONSTRUCTION OF ISAM FILE

### Meaning

If a second file name was specified in the command, this file is empty.

## DMS06FA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06FA A SECOND FILE NAME MAY ONLY BE SPECIFIED DURING MODIFICATION OF AN ALREADY CATALOGED FILE. COMMAND NOT PROCESSED

### Meaning

The operand for the second file name is only permissible with
STATE=UPDATE.
If no STATE operand is specified, the default value is STATE=NEW and no
second file name will be accepted.

### Response

Retry the command or macro without a second file name or specify
STATE=UPDATE.

## DMS06FB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06FB Specification of an execute password or an execute privilege is not allowed for a file generation group

### Meaning

Programs or procedures saved in a file generation are generally
unexecutable. Therefore it makes no sense to specify an execute password
or execute privilege for file generation groups.

### Response

Repeat the command without the invalid specification.

## DMS06FC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06FC UNEXPECTED I/O ERROR DURING IMPORT. COMMAND NOT COMPLETELY PROCESSED

### Meaning

A list of all imported files will be displayed upon request.
Possible reason:
- A file larger than 32 GByte is to be imported on a pubset, where
that is not allowed.

### Response

Check the private disk or the Net-Storage volume to be imported.

## DMS06FD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06FD Invalid address of parameter area

### Meaning

Parameter area:
- memory not allocated
- wrongly aligned
- invalid interface identification
- non-XS interface cannot be used in XS addressing mode.

### Response

Correct the program and try again.

## DMS06FF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06FF BCAM CONNECTION SEVERED. COMMAND NOT PROCESSED

### Meaning

The user has attempted to execute a DMS command or macro on a
remote host corresponding to the specified path name.

### Response

Enter the /SET-RFA-CONNECTION command.
If the error persists, contact the system administrator.

## DMS06F0

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS06F0 Do you want to force unlocking of file '(&00)'? Reply (Y=YES; N=NO)

### Meaning

This message is sent to the system administrator in interactive mode
only.
It follows the warning that the file is locked.
The system administrator is now offered the opportunity of forcing the
file to be unlocked.

### Response

Y: unlocking of the file is forced.
Before doing so, the system administrator should ensure that this
will not adversely affect any users.
N: unlocking of the file is not forced.

## DMS06F1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F1 Only file locks for home system have been reset

### Meaning

The file to be unlocked is still affected by locks from another system
which cannot be reset.

### Response

Contact the operator.

## DMS06F2

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

Warranty : NO

DMS06F2 CANCELLATION OF FILE LOCK REQUESTED FOR FILE '(&00)'

### Meaning

This message informs the operator that the system administrator has
requested cancellation of the file lock for a disk file.

## DMS06F3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F3 FILE '(&00)' UNLOCKED

## DMS06F4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F4 FILE '(&00)' REPAIRED

## DMS06F5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F5 CERTAIN OPERANDS IN COMMAND OR MACRO ARE RESTRICTED TO SYSTEM ADMINISTRATOR OR PRIVILEGED USER. CORRECT OPERANDS

## DMS06F6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F6 ILLEGAL KEYWORD IN COMMAND. CORRECT COMMAND

## DMS06F7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F7 ILLEGAL VALUE SPECIFIED FOR '(&00)' OPERAND

### Meaning

The value specified for the (&00) operand is illegal.

### Response

Eliminate the error and reenter the command.

## DMS06F9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS06F9 EITHER FILE NAME OR 'VOLUME' OPERAND MUST BE SPECIFIED. CORRECT COMMAND

## DMS060A

Destination: USER-TASK Routing code: Weight:

Warranty : YES

DMS060A Block '(&00)' on disk '(&01)' is part of file '(&02)'

## DMS060B

Destination: USER-TASK Routing code: Weight:

Warranty : YES

DMS060B Block '(&00)' on disk '(&01)' is not part of any file

## DMS060C

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

Warranty : NO

DMS060C The catalog entry for the file '(&00)' has reached maximum size. Additional disk defects cannot be recorded

### Response

Export pubset and either exchange defective volumes or repair them
with the utility VOLIN.

## DMS060D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS060D Invalid file name specified for a reference file

### Meaning

Possible reasons:
- The specified reference file does not exist.
- The reference file catalog entry cannot be accessed due to the active
file protection.
- The specified file name is syntactically incorrect or an error was
reported by ACS when using the ACS subsystem.

### Response

Check the file name.

## DMS060F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS060F Command deprecated

### Meaning

Command is no longer supported in the current version
For compatibility reasons, the command is still allowed in procedures
and batch jobs, but has no effect.

### Response

Remove the command from the command files for procedures and jobs.

## DMS0606

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0606 VOLUME REQUEST REJECTED BY MAREN SUBSYSTEM

### Meaning

Possible reasons:
- The volume password is invalid or missing.
- The volume belongs to a foreign user ID and is not shareable.
- The volume has been lent out.
- The volume has an illegal status in its archive entry (e.g. 'defective'
or 'free').
- The volume is reserved for ARCHIVE applications, but the requesting task
is not an ARCHIVE subtask.
- The volume is currently locked by another task on the home computer.
- The volume is currently locked by another task on a remote host.
- The VSN does not exist in the MAREN catalog.
- The volume is not locally available.
- The request has been rejected by the MAREN administrator via a
MAREN-specific computer center exit.
- An internal error has occurred in the MAREN subsystem.

## DMS0607

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0607 Error on creating S-Variable

### Meaning

Possible reasons:
- Not all subsystems required for creation of S variables are
available.
- SDF-P reports internal error.
- SDF-P reports memory shortage.

## DMS0608

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

Warranty : NO

DMS0608 The file '(&00)' is already catalogued but is not a defect garbage. Continuation of processing: Reply (T=Terminate registration function, E=Erase file, R=Use file as defect garbage)

### Meaning

During the registration of a defective disk block it has been found that
a (user) file with the reserved name
$TSOS.SYSCAT.DEFECT.GARBAGE.pvsid already exists.
T: The file will not be used. The defective block will not be
registered.
E: The file will be erased and created again with the same name.
R: An attempt will be made to use the file for defective garbage. If the
structure of the catalog entry does not match, this message will
be repeated until it is answered by 'T' or 'E'.

## DMS0609

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

Warranty : NO

DMS0609 Action not permitted for specified file

### Meaning

The file specified is managed by system software. For more
information about restrictions e.g. regarding deletion, renaming
or write/read access refer to the corresponding handbook.

## DMS061A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS061A Error when reading the storage class

### Meaning

The storage class catalog cannot be accessed or is defective.

### Response

Inform the system administrator.

## DMS0610

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0610 Error during processing of a file/jv set

### Meaning

The operation was executed for a wildcard selection. The job execution
returned an error for at least one of the selected file names.

### Response

Analyze the message log, if it is available.

## DMS0611

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0611 Incorrect construction specified

### Meaning

The job is to be executed for a wildcard. The specified construction
syntax for the second or new file name is not consistent with the
wildcard.

### Response

Repeat the job using the correct syntax.

## DMS0613

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0613 Unknown management class

### Meaning

Possible reasons:
- A management class that does not exist at the SM-pubset was
specified.
- A management class was specified for a file on a SF-pubset.

### Response

Use the name of an existing management class or ask the
system administrator to create the management class.

## DMS0614

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0614 No access authorization for the specified management class

### Meaning

The name of a management class was specified for which the user has
no access authorization.

### Response

Ask the system administrator to enter the access authorization.

## DMS0615

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0615 The file '(&00)' is on the unavailable volumeset '(&01)'

### Meaning

The volumeset on which the file is stored is unavailable. The catalog
entry cannot be read.
(&00): Fully qualified file name
(&01): Volumeset identification code

## DMS0616

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0616 One or more volume sets of the system-managed pubset '(&00)' is/are unavailable

### Meaning

The pubset file list is empty or incomplete due to unavailable
volume sets.
(&00): System-managed pubset identification.

## DMS0617

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0617 Catalog index destroyed

### Meaning

The specified catalog cannot be accessed because the catalog index
was destroyed by a system error. A reconstruction will be carried out
at the next import of the pubset at the latest.

### Response

Repeat the job. Inform the system administrator if the problem persists.

## DMS0618

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0618 Unknown storage class

### Meaning

Possible reasons:
1. The name of a storage class that is not known to the system was
specified.
2. In the context of a STORAGE-CLASS=*UPDATE, the catalog entry of the
specified file contains a storage class that was deleted.
3. When a file is created without the explicit specification of a
storage class, the user table entry of the file owner at the pubset
on which the file is created contains a default storage class
that is not known to the system.
4. When a file generation is created without the explicit specification
of a storage class, the catalog entry of the file generation group
(index) contains a default storage class that is not known to the
system.

### Response

Depending on the reason:
1. Check the name of the storage class and if necessary ask the
system administrator to create it.
2. Use a different storage class, if necessary ask the system
administrator.
3. Ask the system administrator for correction. As long as
the correction has not yet been done, a file can only be
created by specifying STORAGE-CLASS=*NONE
or a different storage class.
4. Ask the system administrator to create the default storage class of the
file generation group or assign a different (default) storage class.

## DMS0619

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0619 No access authorization for the storage class

### Meaning

Possible reasons:
- A storage class was specified for which no access authorization exists.
- When a file is created, the user table entry of the file owner at the
pubset on which the file is created contains a default storage class
for which no access authorization exists.
- When a file generation is created, the catalog entry of the file
generation group (index) contains a default storage class for which
no access authorization exists.
- When the file attributes are updated (STORAGE-CLASS=*UPDATE) the
file catalog entry contains a storage class for which no access
authorization exists.

### Response

Ask the system administrator to enter the access authorization.

## DMS0620

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0620 NO FILE OR JV FOUND TO RESTORE

## DMS0621

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0621 FILE OR JV EXISTING. RESTORE OR IMPORT NOT EXECUTED

## DMS0622

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0622 SNAPSET NOT AVAILABLE

### Meaning

Possible reasons:
- there is no snapset for the referenced pubset
- the specified snapset is not available
- a snapset is in create or delete
- a snapset exists but it is not activated
- invalid area specification for SNAPSET=*INTERVAL

## DMS0623

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0623 AT LEAST ONE GENERATION CANNOT BE RESTORED. FILE GROUP NOT RESTORED.

## DMS0624

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0624 FILE OR JV NAME INVALID

### Meaning

Possible reasons:
- specification of wildcards in catid or userid is not possible

## DMS063B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS063B The RFA transfer area is too small for the required information

### Meaning

During the call of the commands SHOW-FILE-ATTRIBUTES or COPY-FILE,
respectively of the program interfaces FSTAT or COPFILE with wildcards
in the file names via a RFA connection, the required information is too
large for the transfer area allocated by RFA.
The requested function is only partial executed.

## DMS0630

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0630 THE SPECIFIED FILES ARE EQUAL

### Meaning

The content of the two files is equal.

## DMS0631

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0631 THE SPECIFIED FILES ARE NOT EQUAL

### Meaning

The content of the two files is not equal.

## DMS0632

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0632 FILES DIFFERENT FROM RECORD '(&02)'. THIS IS THE RECORD #'(&01)' IN BLOCK #'(&00)'

### Meaning

The content of the two files is not equal.
&00 number of the data block, where the files are different
&01 number of the data record inside the specified data block,
where the files are different
&02 number of the data block inside the file, where the files are
different

## DMS0633

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0633 FILES DIFFERENT FROM RECORD '(&00)'

### Meaning

The content of the two files is not equal.
&00 number of the data record, where the files are different

## DMS0634

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0634 FILES DIFFERENT FROM BYTE '(&01)' IN PAM PAGE '(&00)'

### Meaning

The content of the two files is not equal.
&00 number of the PAM page, where the files are different
&01 number of the data byte inside the specified PAM page, where the
files are different

## DMS0635

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0635 FILES ARE DIFFERENT IN THE USER INFORMATION INSIDE THE PAM KEY FROM BLOCK '(&00)'

### Meaning

The contents of the two UPAM files are equal. The files are different in
the user information inside the PAM key.
&00 number of the data block, where the user information inside the
PAM key is differnt

## DMS0636

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0636 The files cannot be compared, because they are different in the file attribute '(&00)'

### Meaning

&00 file attribute, which is different for the two files

## DMS0637

Destination: USER-TASK Routing code: Weight: 10

Warranty : YES

DMS0637 FILES ARE DIFFERENT, BECAUSE ONLY ONE OF THE COMPARED FILES CONTAINS A BLOCK GAP AT BLOCK '(&00)'

### Meaning

The contents of the two PAM files are not equal. The files are
different, because only one of both files contains a block gap
at the indicated block.
&00 number of the block gap

## DMS0638

Destination: USER-TASK Routing code: Weight: 10

Warranty : NO

DMS0638 FILES ARE DIFFERENT, THEY HAVE DIFFERENT CODED-CHARACTER-SETS

### Meaning

Coded-Character-Sets of the comparing files are different

## DMS064A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS064A NET CLIENT REPORTS PERMISSION DENIED TO FILE ON NET-STORAGE VOLUME.

### Meaning

Possible reason:
- POSIX user number and/or POSIX group number for specified userID
on the specified pubset do not match UID and/or GID for the
corresponding userID on the net server.

### Response

Call system administrator.

## DMS064B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS064B ONETSTOR REPORTS: ACCESS TO NODE FILES NOT SUPPORTED BY NET CLIENT.

### Meaning

Possible reason:
- The current installed net client does not supports node files.

### Response

Ask system administrator for installation of latest net client.

## DMS064C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS064C DIRECTORY OF THE SPECIFIED USER IDENTIFICATION DOES NOT EXIST ON THE NET SERVER

### Response

Call system administrator.

## DMS064D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS064D Specified file is not a node file

## DMS064E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS064E Node file is not located on the specified Net-Storage volume

## DMS064F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS064F Operand FILE-STRUCTURE and the FCB type of the node file do not match

## DMS0640

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0640 Access to Net-Storage refused by the subsystem ONETSTOR due to communication problems with the net client

### Meaning

Possible reasons:
- Error during link connection to the net client.
- Connection to the net client is coming up.
- Connection to the net client is closing down or
has just been released.

### Response

- Repeat command and if necessary call the system administrator.

## DMS0641

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0641 Subsystem ONETSTOR reports that file on Net-Storage already exists

### Meaning

A file should be created, that already exists on Net-Storage but
is uncataloged in BS2000.

### Response

Call the system administrator of the net server, if necessary
delete the file on Net-Storage manually.

## DMS0642

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0642 LARGE FILES NOT ALLOWED ON THE SPECIFIED PUBSET

### Meaning

A file larger than 32 GByte is to be imported from a net-storage
volume. Large files are not allowed on the secified pubset.

## DMS0643

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0643 Net client reports access error

### Meaning

Possible reasons:
- Net client is coming up.
- Net client is closing down.
- Net client reports input/output error.
- Net client reports permission denied.

### Response

- Repeat command and if necessary call the system administrator.

## DMS0644

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0644 Net client reports internal error

### Response

Call the system administrator.

## DMS0645

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0645 Subsystem ONETSTOR reports that file on Net-Storage does not exist

### Meaning

A file on Net-Storage should be accessed, that is cataloged in
BS2000 but does not exist on Net-Storage.

### Response

Call the system administrator of the net server.

## DMS0646

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0646 FGG not allowed on Net-Storage volume

## DMS0647

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0647 SPECIFIED FILE-TYPE DOES NOT MATCH CATALOG ENTRY FOR FILE. COMMAND IGNORED

### Meaning

Possible reasons:
- For a file on Net-Storage volume the specified file type
does not match to the file type in the catalog entry.
- The file is not cataloged on Net-Storage volume.

### Response

Correct command.

## DMS0648

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0648 SPECIFIED FILE TYPE, DEVICE AND VOLUME DO NOT MATCH. COMMAND IGNORED

### Meaning

Possible reasons:
- A file on Net-Storage volume should be created, but no
Net-Storage volume was specified.
- A file on Net-Storage volume should be created, but in
the moment no Net-Storage volume is available.

### Response

Correct command.

## DMS0649

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0649 NET SERVER REPORTS POSIX-ACL ERROR

### Meaning

Possible reasons:
- POSIX-ACL not supported by net server.
- Access to node file on net server, because of missing or wrong
POSIX-ACL entries not possible.
- User name not known at LDAP server configured on net server.
- NFSv4 domain name doesn't match the domain name configured
on net server.

### Response

Call system administrator of the net server or LDAP administrator.

## DMS0650

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0650 No node file could be imported or updated

### Meaning

The operation was executed for a wildcard selection. The job execution
returned an error for all of the selected file names.

### Response

Analyze the message log, if it is available.

## DMS0651

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0651 Node file without any FCB type could not be updated

### Response

Erase node file and import it again or import node file
with REPLACE=*YES

## DMS0652

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0652 ABSOLUTE ALLOCATION REQUEST OF STORAGE SPACE ON NET-STORAGE NOT ALLOWED

### Meaning

An absolut allocation request of storage space is not allowed on
a Net-Storage volume.

## DMS0653

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0653 NET-STORAGE VOLUME OF TYPE NETVOL CANNOT BE IMPORTED

### Meaning

An /IMPORT-FILE command or FILE macro with STATE=FOREIGN operand
was specified for a Net-Storage volume of the NETVOL type.

## DMS0654

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0654 FROM-CATALOG OPERAND NOT POSSIBLE FOR FILES ON NET-STORAGE-VOLUME OF TYPE NETVOL

### Meaning

A /SHOW-FILE-ATTRIBUTES command or FSTAT macro with FROM-CATALOG operand
was specified for a Net-Storage volume of the NETVOL type.
There is no catalog file on a Net-Storage volume of the NETVOL type.

## DMS066A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS066A SPECIFIED CRYPTO-PASSWORD(S) NOT USABLE. COMMAND REJECTED

### Meaning

The user has chosen an unsuitable value for one or more
crypto-passwords.
Due to data security the specified values are rejected.

### Response

Choose another value for the crypto-passwords.

## DMS066B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS066B FILE IS ALREADY DECRYPTED

### Meaning

Decryption was called for a file that is not encrypted.

## DMS066C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS066C FILE WAS ENCRYPTED. ACCESS TO CONTENTS OF FILE ONLY BY CRYPTO PASSWORD. PROTECT CRYPTO PASSWORD FROM GETTING LOST

## DMS066D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS066D EXPLICIT SPECIFICATION OF A CRYPTO PASSWORD WAS RESTRICTED BY SYSTEM ADMINISTRATOR

### Response

Take crypto password from a reference file.
If necessary make an arrangement with the system administrator
for creation of a suitable reference file.

## DMS066E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS066E FILE WAS NOT PROCESSED COMPLETELY. USE HELPFILE 'S.DMS.<TSN>. <YYYYJJJHHMMSS>.CRYPTO'.

### Meaning

Encryption or decryption was called for a file. Part of the
transformed PAM pages could not be written back into the file.

### Response

Find corresponding help file by using LAST-CHANGE-DATE of file.
Reconstruct file by copying help file.

## DMS0660

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0660 INVALID PASSWORD SPECIFIED. COMMAND REJECTED

### Response

Try again with the correct password.

## DMS0661

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0661 PASSWORD WAS NOT CONFIRMED CORRECTLY

### Meaning

Possible reasons:
- Password confirmation is missing.
- Password is different from its confirmation.

## DMS0662

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0662 SPECIFIED FILE LINK NAME MISSING OR INVALID. COMMAND TERMINATED

### Meaning

Either no link name has been defined, or no TFT entry
with the specified link name exists.

### Response

Reenter the command with a valid link name.

## DMS0663

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0663 ENCRYPTION OF FILE NOT ALLOWED

### Meaning

Possible reasons:
- Encryption was called for a file that is already encrypted.
- Encryption was called for a file on private volume.
- Encryption was called for a file on Net-Storage.
- Encryption was called for a PAM file with a last-byte pointer
information in the catalog entry.
- Encryption was called for a file that is on user ID TSOS
and on home pubset.

## DMS0665

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0665 LOGGING ERROR DURING PASSWORD PROCESSING. PROCESSING CONTINUED

### Meaning

The password table contains temporary passwords which were not released
by a previous call. A SERSLOG entry was created. The temporary passwords
were deleted and processing was continued.

## DMS0666

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0666 REQUESTED ACCESS TO FILE NOT PERMITTED DUE TO EXISTING FILE PROTECTION. COMMAND NOT PROCESSED

### Meaning

Possible reasons:
- The file is protected with BASIC-ACL or with GUARD.
- The corresponding subsystem is not loaded.
- The PLAM library is in 'protected mode'.

### Response

If possible, change the access authorization accordingly or change the
PLAM library mode into the 'compatible mode' by activating the default
protection attributes or have subsystem GUARDS started by system
administrator.

## DMS0667

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0667 REFERENCE FILE COULD NOT BE USED

### Meaning

Possible reasons:
- A file that is not encrypted was specified as a
reference file for encryption.
- The encryption attributes of the reference file
cannot be determined.
- The reference file is not on a local pubset.
- The crypto password of the reference file was not specified.

## DMS0668

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0668 COMMAND RESTRICTED TO SYSTEM ADMINISTRATOR. COMMAND NOT PROCESSED

### Meaning

A user other than the system administrator has issued a space management
request.

## DMS0669

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0669 WARNING: PROTECTION ATTRIBUTE OF THE FILE WAS MODIFIED IMPLICITLY. PROCESSING CONTINUES

### Meaning

Possible reasons:
- Read password was deleted at file encryption.
- Execute password was deleted at file encryption.

## DMS0670

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0670 SYNTAX ERROR IN COMMAND

### Response

Eliminate the error and reenter the command.

## DMS0671

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0671 OPERAND ERROR IN COMMAND

### Response

Eliminate the error and reenter the command.

## DMS0672

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0672 SPECIFIED PUBSET IS NOT AVAILABLE

## DMS0673

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0673 MAIN MEMORY BOTTLENECK. COMMAND NOT PROCESSED

### Meaning

The memory allocation has returned an error code.

### Response

Try again, if appropriate.

## DMS0674

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

Warranty : NO

DMS0674 ALLOCATOR REQUEST COUNTER IS NOT POSITIVE. SYSTEM TERMINATED WITH DUMP

### Meaning

The counter shows the value '0' or a negative value, even though it has
been incremented by this task. System error in SPACEMGMT.

### Response

Send the dump off for diagnosis.

## DMS0675

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0675 COMMAND PROCESSED

## DMS068A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS068A MAIL SENDER ERROR '(&01)' WHEN ACCESSING FILE '(&00)'. FOR FURTHER INFORMATION: /HELP-MSG YML(&01)

### Meaning

For more detailed information about the Mail Sender error code
enter /HELP-MSG in system mode or see the manual 'interNet Services'.

## DMS068B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS068B PLAM ERROR '(&01)' WHEN ACCESSING FILE '(&00)'. FOR FURTHER INFORMATION: /HELP-MSG PLA(&01)

### Meaning

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

## DMS068C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS068C USER ID LOCKED

### Meaning

The user ID of the recipient is locked

### Response

The user ID can be unlocked with the /UNLOCK-USER command

## DMS068F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS068F ERROR DURING SDF CORRECTION DIALOG. COMMAND TERMINATED ABNORMALLY

## DMS0680

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0680 GENERATION SPECIFICATION IN FILE NAME '(&00)' INVALID

## DMS0681

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0681 DMS error '(&01)' when accessing file '(&00)'. For further information: /HELP-MSG DMS(&01)

### Meaning

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

## DMS0682

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0682 JVS error '(&01)' when accessing jv '(&00)'. For further information: /HELP-MSG JVS(&01)

### Meaning

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

## DMS0683

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0683 FILE '(&00)' ALREADY EXISTS

## DMS0684

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0684 FILE '(&00)' DOES NOT EXIST

## DMS0685

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0685 File '(&00)' has no allocation

### Meaning

The file specified is cataloged but has neither an allocation given
in the catalog entry nor is cataloged as a tape file. For such files
the specified command or operand value is invalid.

## DMS0686

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0686 Value introducing a structure specified more than once. Only the last structure specified is processed

### Meaning

In an SDF command a value introducing a structure has been specified
more than once within a list.
Only the structure introduced by the last value entered will be effective.

## DMS0687

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0687 The file attributes are incompatible with one another. Processing was terminated with an incomplete target file

### Meaning

An error occurred during the concatenation of SAM files.
Possible reasons:
- The files specified in the concatenation list are different with
regard to the FILE-STRUCTURE, BUFFER-LENGTH, RECORD-FORMAT, or
BLOCK-CONTROL-INFORMATION structure attributes.
- The files specified in the concatenation list do not all have the same
CODED-CHARACTER-SET.
- The first file of the concatenation list is not a SAM file.
The target file may already have been created or modified.

## DMS0688

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0688 Invalid target file specification

### Meaning

Possible reasons:
- The file name specified as the target file is from the concatenation
list but not the first one.
- No target file was specified but the first source file was
specified twice.

### Response

Specify the file name of the target file at the top of the concatenation
list or use a different target file.

## DMS0689

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0689 Specified operands only permitted for files that have no allocation

### Meaning

An operand that is only permitted for the initial allocation was
specified for a file that already has an allocation or a tape type.

### Response

Delete the file or free its memory space completely, then repeat the job.

## DMS069D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS069D ERROR IN CATALOG ENTRY FORMAT. CONTACT SYSTEM ADMINISTRATOR

### Meaning

The file cannot be processed.

## DMS0690

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0690 COMMAND CONTAINS INVALID PARENTHESIZED EXPRESSION. CORRECT COMMAND

### Meaning

Either the parenthesized structure contains an error or there are too many
values enclosed in the parenthesis.

## DMS0691

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0691 (CRYPTO)PASSWORD TABLE AT MAXIMUM SIZE. COMMAND REJECTED

### Response

Before adding a new (crypto)password, at least one (crypto)password
must be deleted from the (crypto)password table by means of the
command /REMOVE-PASSWORD or /REMOVE-CRYPTO-PASSWORD.

## DMS0692

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0692 MAXIMUM NUMBER OF (CRYPTO)PASSWORDS PER TASK REACHED. COMMAND REJECTED

### Meaning

The maximum number of (crypto)passwords per task specified by the system
administrator has been reached. For this task no further (crypto)passwords
will be added to the (crypto)password table.

## DMS0693

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

Warranty : NO

DMS0693 DATA SECURITY. TASK HAS REACHED MAXIMUM NUMBER OF INVALID (CRYPTO)PASSWORD SPECIFICATIONS

### Meaning

Every access to a password protected file or an encrypted file
is counted if the appropriate (crypto)passwords of this file
are not included into the task (crypto)password table in the moment
of access.
If the maximum access number is reached given by the system
administrator, the concerned task will be aborted.

### Response

Contact the system administrator, so that appropriate actions will be
done if necessary.

## DMS0694

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0694 SENDING OF FILE OR ELEMENT NOT ALLOWED

### Meaning

Possible reasons:
- Mail-File was called for a file
whose access method is not SAM and not ISAM
or for a PAM file whose content type is not recognized.
- Mail-File was called for a file that has no creation date.
- Mail-File was called for a file generation group.
- Mail-File was called for an element of a PLAM library
and the type of the element is not textual
(see manual 'LMS SDF Format').
- Mail-File was called for an element of a PLAM library
and the element contains format B records
(see manual 'LMS Subroutine Interface')
and its content type is not recognized.
- Mail Sender backend error
(e.g. file access error, file too large).
The mail service logging file
may contain further details;
if necessary request the mail service logging file
from the administrator.

## DMS0695

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0695 EMAIL-ADDRESS MISSING

### Meaning

The entry of the user ID in the user catalog
does not contain an EMAIL address.

### Response

Ask the system administrator to enter the EMAIL address.

## DMS0696

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0696 EMAIL-ADDRESS OF USER ID TSOS MISSING

### Meaning

The entry of the user ID TSOS in the user catalog
does not contain an EMAIL address or the EMAIL adress
is invalid from the point of view of the mail server.

### Response

Ask the system administrator to enter the EMAIL address.

## DMS0698

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0698 FILE GENERATION GROUPS DO NOT HAVE SAME ATTRIBUTES. COMMAND REJECTED

### Meaning

When copying one FGG (file generation group) into another FGG it became
evident that the attributes relative to the file generation
(MAXIMUM, FIRST-GENERATION, BASE-NUMBER, CURRENT-GENERATION) did not match
or matched only partly.

## DMS0699

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0699 SYSTEM ERROR DURING RFA PROCESSING. TASK TERMINATED ABNORMALLY WITH DUMP

### Response

Contact the system administrator.

## DMS0800

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0800 SPECIFIED FILE '(&00)' DELETED

## DMS0801

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0801 ERROR WHEN DELETING FILE '(&00)'

### Meaning

Due to an error the file could not be deleted
(possible reason: access = READ).
This message is followed by another message identifying the error in more
detail.

### Response

Make the appropriate correction(s) to the file and then delete it.

## DMS0802

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0802 FILE '(&00)' REPAIRED IN FILE '(&01)'

### Meaning

The command has been executed.
File (&00) has been repaired by creating file (&01).

## DMS0803

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0803 ERROR WHILE REPAIRING FILE '(&00)'

### Meaning

An error has occurred when processing the /REPAIR-DISK-FILE command.
This message is followed by a DMS message identifying the error in
more detail.
(&00): file name.

## DMS0804

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0804 File opened with 'WROUT=NO'. Consistency check not practical

### Response

Repair the file by means of the command /REPAIR-DISK-FILE.

## DMS0805

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0805 FILE '(&00)' CHECKED AND WITHOUT ERRORS

### Meaning

The file has been created with WROUT=YES and all blocks have been checked.

## DMS0806

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0806 DRIVE CONTAINING VOLUME '(&00)' CANNOT BE RESERVED

### Meaning

The drive on which the specified volume is mounted is reserved by another
user.
(&00): mnemonic device name of the volume.

### Response

Try again later or contact the system administrator.

## DMS0807

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0807 ERROR FROM SHOW-FILE-ATTRIBUTES FILE-NAME '(&00)'

### Meaning

An error occurred during output of catalog information for file (&00).
This message is followed by another message identifying the error in more
detail.

### Response

Correct filename if necessary.

## DMS0808

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0808 ERROR WHEN RESTORING FILE/JV '(&00)'

### Meaning

Due to an error the file/JV could not be processed.
This message is followed by another message identifying the error in more
detail.

### Response

Make the appropriate correction(s) to the file/JV and then restore it.

## DMS0810

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0810 Execute job for file(s) '(&00)' (Y=Yes; N=No; T=Terminate; ?=Help/further options)

### Meaning

Control dialogs were requested in the preceding command.
(&00): Specifies the file(s) for which the user should give a
job confirmation.
The following responses are possible:
- *YES(...) / *NO(...)
(...)
! DIALOG-CONTROL = *UNCHANGED / *NO / *ERROR /
! *FILE-CHANGE / *CATALOG-CHANGE /
! System administrator: *USER-ID-CHANGE
! ,OUTPUT = *UNCHANGED / *NO / *SYSOUT
- *TERMINATE
See the BS2000 'Commands' manual for more detailed information.

## DMS0811

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0811 '(&00)' DMS error code occurred during execution of the job for the file name '(&01)'. Further information: /HELP-MSG DMS(&00)

### Meaning

An error log was requested for the preceding command.
(&00): DMS return code from the function execution.
(&01): Selected, fully qualified file name.
You can obtain more detailed information using /HELP-MSG DMS(&00) or
in the 'System Messages' manual.

### Response

See the response text for the error code DMS(&00).

## DMS0812

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0812 '(&00)' DMS error code occurred during execution of the job for the file name '(&01)' with the file name '(&02)'. Further information: /HELP-MSG DMS(&00)

### Meaning

An error log was requested for the preceding command.
(&00): DMS return code from the function execution.
(&01): Selected, fully qualified file name.
(&02): Second or new, or constructed file name.

### Response

See the response text for the error code DMS(&00).

## DMS0813

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0813 Continue job after error (Y=Yes; N=No; R=Retry; ?=Help/further options)

### Meaning

An error dialog was requested for the preceding command. While the job
was executed, an error described in the preceding messages (DMS0811 or
DMS0812) occurred.

### Response

The following responses are possible:
- *YES(...) / *RETRY(...) / *SKIP-CATALOG(...) / *SKIP-USER-ID(...)
(...)
! DIALOG-CONTROL = *UNCHANGED / *NO / *ERROR /
! *FILE-CHANGE / *CATID-CHANGE /
! System administrator: *USER-ID-CHANGE
! ,OUTPUT = *UNCHANGED / *NO / *SYSOUT
- *NO
See the BS2000 'Commands' manual for more detailed information.

## DMS0814

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0814 The job was fully or partially withdrawn

### Meaning

In a preceding error dialog or control dialog (messages DMS0810 or
DMS0813) the job was fully or partially withdrawn by the user.

## DMS0815

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0815 Job for the file name '(&00)' successfully executed

### Meaning

A runtime log was requested for the preceding command.
(&00): Fully qualified file name for which the job was successfully
executed.

## DMS0816

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0816 Job for the file name '(&00)' successfully executed with file name '(&01)'

### Meaning

A runtime log was requested for the preceding command.
(&00): Fully qualified file name for which the job was successfully
executed.
(&01): Fully qualified file name with which the job for the
file name (&00) was successfully executed.

## DMS0817

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0817 The job for files '(&00)' cannot be executed completely, because the RFA transfer area is to small. Continue job (Y=Yes; N=No; T=Terminate; ? =Help/further options)

### Meaning

Control dialogs were requested in the preceding command.
(&00): Specifies the files that are not fully processed, because
the RFA transfer area is too small.
The following responses are possible:
- *YES(...) / *NO(...)
(...)
! DIALOG-CONTROL = *UNCHANGED / *NO / *ERROR /
! *FILE-CHANGE / *CATALOG-CHANGE /
! System administrator: *USER-ID-CHANGE
! ,OUTPUT = *UNCHANGED / *NO / *SYSOUT
- *TERMINATE
See the BS2000 'Commands' manual for more detailed information.

## DMS0850

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0850 EAM ERROR ON '(&00)'. DMS ERROR CODE '(&01)'

### Meaning

An unrecoverable error has occurred while extending/reducing file (&00)
(e.g. because no more public space was available).

### Response

See the manual 'System Administrator's Guide'.

## DMS0851

Destination: USER-TASK Routing code: Weight: 98

Warranty : NO

DMS0851 (&00): EAM SPACE EXHAUSTED. REPLY (0=RETRY; 1=ABORT)

### Meaning

The space available in the SYSEAM file (&00) has been used up.
Possible reasons:
- This message indicates a genuine emergency situation or
- the specified MAXIMAL-SIZE is too small.

### Response

0 (RETRY): the system will wait 60 seconds before repeating the request.
If another user has released space during this time,
the attempt may be successful.
1 (ABORT): the requesting task will be terminated.
The system administrator should increase the above value by means of the
command /MODIFY-MASTER-CATALOG-ENTRY or should generate a new system with
a reduced value for the system parameter EAMSIZ and/or create new SYSEAM
files on other volume sets.

## DMS0852

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0852 (&00): (&01) PAM PAGES AND (&02) EXTENTS

### Meaning

The SYSEAM file (&00) has been dynamically extended/reduced.
At the moment it has (&01) PAM pages and (&02) extents.
If this message occurs frequently, it is an indication that the value
specified for MINIMAL-SIZE is too small.
If (&02) has a value of approximately 100, a higher value should be
selected for the SECONDARY-SIZE extension.

## DMS0853

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0853 UNRECOVERABLE ERROR IN EAM BOURSE

### Meaning

The EAM lock mechanism is not working because of a bourse error.

### Response

Request the system administrator to prepare diagnostic material.

## DMS0854

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0854 FILE SIZE OF SYSEAM FILE (&00) MAY NOT EXCEED 32 GIGABYTES

### Meaning

SYSEAM file (&00) has been created with unallowed file size higher
than 32 gigabytes (by CREATE-FILE).

### Response

Delete SYSEAM-file (&00) and create it again with allowed file size
below 32 gigabytes.
L

## DMS0855

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0855 INPUT/OUTPUT ERROR (&00) DURING PROCESSING OF SYSEAM FILE (&01)

### Meaning

PPAM has reported returncode (&01) to EAM during update of SYSEAM
file (&01)

### Response

Please contact system administrator

## DMS0880

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0880 PPD: UNRECOVERABLE ERROR WHILE CHECKING WRITE AUTHORIZATION

### Meaning

Due to an unrecoverable error when calling the lock manager or device
management, PPD (Protected Private Disk) cannot receive information
about the disk.
The task concerned is terminated. A system dump is produced.

### Response

Contact the system administrator.

## DMS0881

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0881 PPD: DISK WITH VSN '(&00)' IS PROTECTED

### Meaning

PPD has rejected an attempt to write to files or labels of the specified
private disk because the disk is write-protected either explicitly by the
CONDMPPD utility routine statement or implicitly by being mounted on a
disk drive generated as switch-selectable (*). A DMS error code will be
generated and another DMS message will follow.

### Response

If the disk is implicitly protected and is to be write-accessible, it can
be remounted or the system administrator may load the CONDMPPD utility
routine and cancel write protection by means of ADD <vsn>,PRV=Y. If it
is explicitly protected, the system administrator may revoke this
protection by means of the CONDMPPD statement DEL <vsn>.

## DMS0882

Destination: CONSOLE Routing code: D Weight: 99

Warranty : NO

DMS0882 PPD: VSN LIST OVERFLOW. '(&00)' NOT PROTECTED

### Meaning

PPD: Protected Private Disk.
(&00): VSN of the disk concerned.
The private disk with the specified VSN, which is mounted on a disk drive
generated as switch-selectable (*), is not write-protected by PPD.
This message is displayed during allocation of the disk when PPD is active
and the VSN cannot be added to the PPD VSN list because the system
administrator has entered too many ADD statements.
580 VSNs are possible, including automatic VSN transfer.

### Response

If necessary, interrupt disk access or grant it to a single system.
Use the DEL statement to delete from the list all VSNs which are no
longer needed. After this the system administrator may enter the
CONDMPPD statement with ADD <vsn> if the disk is to be write-protected.

## DMS09AA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09AA PROGRAM ERROR: EVENT ITEM NOT DEFINED

### Response

Check the values of the ENAEI macro or FECB operand in the PAM macro.

## DMS09AB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09AB PROGRAM ERROR: CHAINED I/O WITH 'SETL' OPERAND IN 'PAM' MACRO NOT PERMITTED

### Response

Correct the program and try again.

## DMS09AC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09AC PROGRAM ERROR: TOO MANY SIMULTANEOUS I/O REQUESTS

### Response

Check the PAMREQS operand in the FCB macro or the REQNO operand in the
PAM macro.

## DMS09AD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09AD FILE SIZE GREATER THAN 32 GIGABYTES IS NOT ALLOWED..

### Meaning

In FCB or ADD-FILE-LINK LARGE_FILE=*FORBIDDEN has been set,
but concerned file exceeds 32 gigabytes.

### Response

Correct program. If the error persists, contact system administrator.

## DMS09A0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A0 PROGRAM ERROR: OPERAND LIST ADDRESS OR 'FECB' ADDRESS FOR 'UPAM' NOT ALIGNED ON WORD BOUNDARY

### Response

Correct the program and try again.

## DMS09A1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A1 PROGRAM ERROR: ADDRESS OF OPERAND LIST OR 'FECB' FOR 'UPAM' NOT IN VALID ADDRESS SPACE

### Response

Correct the program and try again.

## DMS09A2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A2 PROGRAM ERROR: OPERAND LIST CHAIN FOR 'UPAM' TOO LARGE

### Meaning

This error may also be due to an operand list chain being linked to
itself (in a loop).

### Response

Correct the program and try again.

## DMS09A3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A3 PROGRAM ERROR: 'FCB' ADDRESS IN 'PAM' MACRO NOT ALIGNED ON WORD BOUNDARY

### Response

Correct the program and try again.

## DMS09A4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A4 PROGRAM ERROR: 'FCB' ADDRESS IN 'PAM' MACRO NOT IN PROGRAM

### Response

Correct the program and try again.

## DMS09A5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A5 PROGRAM ERROR: INVALID 'FCB' ADDRESS IN 'PAM' MACRO

### Meaning

Possible reasons:
1) the file has not been opened
2) the FCB has been overwritten
3) the specified address is not an FCB address.

### Response

Correct the program and try again.

## DMS09A6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A6 PROGRAM ERROR: INVALID OR MISSING 'KEYFLD' OPERAND IN 'PAM' MACRO

### Response

Correct the program and try again.

## DMS09A7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A7 PROGRAM ERROR: IDENTICAL EVENT ITEM FOR TWO OUTSTANDING I/O OPERATIONS (UPAM) NOT PERMITTED

### Meaning

The same FECB operand value has been used in two different PAM macros
for two outstanding I/O operations.

### Response

Correct the program and try again.

## DMS09A8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A8 PROGRAM ERROR: WAIT OPERATIONS NOT PERMITTED IN PAM MACRO DURING EVENT-DRIVEN I/O

### Meaning

An FECB has been specified in the PAM macro but the operation is illegal.
Only WRITE, READ, LOCK and READ, LOCK, UNLOCK and SETL are permitted
in this case.
For further details, see the notes in the DMS manuals.

### Response

Correct the program and try again.

## DMS09A9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09A9 REQUESTED BLOCK NOT FOUND

## DMS09B0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B0 DEADLOCK SITUATION. WITHIN SPECIFIED TIME LIMIT NO FURTHER PAM PAGES CAN BE LOCKED. RELEASE ALL EXISTING LOCKS AND RETRY

### Meaning

The user has tried to lock additional PAM pages, but one or more
pages have already been locked and he/she is not permitted to
lock more pages within the specified time limit.

### Response

Release all existing locks and try again.

## DMS09B1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B1 REQUESTED HALF-PAGES USED BY ANOTHER TASK AND CANNOT BE LOCKED WITHIN SPECIFIED TIME LIMIT. LOCK REQUEST IGNORED

### Meaning

One or more PAM half-pages for which a lock by a single operand list
chain was requested were not available within the specified time
limit (they have been locked by another task).

### Response

Repeat the request. If the error persists, take the necessary steps
to have your access to the shareable files brought into line
with that of the user(s) responsible for the lock.

## DMS09B2

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B2 PROGRAM ERROR: USER HAS ATTEMPTED TO UNLOCK PAGE THAT IS NOT LOCKED

### Response

Correct the program and try again.

## DMS09B3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B3 PROGRAM ERROR: PAGE ALREADY LOCKED

### Response

Correct the program and try again.

## DMS09B4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B4 PROGRAM ERROR: SIMULTANEOUS LOCKING OF MORE THAN 255 HALF-PAGES IS ILLEGAL

### Response

Correct the program and try again.

## DMS09B5

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS09B5 UPAM: Internal error during a lock request.

### Meaning

- Subsystem MSCF is not loaded.
- The system parameter MCXSPXCS=V is set
- and the subsystem MSCF does not run in XCS mode.

### Response

Contact system administration.

## DMS09B6

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS09B6 UPAM: Internal error during a lock release.

### Response

Contact system administration.

## DMS09B7

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS09B7 UPAM: Access on net-storage volume is not possible

### Response

Contact system administration.

## DMS09B8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B8 END OF TAPE DETECTED

## DMS09B9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09B9 PROGRAM ERROR: BLOCK CONTROL FIELD OVERWRITTEN

### Meaning

Between the beginning and the termination of an UPAM write job to a
BLKCTR=DATA file the block control field of the beginning of the data
buffer is destroyed. An asynchron write job is terminated finally
after a WAIT (or an implicit WAIT due to a new PAM of the same REQNO), or
if a P1 eventing during an information to the user. The error can also
happen due to a parallel write job for another file with the same buffer.
Attention: a block was written with an invalid file ID. If the error has
been detected during an implicit WAIT the preceding job is
concerned, the actual job will not be executed.

### Response

Correct the program.

## DMS09E0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09E0 SYSTEM ERROR DURING OPEN/CLOSE/REMOTE PROCESSING OF UPAM FILE

### Response

Send a dump to the diagnostics staff.

## DMS09FE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09FE BCAM CONNECTION ERROR. TRY AGAIN LATER

### Meaning

A BCAM error has occurred during PAM macro processing and will be
displayed on operator console.

### Response

If the error persists, contact the system administrator.

## DMS09FF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS09FF INVALID REQUEST FOR DEVICE DRIVER OR BCAM CONNECTION INOP OR ABOUT TO BE SEVERED. TRY AGAIN LATER

### Meaning

Possible reasons:
1. During the request for the device driver an invalid request was
reported.
2. A BCAM error has occurred during PAM macro processing and will be
displayed on the operator console.

### Response

1. Contact the system administrator.
2. If the error persists, contact the system administrator.

## DMS0901

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0901 UPAM RECEIVED ERROR WHILE CALLING LOCK MANAGER

### Meaning

While calling the task lock manager UPAM received an unexpected return
code. The PAM task could not be processed.

### Response

Try again, if the error persists, contact the system administrator.

## DMS0902

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS0902 Requested catalog in QUIET or HOLD state. Waiting time is over. Command not processed

### Meaning

The catalog containing the processed file is currently not accessible.

## DMS0905

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0905 ALLOCATOR REPORTS TO UPAM: ERROR IN CONNECTION WITH REMOTE HOSTS DURING SECONDARY ALLOCATION

### Meaning

After a secondary allocation the error code '0305' is returned to UPAM.
The MRS connection is destroyed.

### Response

Contact the system administrator.

## DMS092C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS092C PPAM REPORTS TO UPAM: INVALID EXTENT TABLE

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS092D

Destination: CONSOLE Routing code: D Weight: 99

Warranty : NO

DMS092D PPAM REPORTS TO UPAM: 'WAIT' AND 'CONTINGENCY' REQUESTED

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS092E

Destination: CONSOLE Routing code: D Weight: 98

Warranty : NO

DMS092E PPAM REPORTS TO UPAM: DEVICE ACCESS AUTHORIZATION WITHDRAWN BY OPERATOR

### Meaning

A given volume is no longer accessible.
In the case of write operations for magnetic tape cartridges, there
may still be jobs in the cartridge buffer.

## DMS092F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS092F PPAM REPORTS TO UPAM: BOURSE ERROR

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0920

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0920 PPAM REPORTS TO UPAM: WRITE ERROR WITH BUFFERED OUTPUT RESULTING IN LOSS OF DATA

### Meaning

Despite repeated attempts a write operation could not be performed.
The data in the magnetic tape cartridge buffer has not been written
to the cartridge in its entirety. The data remaining in this buffer
has been lost.

## DMS0921

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0921 PPAM REPORTS TO UPAM: MEMORY SATURATION

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0922

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0922 PPAM REPORTS TO UPAM: LOGICAL HALF-PAGE DEFINED IN PAM MACRO IS NOT CONTAINED IN FILE

### Response

Allocate more space using the /MODIFY-FILE-ATTRIBUTES command.
Modify the program, if necessary. If the PAM macro operation code SETLPP
has been defined, check whether the half-page number specified in the HP
operand is larger than the file size. If this is the case, adjust its
value accordingly.

## DMS0923

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0923 PPAM REPORTS TO UPAM: ERROR WHEN DEFINING PAGES

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0924

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0924 PPAM REPORTS TO UPAM: MEMORY REQUEST ERROR

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0925

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0925 PPAM reports to UPAM: Illegal operation

### Meaning

Possible reasons:
- the operation is not possible for the specified volume type on the
allocated device. E.g. no writing is possible if a device type C4 is
allocated on the specification of the volume type TAPE-C2 because no
compatible devices for writing in TAPE-C2 format are available.
- An attempt has been made to write to a shortened tape.
- In case of operation RDEQU the value of the operand LEN has to be
a multiple of 2K or 4K in case of NK4 volumes.

### Response

Case 1: select a volume type specification compatible with the device
installation.
Case 2: Use a tape with normal length.
Case 3: Correct and retry.

## DMS0926

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0926 PPAM REPORTS TO UPAM: DEVICE TEMPORARILY LOCKED

### Meaning

The application is working with the function OPTION=NOWAIT (FCB operand).
The volume monitor has temporarily locked the device.

### Response

Try again.

## DMS0927

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0927 PPAM REPORTS TO UPAM: I/O OPERATION TERMINATED DUE TO HARDWARE ERROR

### Response

Check the logical return code or the status bytes in the FCB.
Try again; if the problem persists, contact the system
administrator.

## DMS0928

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0928 PPAM REPORTS TO UPAM: INCONSISTENCY BETWEEN DMS AND NDM TABLES

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0929

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0929 PPAM REPORTS TO UPAM: INVALID SLOT ADDRESS

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS093A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS093A CMS REPORTS TO UPAM: ERROR DURING F1 LABEL PROCESSING

## DMS093C

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS093C Allocator reports to UPAM: Catalog block request was not successful

### Meaning

Return code '033C' has been returned to UPAM after an abortive attempt
to perform secondary allocation.

### Response

Reorganize file extents, delete unused files or ask the system
administrator to extend the TSOSCAT file.

## DMS0930

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0930 REQM ERROR

### Meaning

CMS has passed returncode '0330' to UPAM.

### Response

Try again later. If the error persists, contact the system administrator.

## DMS0937

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0937 CMS REPORTS TO UPAM: NO CATALOG BLOCK AVAILABLE

### Meaning

When requesting a secondary allocation UPAM received return code
'0337' from the allocator. The file cannot be extended as the catalog
is already full.

### Response

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

## DMS094A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS094A NOT ENOUGH SPACE AVAILABLE FOR PAM FILE BUT SOME PAM PAGES HAVE BEEN ALLOCATED

### Meaning

There is not enough space available to the user ID for the complete
secondary allocation to be implemented. However, a number of pages have
been allocated.

### Response

Delete unused files or request the system administrator to allocate more
space.

## DMS094B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS094B ALLOCATOR REPORTS TO UPAM: PUBSET NOT FOUND OR NOT ACCESSIBLE

## DMS094D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS094D NO ADDITIONAL PUBLIC SPACE AVAILABLE FOR PAM FILE

### Meaning

The allocator could not make a secondary allocation for this PAM file
as all the space available to this user ID has been used up.

### Response

Delete unused files and/or request more public space for this
user ID from the system administrator.

## DMS0941

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0941 ALLOCATOR REPORTS TO UPAM: NOT ENOUGH SPACE AVAILABLE

### Meaning

Return code 0441 has been returned to UPAM after an abortive attempt to
perform secondary allocation.

### Response

Delete unused files and/or request more public space for this
user ID from the system administrator.

## DMS0942

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0942 ALLOCATOR REPORTS TO UPAM: DEVICE OR DISK NOT AVAILABLE

### Meaning

Following a secondary allocation error code '0442' has been reported to
UPAM.

### Response

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

## DMS0945

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0945 ALLOCATOR REPORTS TO UPAM: PUBLIC VOLUME NOT ATTACHED

## DMS0946

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0946 SECONDARY ALLOCATION NOT POSSIBLE. CATALOG ENTRY FULL

### Meaning

UPAM has tried to extend the file, but the allocator has issued return
code 0446.

### Response

Reorganize the file by having it copied or mount another private volume
and copy the file to it.

## DMS0948

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0948 SYSTEM ERROR: NON-PRIVILEGED PAM. $REQM ERROR '04'

### Response

Contact the system administrator and request diagnostic material,
if necessary.

## DMS0949

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS0949 UPAM: Invalid allocator request.

### Response

Contact system administration.

## DMS095B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS095B Internal error during the CONCURRENT COPY session

### Response

Abort the session.

## DMS095C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS095C A CANCEL was given for the CONCURRENT COPY session

### Response

Abort the session.

## DMS095D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS095D During the CONCURRENT COPY session the MSCF connection to a slave host was interrupted.

### Response

Abort the session.

## DMS0950

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

Warranty : NO

DMS0950 CONCURRENT COPY systemtask abnormally terminated

## DMS0951

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0951 During an OPEN FOR BACKUP call an invalid session id was specified

### Meaning

The specified CONCURRENT COPY session does not exist, or the file to be
opened is not being processed in this session.

### Response

Abort CONCURRENT COPY session.

## DMS0952

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0952 A file specified at creation time of the CONCURRENT COPY session cannot be saved by CONCURRENT COPY

## DMS0953

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0953 The file was already saved by ARCHIVE during a CONCURRENT COPY session

### Meaning

An OPEN FOR BACKUP is not possible if the file was already saved by
CONCURRENT COPY.

### Response

Correct the program.

## DMS0954

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0954 Errored READ FOR BACKUP

### Meaning

Possible reasons:
- operation code of PAM is neither READ nor READWT nor WAIT,
- process is running with P1 eventing,
- the specified block number was already read,
- the block number is less than the previous one,
- the user tries to read beyond the logical end of file,
- block size is not the same as obtained from the
CREATE CONCURRENT COPY session.

### Response

Correct the program.

## DMS0955

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0955 A CCOPY backup was cancelled with reason '(&00)' while copying a block into the CCOPY work file.

### Meaning

The reason is detailed in the insert '(&00)'.
01: A request for virtual memory could not be fulfilled. Possible
causes are
- space saturation;
- size of request exceeds user limit;
Contact system administrator.
02: Internal error.
Evaluate SERLOG file, record DCH0001.
03: A loss of an MSCF connection occurred, as a consequence
consistency of the backup file cannot be ensured.
Check master/slave connections of affected shared pubset.
04: I/O processing reported hardware error.
Contact system administrator.
05: A request for secondary allocation could not be fulfilled.
Possible causes are
- size of request exceeds user limit;
- shortage of disk space;
Contact system administrator to increase user limit or to make
additional disk space available.

## DMS0956

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0956 OPEN FOR BACKUP is only allowed for access method UPAM

### Meaning

A valid CCOPY Session-Id has been specified in the P1FCB,
but the file is not opened for the access method UPAM.

### Response

Correct the program and try again.

## DMS0957

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0957 OPEN FOR BACKUP is only possible for files on public volumes.

### Meaning

OPEN FOR BACKUP is forbidden for
- Tapefiles
- Files on private disks
- migrated files

### Response

Correct the error and try again.

## DMS099A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS099A PROGRAM ERROR: UPAM RECEIVED INVALID OR ILLEGAL HALF-PAGE NUMBER

### Meaning

Possible reasons:
- The first byte of the half-page number is invalid or the number is zero
or negative.
- BLKCTRL=DATA or =NO and the page is not the last (SETL, SETLPP) or the
first (other PAM operations) page of a logical block.
- SETLPP on a page outside of the file.

### Response

Correct the program and try again.

## DMS099B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS099B PROGRAM ERROR WHEN READING *DUMMY FILE. 'EOFADDR' NOT DEFINED IN 'EXLST' MACRO

### Meaning

The program will be continued with the EXLST exit EOFADDR, if defined;
otherwise it will be aborted.

### Response

Correct the program and try again.

## DMS099C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS099C PROGRAM ERROR: INVALID 'REQNO' OPERAND IN PAM MACRO

### Meaning

Possible reasons:
- The value of the REQNO operand in the PAM macro is negative or greater
than the value specified in the PAMREQS operand of the FCB, or
- more different values are used in the REQNO operand in the PAM macro
than
specified in the PAMREQS operand of the FCB.

### Response

Correct the program and try again.

## DMS099D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS099D PROGRAM ERROR: UPAM RECEIVED INVALID HIGHER-ORDER BYTE IN 'KEYFLD' OPERAND OF 'PAM' MACRO

### Response

Correct the program and try again.

## DMS099E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS099E PROGRAM ERROR: UPAM RECEIVED KEYFLD ADDRESS NOT IN VIRTUAL MEMORY

### Response

Correct the program and try again.

## DMS099F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS099F REQUESTED CLASS 5 MEMORY CANNOT BE ALLOCATED. CHECK MEMORY REQUEST IN PROGRAM FOR PAM FILE

### Meaning

Possible reason:
The highest possible class 6 memory page requested by the REQM macro
prevents class 5 memory from being extended.

### Response

Reorganize the use of virtual memory in the program and try again.

## DMS0990

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0990 PROGRAM ERROR: USER PAM NOT GIVEN FCB ADDRESS BY PAM MACRO OR HIGHEST-ORDER BYTE OF FCB ADDRESS IS NOT '0'

### Response

Correct the program and try again.

## DMS0991

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0991 PROGRAM ERROR: 'SETLPP' OR 'WRITE' NOT PERMITTED FOR A UPAM FILE OPENED IN INPUT MODE

### Meaning

Possible reasons:
- The user program attempted a WRITE or WRITE and WAIT or WRITE and WAIT
and UNLOCK operation on a file opened in INPUT mode.
- The user tried to use a PAM macro with the operand SETLPP on a
UPAM file opened in INPUT mode.

### Response

Correct the program and try again.

## DMS0992

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0992 PROGRAM ERROR: UPAM RECEIVED NO OR INVALID BUFFER ADDRESS FOR PAM FILE

### Meaning

Either no buffer address has been specified in the user program, or the
highest-order byte of the address is not zero or the buffer address is
invalid.

### Response

Check the buffer address and its flag byte.

## DMS0993

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0993 PROGRAM ERROR: BUFFER ADDRESS FOR PAM FILE NOT IN PROGRAM

### Response

Check buffer address and its flag byte.

## DMS0994

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0994 PROGRAM ERROR: FILE SPECIFIED IN PAM MACRO NOT OPENED AS PAM FILE

### Response

Correct the program and try again.

## DMS0995

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0995 PROGRAM ERROR: INVALID OPERATION CODE IN PAM MACRO

### Meaning

- User program error.
- The SETLPP operation was used for a SAM or ISAM file.
- The disk containing the file is write-protected by the PPD function.

### Response

Correct the program and try again. If SETLPP mode is not involved and
the file is a SAM or ISAM file opened in UPAM mode, abort the PAM
action.

## DMS0996

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0996 PROGRAM ERROR: 'CHECK' OPERATION IN PAM MACRO REQUIRES ADDRESS IN 'LOC' OPERAND

### Response

Correct the program and try again.

## DMS0997

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0997 INPUT/OUTPUT ERROR DURING EARLIER ACCESS TO PAM FILE

### Meaning

The program will be continued with the EXLST exit ERRADDR, if defined;
otherwise it will be aborted.

### Response

Try again; if the problem persists, contact the system administrator.

## DMS0998

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0998 PROGRAM ERROR: INVALID LENGTH SPECIFICATION IN PAM MACRO FOR I/O OPERATION FOR PAM FILE

### Meaning

Possible reasons:
- length > 32768 bytes
- length = 0
- no separate buffer specified and length > the buffer size (block size)
requested by OPEN
- a file with the attribute BLKCTRL=DATA is being processed and the length
terminates in the middle of a control field
- a tape file with the attribute BLKCTRL=DATA or =NO is being processed
and
the length is greater than BLKSIZE.
- a tape file with the attribute BLKCTRL=PAMKEY is being processed and the
length is not equal to 2048 or (STD/1).

### Response

Correct the program and try again.

## DMS0999

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS0999 PROGRAM ERROR: UPAM RECEIVED INVALID OPERAND LIST TYPE FROM PAM MACRO

### Meaning

Normally this error occurs when the operand table of the PAM macro
is overwritten or modified incorrectly.

### Response

Correct the program and try again.

## DMS1CFF

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1CFF UNEXPECTED ERROR AT COMMAND '(&00)'

## DMS1C0A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C0A Net-Storage volume (&00) is already assigned to the pubset.

### Meaning

The reference to the Net-Storage volume (&00) is already registered
in the CE of the pubset.
Therefore the Net-Storage volume cannot be created or imported.

### Response

Contact system administrator, or import/delete with FORCE=*YES

## DMS1C0B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C0B .FSL of Net-Storage volume (&00) has already been created.

### Meaning

The reference to the Net-Storage volume (&00) by the FSL
has already been registered in the net storage.
Therefore the Net-Storage volume cannot be created or imported.

### Response

Contact system administrator, or import/delete with FORCE=*YES

## DMS1C0C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C0C Net-Storage volume (&00) is not empty, Net-Storage volume cannot be deleted

### Meaning

On the Net-Storage volume (&00) files are created.
Therefore the Net-Storage volume cannot be deleted.

### Response

Contact system administrator

## DMS1C0D

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C0D Net-Storage volume (&00) is inconsistent with pubset (&01), or is exported.

### Meaning

- The timestamps in the entry of the Net-Storage volume (&00) on the
pubset and the FSL on the Net-Storage volume are different.
- In the FSL of the Net-Storage volume a different pubset is registered.
- There is no entry for the Net-Storage volume on the specified pubset.
- There is no FSL on the Net-Storage volume.
- The Net-Storage volume is exported and therefore is not associated
to any pubset.

### Response

Contact system administrator or import Net-Storage volume.

## DMS1C0E

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C0E There are files on the Net-Storage volume (&00) without CE

### Meaning

There are files on the Net-Storage volume (&00) without
a catalog entry.
Therefore it is not possible to delete the respective directory
on the Net-Storage.

### Response

Contact system administrator

## DMS1C0F

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C0F Creation/remove of the Net-Storage volume is only possible on the master

### Response

Enter ADD-NET-STORAGE-VOLUME command on the master.

## DMS1C01

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1C01 Command '(&00)' has been executed correctly.

## DMS1C02

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C02 No Net-Storage volume found for pubset '(&00)'

## DMS1C04

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C04 Error '(&00)' at the access on the NET CLIENT

### Meaning

This message provides information about a problem
(open, close, create or delete of a file, respectively
create or delete of a Net-Storage volume),
that are reported from the subsystem ONETSTOR during
Net-Storage access.
(&00) contains the 8 hex-character error information 'xxxxxxxx'.
xxxxxx01 : internal error in the subsystem ONETSTOR
0Axxxx02 : the file-identifier is no more valid.
(e.g. after UMOUNT with FORCE=YES)
xxxxxx02 : if first character not equal '0A': internal error
xxxxxx03 : Timeout. Request was not terminated within the expected
time..
xxxxxx04 : no more memory
xxxxxx07 : communcation / connection error to net client
xxxxxx80 : net client not available
xxxxxxFE : internal error in the net client
84xxxxFE : mount id in the net client is no longer valid
xxxxxxFF : net client returns a specific error that is specified in the
first 2 characters
09xxxxFF : invalid file descriptor
0DxxxxFF : permission denied
1ExxxxFF : file system read only

### Response

Contact system administrator

## DMS1C05

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C05 PUBSET NOT FOUND. COMMAND REJECTED

### Meaning

The pubset with the specified catalog ID or with the
specified characteristics does not exist.

### Response

Correct the command.

## DMS1C06

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C06 PUBSET NOT ACCESSIBLE. COMMAND REJECTED

### Meaning

The specified pubset is not accessible.

### Response

Import the pubset.

## DMS1C07

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C07 Allocation/deallocation of Net-Storage volume (&01) failed. Internal RC (&00)

### Meaning

NDM could not allocate/deallocate Net-Storage resources
(&00) contains the 8 hex-character error information 'xxxxxxxx'
(&01) VSN of the Net-Storage volume
01400001 : mount not possible, mount point not available

### Response

Contact system administrator

## DMS1C08

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C08 Internal error '(&00)' after a CMS call

### Meaning

An internal error '(&00)' occurred during the call of a
CMS function.

### Response

Contact system administrator

## DMS1C09

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C09 Internal error (&00) after the call of a function for the catalog on the Net-Storage volume.

### Response

Contact system administrator

## DMS1C1A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C1A Net-Storage volume (&00) is already IN USE.

## DMS1C1B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C1B Net-Storage volume (&00) doesn't exist. Therefore the Net-Storage volume cannot be imported.

## DMS1C1C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C1C PERMISSION ON NET DIRECTORY (&00) DENIED.

## DMS1C1D

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C1D Error '(&00)' during access to file '(&01)'

### Meaning

This message provides information about a problem
that is reported during Net-Storage access.
(&01) contains the affected file.
(&00) contains the 8 hex-character error information 'xxxxxxxx'.
xxxxxx01 : internal error in the subsystem ONETSTOR
0Axxxx02 : the file-identifier is no more valid.
(e.g. after UMOUNT with FORCE=YES)
xxxxxx02 : if first character not equal '0A': internal error
xxxxxx03 : Timeout. Request was not terminated within the expected
time..
xxxxxx04 : no more memory
xxxxxx07 : communcation / connection error to net client
xxxxxx80 : net client not available
xxxxxxFE : internal error in the net client
84xxxxFE : mount id in the net client is no longer valid
xxxxxxFF : net client returns a specific error that is specified in the
first 2 characters
02xxxxFF : file not exists
09xxxxFF : invalid file descriptor
0DxxxxFF : permission denied
11xxxxFF : file already exists
1ExxxxFF : file system read only
xxxx0222 : INPUT/OUTPUT error, half page not in file
xxxx0225 : INPUT/OUTPUT error, illegal operation
xxxx0226 : INPUT/OUTPUT terminated with logical error
xxxx0227 : INPUT/OUTPUT terminated without data transfere
xxxx0228 : INPUT/OUTPUT error, invalid DAR index
xxxx022C : INPUT/OUTPUT error, invalid extent list

### Response

Contact system administrator

## DMS1C1E

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C1E Error '(&00)' at access to CE or .FSL of Net-Storage volume

### Meaning

Error happens at administration files on Net-Storage volume
(&00) contains the reason.
01xx0026 : CE or .FSL already exists
02xx0026 : CE or .FSL do not exists
03xx0026 : there are files on Net-Storage volume
04xx0026 : CMS Error
0Bxx0026 : Permission denied on .FSL
0000000D : File system could only be read (Soft WORM)

### Response

Contact system administrator

## DMS1C10

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C10 Files are locked on NET-STORAGE VOLUME (&00)

### Meaning

On the Net-Storage volume (&00) files are locked.
Therefore the Net-Storage volume cannot be exported.

### Response

Contact system administrator

## DMS1C11

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C11 Net-Storage volume (&00) exists, therefore the IMPORT is not possible

### Meaning

The Net-Storage volume (&00) has already been created.
Therefore the IMPORT of the Net-Storage volume under this name
is not possible.

### Response

Contact system administrator or correct the command

## DMS1C12

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C12 Net-Storage volume cannot be added to a home pubset

## DMS1C13

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C13 Internal error (&00) at the access to the host (&01)

### Meaning

An internal error (&00) occurred during the call of
$MCSSNDI for host (&01).

### Response

Contact system administrator

## DMS1C14

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C14 Internal error '(&00)' after WATCHDOG call

### Meaning

An internal error '(&00)' occurred during the call of
$DPSWDGI.

### Response

Contact system administrator

## DMS1C15

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C15 Internal error (&00) during allocation/deallocation of Net-Storage volume for slave (&01)

### Response

Contact system administrator

## DMS1C16

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C16 Files on Net-Storage VOLUME (&00) have not been imported, deleting is not possible

### Meaning

On the Net-Storage volume (&00) there are files, which
have not yet been imported on the pubset.
Therefore REMOVE-NET-STORAGE-VOLUME with FILES-ON-VOLUME = *DELETE
is not possible.

### Response

Import the files from the Net-Storage volume to the pubset.

## DMS1C17

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C17 THE ACCESS OF THE NET DIRECTORY (&00) IS NOT POSSIBLE.

### Meaning

Possible reasons :
- Net directory does not exist
- Invalid specification of the server.
- Mount of the net directory is missing.

### Response

Contact system administrator or correct the command.

## DMS1C18

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C18 The access of the Net-Storage volume (&00) is not possible

### Meaning

Possible reasons :
- Net-Storage volume does not exist.
- Associated net directory is not mounted.
- Net-Storage volume is only ONLINE.
If catalog entries still exist for the NET-STORAGE-VOLUME
from an earlier session, they are deleted with a
REMOVE-NET-STORAGE command with FILES-ON-VOLUME=*DELETE(FORCE=*YES).

### Response

If necessary contact the system administrator or correct the command.

## DMS1C19

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C19 Net-Storage volume (&00) already exists under another directory.

### Response

Contact system administrator or correct the command.

## DMS1C20

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C20 Name of the VSN of the Net-Storage volume (&00) is not valid.

### Meaning

- VSN of the Net-Storage volume is not permitted to start with PUB.
- In the name of VSN of the Net-Storage volume a dot is not allowed.

### Response

Correct the command.

## DMS1C21

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C21 Invalid IP address (&00)

## DMS1C30

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C30 There is no occupation for mount-id '(&00)'.

## DMS1C31

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C31 Invalid mount-id '(&00)'.

### Response

Contact system administrator or correct the command.

## DMS1C32

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1C32 Warning: TASK ID '(&00)' is in the lock list, but the task does not exist.

### Response

Contact system administrator

## DMS1DA1

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DA1 Warning: Invalid VSN for device '(&00)'. Mount VSN '(&01)' for file '(&02)', VSEQ '(&03)'. Processing continue.

### Meaning

The VSN in the specified label does not have the expected value.
(&00): mnemonic device name
(&01): volume serial number
(&02): file name
(&03): file section number.

## DMS1DA3

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DA3 Warning: Tape write protected: VSN '(&00)' for file '(&01)', VSEQ '(&02)'. Processing continues.

### Meaning

A tape was overwritten (partially) whose contents have been
defined as read-only or whose retention period has not yet expired.

## DMS1DA5

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DA5 Warning: Invalid file identification: VSN '(&00)' for file '(&01)', VSEQ '(&02)'. Processing continues.

### Meaning

On checking the file header labels HDR1 and HDR3 it was found that
the file name, the generation number or the file section did not
match the expected value.
(&00): VSN
(&01): file name.
(&02): file section number.

## DMS1DCF

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DCF Warning: Invalid tape label with VSN '(&00)' for file '(&01)', VSEQ '(&02)'. Processing continue.

### Meaning

A field of a standard file label (HDR1, HDR2 or HDR3) does not
correspond to the defined format.

## DMS1DDF

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DDF INVALID FILE SEQUENCE NUMBER. MOUNT VSN '(&00)' FOR FILE '(&01)', VSEQ '(&02)'.

### Meaning

Error in the file sequence numbers:
FILE-SEQUENCE or FSEQ=NEW or >1 has been specified and the tape has
standard labels although LABEL=NON-STD or NO was specified.

## DMS1DD4

Destination: USER-TASK, CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DD4 Warning: Illegal use of BTAM or PAM in OUTPUT mode. VSN '(&00)' for file '(&01)', VSEQ '(&02)'. Processing continue.

### Meaning

Use of BTAM or PAM in output mode is not possible as the
DIN-REVISION-NUMBER of the standard label is greater than 1.

## DMS1DD6

Destination: CONSOLE Routing code: T Weight: 98

Warranty : NO

DMS1DD6 Warning: Invalid file set identifier on VSN '(&00)' for file '(&01)', VSEQ '(&02)'. Processing continues.

### Meaning

The file set identifier of a file being opened or continued on the
requested tape does not match the specified value or the value from the
first file section.

## DMS1D0A

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D0A Invalid file. Command not processed

### Meaning

The specified file does not exist, does not reside on a public
volume or is not local accessible.

## DMS1D0B

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D0B Changed file data must be immediately saved. Command not processed

### Meaning

The user wanted to cache write IOs to a file which may be
opened only for output operations where the data are saved
immediately. The actual cache medium does not support this
higher security requirement.

### Response

If the output data to this file should be cached anyhow,
please change the file attribute in the catalog and
enter the command again.

## DMS1D0C

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D0C Error on saving/invalidating the data in cache. Command not processed

### Meaning

Possibly the error cause is a defective block in the file or
some other hardware error.

### Response

Try again; if the problem persists, inform the system
administrator.

## DMS1D0D

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D0D No memory available. Command aborted

### Meaning

A memory request was not fulfilled.

## DMS1D0E

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D0E MSCF connection error. Command aborted

### Meaning

The command could not be processed because it could not attain
the information required from the master of the shared pubset,
on which the file resides, because of an error in the MSCF
connection.

### Response

Check the MSCF state of the pubset and retry the command.

## DMS1D0F

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D0F Error on calling Catalog Management. Returncode '(&00)', internal error number '(&01)'. Command aborted

### Meaning

The exact error cause may be determined by means of the command
/HELP-MSG-INFORMATION, where the MSG-ID should be built by
concatenating the prefix "DMS" with the last 4 digits of
the returncode (&00).

### Response

The recommended action is specified in the DMS message.

## DMS1D01

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D01 No action is necessary. Command terminated

### Meaning

Several situations may occur:
a) The command /START-FILE-CACHING was entered for a file which
is already being cached. This comprises a situation where the
IO performance attribute *HIGH is already in effect and the caller
wanted to upgrade this attribute to *VERY-HIGH. The attribute
remains unchanged.
b) The command /STOP-FILE-CACHING was entered for a file which is
not cached and of which there are no data left in the cache.

## DMS1D02

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D02 Wrong syntax file

### Meaning

The command /START-FILE-CACHING or /STOP-FILE-CACHING was
called with syntactically invalid operands.

### Response

Contact Your system administrator or customer support.

## DMS1D03

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D03 User has no access right for the specified file

### Meaning

The command /START-FILE-CACHING or /STOP-FILE-CACHING was
entered for a file which the user may neither write, read,
nor execute. The access right for the file is also denied,
if there is some access limitation (GUARDS) which inhibits
the access actually.

### Response

Check the protection attributes of the specified file

## DMS1D04

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D04 A not actual or remote cache contains file data. Command not processed

### Meaning

The command /START-FILE-CACHING was entered for a file
for which there are still data in a cache (a previous attempt
to write the cached data back to disc failed) or the file is
cached by DAB on a remote system or a
/STOP-FILE-CACHING was entered for a file for which there
are data in a cache which is not accessible (e.g. the
cache of another host).

### Response

For START-FILE-CACHING: save the file data with
/STOP-FILE-CACHING after having connected the cache.
Any new open will also clear the file state.
For STOP-FILE-CACHING: Connect again the cache containing the
file data. If this cache cannot be connected again, the
file can be made accessible again with loss of the data
in cache by means of the command
/REMOVE-FILE-ALLOCATION-LOCKS OPEN-ALLOWED=*YES.

## DMS1D05

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D05 The specified file is not open

### Meaning

The file specified as /START-FILE-CACHING or /STOP-FILE-CACHING
operand is not opened in the local system.
For /STOP-FILE-CACHING this message is only displayed if the data
in the cache do not origin from a previous file access but from
a remote system.
Also a POSIX file may be specified.
Such files are not supported by User-PFA.

## DMS1D06

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D06 No cache available

### Meaning

No active cache is connected to the pubset on which the file
resides. Therefor it is not possible to start file caching.

## DMS1D07

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D07 The user privilege for high performance IOs is missing

### Meaning

The command /START-FILE-CACHING could not be executed,
because the user is only privileged for standard performance
file access.

### Response

Ask Your system/user administrator to confer the privilege
for higher performance file access to Your user id by means
of the command /MODIFY-USER-ATTRIBUTES ...
DMS-TUNING-RESOURCES=*EXCLUSIVE-USE or =*CONCURRENT-USE.

## DMS1D08

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D08 Caching is not allowed for this file

### Meaning

The command /START-FILE-CACHING was entered for a file which
has been opened with explicit specification "PERFORMANCE=STD".
Therefore the command was not processed.

## DMS1D09

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D09 The file is opened with XCS environment. Command aborted

### Meaning

While a file is opened with XCS environment, it can be cached
only by controller. As the actual cache medium is another
medium, the command /START-FILE-CACHING could not be processed.

## DMS1D1F

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D1F The catalog entry lock could not be released

### Meaning

The catalog entry lock requested during the execution of the
command /START-FILE-CACHING or /STOP-FILE-CACHING could not be
released.

### Response

Contact the system maintenance.

## DMS1D10

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D10 Internal error. Returncode '(&00)', internal error number '(&01)'. Command aborted

### Meaning

During command processing, a system call was not correctly
executed.

### Response

Contact the system maintenance.

## DMS1D11

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D11 Subsystem 'DAB' not available. Command not processed

### Response

Start the subsystem DAB and enter the command again.

## DMS1D12

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D12 Write DAB-caching not possible at the moment. Command not processed

### Meaning

The file is currently being opened by another system.

### Response

Retry the command later again.

## DMS1D13

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1D13 DAB-caching is not possible at the moment. Command not processed

### Meaning

The file is possibly currently being opened in write-mode by
another system.

### Response

Retry the command later again.

## DMS13AA

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

Warranty : NO

DMS13AA Pubset (&03), catalog (&00): destroyed PBN-block "(&02)" of user '(&01)' was newly initialized.

### Meaning

(&00): name of catalog
(&01): userid
(&02): LHP of newly initialized PBN-block
(&03): pubset-id

## DMS13AB

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

Warranty : NO

DMS13AB Pubset (&03), catalog (&00): partition of user '(&01)' was truncated behind catalog block "(&02)".

### Meaning

(&00): name of catalog
(&01): userid
(&02): new last logical block of the truncated partition
(&03): pubset-id

## DMS13AC

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

Warranty : NO

DMS13AC Pubset (&03), catalog (&00): PBN-block "(&02)" of user '(&01)' destroyed. The user partition was deleted from catalog.

### Meaning

(&00): name of catalog
(&01): userid
(&02): logical block number of PBN block
(&03): pubset-id

## DMS13AD

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

Warranty : NO

DMS13AD Pubset (&00): repair of catalog '(&01)' failed.

### Meaning

(&00): pubset-id
(&01): catalog name

## DMS13AE

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

Warranty : NO

DMS13AE Pubset (&00): At least one catalog block, containing CE's, must be deleted in catalog "(&01)". Continue repair of catalog (Y/N)

### Meaning

(&00): pubset-id
(&01): name of catalog

### Response

The repair of catalog is continued, if the answer is "Y" (this answer
should only be given after contacting the system service).
If the answer is "N", the import of the pubset will be terminated.

## DMS13AF

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

Warranty : NO

DMS13AF Pubset (&00), PBN-block of user TSOS in catalog '(&01)' is destroyed.

### Meaning

(&00): pubset-id
(&01): name of catalog

## DMS13A0

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

Warranty : NO

DMS13A0 Pubset (&00): Enlargement of catalog file (&01) failed.

### Meaning

The catalog file (&01) in pubset (&00) has been enlarged. Because of
internal CMS problems during update of the CMS management tables
affected by the enlargement, the catalog enlargement does not take
effect immediately, but at the next import of the pubset.

### Response

Export and then re-import pubset so that the catalog enlargement
can become effective.

## DMS13A1

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

Warranty : NO

DMS13A1 Pubset (&00): The Task with the TSN '(&01)' for reconstruction of (&02) was started.

### Meaning

The CMS has detected an error in the structures of the catalog index.
Therefore the catalog index, or parts of the catalog index, will be
reconstructed from partial catalogs of the SM pubset (&00) by
the task (&01).
(&02) specifies the part of the catalog index that will be reconstructed:
- the entire catalog index
- the user PBN table of the catalog index
- the directory and the freelist of catalog TSOSCAT.<xxxx>
- the freelist of catalog TSOSCAT.<xxxx>
where <xxxx> is a volumeset ID or the ID of a special ca-
talog (#JVC = JV-catalog, #MIN = catalog for migrated or not al-
located files, #PVT = catalog for files on tape or private disc)

## DMS13A2

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

Warranty : NO

DMS13A2 Pubset (&00): Reconstruction of (&01) done.

### Meaning

The reconstruction of the catalog index or one of its substructures
in the SM pubset was successfully completed.
(&01): specifies the part of catalog index that was reconstructed:
- the whole catalog index
- the user PBN table of the catalog index
- the directory and freelist of catalog TSOSCAT.<xxxx>
- the freelist of catalog TSOSCAT.<xxxx>
where <xxxx> is the ID of a volumeset or a special ca-
talog (#JVC = JV-catalog, #MIN = catalog for migrated or not al-
located files, #PVT = catalog for files on tape or on private
disc)

## DMS13A3

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

Warranty : NO

DMS13A3 Pubset (&00): Reconstruction of (&01) failed.

### Meaning

The reconstruction of the catalog index or one of its substructures
in the SM pubset failed.
(&01): specifies the part of catalog index that was reconstructed:
- the whole catalog index
- the user PBN table of the catalog index
- the directory and freelist of catalog TSOSCAT.<xxxx>
- the freelist of catalog TSOSCAT.<xxxx>
where <xxxx> is the ID of a volumeset or a special catalog
(#JVC = JV-catalog, #MIN = catalog for migrated or not al-
located files, #PVT = catalog for files on tape or on private
disc)

## DMS13A4

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

Warranty : NO

DMS13A4 Pubset (&00): Catalog index at maximum size.

### Meaning

Request the system administrator to erase files or JV's that are no longer
required.

### Response

Files and JV's that are no longer required should be erased by the system
administrator.

## DMS13A5

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

Warranty : NO

DMS13A5 Pubset (&00): Catalog index destroyed.

### Meaning

The CMS operation cannot be executed because the catalog index of the
specified SM pubset is destroyed.

### Response

Retry, as the catalog index may be reconstructed in the meantime.
Reconstruction will be performed during the next IMPORT-PUBSET
at the latest.

## DMS13A6

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

Warranty : NO

DMS13A6 Pubset (&00): Reconstruction of (&01) not possible. Reason is (&02).

### Meaning

The reconstruction of the catalog index or one of its substructures in
the SM pubset (&00) is not possible. Insert (&02) gives the reason.
(&01): specifies the part of catalog index that will be reconstructed:
- the whole catalog index
- the user PBN table of the catalog index
- the directory and freelist of catalog TSOSCAT.<xxxx>
- the freelist of catalog TSOSCAT.<xxxx>
where <xxxx> is the ID of a volumeset or a special catalog
(#JVC = JV-catalog, #MIN = catalog for migrated or not al-
located files, #PVT = catalog for files on tape or on private
disc)
(&02): number that describes the cause of the error
01: problems, when resetting internal lock
02: problems, when setting internal lock
03: reconstruction not allowed during IMPORT or EXPORT-PUBSET
for SM pubset
04: reconstruction already failed before
05: synchronization error, when creating the reconstruction task
06: error, when destroying catalog index bourse
07: internal error
08: reconstruction task could not be created
09: error when calling the CMS-buffermanagement

## DMS13A7

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

Warranty : NO

DMS13A7 Pubset (&03), catalog (&00): (&04)-partition of user '(&01)' : '(&02)'

### Meaning

The user chain of the user in the catalog is displayed.
(&00): name of catalog
(&01): userid
(&02): user chain (or a part of it)
(&03): pubset-id
(&04): insert "file" or "JV"

### Response

Please contact the system service!

## DMS13A8

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

Warranty : NO

DMS13A8 Pubset (&03), catalog (&00): partition of user '(&01)' could only be read up to LHP '(&02)'.

### Meaning

The user chain of the user in the catalog is displayed.
(&00): name of catalog
(&01): userid
(&02): last LHP of user chain that could be read
(&03): pubset-id

## DMS13A9

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

Warranty : NO

DMS13A9 Pubset (&03), catalog (&00): catalog block "(&02)" of user '(&01)' was deleted from users partition.

### Meaning

(&00): name of catalog
(&01): userid
(&02): LHP, that was deleted from user's partition
(&03): pubset-id

## DMS13BA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13BA LIST-CATALOG-ENTRY IN FILE (&00) REJECTED. A FILE WITH THE SAME NAME ALREADY EXISTS.

### Meaning

LIST-CATALOG-ENTRY rejected.
(&00): name of output file

### Response

Correct the problem and repeat the command.

## DMS13BB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13BB ADD-CATALOG-FILE OF PUBSET (&00) AND CATALOG (&01) REJECTED. REASON (&02).

### Meaning

(&00): PUBSET ID
(&01): type of catalog
(&02): reason
(&02): '1'; maximal file number of special catalog reached
'2'; pubset is no sm pubset with catalog format EXTRA LARGE
'3'; limit of pubspace reached
'4'; pubset is not master in 'Shared Pubset'
'5'; time problems (no correction, only repeat)

### Response

Correct the problem and repeat the command.

## DMS13BC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13BC ADD-CATALOG-FILE OF FILE (&00) REJECTED. REASON (&01).

### Meaning

(&00): name of catalog file
(&01): reason
(&01): '1'; a file with the same name already exists

### Response

Correct the problem and repeat the command.

## DMS13BD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13BD CATALOG FILE (&00) WAS CREATED AND ADDED TO THE CATALOG (&01).

### Meaning

(&00): name of catalog file
(&01): type of catalog

## DMS13BE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13BE SHOW-PUBSET-CATALOG-ALLOCATION OF PUBSET (&00) REJECTED. REASON (&01).

### Meaning

(&00): PUBSET ID
(&01): reason
(&01): '1'; pubset is not locally accessible

### Response

Correct the problem and repeat the command.

## DMS13BF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13BF CATALOG INDEX OF PUBSET (&00) IS RECONSTRUCTED.

### Meaning

(&00): PUBSET ID

## DMS13B0

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

Warranty : NO

DMS13B0 Pubset (&00): Volumeset (&01) not added in user PBN table.

### Meaning

Not enough memory to enlarge the user PBN table and to add a new
volumeset.

### Response

Release memory and repeat the addition of the new volumeset.

## DMS13B1

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

Warranty : NO

DMS13B1 Pubset (&00): Release of empty PBN block in volumeset (&01) failed.

### Response

Evaluate the serslog file.

## DMS13B2

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

Warranty : NO

DMS13B2 Pubset (&00): Volumeset (&01) is exported by the reconstruction.

### Meaning

Import of volumeset is not completed or deactivation of volumeset is
already started.

## DMS13B3

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

Warranty : NO

DMS13B3 Pubset (&00): Reconstruction type changed to 'GLOBAL' because type '(&01)' error occurred.

### Meaning

(&01): cause of error:
01: No CMS file ID given
02: No valid reconstruction type given

## DMS13B4

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

Warranty : NO

DMS13B4 Pubset (&00): Reconstruction failed because a type '(&01)' error occurred.

### Meaning

(&01): cause of error:
01: internal error
02: invalid internal pubsetid
03: no more memory available

### Response

if cause of error is '01' or '03': serslog entry must be evaluated

## DMS13B5

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

Warranty : NO

DMS13B5 Pubset (&00): PPAM error occurred. Volumeset (&01) has to be frozen.

### Response

Evaluate serslog file.

## DMS13B6

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

Warranty : NO

DMS13B6 Pubset (&00): Please enlarge catalog index file! System administrator informed? Reply (Y=YES)

### Response

Request the system administrator to enlarge the catalog index file.
Y: the system administrator has been informed and has enlarged the file.

## DMS13B7

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

Warranty : NO

DMS13B7 Pubset (&00): Catalog index file invalid because it is not big enough.

## DMS13B8

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

Warranty : NO

DMS13B8 Volumeset (&01) is not part of pubset (&00) and therefore is not reconstructed.

### Meaning

Reconstruction is terminated immediately.

## DMS13B9

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

Warranty : NO

DMS13B9 Pubset (&00): IMPORT-PUBSET aborted because the version of the catalog index file is invalid.

## DMS13CA

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS13CA Master change of pubset '(&00)' aborted with error '(&01)'

### Meaning

An error occurred during master change import at consistency check of
volume list or while restarting an interrupted pubset reconfiguration.
(&00): reason of abort
'01': param error
'02': internal error
'03': pubset not available
'04': pubset not found
'05': configuration error
'06': memory saturation
'99': other error

### Response

The pubset should be exported

## DMS13CB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13CB Specified lock does not exist

### Meaning

The lock specified by locktype, lock location, sysid of
lockholder and taskid of lockholder does not exist. Possibly
an invalid sysid was specified or there is currently no MSCF connection
to the system identified by the sysid.

## DMS13CC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13CC Specified lockholder task is still active

### Meaning

The lockholder task of the specified lock is still active. Only
locks without a valid lockholder task or with their lockholder
task in state 'pended indefinitely' can be removed.
This message is also issued if the state of the lockholder task could not
be determined because of failure of the MSCF connection to the
lockholder host.

### Response

Repeat the command on the lockholder host in case of a failed MSCF
connection.

## DMS13CD

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

Warranty : NO

DMS13CD Pubset reconfiguration management lock removed for pubset '(&00)'

## DMS13CE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13CE There are no locks for the specified pubset

## DMS13CF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13CF Interrogation of locks on host '(&00)' is not possible. Reason: '(&01)'

### Meaning

Lock information could not be obtained from the specified host.

## DMS13C0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13C0 Export with masterchange of pubset '(&00)' failed with errorcode '(&01)'

### Meaning

(&00): pubset id
(&01): cause of error
01, no slaves imported
02, there is least one slave, whose bs2000 version is
less than OSD-BC V3.0

### Response

measures on errorcode:
01, call export pubset without masterchange
02, export slave(s) with version less than OSD-BC V3.0 explicitly

## DMS13C1

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

Warranty : NO

DMS13C1 Reconfiguration task with TSN '(&00)' for pubset '(&01)' not yet finished

### Meaning

This message is called every five minutes if a reconfiguration
task running on the master host has not yet finished. While a
reconfiguration task is running, import and export tasks are
accepted but waiting in a signal queue for the end of the
reconfiguration
(&00): TSN of reconfiguration task
(&01): pubset id

### Response

If the reconfiguration task is waiting for a resource, the resource
should be granted. Import- or export tasks waiting in the signal
bourse can be cancelled by /EXPORT-PUBSET or /CANCEL-PUBSET-EXPORT
command

## DMS13C2

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

Warranty : NO

DMS13C2 '(&00)' task with TSN '(&01)' on slave host '(&02)' is occupying the reconfiguration lock for pubset '(&03)'

### Meaning

This message is called every five minutes, if an import/export task
on a slave host has not yet released the reconfiguration lock.
Incoming reconfiguration services are placed in a signal queue
waiting for the release of the reconfiguration lock
(&00): SLAVE-IMPORT or SLAVE-EXPORT
(&01): TSN of the import/export task
(&02): MSCF name of slave host
(&03): pubset id

### Response

If the import-export task is waiting for a resource, it should be
provided.

## DMS13C3

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

Warranty : NO

DMS13C3 MRSCAT access error '(&00)' for volumeset '(&01)' of pubset '(&02)' with access type '(&03)'

### Meaning

An error occurred when accessing volumeset MRSCAT via the $CATM
interface (on create, update or delete). For an error description of
error &00 (&00=XXXX) look at message CMSXXXX.
(&00): error-code XXXX of message CMSXXXX
(&01): volumeset id
(&02): SM pubset id
(&03): access type = 1: create
access type = 2: update
access type = 3: delete

## DMS13C4

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

Warranty : NO

DMS13C4 Warning: Internal error occurred in reconfiguration lock management

### Meaning

An internal error occurred within the reconfiguration lock management:
continuing the task. A serslog entry was written and the task
continued processing.

### Response

Read the serslog entry

## DMS13C5

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

Warranty : NO

DMS13C5 Volume '(&00)' does not match volume '(&01)' because of '(&02)'

### Meaning

A mismatch between the new volume (&00) and the pubres/volres
volume (&01) occurred due to error (&02) while trying to add a
new volume to a SF pubset or to a volumeset of a SM pubset.
(&00): VSN of volume you want to add
(&01): VSN of pubres/volres volume
(&02): errorcode = 1: volume (&00) is a GS volume, but volume (&01)
is not
errorcode = 2: volume (&00) is not a GS volume,
but volume (&01) is
errorcode = 3: GS volume (&00) does not match
GS volume (&01)
errorcode = 4: GS subsystem not accessible, both volumes
cannot be checked
errorcode = 5: error on calling of $NDGCHKI

### Response

on errorcode 1-3 you must add a volume with correct GS-type, on
errorcode 4 you must activate subsystem GSVOL.

## DMS13C6

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

Warranty : NO

DMS13C6 Warning: Internal error occurred in import-export processing

### Meaning

An error has occurred in import-export processing.
A serslog entry was written and the task continued processing

### Response

Evaluate the serslog entry

## DMS13C7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13C7 Host with sysid '(&00)' is the master of pubset '(&02)' according to the svl of pubres '(&01)'. Do you still want to force the master import ? Reply (FORCE-MASTER-IMPORT=yes; N=no)

### Meaning

This message is issued if the pubset (&02) has to be imported as
master, but the svl of pubres (&01) indicates that host (&00) is
occupying the pubset as master. Trying to get the status of pubset
(&02) via mscf communication with host (&00) did not succeed or
obtained the pubset status inacc.

### Response

FORCE-MASTER-IMPORT: By calling an internal "unlock disk" the
occupation of the pubset by host (&00) in the svl is removed.
But pay attention ! If the old master is actually working on the
pubset, there are now two masters working concurrently, which will
lead to the destruction of the pubset
N: The import is aborted

## DMS13C8

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

Warranty : NO

DMS13C8 Error on access of configuration file of pubset '(&00)' with error code '(&01)'

### Meaning

an error occurred either creating the configuration file, or while
reading or writing a configuration record (interface DPSCFGF)
(&00): pubset id
(&01): reason of the error
01, pubset record in TSOSCAT inconsistent
02, error on function create-file
03, error on function read-ctl-volset-record
04, error on function read-pubset-record
05, error on function read-all-volsets
06, error on function read-volset
07, error on function update-volset
08, error on function write-pubset-new
08, error on function write-volset-new

### Response

If error is caused by transient hardware problems, you should
retry the pubset import (for error codes 1-8 a serslog entry was
written).

## DMS13C9

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS13C9 Remote pubset '(&00)' cannot be imported (errorcode '(&01)')

### Meaning

(&00): pubset ID
(&01): error code:
'01': the pubset cannot be imported exclusively
'02': the pubset mrscat is defined as exclusive
'03': the pubset cannot be imported as shared master

### Response

measures:
the pubset can only be imported as slave, provided that the
mrscat is defined sharable.

## DMS13DA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13DA The snapset limit has to be in the range of '(&00)' to '(&01)'

### Meaning

(&00): Minimum value of snapset limit
(&01): Current maximum value of snapset limit
The snapset limit could not be modified for one of the following
reasons:
1. The specified value is less than the current number of snapsets.
2. The specified value is greater than the number of remaining
available snap mirrors.
3. The pubset is not imported. In this case it is not possible to
determine whether or not active snap mirrors are used as snapsets.
Therefore checks 1 and 2 are performed with worst-case assumptions.
4. A value greater than 26 was specified for a shared pubset imported
by one or more systems running BS2000/OSD V7.0.

### Response

1. Delete one or more of the active snapsets (Note: When deleting
all snapsets by means of command /DELETE-SNAPSET *ALL the snapset
limit is automatically reset to 0)
2. Reduce the number of pubset mirrors that are not used as snapsets.
3. Import pubset.
4. Export pubset from all systems running BS2000/OSD V7.0.

## DMS13DB

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS13DB Homogeneity check for pubset '(&00)' cancelled due to not unique volume serial number '(&01)'

### Meaning

During homogeneity check of the pubset mirroring a not unique
volume serial number has been detected
(e.g.: volume is mirrored by DRV).

### Response

Uniqueness of concerned volume should be ensured, afterwards
homogeneity check for pubset can be repeated.

## DMS13DC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13DC Creation of a snapset for pubset '(&00)' failed because of error '(&01)'. Command was not executed

### Meaning

(&00): Catalog Id
(&01): Error Type
'01': Volume Serial Number not unique
'02': DRV volume
'03': Volume Set in state 'DEFECTIVE'
'04': Volume Set in state 'IN HOLD'
'05': Mirror volume

## DMS13DD

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13DD Saturation level of '(&00)' is exceeded for save pool '(&02)' on Symmetrix with serial number '(&01)'. Snapset '(&03)' on pubset '(&04)' is deleted

### Meaning

(&00): saturation level
(&01): Symmetrix serial number
(&02): save pool
(&03): snapset id
(&04): catalog id
(&04): catalog id

## DMS13DE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13DE SNAPSET '(&00)' OF PUBSET '(&01)' IS NOT AVAILABLE. EITHER IT IS STILL BEING PROCESSED OR IMPORT PROCESSING FAILED FOR THE SNAPSET

### Meaning

(&00): snapset id
(&01): catalog id

## DMS13DF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13DF Subsystem SHC-OSD not available. Command not processed

### Response

Contact your system administrator.

## DMS13D0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D0 /SHOW-PUBSET-IMPORT-EXPORT for Pubset '(&00)' failed with error '(&01)'

### Meaning

(&00): pubset id of pubset for which an error (&01)' occurred
(&01): Errorcode
'01' pubset mrscat not found
'02' specified volset mrscat not found
'03' pubset/volset mrscat type not correct
'04' specification of control volset not possible
'05' internal syntax error
'06' internal mrscat error
'07' error on sysout
'08' error on OPS output
'09' internal OPS error
'10' OPS- operational error
'11' OPS subsystem error

### Response

for error code 1-4: correct the command operands

## DMS13D1

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS13D1 /CANCEL-PUBSET-IMPORT for pubset '(&00)' completed with error code '(&01)'

### Meaning

(&00): pubset id
(&01): error code
'01': mrscat not found
'02': wrong mrscat type
'03': pubset not in import
'04': cancel already issued
'05': mrscat internal error
'06': error reading the volume list
'07': error on release of darid
'08': error on release of volume list lock
'09': error on sending signal on signal bourse
'10': cancel import not allowed (e.g. in master change)

### Response

measures on error code '(&01)':
'01'-'02' repeat command with correct pvsid

## DMS13D2

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS13D2 volumeset status inconsistency for volset '(&00)' in pubset '(&01)' with error code '(&02)'

### Meaning

(&00): volumeset id
(&01): pubset id
(&02): error code
'01': volset specified both in 'in hold list' and in
'defective list'.
'02': volset specified as defect in configuration file but
not in defect list.
'03': volset status inconsistent in configuration file and
mrscat entry.
'04': volset specified in 'in hold list' does not belong
to pubset.
'05': volset specified in 'in hold list' is specified as
'defined only' in configuration file

### Response

measures on error code '(&02)':
'01': specify Volset in 'in hold-list' or 'defect list'.
'02': specify Volset in 'defect list'.
'03 : export pubset.
'04-05 : repeat IMPORT with correct 'in hold list'

## DMS13D3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D3 Host with sysid '(&00)' is slave sharer of pubset '(&02)' according to the svl of pubres '(&01)'. Do you want to continue the master import with unlock-disk ? Reply (Y=yes; N=no)

### Meaning

This message is issued if the pubset (&02) has to be imported as
master, but the svl of pubres (&01) indicates that host (&00) has
imported the pubset as slave. Trying to get the status of the pubset
(&02) via mscf communication from host (&00) did not succeed.

### Response

Answer=Y: By calling an internal "unlock disk" the occupation of
the pubset by host (&00) in the svl is removed.
But pay attention ! If the slave (&00) is actually working on the
pubset, data destruction is possible.
In any case you should try to delete the slave sharer from the svl
via EXPORT-PUBSET locally on host (&00)
Answer=N: The master import is aborted

## DMS13D4

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS13D4 EXPORT-PUBSET processing of pubset '(&01)' continues with error code' '(&00)'

### Meaning

(&00): error code
'01': POSIX subsystem occupies pubset
'02': POSIX task occupies pubset
'03': Linkage error and occupation by POSIX
'04': POSIX temporarily unable to reduce all occupations
(&01): pubsetid

### Response

measures on error code '(&00)':
(&00): '01': stop POSIX subsystem
'02': end Posix Pubset occupation
'03': take measure '01' or '02'
'04': none: Posix calls are repeated internally

## DMS13D5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D5 THE SPECIFIED SNAPSET '(&00)' DOES NOT EXIST FOR PUBSET '(&01)' . COMMAND NOT PROCESSED

### Meaning

(&01) : Catalog Id
(&00) : Snapset Id

## DMS13D6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D6 Snapset limit not specified for pubset '(&00)' or snapset limit has maximum value

### Meaning

(&00) : Catalogue Id

### Response

Set Snapset-limit with command /SET-PUBSET-ATTRIBUTE or specify a value
<> *NO for parameter DELETE-EARLIEST in command CREATE-SNAPSET

## DMS13D7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D7 Snapset processing for Pubset '(&00)' failed with error '(&01)'

### Meaning

(&00): pubset id of pubset for which error '(&01)' occurred
(&01): Error reason
'01' Subsystem GCF
'02' Device Management
'03' Basic SVL
'04' Pubset Reconfiguration
'05' Volume List
'06' Subsystem SHC-OSD
'07' Subsystem CCOPY
'08' File/library on a snapset is being accessed
'09' Only the oldest snapset can be deleted
(depends on the respective storage system)

### Response

Determine the failure and repair if possible.

## DMS13D8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D8 No snapset was found on pubset '(&00)'. Command was not executed

### Meaning

(&00): catalogue id

## DMS13D9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13D9 SNAPSET '(&00)' OF PUBSET '(&01)' IS NOT CONSISTENT. SNAPSET IS DELETED

### Meaning

(&00): snapset id
(&01): catalog id

## DMS13EA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13EA Internal error during command processing.

### Meaning

An internal error occurred while processing the command
SHOW-FILE-LOCKS.

### Response

Contact the system administrator.

## DMS13EB

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13EB No support of RFA files.

### Meaning

The command SHOW-FILE-LOCKS gives no information about RFA files.

## DMS13EC

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13EC No output to S variable possible.

### Meaning

For internal reasons, it is not possible to output to S variable.

### Response

Contact the system administrator.

## DMS13ED

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13ED No output to SYSOUT possible.

### Meaning

For internal reasons, it is not possible to output to SYSOUT.

### Response

Contact the system administrator.

## DMS13EE

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13EE No file locks exist.

### Meaning

There are no locks for specified file.

## DMS13EF

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13EF No access to the file meta data possible.

### Meaning

Possible reasons:
- The file was deleted in the meantime.
- A catalog lock for this file is still held.

## DMS13E0

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E0 Lack of resources.

### Meaning

A lack of resources occurred while processing the command SHOW-FILE-LOCKS.

### Response

Contact the system administrator.

## DMS13E1

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E1 The catalog entry of the specified file is not accessible as file protection is active. Command rejected

### Meaning

The user tried to access a catalog entry of a file which he/she is not
authorized to access owing to its protection attributes.
One of the following protection mechanisms can be active:
- tempfile of a foreign task
- standard file protection
- simple access control (Basic ACL)
- profile protection (GUARDS).

### Response

Contact the owner to change the access right if necessary.

## DMS13E2

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS13E2 User not authorized to access the pubset

### Meaning

The file is allocated on a pubset for which the user has no access right.

### Response

Request the system administrator to authorize you to access the pubset.

## DMS13E3

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E3 Specified user ID does not exist in HOME pubset.

### Meaning

No default pubset ID could be found.

### Response

Reenter the command with the correct pubset ID or request the system
administrator to join the user ID to the pubset.

## DMS13E4

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E4 Snapset catalogue on Pubset '(&00)' is not consistent with catalogue id or device mnemonics of pubset. Snapset catalogue is deleted

### Meaning

(&00): catalog id
For a pubset created by copying another pubset, a clean-up
needs to be performed for any snapset catalogue
copied from the source pubset: It is deleted when the copied
pubset is import for the first time.

## DMS13E5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E5 No snapset catalog exists on pubset '(&00)'

### Meaning

(&00): catalog id

## DMS13E6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E6 Snapset catalog on Pubset '(&00)' is not supported in this OSD Version. Its snapsets will not be activated

### Meaning

(&00): catalog id

## DMS13E7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E7 Snapsets are not supported for pubset '(&00)' with error code '(&01)'

### Meaning

(&00): catalog id
(&01): Error code:
01 Storage system not supported
02 GS volume

## DMS13E8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E8 Snapset '(&00)' on pubset '(&01)' is waiting to be activated. No further snapsets can be created before this snapset has been activated.

### Meaning

(&00): snapset id
(&01): catalog id

## DMS13E9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13E9 SNAPSET '(&00)' OF PUBSET '(&01)' COULD NOT BE IMPORTED. FOR THIS SESSION ACCESS TO THE SNAPSET IS NOT POSSIBLE.

### Meaning

(&00): snapset id
(&01): catalog id

## DMS13FA

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13FA The Command cannot be executed as the command is not available at the BS2000/OSD system on the master.

## DMS13FB

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS13FB ERROR AT COMMAND '(&00)' FOR PUBSET/VOLSET '(&01)'

### Meaning

An error occurred during the command (&00) for pubset/volset (&01).
This message is followed by another message identifying the error in more
detail.

### Response

Correct pubset ID if necessary.

## DMS13FC

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS13FC THE PUBSET/VOLSET (&00) INCLUDING VOLUME (&01) EXCEEDS THE MAXIMAL SIZE.

### Meaning

By adding the volume (&01) the pubset/volset (&00)
exceeds the maximal size.
The maximal size of a pubset/volset is
2.147.483.647 (X'7FFFFFFF') half pages.

## DMS13FD

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS13FD PUBSET/VOLSET (&00) EXCEEDS THE MAXIMAL SIZE.

### Meaning

The pubset/volset (&00) is larger than the maximal size.
The maximal size of a pubset/volset is
2.147.483.647 (X'7FFFFFFF') half pages.

## DMS13F0

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

Warranty : NO

DMS13F0 PUBSET ID: (&00), THE TASK WITH TSN '(&02)' FOR ENLARGEMENT OF CATALOG FILE (&01) WAS STARTED.

### Meaning

A catalog enlargement was started asynchronously.
(&00): CAT-ID
(&01): name of catalog file
(&02): TSN of catalog enlargement task

### Response

none

## DMS13F1

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

Warranty : NO

DMS13F1 CATALOG FILE (&00) WAS ENLARGED BY (&01) PAGES.

### Meaning

The asynchronous catalog enlargement was successfully done.
(&00): name of catalog file
(&01): number of pam-pages

### Response

none

## DMS13F2

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

Warranty : NO

DMS13F2 Pubset (&00), (&01) catalog (&02) has reached its maximum size.

### Meaning

The catalog cannot be extended in the given format. If the catalog is
a normal one, it may be converted into a large or extra-large catalog.
If the catalog is a large one, it may be converted into an extra-large
catalog.
(&00): CAT ID
(&01): format of catalog
(&02): name of catalog

### Response

Export the pubset. A large catalog may be created by changing the
pubset into a pubset with "large objects". A conversion to an
extra-large catalog will be done, if next import runs with the
parameter "extra-large-cat-conv=*yes".

## DMS13F3

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

Warranty : NO

DMS13F3 ENLARGEMENT OF CATALOG FILE (&00) FAILED WITH ERROR CODE '(&01)'.

### Meaning

The asynchronous catalog enlargement failed.
(&00): name of catalog file
(&01): error code (decimal value)
'01': catalog file at maximum size
'02': $GETMEM error
'03': $RETMEM error
'04': error in structures of CMS-buffermanager
'05': error when creating the catalog file enlargement task
'06': $DCACALL error
'07': error when setting catalog file enlargement lock
'08': error at FILE call
'09': $SETOCC error
'10': error when locking catalog-index-requestcounter
'11': no free space in pubset available
'12': catalog entry of catalog file has maximum size
'13': error when creating a new catalog file for an extra large
special catalog
'14': $SETPRV-error
'15': file locked because currently in use
'16': other errors

### Response

none

## DMS13F4

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

Warranty : NO

DMS13F4 THE CMS-STRUCTURES OF SM-PUBSET (&00) COULD NOT BE ENLARGED, AS THE FILE(S) (&01) AND/OR (&02) ARE (&03) PAM-PAGES TOO SMALL.

### Meaning

As one or more SF-pubsets are added to the SM-pubset, new
namelist-entries have to be created. However, there is a
lack of free slots in the namelist.
(&00): catalog id
(&01): name of namelist
(&02): name of namelist-copy
(&03): number of additionally needed pam-pages in the smaller file

### Response

Namelist and namelist-copy should be enlarged by a file-command.
The smaller one has to be enlarged by the number of pam-pages,
as told in the message, the other one in the way, that it has
at least the size of the enlarged smaller one.
Both files should have the same size, as only the size of the
smaller one can be used.

## DMS13F5

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13F5 Snapset Limit cannot be set for pubset '(&00)'

### Meaning

(&00): catalog id
The snapset limit cannot not be set because:
- snapshots are active and it is not allowed to mix them with
snapsets on the given storage system
- the maximum number of supported pubset mirrors is reached.

## DMS13F6

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13F6 the homogeneity check for the pubset '(&00)' detected at least one volume with the attribute '(&01)'. The snapset limit was set to '(&02)'

### Meaning

(&00): catalog id
(&01): volume characteristic
'01' Enginuity microcode version less than 5571
'02' Enginuity microcode version equal to 5571
'03' Not Device D3435 and FBA disc
'04' FibreCAT
'05' Eternus
(&02): maximum value of snapset limit

## DMS13F7

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13F7 No Snapset could be created for pubset '(&00)'. The target unit of a remote copy pair is not active or the remote copy pair is not synchronous.

### Meaning

(&00): catalog id

## DMS13F8

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13F8 No Snapset could be created for pubset '(&00)'. The target unit of a remote copy pair is not unique although specified as *UNIQUE or the RA group could not be found.

### Meaning

(&00): catalog id

## DMS13F9

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS13F9 LARGE-FILES = *ALLOWED is forbidden for the home-pubset.

### Meaning

If the pubset has been imported as home pubset, the parameter
LARGE-FILES cannot be set to the value ALLOWED.

## DMS1310

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS1310 System error. SERSLOG entry written during pubset cache administration or pubset reconfiguration.

### Meaning

An unexpected system error occurred during administration of the
pubset cache or the pubset reconfiguration.
An entry into the SERSLOG file has been written.

### Response

Evaluate the SERSLOG file and contact maintenance, if necessary.

## DMS1320

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

Warranty : NO

DMS1320 THE STATUS OF THE CATALOG FILE .BS2FSCAT OF THE NET-STORAGE VOLUME '(&00)' FOR CATID '(&01)' IS CHANGED TO '(&02)'.

### Meaning

The CATALOG FILE .BS2FSCAT was opened or closed.
&00 VSN of the Net-Storage volume
&01 catid of the corresponding pubset
&02 OPENED catalog file on Net-Storage was opened.
CLOSED catalog file on Net-Storage was closed.

### Response

none

## DMS1321

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

Warranty : NO

DMS1321 THE SIZE OF CATALOG FILE .BS2FSCAT OF THE NET-STORAGE VOLUME '(&02)' FOR CATID '(&01)' HAS REACHED '(&00)' PERCENT OF THE MAXIMUM SIZE.

### Meaning

&00 percent of max. catalog size have been reached.
&00 percent of the maximum size of the .BS2FSCAT
&01 Catid of the pubset
&02 VSN of the Net-Storage volume

### Response

none. Message was only sent for information.
(The catalog file .BS2FSCAT can neither be increased
nor decreased by command.)

## DMS1325

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

Warranty : NO

DMS1325 THE CATALOG FILE .BS2FSCAT ON NET-STORAGE VOLUME '(&00)' FOR CATID '(&01)', WAS NOT OPENED DUE TO REASON '(&02)'.

### Meaning

The catalog file .BS2FSCAT was not opened, because
- the catalog file .BS2FSCAT is destroyed or inconsistent
- administration flags of catalog file .BS2FSCAT prevent open
&00 VSN of Net-Storage volume
&01 Catid of the concerned pubset
&02 Reason of the message
Catalog file .BS2FSCAT destroyed or inconsistent
- CATCHEYE .BS2FSCAT has not the correct format
- CATVER version of .BS2FSCAT is not supported in this BS2000 version
- FIRST PAGES INCOMPLETE
The header of the .BS2FSCAT of the Net-Storage volume is not
complete.
Administration flags of the catalog file
- CATID The catid entry in the catalog file .BS2FSCAT and the catid
of the pubset are different
- VSN The volume entry in the .BS2FSCAT and the VSN of the
Net-Storage volume &00 are different
- STATE O The catalog file .BS2FSCAT is open but the sysid entry in
the .BS2FSCAT and the sysid of the home pubset are different
or invalid open/close status of the .BS2FSCAT
- TIME Time stamps of close/open/real time are not ascending
- RENAME(NEWVSN,NEWCATID)
Command ADD-NET-STORAGE-VOLUME with renaming the VSN
is running or a previous command was interrupted.

### Response

Inform system administrator.
In case of reason 'rename' an error occurred during
ADD-NET-STORAGE-VOLUME; complete the operation with
/ADD-NET-STORAGE-VOLUME VOLUME=<newvsn>,PUBSET=<newcat>
IMPORT=*YES(OLD-VOLUME-NAME=<oldvsn>,FORCE=*NO)

## DMS1326

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

Warranty : NO

DMS1326 NET-STORAGE VOLUME '(&00)'(CATID '(&01)') OPENED BY ANOTHER SYSTEM OR LAST SESSION TERMINATED ABNORMALLY. HINT '(&02)'. CONTINUE (Y/N)?

### Meaning

The catalog file .BS2FSCAT was not closed, because of
- last session terminated abnormally
- BCAM was unloaded before catalog file .BS2FSCAT was closed
- the catalog file .BS2FSCAT is currently opened by another system.
&00 VSN of the Net-Storage volume
&01 Catid of the pubset
&02 Further Hint:
- CATID The catid entry in the catalog file .BS2FSCAT and the catid
of the pubset are different
- VSN The volume entry in the .BS2FSCAT and the VSN of the
Net-Storage volume &00 are different
- STATE O The catalog file .BS2FSCAT is open but the sysid entry in
the .BS2FSCAT and the sysid of the home pubset are different
or invalid open/close status of the .BS2FSCAT
- TIME Time stamps of close/open/real time are not ascending

### Response

Check whether the Net-Storage volume is already in use.
Y: Open .BS2FSCAT and continue processing.
N: .BS2FSCAT will not be opened, processing will be aborted.

## DMS1327

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

Warranty : NO

DMS1327 THE CATALOG FILE .BS2FSCAT ON NET-STORAGE VOLUME '(&00)' FOR CATID '(&01)' OPENED WITH NOTICE '(&02)'.

### Meaning

The catalog file .BS2FSCAT was opened. The reason of the message could be:
- the catalog file .BS2FSCAT was still open, because the last session was
terminated abnormally
- a master change required a new open of the catalog file .BS2FSCAT
&00 VSN of the Net-Storage volume
&01 Catid of the pubset
&02 Notice:
- STATE O The catalog file .BS2FSCAT is already open; the sysid entry in
the .BS2FSCAT and the sysid of the home pubset are equal
- TIME Time stamps of close/open/real time are not ascending
- MASTER CHANGE
The master of a shared pubset changed and therefore the
catalog file .BS2FSCAT was opened again.
- CATID x The catalog file .BS2FSCAT change its belonging from
CATID x to &01.
(ADD-NET-STORAGE-VOLUME with operand FORCE was given)

### Response

none. The message is for information only.

## DMS1331

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1331 Wrong catalog operation

### Meaning

The desired catalog operation (system interface $DCACALL (DCMCTLGS))
is not allowed. The pathname lock that has possibly been set by a
preceding operation has been released.
Secondary return code (hexadecimal):
01: The catalog entry cannot be moved to a different subcatalog of the
SM pubset.
02: The desired operation is not allowed for a system file of the
catalog management.
03: The desired operation is only possible on SM pubsets.

### Response

Contact the service.
The secondary returncode helps in diagnosing the error.

## DMS134A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS134A SPECIFIED USERID IS NOT KNOWN TO THE SYSTEM OR CANNOT BE DETERMINED.

## DMS134B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS134B PROBLEMS WITH INTERNAL CMS LOCKS

### Response

Try the command again. If the error occurs again contact the system
administrator.

## DMS134C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS134C MRS CATALOG OF PUBSET '(&00)' CANNOT BE DETERMINED. ERROR CODE '(&01)'

### Meaning

(&01): Returncode of call of mrscat

## DMS1340

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

Warranty : NO

DMS1340 Pubset: (&00), CMS remote recovery on master host '(&01)' done.

### Meaning

A CMS-remote-recovery for the shared pubset was done from own slave
on the master, to equalize the CE-locks on slave and master.
(&00): pubset ID
(&01): name of master

## DMS1341

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

Warranty : NO

DMS1341 Pubset: (&00), CMS remote recovery on master host '(&01)' failed.

### Meaning

The CMS-remote-recovery to equalize the CE-locks of own slave
and master failed.
(&00): pubset ID
(&01): name of master

## DMS1342

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1342 REMOVE-CE-LOCK was successfully done.

## DMS1343

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS1343 (&00) is locked. TID (&01). SYSID (&02).

## DMS1344

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1344 During processing the command an unexpected internal error in system with sysid (&00).

### Meaning

An internal error has occurred when processing the command. A SERSLOG
entry has been written. If possible, the command will be continued.

### Response

Evaluate the SERSLOG entry.

## DMS1345

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1345 NAME OF FILE/JV DOES NOT SATISFY THE CONDITIONS OF THE COMMAND.

### Meaning

Possible reasons:
- CATID and/or USERID have not been specified.
- Filename/JV-name with relative generation.
- Specified Catid is a remote Catid.
- Filename with catid and userid is longer than 54.
- Subsystem ACS reported an error after conversion of the filename
(e.g. too long).

## DMS1346

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1346 THERE IS NO CE-LOCK OF SPECIFIED FILE/JV.

## DMS1347

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1347 THE TASK OF LOCK-HOLDER IS STILL EXISTING OR CANNOT BE DETERMINED.

### Response

Try to cancel the task of lockholder. Then try the command again.

## DMS1348

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1348 INTERNAL CMS-LOCK OF TASK WITH TASK-ID (&00) IN SYSTEM WITH SYSID (&01).

### Response

Try command again. If the error occurs again check the specified task.

## DMS1349

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1349 The BS2000/OSD version of system with sysid (&00) is less than V4.

## DMS135A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS135A No cache buffer in medium '(&00)' reserved for SHARED PUBSET with pubset ID '(&01)'

### Meaning

Possible Causes:
1. One of the hosts accessing the shared pubset has a version which
does not support the DAB cache for a shared pubset.
2. For a XCS-Pubset no GLOBAL-STORAGE is allowed.
3. The pubset already uses a GLOBAL-STORAGE with a different
characteristic (local or global GLOBAL-STORAGE).
4. A cache buffer in a different cache medium or with a different
security resp. with a different GS-UNIT number is already assigned
to the SF pubset or volumeset on another host.
(&00): GLOBAL-STORAGE, MAIN-MEMORY or UNDEFINED.

## DMS135B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS135B Space saturation in cache medium '(&00)' for pubset or volumeset '(&01)'.

### Meaning

There is no more free space available in the cache medium.
(&00): CONTROLLER, EXPANDED-STORAGE, GLOBAL-STORAGE,
MAIN-MEMORY or UNDEFINED.

### Response

Check the cache medium and try again.

## DMS135C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS135C Cache buffer in medium '(&00)' with id '(&01)' no longer exists.

### Meaning

The cache buffer with ID '(&01)' no longer exists in medium '(&00)'.

### Response

Check the cache medium and try again.

## DMS135D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS135D Unable to activate the cache buffer in the medium '(&00)' for pubset or volumeset '(&01)'.

### Meaning

Due to problems in the cache medium it is not possible to
activate a previously deactivated cache buffer.
(&00): CONTROLLER, EXPANDED-STORAGE, GLOBAL-STORAGE,
MAIN-MEMORY or UNDEFINED.

### Response

Check the cache medium and try again.

## DMS135E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS135E Subsystem for cache buffer handling in medium '(&00)' for pubset or volumeset '(&01)' not available.

### Meaning

The subsystem to serve the requested cache medium is not available.
(&00): CONTROLLER, EXPANDED-STORAGE, GLOBAL-STORAGE,
MAIN-MEMORY or UNDEFINED.

### Response

Start subsystem DAB or PCA.

## DMS135F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS135F Internal system error

### Meaning

An internal error occurred during processing of the commands
/START-PUBSET-CACHING or /STOP-PUBSET-CACHING.
A Serslog entry has been written.

### Response

Inform the system administrator.

## DMS1350

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS1350 Cache buffer with the ID '(&00)' can no longer be connected. Reason '(&01)'. Data may be inconsistent. Continue import? Reply (Y=Yes; N=No)

### Meaning

The last session of the pubset was terminated abnormally. Eventually
the modified pages in the cache could not be written to disk.
The cache can no longer be connected and there may
be inconsistent data on the pubset if importing is continued.
(&01): reason
'01': other reasons
'02': the cache buffer doesn't exist anymore

### Response

Y: Import will be continued.
All files with modified pages in the cache eventually will be
inconsistent and cannot be opened with the exception of
reason '02'. In this last case the concerned files can be
opened after a VERIFY.
N: Import will be aborted.

## DMS1351

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1351 Pubset management parameter error. Serslog entry written

### Meaning

An internal parameter error occurred during command processing.

### Response

Send diagnostic material to the system administrator.

## DMS1352

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1352 COMMAND RESTRICTED TO SYSTEM ADMINISTRATION

### Meaning

The commands /START-PUBSET-CACHING or /STOP-PUBSET-CACHING
are restricted to the system administrator.

## DMS1353

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1353 MRSCAT entry for pubset or volumeset '(&00)' not found.

### Meaning

No MRSCAT entry exists for the specified pubset or volumeset ID.

### Response

Correct and try again.

## DMS1354

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1354 Pubset with pubset id '(&00)' not locally imported

### Meaning

It is a prerequisite for the commands /START-PUBSET-CACHING
and /STOP-PUBSET-CACHING that the pubset is locally accessible
and not in the state of importation or exportation.

### Response

Set the pubset to the accessible state (import).

## DMS1355

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1355 Cache configuration not allowed for pubset or volumeset '(&00)'. Error type '(&01)'.

### Meaning

The cache configuration specified in the MRSCAT entry is not allowed.
(&01): error type
'01': No support for double buffering mode. Possible reasons:
- the specified cache does not offer this feature;
- only one GS-UNIT of the medium GLOBAL-STORAGE is connected.
'02': The specified cache medium is defect (defect ES/GS partition
or IO error of cache control) or the control device is not
attached.
'03': Another cache medium was already active for the current
pubset session.
'04': No defined cache medium or defined cache medium in the MRSCAT
not available.
'05': At least one volume of the pubset/volumeset is a
GS volume or a fast disk (SSD).
'06': Single buffering not allowed: A cache buffer in the GS in the
single buffering mode must not be added to a pubset/volumeset
in the DRV mode.
'07': A cache buffer is still defined for the pubset/volumeset (&00)
in the specified cache medium. Creation of a new cache buffer
is therefore not possible.
'08': The cache size has not been specified.

### Response

'01': Use a suitable cache medium or switch to single buffering.
'02': Attach the control device.
In case of a hardware error message inform the system engineer.
'03': Use the previously active cache medium.
'04': Modify the cache configuration defined in the MRSCAT entry
or make the cache medium available.
'05': Pubsets/volumesets consisting of Fastdisks or GS volumes
are already high performant without caching. Remove the cache
medium entry from MRSCAT entry.
'06': Set GS-UNIT=DUAL for the cache buffer in the MRSCAT entry
(requirement: two GS units).
'07': Delete the old cache buffer with the commands
/FORCE-DESTROY-CACHE (PFA) or /STOP-DAB or /FORCE-STOP-DAB or
/STOP-CONTROLLER-CACHING or /FORCE-CONTROLLER-CACHING-STOP
(ADM-PFA) and repeat the command.
'08': Specify the cache size with /MODIFY-PUBSET-CACHE-ATTRIBUTES.

## DMS1356

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1356 Cache buffer already active or in status 'IN-HOLD' for pubset or volumeset '(&00)'

### Meaning

The cache buffer to be activated for the specified pubset or
volumeset is already active or is being activated or is in status
'IN-HOLD'.

## DMS1357

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1357 No cache buffer active for pubset or volumeset '(&00)'

### Meaning

The /STOP-PUBSET-CACHING is only allowed for an
activated pubset cache.

## DMS1358

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1358 Function not supported. Error type '(&00)'

### Meaning

(&00): Error type
'01': The pubset or individual volumes of the pubset are
already cached via ADM-PFA interfaces.

## DMS1359

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS1359 Some files of the pubset '(&00)' are inconsistent because the assigned cache buffer is no more available. Shall the system startup nevertheless to be continued ? Reply (Y=yes; N=no)

### Meaning

In the last session the pubset has been a data pubset with an
attached PFA cache buffer. This cache buffer hasn't been written
back completely to the volumes of the pubset and is not available
now for reading the data.

### Response

N: Import the pubset as data pubset and terminate the pubset session
with the command /EXPORT-PUBSET normally. Then import the pubset
as home pubset.
Y: Should given only if absolutely necessary because no other home
pubset is available or if the inconsistence of some user files
is no problem.

## DMS136A

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS136A Internal error during pubset homogeneity check for pubset '(&00)'; concerned volume: '(&01)'

### Meaning

During homogeneity check of the pubset mirroring an internal error
occured (e.g.: call of a system function returned an unexpected error)

### Response

Analyze serslog-entry with record type DMS1311 and
contact system administrator.

## DMS136B

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS136B Pubset '(&00)' is not homogenous regarding the mirroring attributes. Concerned volume: '(&01)'

### Meaning

During homogeneity check of the pubset mirroring different attributes
have been detected for a volume of that pubset.

### Response

The state of the pubset regarding local and remote mirroring should be
checked by the system administrator by using SHC-OSD commands
and, if necessary, homogeneity of all pubset volumes should be ensured.

## DMS136C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS136C Mirroring for pubset '(&00)' homogenous

### Meaning

During homogeneity check of the pubset mirroring identical mirroring
attributes for all pubset volumes have been detected.

## DMS136D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS136D Mirroring for pubset '(&00)' inhomogeneous

### Meaning

During homogeneity check of the pubset mirroring different mirroring
attributes have been detected for at least one volume.

### Response

Identify concerned volume(s) by means of message DMS136B,
the state of the pubset regarding local and remote mirroring should be
checked by the system administrator by using SHC-OSD commands
and, if necessary, homogeneity of all pubset volumes should be ensured.

## DMS136E

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS136E Check of homogeneity for pubset '(&00)' not possible. Reason '(&01)'

### Meaning

Check of homogeneity for specified pubset cannot be performed.
(&01): Possible reasons:
01: Privilege TSOS missing.
02: Specified Pubset not existing.
03: Specified Pubset not accessible.
04: Homogeneity check not allowed for volume set.
05: Subsystem SHC-OSD not available.
06: Unexpected return code provided by call of subsystem SHC-OSD.

### Response

Import pubset, possibly install subsystem SHC-OSD resp. analyze return
code provided by call of subsystem SHC-OSD (serslog entry with record
type DMS1311, message given by subsystem SHC-OSD with prefix NDE).

## DMS136F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS136F Unexpected system error during check of pubset '(&00)'

### Meaning

During homogeneity check of pubset mirroring an unexpected system
error occurred.

### Response

Analyze serslog entry with identification DMS1311.

## DMS1360

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1360 The following system message has been caused by an error returned by the host '(&00)'.

### Meaning

(&00): MSCF name of the host

## DMS1361

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1361 The system file '(&00)' containing the names of the defective files has been created.

### Meaning

The file has been created on the affected pubset. The filename
contains the identifier of the affected volumeset followed by the date.

## DMS1362

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1362 Only controller cache buffer allowed for home pubset

### Meaning

It is only possible to cache the home pubset in the controller.

## DMS1363

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1363 System space saturation during command processing

## DMS1364

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1364 Unable to save contents of cache buffer in medium '(&00)' for pubset or volumeset '(&01)'.

### Meaning

The data in the cache buffer cannot be saved at present.
Possible causes:
1. Disk error (reported separately, look into CONSLOG protocol)
2. Cache error (reported separately, look into CONSLOG protocol)
3. Internal system error (see SERSLOG file)
The cache buffer remains active.
(&00): CONTROLLER, EXPANDED-STORAGE, GLOBAL-STORAGE,
MAIN-MEMORY or UNDEFINED.

### Response

If necessary inform the system engineer and observe the issued hardware
error messages. After termination of all applications that use the
affected pubset/volumeset, the files not saved can be determined with
the command /SHOW-FILE-ATTRIBUTES :pvsid:*,STATUS=*PAR(CACHED=YES).
1. In case of disk error all data not yet written back are still
readable in the cache. The affected files can be reconstructed
with
/CREATE-FILE new-filename
/COPY-FILE old-filename,new-filename.
Ask the service engineer to check the disk subsystem.
2. In case of cache error there is a loss of data on the
pubset/volumeset. The affected files on the volume are not in
the current state.
3. There is no loss of data. Send the diagnosis information
(SERSLOG) to the system support.

## DMS1365

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1365 Pubset reconfiguration file locked permanently.

### Meaning

The pubset reconfiguration file has been opened some time ago by
another task but not yet closed until now.

### Response

Inform the system administrator.

## DMS1366

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS1366 Creation or connection of a cache buffer for volumeset '(&00)' of the pubset '(&01)' rejected with reason '(&02)', /IMPORT-PUBSET continued.

### Meaning

Creation with defined parameters in the MRSCAT entry impossible or
error during call of the cache management.
(&02): error type
'01': Space saturation the cache medium
'02': Cache buffer defined in the cache medium
'03': Cache medium not available or not allowed for SHARED PUBSET
'04': Cache medium out of order or control device not attached
'05': Double buffering not available
'06': At least one fastdisk (SSD) or GS volume
'07': Cache size not specified
'08': No memory available
'09': Subsystem not loaded
'10': Internal system error
'11': DAB medium requested, but another sharer with version < OSDV4
'12': Last and current import mode or DAB versions are different
'13': Cache state error or some volumes are cached via ADM-PFA

### Response

Modify cache parameters after import and import the pubset again or
send error report to system support.
(&02): error type
'02': delete the old cache buffer with /FORCE-DESTROY-CACHE (PFA)
or /STOP-DAB resp. /FORCE-STOP-DAB (ADM-PFA)
and try /IMPORT-PUBSET again.
'13': If any volume is cached via ADM-PFA, the medium setting of
the volset should be reset by /MODIFY-PUBSET-ATTRIBUTES

## DMS1367

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1367 No disk space available on the pubset with pubset id '(&00)'. Command rejected.

### Meaning

A system function has been terminated because of disk space
shortage

### Response

Delete files on the pubres and repeat the command.

## DMS1368

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1368 Cache buffer cannot be connected on caching activation of pubset/volumeset '(&00)'.

### Meaning

A cache buffer in a DAB medium is still assigned to the pubset.
The cache buffer cannot be connected, because
- it was created in version < OSDV4 and is actually imported in
a version >= OSDV4
- it was created in version >= OSDV4 for an exclusively imported
pubset and the pubset is actually imported as shared pubset or
vice versa

### Response

Connect the cache buffer by importing the pubset in the old
environment (BS version resp. shared modus), export the pubset
and import it again in the actual environment.

## DMS1369

Destination: USER-TASK, CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS1369 Pubset '(&00)' is not homogenous regarding the mirroring attributes. Concerned volume: '(&01)'. Continue processing? Reply (Y=Yes; N=No)

### Meaning

During pubset import/extension different mirroring attributes have
been detected for a volume.

### Response

Y: Continue processing.
N: Abort processing.
The state of the pubset regarding local and remote mirroring should be
checked by the system administrator by using SHC-OSD commands
and, if necessary, homogeneity of all pubset volumes should be ensured.

## DMS137A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS137A PUBSET WITH PUBSET ID '(&00)' STILL CONNECTED TO CACHE BUFFER. PUBSET CANNOT BE IMPORTED AS 'HOME-PUBSET'. STARTUP ABORTED

### Meaning

The pubset with pubset ID (&00) was imported as data pubset and connected
to a cache buffer. The previous pubset session was terminated abnormally.
Since data in the cache cannot be saved on disks during the startup,
the startup was aborted.

### Response

Import the pubset as a data pubset again and issue a normal termination
of the pubset session by an /EXPORT-PUBSET. Afterwards try HOME-PUBSET
import again.

## DMS137B

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

Warranty : NO

DMS137B Task with TSN '(&00)' for '(&01)' of volumeset '(&02)' not yet finished

### Meaning

(&00): TSN of Import/Export task
(&01): 'Import' or 'Export'
(&02): Volumeset id

### Response

Reply message if reply outstanding

## DMS137C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS137C Export of pubset '(&00)' with specified operand values not possible because of error '(&01)'

### Meaning

(&00): pubset id
(&01): cause of error
01, SHARER-TYPE=*SLAVE specified, but pubset is imported
as master
02, SHARER-TYPE=*MASTER specified, but pubset is imported
as slave
03, SHARER-TYPE=*MASTER/*SLAVE specified, but pubset
is imported exclusively
04, USE=*BY-REMOTE specified, but pubset is imported locally
05, USE=*STANDARD specified, but pubset is imported remotely

### Response

Repeat EXPORT-PUBSET with correct operand values

## DMS137D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS137D Remote import of pubset '(&00)' on host '(&01)' failed with error '(&02)'

### Meaning

(&00): pubset id
(&01): MSCF name of host which imported pubset &00 exclusively
or as shared master
(&02): error code
'01': host &01 not connected or local host
'02': BS2000 host version < V12
'03': no MSCF connection to host &01
'04': catid &00 on host &01 is volumeset catid
'05': pubset &00 not defined on host &01
'06': pubset &00 on host &01 inaccessible
'07': pubset &00 on host &01 remote imported or
slave imported
'08': import/export in progress for pubset &00 on host &01

### Response

Repeat import command with correct MSCF hostname or import pubset
on host

## DMS137E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS137E Volumeset '(&00)' of SM pubset '(&01)' is not declared as 'defective'. Should the volumeset be removed from the pubset? Reply (Y=Yes; N=No)

### Meaning

This message is issued if a volumeset (&00) specified in the operand
DEFECT-LIST of IMPORT-PUBSET has to be removed from SM pubset (&01),
but is not declared as 'defective' in the pubset configuration file.

### Response

Y: The volumeset is removed
N: the volumeset remains in the SM pubset, the import is aborted.

## DMS137F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS137F Import processing must be aborted because of missing declaration of defective volumeset '(&00)' of pubset '(&01)'

### Meaning

This message is issued if a volumeset (&00) is declared as 'defective'
in the pubset configuration file of pubset (&01) but not specified
in the operand DEFECT-VOLUME-SET of command IMPORT-PUBSET.
The import processing is aborted.

### Response

The volumeset must be specified in the operand DEFECT-VOLUME-SET
of command IMPORT-PUBSET.

## DMS1370

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS1370 Extension of pubset/volumeset '(&00)' with volume '(&01)' causes change of HIGH-AVAILABILITY from 'ACTIVE' to 'DEACTIVATED'. Continue? Reply (Y=Yes; N=No).

### Meaning

This message is issued if for a SF pubset or volumeset consisting of
dualcopy-pairs a dualcopy-possible-volume has to be added.

### Response

Y: The pubset/volumeset is extended to include the volume
N: The pubset/volumeset is not extended.

## DMS1371

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS1371 Extension of pubset/volumeset '(&00)' with volume '(&01)' causes change of HIGH-AVAILABILITY from 'ACTIVE' to 'NORMAL'. Continue? Reply (Y=Yes; N=No).

### Meaning

This message is issued if for a SF pubset or volumeset consisting of
dualcopy pairs a volume has to be added which is neither of type
dualcopy-possible nor dualcopy-pair.

### Response

Y: The pubset/volumeset is extended to include the volume.
N: The pubset/volumeset is not extended.

## DMS1372

Destination: CONSOLE Routing code: E Weight: 99

Warranty : NO

DMS1372 Extension of pubset/volumeset '(&00)' with volume '(&01)' causes change of HIGH-AVAILABILITY from 'DEACTIVATED' to 'NORMAL'. Continue? Reply (Y=Yes; N=No).

### Meaning

This message is issued if for a SF-Pubset or volumeset consisting of
dualcopy-possible-volumes a volume has to be added which is neither
of type dualcopy-possible nor dualcopy-pair.

### Response

Y: The pubset/volumeset is extended to include the volume
N: The pubset/volumeset is not extended.

## DMS1373

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

Warranty : YES

DMS1373 Import volumeset task with TSN '(&00)' for volumeset '(&01)' and pubset '(&02)' has been created and started

### Meaning

This message marks the start of import volumeset processing for the
volumeset with id (&01) belonging to SM pubset (&02).
(&00): TSN of import task
(&01): volumeset id
(&02): pubset id

## DMS1374

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

Warranty : YES

DMS1374 Import volumeset processing for volumeset '(&00)' completed

### Meaning

This message marks the end of import volumeset processing for the
volumeset with id (&00).
(&00): volumeset id.

## DMS1375

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

Warranty : NO

DMS1375 Import volumeset processing for volumeset '(&00)' completed with error

### Meaning

This message marks the end of import volumeset processing for the
volumeset (&00) because of error.
(&00): volumeset id

## DMS1376

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

Warranty : YES

DMS1376 Export volumeset task with TSN '(&00)' for volumeset '(&01)' and pubset '(&02)' has been created and started

### Meaning

This message marks the start of export volumeset processing for the
volumeset (&01) belonging to SM pubset (&02).
(&00): TSN of import task
(&01): volumeset id
(&02): SM pubset id

## DMS1377

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

Warranty : NO

DMS1377 Export volumeset processing for volumeset '(&00)' completed

### Meaning

This message marks the end of export volumeset processing for the
volumeset (&00).
(&00): volumeset id.

## DMS1378

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

Warranty : NO

DMS1378 Export volumeset processing for volumeset '(&00)' completed with error

### Meaning

This message marks the end of import volumeset processing for the
volumeset (&00). However, error(s) occurred during export processing.
(&00): volumeset id

## DMS1379

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

Warranty : NO

DMS1379 SVL of pubres/volres volume not consistent with VSN '(&00)' or not valid with pubset MRSCAT (errorcode '(&01)')

### Meaning

Information from the SVL of the pubres/volres volume with VSN
'(&00)' is incorrect or not consistent with information from the
MRSCAT of the corresponding pubset
(&00): VSN of pubres/volres of pubset/volumeset
(&01): error code
'01': SVL type: empty volumeset
'02': MRSCAT type: SM pubset and SVL type <> volumeset
'03': MRSCAT type: SF pubset and SVL type <> SF pubset
'04': MRSCAT pubset id <> SVL pubset id
'05': pubres/volres volume not in volume list of SVL

### Response

If case of an incorrect MRSCAT type, create a new MRSCAT entry

## DMS138A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS138A Pubset reconfiguration parameter error. Serslog entry written command rejected

### Meaning

An internal parameter error occurred during command processing.

### Response

Send diagnostic material to the system administrator.

## DMS138B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS138B Pubset not found. Command rejected

### Meaning

There exists no pubset with the specified identifier or with the
specified characteristics.

### Response

Correct the command.

## DMS138C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS138C Pubset not accessible. Command rejected

### Meaning

The specified pubset is not accessible.

### Response

Import the pubset.

## DMS138D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS138D Wrong pubset type. Command rejected

### Meaning

Pubset not of specified type (SF or SM).

### Response

Correct the command.

## DMS138E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS138E Volumeset not found. Command rejected

### Meaning

Volumeset with specified identifier does not exist.

### Response

Correct the command.

## DMS138F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS138F Volumeset not accessible. Command rejected

### Meaning

Volumeset not CONNECTED or in the state DEFINED ONLY (volume operation).

### Response

Define the volumeset with /MODIFY-PUBSET-DEFINITION-FILE and/or add
the volumeset with /MODIFY-PUBSET-PROCESSING.

## DMS1380

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1380 SF pubset or volumeset inconsistent. Error type '(&00)'. Command rejected

### Meaning

(&00): error type
'01': VSN of volres not found in the existing volume catalog.
'02': Allocation unit of the volume does not match the volres.
'03': Format of the volume does not match the volres.
'04': Timestamp of the volume does not match the volres.
'05': Timestamp of the volres reserved by the slave does not match
the master.

### Response

Dependent on cause.

## DMS1381

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1381 Volumeset conflict. Error type '(&00)'. Command rejected

### Meaning

(&00): error type
'01': The MRSCAT entry with the specified volumeset id does not
belong to a volumeset.
'02': The specified volumeset belongs to another pubset.
'03': A record in the configuration file for the new volumeset
already exists, but the data differ.
'04': The volumeset is not in the state DEFINED ONLY.
'05': The volumeset is not in the state NORMAL USE.
'06': The volumeset is not in the state STANDALONE.

### Response

'01': Correct the command.
'02': Correct the command.
'03': Correct the command.
'04': Remove the volumeset with /MODIFY-PUBSET-PROCESSING.
'05': Add the volumeset with /MODIFY-PUBSET-PROCESSING.
'06': Dependent on the state (e.g. DEFECT).

## DMS1382

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1382 Volume not found. Command rejected

### Meaning

The specified volume does not exist in the volume catalog.

### Response

Correct the command.

## DMS1383

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1383 Volume inconsistent. Error type '(&00)'. Command rejected

### Meaning

(&00): error type
'01': The raid mode of the volume does not match the pubset/volumeset.
'02': The GS mode of the volume does not match the pubset/volumeset.
'03': Returncode "bad volume" from the allocator.
'04': The dual recording mode of the volume does not match the
pubset/volumeset.
'05': The timestamp of the volume reserved by the slave does not match
the master.
'06': A volume is larger than 32 GB, but the pubset doesn't have
the attribute for large volumes.

### Response

Dependent on cause.

## DMS1384

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1384 Modification impossible. Error type '(&00)'. Command rejected

### Meaning

(&00): error type
'01': USAGE specified but volumeset not in the state DEFINED-ONLY
or PROCESS-STATE or NEW-FILE-ALLOCATION (NOT-ALLOWED)
specified for control volumeset.
'02': AVAILABILITY specified (change to *STD) but either volumeset
not in the state DEFINED-ONLY or NEW-FILE-ALLOCATION not
restricted (control volumeset: *PHYSICAL-ONLY, otherwise
*NOT-ALLOWED) or volumeset contains files with the attribute
"high available"
or PROCESS-STATE specified but volumeset is in the state
DEFINED-ONLY or DEFECT.
'03': PROCESS-STATE = RESTART not successful.
'04': VOLUME-SET-ACCESS to be restricted: NEW-FILE-ALLOCATION =
*NOT-ALLOWED necessary.
'05': NEW-FILE-ALLOCATION to be restricted but default file format
supported only by this volumeset.
'06': Restriction of NEW-FILE-ALLOCATION to be cancelled but
VOLUME-SET-ACCESS still restricted.
'07': ALLOCATION-ON-VOLUME specified but volumeset in the state
DEFINED-ONLY.
'08': ALLOCATION-ON-VOLUME must not be restricted because of
space saturation.

### Response

Dependent on cause.

## DMS1385

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1385 Volumeset/volume cannot be removed. Error type '(&00)'. Command rejected

### Meaning

(&00): error type
'01': Remove of the control volumeset not possible.
'02': Default file format supported only by this volumeset.
'03': CONDITION = *EMPTY but NEW-FILE-ALOCATION not restricted.
'04': TERMINATE-JOBS = *NO but volumeset still occupied.
'05': CONDITION = *DEFECT but volumeset not in the state DEFECT
or IN-HOLD.
'06': CONDITION = *EMPTY but volumeset not empty.
'07': CONDITION = *EMPTY but volumeset not in the state NORMAL-USE.
'08': Volume not empty.
'09': Volume not removable because of space saturation.
'10': Volume contains parts of the garbage file and can only be
removed if a new allocation is not allowed.

### Response

Dependent on cause.

## DMS1386

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1386 No memory available. Command rejected

### Meaning

A system function has been terminated because of memory shortage.

### Response

Repeat the command later.

## DMS1387

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1387 Volume cannot be reserved. Command rejected

### Meaning

Device or volume not available or allocation of the device not
allowed.

## DMS1388

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1388 Connection of the volume '(&01)' to the cache buffer '(&02)' added to the pubset/volumeset with id '(&00)' not possible. Error type '(&03)'.

### Meaning

(&00): error type
'01': The requested cache medium is defective (e.g. IO error of
cache control).
'02': The new configurated volume is a fastdisk (SSD) or has been
already connected to a cache buffer.
'03': Internal system error.
'04': Space saturation in the cache medium
'05': The volume is already cached via ADM-PFA interfaces.

### Response

'01': In case of a hardware error message, inform the system engineer.
'02': The new configurated fastdisk volume is not cached.
For a pubset/volumeset consisting of volumes and fastdisks
no new cache buffer will be created after deletion of the
cache buffer !
'03': Send the SERSLOG file to the system support.

## DMS1389

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1389 A Shared Pubset Error occurred during Command Processing. The Command is rejected

### Meaning

While the command was being processed an error related to one or more
shared pubsets occurred or a BS2000/OSD system with a version older
than V7.0A is running on the master host.

## DMS139A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS139A Another pubset reconfiguration order is still active.

### Response

Repeat the command later.

## DMS139B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS139B Volume of the pubset or volumeset '(&00)' reserved.

### Meaning

- A volume of the pubset or volumeset has been reserved by another
function for a longer time.

### Response

Repeat the command later.

## DMS139C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS139C Configuration file of the pubset '(&00)' permanently locked.

### Meaning

- The configuration file of the pubsets could not be opened because
it has not been closed by another task.

### Response

Inform the system administrator.

## DMS139D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS139D Volume of the pubset or volumeset '(&00)' not accessible.

### Meaning

- A volume of the pubset or volumeset has been removed from the
system.

### Response

Make the volume accessible again.

## DMS139E

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS139E The finishing of the reconfiguration command '(&00)' during the master change processing for the pubset '(&01)' has been terminated with an error.

### Meaning

(&00): /START-/STOP-PUBSET-CACHING, /MODIFY-PUBSET-DEFINITION-FILE,
/MODIFY-PUBSET-PROCESSING, /MODIFY-PUBSET-RESTRICTIONS

## DMS139F

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS139F Volumeset '(&00)' set by the system to the state '(&01)'.

### Meaning

(&01): HOLD or RESTART

## DMS1390

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1390 Reconfiguration not finished. Command rejected

### Meaning

An earlier reconfiguration has not been finished.

### Response

Finish last reconfiguration with /RESUME-PUBSET-RECONFIGURATION
and repeat command.

## DMS1391

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1391 Configuration error. Command rejected

### Meaning

The specified SM pubset does not have a configuration file.

### Response

Generate the SM pubset again.

## DMS1392

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1392 Wrong vsn '(&00)' specified. Command rejected

### Meaning

The format of the specified VSN doesn't fit to the specified pubset
or volumeset or to a public volume.
(&00): Invalid vsn.

### Response

Correct the command.

## DMS1393

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1393 Disconnection of the volume '(&01)' from the cache buffer with id '(&02)' removed from the pubset/volumeset with id '(&00)' not possible. Error type '(&03)'.

### Meaning

(&00): error type
'01': The requested cache medium is defective (e.g. IO error of
cache control).
'02': The new configurated volume is a fastdisk (SSD).
'03': Internal system error.

### Response

'01': In case of a hardware error message inform the system engineer.
'02': The new configurated fastdisk volume is not cached.
For a pubset/volumeset consisting of volumes and fastdisks
no new cache buffer will be created after deletion of the
cache buffer !
'03': Send the SERSLOG file to the system support.

## DMS1394

Destination: CONSOLE Routing code: E Weight: 98

Warranty : NO

DMS1394 A cache buffer in the cache medium controller is still assigned to the pubset '(&00)' but cannot be connected at this time.

### Meaning

The DSSM subsystem PCA is not currently loaded.

### Response

After the message "ESM0220 FUNCTION 'CREATE' FOR SUBSYSTEM 'PCA'
COMPLETELY PROCESSED", the command /START-PUBSET-CACHING with the
cache ID '(&00)' should be issued to connect the cache buffer.
Then the caching for the pubset is continued.

## DMS1395

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1395 Volumeset or volume cannot be added. Command rejected

### Meaning

- Maximum number of volumesets or volumes reached
- XCS pubset must not be extended with a GS volumeset
- Inhomogeneity of mirroring by remote-copy and/or multi-mirror of
pubset has been detected
- Snapset support is defined for the pubset and the maximum number
of snaps for one of the discs to be added is inconsistent with
the current maximum values of the pubset

### Response

Remote-copy and multi-mirror status of the pubset
should be checked by system administrator using
commands /SHOW-REMOTE-COPY-STATUS and/or /SHOW-MULTI-MIRRORING-STATUS
and, if necessary, homogeneity of all pubset volumes should be ensured.

## DMS1396

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1396 Hostname invalid. Command rejected

### Meaning

- Hostname unknown.
- Host without access on the pubset.
- Remote host specified but local host is not the master.

### Response

Dependent on the user's intention.

## DMS1397

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1397 Remote host with invalid version. Command rejected

### Meaning

- One of the hosts accessing the shared pubset has a version which
does not support the reconfiguration.

## DMS1398

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1398 Reconfiguration rejected.

### Meaning

- After termination of the task RLKM because of an internal error the
reconfiguration lock manager can't handle any reconfiguration lock.
A reconfiguration for this pubset is no more possible during this
session.
Messages in the conslog file and serslog entries are possible.

## DMS1399

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1399 Maximum number of MRSCAT entries reached.

### Meaning

- A new MRSCAT entry could not be created.

### Response

Increase maximum number of MRSCAT entries (Class 2 system parameter
DMCMAXP).

## DMS140A

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

Warranty : NO

DMS140A F5 label reconstruction for volumeset '(&00)' of pubset '(&01)' completed

### Meaning

(&00): volumeset id
(&01): corresponding pubset id

## DMS140B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS140B Pubset not found or not accessible. Command rejected

### Meaning

Possible reasons:
- MRSCAT entry for specified identifier does not exist
- it is a SM-pubset which is not local accessible
- for a SF-pubset a modification with temporary or permanent
scope is desired and the pubset is not local accessible
- for a SF-pubset a modification with temporary or permanent
scope is desired, the pubset is a shared pubset and the
master-host runs a BS2000-version which does not support the
actual command
- /SHOW-PUBSET-SPACE-ALLOCATION was issued for a pubset which
is not local accessible

## DMS140C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS140C Pubset type conflict. Command rejected

### Meaning

Type of pubset does not match pubset type specified in command or
default value of corresponding operand.

## DMS140D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS140D Volumeset does not belong to pubset. Command rejected

## DMS140E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS140E Operand error. Command rejected

### Meaning

Values given for LEVEL operands must be specified in descending
order.

## DMS140F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS140F Error on request for memory space during command processing

## DMS1400

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

Warranty : NO

DMS1400 Space saturation level '(&03)' reached on volumeset '(&00)' of pubset '(&04)'. Space used = (&01) HP's, available space = (&02) HP's

### Meaning

A saturation level is reached when there is less available space
on volumeset as specified by the current setting for the
corresponding saturation level
(&00): volumeset id
(&04): corresponding pubset id
(&01): space used on volumeset, excluding volumes with
allocation restrictions
(&02): available space on volumeset, excluding volumes with
allocation restrictions
(&03): saturation level reached

## DMS1401

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1401 Specified file format not supported by pubset. Command rejected

## DMS1402

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1402 Function only partially executed.

### Meaning

A modification with permanent scope was requested, but only the
current values have been changed

## DMS1403

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1403 Saturation level exceeds capacity. Command rejected

### Meaning

When setting saturation levels with permanent or temporary scope,
a value was specified which exceeds the pubset/volumeset capacity

### Response

Determine capacity with /SHOW-PUBSET-SPACE-ALLOCATION and
correct values of LEVEL operands accordingly.

## DMS1404

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1404 Specified values do not match current levels. Command rejected

### Meaning

When setting saturation levels to take immediate effect (operand
SCOPE=*PERMANENT or *TEMPORARY), values were not specified
for all levels and the ones specified together with the unchanged
current settings are not in descending order.

### Response

Determine current settings with /SHOW-PUBSET-PARAMETERS
and correct values of LEVEL operands accordingly.

## DMS1405

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1405 Specified values do not match defined levels. Command rejected

### Meaning

When setting saturation levels permanently (operand SCOPE=*PERMANENT
or *NEXT-PUBSET-SESSION), values were not specified for all levels and
the ones specified together with the unchanged defined settings are
not in descending order.

### Response

Determine current settings with /SHOW-PUBSET-PARAMETERS and
correct values of LEVEL operands accordingly.

## DMS1406

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1406 No combination of file attributes corresponding to specified operands

## DMS1407

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1407 Error on calling storage class management. Command rejected

### Response

Contact the system administrator

## DMS1408

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1408 Volumeset list '(&00)' is not defined for pubset '(&01)'. Command rejected

## DMS1409

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1409 Storage class '(&00)' is not defined for pubset '(&01)'. Command rejected

## DMS141A

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

Warranty : NO

DMS141A Incorrect F5-Label on volume '(&00)'. Disk space management tables for pubset/volumeset '(&01)' cannot be set up

### Meaning

After reading in the F5 label of volume '(&00)', the F5 label
header is checked. One of the following errors has been
encountered thereby:
- invalid version
- invalid checkbyte or identification string
- size or structure information is different from the information
derived from the volume characteristics stored in the SVL
- different information has been obtained by a former read in of
the same F5 label

## DMS141B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS141B Specified pubset is not a SM pubset. Command rejected

### Meaning

The requested function is supported only for SM pubsets

## DMS141C

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

Warranty : NO

DMS141C Space saturation level 'ZIP' reached on pubset '(&00)'. Space used = (&01) HP's, available space = (&02) HP's. Immediately erase files no longer required

### Meaning

On the specified pubset, there is less space available as
specified by the current setting of ZIP-LEVEL.
On this pubset, only privileged disk space allocation is still
allowed, and only if the current system session was started with
startup type ZIP.

### Response

Erase as many files as possible immediately.
If the current system session was started with startup type ZIP,
a new session with normal startup type should be started after
reducing disk space allocation on pubset.

## DMS141D

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

Warranty : NO

DMS141D Saturation level exceeds capacity. Current setting for pubset/volume set '(&00)' has been adjusted

### Meaning

The current value of one or several saturation levels of specified
SF pubset or volume set was implicitly modified, as it would
exceed the capacity of pubset/volume set.

### Response

Get actual settings by means of /SHOW-PUBSET-PARAMETERS and change
them with /MODIFY-SPACE-SATURATION-LEVEL if desired

## DMS141E

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

Warranty : NO

DMS141E Defined saturation levels not usable for pubset/volume set '(&00)'. Current values have been set by system

### Response

Get actual settings by means of /SHOW-PUBSET-PARAMETERS and change
them with /MODIFY-SPACE-SATURATION-LEVEL if desired

## DMS141F

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

Warranty : NO

DMS141F Error on request memory for the disk space management tables for pubset/volumeset '(&00)'

### Meaning

When setting up the disk space management tables, a request
for class 4 or class 5 memory has been rejected.
One possible reason is memory shortage.
The size of memory space needed for the disk space management
tables is increasing with pubset capacity. A considerable part of
this tables consists of the F5 label buffers in class 4 memory
which are needed during the whole pubset session. During F5 label
reconstruction an additional need for class 5 memory of
considerable size exists.

### Response

If importation of pubset is still desired, the error cause must
be eliminated and a new /IMPORT-PUBSET command must be issued

## DMS1410

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

Warranty : NO

DMS1410 Current value of default file format for SM pubset '(&00)' has been adjusted

### Meaning

The current value of the default file format for the specified
SM pubset has been implicitly modified, as it is not
supported by the pubset

### Response

Get actual settings by means of /SHOW-PUBSET-PARAMETERS and change
them with /MODIFY-PUBSET-SPACE-DEFAULTS if desired

## DMS148A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS148A The storage class '(&00)' does not exist for the pubset '(&01)'. Command not processed

## DMS148B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS148B The volumeset list '(&00)' does not exist for the pubset '(&01)'. Command not processed

## DMS148C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS148C The maximum number of volumesets will be exceeded for the specified volumeset list. Command not processed

### Meaning

A volumeset list can contain at most 255 volumesets.

## DMS148D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS148D Error on request memory. Command not processed

### Response

Try again later.

## DMS148E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS148E Error on communication with the master host of the pubset '(&00)'. Command not processed

### Response

Try again later.

## DMS148F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS148F Subsystem GCF not available. Command not processed

### Response

Contact the system administrator.

## DMS1480

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1480 Internal error in the storage class management. Task continues

### Meaning

On calling an external function, an error occurred in the storage
class management. A SERSLOG entry has been written.

## DMS1481

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1481 Error on access to the storage class catalog due to DMS error (&00). Command aborted

### Meaning

On access to the catalog containing the storage class definition the
DMS error (&00) occurred. Further information: /HELP-MSG DMS(&00)

### Response

Contact the system administrator

## DMS1482

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1482 Error on access to the volumeset list catalog due to DMS error (&00). Command aborted

### Meaning

On access to the catalog containing the volumeset list definition the
DMS error (&00) occurred. Further information: /HELP-MSG DMS(&00)

### Response

Contact the system administrator

## DMS1483

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1483 Storage class catalog of pubset '(&00)' destroyed

### Meaning

There are invalid data in the catalog containing the storage class
definitions.

### Response

Contact the system administrator. The catalog must be replaced
by a backup catalog.

## DMS1484

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1484 Volumeset list catalog of pubset '(&00)' destroyed

### Meaning

There are invalid data in the catalog containing the volumeset
list definitions.

### Response

Contact the system administrator. The catalog must be replaced
by a backup catalog.

## DMS1485

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1485 The specified pubset is unknown to the system. Command not processed

## DMS1486

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1486 The specified pubset is not an SM pubset. Command not processed

### Meaning

Storage classes and volumeset lists are defined only for SM pubsets.

## DMS1487

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1487 The specified pubset is not accessible. Command not processed

### Response

Contact the system administrator to import the pubset.

## DMS1488

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1488 The storage class '(&00)' already exists for the pubset '(&01)'. Command not processed

## DMS1489

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1489 The volumeset list '(&00)' already exists for the pubset '(&01)'. Command not processed

## DMS149A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS149A No storage class corresponding to specified selection criteria.

## DMS149B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS149B No volumeset list corresponding to specified selection criteria.

## DMS149C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS149C No storage class exists for the pubset '(&00)'

## DMS149D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS149D No volumeset list exists for the pubset '(&00)'

## DMS149E

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS149E SYSLST write error

### Meaning

No secondary allocation possible for the file assigned to SYSLSTnn.

## DMS149F

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS149F Storage class not accessible due to protection attributes. Command not processed

### Meaning

The user attempted to access information about a storage class which
is not accessible for him/her due to profile protection (via GUARDS).

## DMS1490

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1490 The storage class management is not available for the pubset '(&00)'. Command not processed

### Response

Contact the system administrator.

## DMS1491

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1491 Delete storage class(es) '(&00)'? Reply (Y(ES)=Yes; N(O)=No; T(ERMINATE)=Terminate; S(HOW)=Show; ?=Help)

### Meaning

The user can decide, in interactive mode, whether or not to execute the
specified delete task.
(&00): Full or partially qualified storage class name
Y: The storage class(es) will be deleted.
N: The displayed storage class(es) will not be deleted.
T: Processing of the entered delete command will be terminated.
S: The definition(s) of the displayed storage class(es) will be shown,
followed by a renewed display of this message.
?: The replies that are possible will be displayed.

### Response

Enter the appropriate reply according to the explanation in the
'Meaning' text.

## DMS1492

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1492 Delete request for storage classes withdrawn by caller

## DMS1493

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1493 Delete volumeset list(s) '(&00)'? Reply (Y(ES)=Yes; N(O)=No; T(ERMINATE)=Terminate; S(HOW)=Show; ?=Help)

### Meaning

The user can decide, in interactive mode, whether or not to execute the
specified delete task.
(&00): Full or partially qualified volumeset list name
Y: The volumeset list(s) will be deleted.
N: The displayed volumeset list(s) will not be deleted.
T: Processing of the entered delete command will be terminated.
S: The definition(s) of the displayed volumeset list(s) will be shown,
followed by a renewed display of this message.
?: The replies that are possible will be displayed.

### Response

Enter the appropriate reply according to the explanation in the
'Meaning' text.

## DMS1494

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1494 Delete request for volumeset lists withdrawn by caller

## DMS1495

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1495 Invalid backup catalog. Catalog not replaced

### Meaning

For the CHANGE-STORAGE-CLASS-CATALOG or CHANGE-VOLUME-SET-LIST-CATALOG
command, an invalid backup catalog has been provided.

## DMS1496

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1496 Backup catalog does not exist. Catalog not replaced

### Meaning

For the CHANGE-STORAGE-CLASS-CATALOG or CHANGE-VOLUME-SET-LIST-CATALOG
command, the backup catalog named $TSOS.SYSCAT.STORCLS.BAK or
$TSOS.SYSCAT.VSETLST.BAK does not exist.

## DMS1497

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1497 Invalid file attribute combination for the specified storage class. Command not processed

### Meaning

Either a storage class with an invalid file attribute combination was to
be created or an existing storage class was to be modified so that
the resulting file attribute combination would become invalid.
Invalid file attribute combination:
WORK-FILE = *YES and AVAILABILTY = *HIGH.

## DMS1498

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1498 Subsystem GUARDS not available. Command aborted

### Response

Contact the system administrator.

## DMS1499

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS1499 Backup catalog not present on control volumeset. Catalog not replaced

### Meaning

For the CHANGE-STORAGE-CLASS-CATALOG or CHANGE-VOLUME-SET-LIST-CATALOG
command, an backup catalog has been provided that is not located on the
control volumeset.

## DMS3001

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3001 Internal error in Command /RESTORE-PUBSET-FROM-SNAPSET . A serslog entry was written.

### Response

Contact Your system administrator or customer support.

## DMS3002

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3002 Error at message output to '(&00)'

### Meaning

(&00) = SYSOUT / SYSLST

## DMS3003

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3003 Error at request of class '(&00)' memory

## DMS3006

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3006 DMS error '(&00)' at processing of file '(&01)'

### Meaning

A DMS call returned error code '(&00)'.
Error code 'FFFF' denotes a missing subsystem (JV,..) that is required.

### Response

For more information, enter
/HELP-MSG-INFORMATION MSG-ID=DMS(&00).

## DMS310A

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS310A The TSOS or HSMS privilege is required for executing this command

## DMS340D

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS340D Error at acquiring of disc '(&00)'

### Response

Contact your system operator.

## DMS3402

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3402 Import for pubset '(&00)' was not possible

### Response

Contact Your system operator.

## DMS3403

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3403 Waiting for the import of pubset '(&00)' was aborted

### Response

Contact Your system operator.

## DMS3405

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3405 The pubset type of pubset '(&00)' specified in interface RESTORE-PUBSET-FROM-SNAPSET does not agree with the pubset type in the corresponding MRSCAT Entry.

### Meaning

(&00): Catalog id

### Response

Response:
- Correct command/macro call or MRSCAT entry.
- Re-issue command/repeat program execution.

## DMS3406

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3406 No MRSCAT entry was found for catalog id '(&00)'.

### Meaning

(&00): Catalog id

### Response

Response:
- Create MRSCAT entry or correct catalog id.

## DMS3407

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3407 In/Output error at accessing the MRSCAT entry

## DMS3408

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3408 The master catalog entry for the new SM pubset to be restored contains unexpected settings (e.g. control volume set id, type of entry). Reason '(&00)'

### Meaning

(&00): Detailed error specification:
1 = an entry with the same id exists already
2 = the maximum number of MRSCAT entries must not be exceeded.
3 = the MRSCAT entry was modified by command or by importing
the pubset, while the command was being processed.
4 = the MRSCAT entry was modified by command or by importing
the pubset during command processing.

## DMS341A

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS341A Attaching of Device '(&00)' failed

### Meaning

(&00): mnemonic device code

### Response

- Determine cause of failure using the SHOW commands of NDM and SHC-OSD
and if possible fix error.
- Re-issue command /RESTORE-PUBSET-FROM-SNAPSET.
- If problem persists, contact your system engineer.

## DMS341B

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS341B No Snapset Volume was found for Volume '(&01)' of Pubset '(&00)'.

### Meaning

(&00): Catalogue Id
(&01): Volume Serial Number

## DMS341C

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS341C Pubset '(&00)' is used by PVSREN.

### Meaning

(&00): Pubset

### Response

Response: none

## DMS341D

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS341D Restart of command /RESTORE-PUBSET-FROM-SNAPSET for catalog id '(&00)' .

### Meaning

(&00): Catalog id

### Response

Response: none

## DMS341E

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS341E Volume Set '(&01)' is not part of Pubset '(&00)'. Restore fails.

### Meaning

'(&00)' : Catalogue Id
'(&01)' : Snapset Id

## DMS341F

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS341F Volume '(&01)' is not part of Pubset '(&00)'. Restore fails.

### Meaning

'(&00)' : Catalogue Id
'(&01)' : VSN

## DMS3410

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3410 Pubset '(&00)' is not in state 'INACCESSIBLE'.

### Meaning

A pubset has to be in state INACCESSIBLE if it is to be restored.
(&00): Catalog id

### Response

Response:
- Export pubset at a suitable time.
- Re-issue command.

## DMS3411

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3411 Volume Serial Number '(&00)' is not unique or volume is in state 'DRV-MONO'

### Meaning

More than one volume with VSN (&00) is attached or the volume is part
of a logical volume for DRV operation. Thus the VSN is not
unique, and selection of a volume for processing is not possible.

### Response

Response:
- Detach all the volumes with VSN (&00) but the one to be processed
or switch to SRV mode.
- Repeat command.

## DMS3412

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3412 Device Management reports inconsistency of volume '(&00)'.

### Meaning

(&00): Volume Serial Number (VSN)

### Response

Response:
- Contact your system engineer.

## DMS3413

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3413 Subsystem DRV is not created.

### Response

Response:
- Contact system administrator.

## DMS3414

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3414 Pubset '(&00)' contains no snapset catalogue.

### Meaning

(&00): Pubset Id

## DMS3415

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3415 An error occurred while determining the volumes of the SM-Pubset '(&00)'

### Meaning

(&00): Catalog ID of SM pubset
In order to determine the volume list of the SM pubset the SVLs of all
its volres's have to be read. This read operation failed for one or
more of these volumes.
The message may also be issued in a remote copy configuration if both
the snap units of source and target are attached.

### Response

Response:
Make volumes available, if possible. To determine the cause of the error
refer to the CONSLOG file. In case of a remote copy configuration,
detach source or target snapset.

## DMS3416

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3416 Pubset '(&00)' contains fewer volumes than its snapset '(&01)'

### Meaning

'(&00)' : Catalogue Id
'(&01)' : Snapset Id

## DMS3417

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3417 Restoration of Pubset '(&00)' from a Snapset failed

### Meaning

(&00): Catalog Id

### Response

- Determine the failure based on SHC-OSD messages and repair
if possible.
- Determine state of snap units with SHC-OSD commands.
- If possible, re-issue command.
- If problem persists, contact the system administration.

## DMS3418

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3418 TERMINATION OF SNAPSET '(&00)' OF PUBSET '(&01)' FAILED

### Meaning

(&00): Snapset Id
(&01): Catalog Id of Pubset

### Response

- Determine state of snap unit with SHC-OSD commands.
- If possible, terminate snap unit with SHC-OSD commands.

## DMS3419

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3419 Snap Device '(&00)' is not associated to disk device '(&01)'.

### Meaning

(&00): mnemonic of snap device
(&01): mnemonic of disk device

### Response

Response:
- Check configuration of pubset and its associated snapsets by means
of the information commands of pubset management, NDM and SHC-OSD.
- Repeat command, if possible.

## DMS3420

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3420 Attaching of Pubset '(&00)' failed

### Meaning

(&00): Catalog id of pubset

### Response

- Determine cause of failure using the SHOW commands of NDM and SHC-OSD
and if possible fix error.
- Re-issue command /RESTORE-PUBSET-FROM-SNAPSET.
- If problem persists, contact your system engineer.

## DMS3421

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3421 No Snapset Volume was found for Volume '(&01)' of Pubset '(&00)'.

### Meaning

(&00): Catalog Id
(&01): Volume Serial Number

## DMS3422

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3422 Volume '(&00)' is not supported in BS2000/OSD V7

### Meaning

(&00): Volume Serial Number (VSN)

### Response

Response:
- Retry command in a later version of BS2000/OSD

## DMS3423

Destination: USER-TASK Routing code: Weight: 99

Warranty : YES

DMS3423 FOR THE PRESENT STORAGE SYSTEM ONLY SNAPSET=*LATEST IS ALLOWED

### Meaning

It is not allowed to specify a definite snapset ID for the
present storage system.

### Response

Correct the command.

## DMS3500

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3500 Subsystem SHC-OSD is not available.

### Response

Contact Your system administrator or customer support.

## DMS3503

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

DMS3503 Interface '(&00)' returns Error Code '(&01)'

### Meaning

During command processing interface '(&00)' was called.
The call was not successful, error code '(&01)' was reported.

### Response

Response:
Contact your system engineer.

## DMS3631

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3631 UNEXPECTED RETURN CODE OF COMMAND '(&00)'. MAINCODE='(&01)'

## DMS3634

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3634 MAXIMAL NUMBER OF VOLUMES REACHED FOR PUBSET/VOLSET '(&00)'

## DMS3635

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3635 SUBSYSTEM '(&00)' NOT AVAILABLE

## DMS3642

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3642 INVALID DISK STATUS OF VOLUME '(&00)'

## DMS3651

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3651 INVALID DEVICE STATUS '(&00)' OF DISK '(&01)'

### Meaning

'(&00)': device status
'(&01)': device MN

## DMS3652

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3652 UNSUPPORTED DEVICE TYPE '(&00)'

## DMS3653

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3653 FORMAT '(&00)' NOT SUPPORTED FOR DEVICE TYPE '(&01)'

## DMS3654

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3654 UNKNOWN DEVICE TYPE '(&00)'

## DMS3655

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3655 VOLIN ERROR '(&00)'

## DMS3656

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3656 UNRECOVERABLE ERROR AT VOLIN RUN

## DMS3657

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3657 NEW-VSN=*NON-STD NOT SUPPORTED BY VOLIN FOR DEVICE-TYPE D3475-8F

## DMS3660

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3660 FROM-DISK AND TO-DISK ARE *NON-STD. NO ACTION REQUIRED

## DMS3661

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3661 PUBSET '(&00)' NOT AVAILABLE

## DMS3666

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3666 FROM-PUBSET AND TO-PUBSET MUST BE DIFFERENT

## DMS3667

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3667 INVALID VOLSET SPECIFICATION FOR PUBSET '(&00)'

## DMS3668

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3668 INVALID SPECIFICATION OF VOLRES FOR PUBSET '(&00)'

## DMS3669

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3669 SPECIFIED FROM-VOLUME '(&00)' NOT FOUND

## DMS3670

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3670 INVALID TO-VOLUME '(&00)' SPECIFIED

## DMS3671

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3671 SPECIFIED FROM-VOLUME '(&00)' COULD NOT BE CLEARED

## DMS3672

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3672 FORMER PUBSET-VOLUME '(&00)' MOVED TO PUBSET '(&01)'. NEW VSN IS '(&02)'

## DMS3673

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3673 VOLIN WILL BE STARTED. FORMATTING OLD VSN '(&00)' TO NEW VSN '(&01)' ON DEVICE '(&02)'. PLEASE STAND BY

## DMS3674

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3674 DISK '(&00)' MOVED TO PUBSET '(&01)'. NEW VSN IS '(&02)'

## DMS3675

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3675 FORMER PUBSET-VOLUME '(&00)' MOVED TO VOLUME WITH VSN '(&01)'

## DMS3676

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3676 DISK '(&00)'/'(&01)' INITIALIZED WITH VSN '(&02)'

### Meaning

'(&00)': device MN
'(&01)': original VSN
'(&02)': current VSN

## DMS3677

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3677 CURRENT VSN OF DISK '(&00)' IS '(&01)'. INITIALIZATION REJECTED

### Meaning

'(&00)': device MN
'(&01)': current VSN

## DMS3678

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3678 FORMAT OF FROM-DISK AND TO-DISK ARE DIFFERENT. DISK MUST BE FORMATTED

## DMS3679

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3679 ERROR AT VOLIN RUN

## DMS3683

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3683 DISK '(&00)' NOT ATTACHED OR NOT AVAILABLE

### Meaning

'(&00)': device MN

## DMS3685

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3685 FROM-PUBSET/VOLSET '(&00)' CONSISTS OF ONE VOLUME ONLY

## DMS3686

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3686 PUBSET '(&00)' IS A SHARED PUBSET BUT OWN HOST IS NOT PUBSET-MASTER. COMMAND REJECTED

## DMS3699

Destination: USER-TASK Routing code: Weight:

Warranty : NO

DMS3699 INTERNAL ERROR OCCURRED. ERROR CAUSE '(&00)'

### Response

Contact the system administration.

©2025 Fujitsu | BS2000 System Messages