## NDV0002

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

Warranty : NO

NDV0002 ACCESS TO SVL OF '(&00)' ON '(&01)' LOCKED BY SYSTEM '(&02)'. REPLY (R=RETRY, T=TERMINATE, F=FORCE LABEL ACCESS)

### Meaning

The Standard Volume Label (SVL) of volume (&00) on device (&01) has been
locked by system (&02) for an unusually long time.
Check the state of system (&02). Do n o t reply with 'F' as long as
system with SYSISD (&02) is working with the volume concerned, as
otherwise data integrity cannot be guaranteed.

### Response

Enter R, T or F. Minimum retry-time is about 40 sec.

## NDV0003

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

Warranty : NO

NDV0003 ILLEGAL RESPONSE

### Meaning

Illegal response to NDV0002 or NDV0004.

### Response

Valid answers for NDV0002:
R : Retry (and wait again min. 40s)
T : Terminate
F : Force label access
Valid answers for NDV0004:
R : Retry
I : Retry and Inform
T : Terminate

## NDV0004

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

Warranty : NO

NDV0004 WRITE INHIBIT SWITCH OF '(&01)' IS ON. SVL-UPDATE OF '(&00)' FAILED. RETRY WITH WRITE INHIBIT OFF? REPLY (R=RETRY, I=RETRY+INFORM, T=TERMINATE)

### Meaning

The position of the WRITE INHIBIT switch on the device (&01) prevents
allocation data from being included in the Standard Volume Label (SVL) of
volume (&00).
Switch WRITE INHIBIT off and reply with 'R' or 'I', if the volume is to be
allocated or deallocated.
If 'I' is replied, message NDV0005 will be issued after the SVL has been
completely updated. This provides the opportunity to renew the WRITE
INHIBIT before any further IO is directed to the volume.

## NDV0005

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

Warranty : NO

NDV0005 SVL-UPDATE OF '(&00)' COMPLETED. WRITE INHIBIT CAN BE SET FOR '(&01)'. CONTINUE? REPLY (EOT=YES)

### Meaning

Update of the Standard Volume Label (SVL) of volume (&00) has been
completed.
WRITE INHIBIT can be switched on again at device (&01).
Enter EOT if the WRITE INHIBIT switch has been set as desired.

### Response

EOT: Continue system-action

## NDV0006

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

Warranty : NO

NDV0006 '(&05)' BAVOLMON-ERROR: '(&04)'-RC='(&00)', LRC='(&01)', ERROR-ID '(&02)' FOR TSN '(&03)', MN='(&06)', VSN='(&07)'

### Meaning

Output of each BAVOLMON-error-traceentry as an Emergency-message on
main-console is switched on for diagnostic aid.
To limit the amount of MSGs, selection by various criteria is possible.
Each entry is protocolled in short form.
--------------------------------------------------------------------------
(&05): error-time.
(&04): called BAVOLMON function,
RC (&00): BAVOLMON return code sent to caller,
LRC (&01): logical io return code,
Error-ID (&02): position, where the RC was build in BAVOLMON,
TSN (&03): calling task,
MN (&06): MN of device or NOMN,
VSN (&07): volume serial number or NO-VSN.
--------------------------------------------------------------------------

### Response

Dont forget to switch off this feature.
Emergency messages are output only once a second.

## NDV0007

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV0007 ASSIGN-END OF '(&00)' ON '(&01)' BUT SVL IS STILL RESERVED BY '(&02)', '(&03)','(&04)','(&05)','(&06)','(&07)','(&08)','(&09)','(&10)','(&11)'.

### Meaning

BAVOLMON receives an ASSIGN-END-order for disk (&00) on device (&01)
although several tasks have still reserved the Standard Volume Label (SVL)
of (&00).
BAVOLMON cancels the reservations and executes the ASSIGN-END-order.
It may be that the tasks (&02),...,(&11) terminate soon abnormally.
(&00): VSN of Volume
(&01): MN mnemotechnical identifier of device

## NDV0008

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

Warranty : NO

NDV0008 RELEASE-I/O FAILED FOR '(&00)' ON '(&01)' WITH RC '(&02)' AND LRC '(&03)' AT INTERFACE '(&04)'.

### Meaning

BAVOLMON was not successfull to RELEASE a HardWare-RESERVE
used for SVL-Update.
This occurred to the volume with VSN (&00)
mounted on the device with MNemonic (&01)
As a consequence this device (&01) could not be accessed
by other hosts anymore.
Further details are given to support erroranalysis:
(&02) : Return-Code to caller of Interface (&04)
(&03) : I/O-Return-Code (last LRC)
(&04) : BAVOLMON-function, which issued the RELEASE-I/O

### Response

If another host gets the message "EXC0857 -RESV--DEVICE RESERVED
ELSEWHERE-" or "EXC0857 -BUSY--DEVICE BUSY" concerning
this device, "UNCONDITIONAL RESERVE" should be
choosen by the operator, when answering the console question.
The RESERVE on the former host is thus released.
ONLY if it is guaranteed, that NO further HOST is using this
device a command UNLOCK-DEVICE <mn> could be issued alternatively.

## NDV0009

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

Warranty : NO

NDV0009 ASSIGN OF '(&00)' ON '(&01)' REJECTED AS SYSTEMS OF '(&02)'IBF/FCP-TYPE ARE ASSIGNED WITH IDS '(&03)'.

### Meaning

An assign order has been rejected, as other systems have
already assigned this volume via an other channeltype.
For consistent operating and correct sharing all systems involved
have to assign homogeneously as far as the channeltype is
concerned. This means, that all systems use the volume via IBF/FCP
channel or via the NON-IBF/FCP channel but not in a mixed way.
(&00): VSN (Volume Serial Number)
(&01): Device Mnemonic
(&02): Channeltype IBF/FCP or NON-IBF/FCP (Insert NON-)
(&03): List of System-IDs already assigned to this Volume (max. 16)

### Response

Use the device mnemonic corresponding to the other channeltype
to get assignment of the current system. Otherwise end assignment
of this volume on all systems indicated in the list, followed by a
reassignment via the same channeltype as used in current system.

## NDV0020

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

Warranty : NO

NDV0020 SNAP-SHOT-DUMP CAUSED BY A BAVOLMON-ERROR-TRACE-ENTRY

### Meaning

Snap-Shot -Dump combined with the BAVOLMON-Error-trace is switched on.
Each error-trace-event triggers a $SNAP-call for diagnostic aid.

## NDV0022

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

Warranty : NO

NDV0022 ERROR IN ESTABLISHING BAVOLMON TASK-LOCK

### Meaning

$GTLOCK reports inconsistent parameters.
It may be caused by contingency-handling or a BAVOLMON-error.
SNAP-SHOT-dump is initiated.

## NDV1111

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1111 ERROR IN BAVOLMON DURING RELEASE OF RESOURCES. PL:

### Meaning

A $RELM-, $RETMEM- or $RETSL-call by BAVOLMON supplied a negative
returncode.

## NDV1112

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1112 BAVOLMON OWN SVL BUFFER: SEM,QUE,LST:'(&00)', BAVOLMON SVL-TRACE:'(&01)'

### Meaning

An inconsistency in SVL-data is detected.
SVL-Semaphor, sharer-queue and sharer-list (&00) of BAVOLMON own SVL
buffer
and the SVL-Trace-area (&01) are saved in the error-logging-entry.

## NDV1113

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1113 VT-LOCK-INCONSISTENCY DETECTED FOR TID: '(&00)', INPUT-PARAMETER: '(&01)'

### Meaning

An inconsistency is detected in RESERVE=*SYSTEM-handling.
The input-parameter are saved in an error-logging-entry.

## NDV1114

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1114 TASK-LOCK-MANAGER-ERROR DETECTED BY BAVOLMON. PL:

### Meaning

Error-logging entry caused by a negative RC detected by BAVOLMON during
Task-Lock-Handling.

## NDV1115

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1115 ACCESS-RIGHT TO SVL WITHDRAWN: TSN, MN, VSN

### Meaning

Due to a deadlock-situation the tasklock of a pending task TSN is
removed. The device MN with VSN is concerned.

## NDV1116

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1116 RELEASE-LOCK-ERROR DETECTED BY BAVOLMON FOR TID: '(&00)' REASON: '(&01)'

### Meaning

BAVOLMON has detected an illegal state of a Task-Lock
for F5-Label at release-time.
(&00) : TID Task-ID
(&01) : Reason: LOCK DESTROYED
or LOCK NOT HELD

## NDV1117

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1117 $NBSRV-ERROR DETECTED BY BAVOLMON. PL:

### Meaning

A $NBSRV-call by BAVOLMON supplied a negative
returncode.

## NDV1118

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1118 $NDGRR-ERROR DETECTED BY BAVOLMON. PL:

### Meaning

A $NDGRR-call by BAVOLMON supplied a negative
returncode.

## NDV1119

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1119 $TYPIO-ERROR DETECTED BY BAVOLMON. PL:

### Meaning

A $TYPIO-call by BAVOLMON supplied a negative
returncode.

## NDV1120

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1120 $CHKPRV-ERROR DETECTED BY BAVOLMON. PL:

### Meaning

A $CHKPRV-call by BAVOLMON supplied a negative
returncode.

## NDV1121

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1121 BAVOLMON OWN SVL BUFFER: SEM,QUE,LST:'(&00)', BAVOLMON SEM-INKO-TRACE FROM NDVMWRA: '(&01)'

### Meaning

An semaphor-inconsistency in SVL-data is detected.
SVL-Semaphor, sharer-queue and sharer-list (&00) of BAVOLMON own SVL
buffer
and the WRA-Data (VT and SVL-Parts) relevant for sem-inconsistency (&01)
are saved in the error-logging-entry.

## NDV1122

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1122 $VGDIEX-ERROR DETECTED BY BAVOLMON. MN SEE PL:

### Meaning

A $VGDIEX-call by BAVOLMON supplied a negative
returncode. The returncode and device-MN are dumped in parameterlist.

### Response

Check device-configuration in each virtual machine

## NDV1123

Destination: USER-TASK Routing code: Weight: 99

Warranty : NO

NDV1123 TASKLIST OF BAVOLMON-RESERVE NOT EMPTIED FOR LONG TIME - TASK WAITS FOR MN, VSN: '(&00)' DUMP OF INTERNAL DATA NDIVBVMP '(&01)'

### Meaning

The issuing Task is waiting for a long time for BAVOLMON-RESERVE con-
cerning the disk with deviceidentifier MN and Volume-Serial-Number VSN.
One or more tasks dont release their reservation = emptiing the tasklist
The TIDs of this task are shown in the DUMP-Data.
(&00) MN VSN
(&01) DUMPDATA LAYOUT NDIVBVMP
This error-logging-entry occurs periodically.

### Response

Check state of Tasks holding the reservation.
(e.g: answer Operatorquestions)

## NDV1200

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1200 NKDINF-FATAL-ERROR: DETAILS SEE PL:'(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to detect the
relationship between the device-MNs and the VSNs of PUBSET and
save this in metadata residing on PUBRES/VOLRES-Disks.
The information-function has failed, no update takes place.
To analyse the reason the parameterlist dumped.

### Response

PUBSET-type commands should not used for this PUBSET.
Next IMPORT/EXPORT a retry is started

## NDV1201

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1201 NKDINF-RECORDS INCOMPLETE: DUMP OF INTERNAL DATA '(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to detect the
relationship between the device-MNs and the VSNs of PUBSET and
save this in metadata residing on PUBRES/VOLRES-Disks.
The information-function has failed partially, no update takes place.
To analyse the reason internal data are dumped.

### Response

PUBSET-type commands should not used for this PUBSET.
Next IMPORT/EXPORT a retry is started.

## NDV1240

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1240 $NDVGMN(I)-ERROR DETECTED - DETAILS SEE PL:'(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to get the
relation between the VSNs of a PUBSET and the device-MNs and
reads the metadata residing on PUBRES/VOLRES-Disks.
The function $NDVGMN has failed fully or partially, thus the
commands could have covered only parts of the PUBSET-Devices.
To analyse the reason the parameter list is dumped.

### Response

Testing the data stored is possible by issueing SHOW-DEVICE-
CONFIGURATION *P(catid). A second possibility is to issue
SHOW-DEVICE-CONFIGURATION *P(*B(mn)) using the PUBRES-MN.
If the relation is not uptodate, wait until next IMPORT/EXPORT-
PUBSET action.

## NDV1241

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1241 ERROR IN MIRROR-INFO DETECTED - DUMP OF PL-DATA:'(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to get the
relation between the VSNs of a PUBSET and the device-MNs and
reads the metadata residing on PUBRES/VOLRES-Disks.
The evaluation of additional information of mirrored disks
(MULTI-MIRROR, REMOTE-COPY) has failed fully or partially.
Thus the commands could have covered only parts of the PUBSET-Devices.
To analyse the reason the parameter list is dumped.

### Response

Testing the data stored is possible by issueing SHOW-DEVICE-
CONFIGURATION *P(catid). A second possibility is to issue
SHOW-DEVICE-CONFIGURATION *P(*B(mn)) using the PUBRES-MN.
If the relation is not uptodate, wait until next IMPORT/EXPORT-
PUBSET action.

## NDV1250

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1250 $NDVUMN(I)-ERROR DETECTED - DETAILS SEE PL:'(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to detect the
relation between the device-MNs and the VSNs of PUBSET and
save this in metadata residing on PUBRES/VOLRES-Disks.
The function $NDVUMN has failed fully or partially.
The usage of these old or incomplete data is not recommended.
To analyse the reason the parameter list is dumped.

### Response

PUBSET-type commands should not used for this PUBSET until the
reason is cleared.
At next IMPORT/EXPORT-PUBSET a retry is started.

## NDV1251

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1251 NDEINF-ERROR DETECTED BY BAVOLMON AT UPD-MN-FUNCTION. DEVICE-MN(S) OF SRDF-MIRROR(S) ARE MISSING.- DETAILS SEE PL-DATA: '(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to detect the
relationship between the device-MNs and the VSNs of a PUBSET and
save this in metadata residing on PUBRES-/VOLRES-Disks.
The informationfunction NDEINF, called in addition to cover
mirrored disks has failed fully or partially.
Thus old or incomplete data on Target- or Source-Units could spoil
the full functionality.
To analyse the reason the parameter list is dumped.

### Response

PUBSET-type commands should be used for this PUBSET with caution.
The functionality for mirrored disks is not guaranteed.
At next IMPORT/EXPORT-PUBSET a retry is started.

## NDV1253

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1253 $NKRGMN-ERROR DETECTED BY BAVOLMON AT UPD-MN-FUNCTION. DEVICE-MN(S) OF SRDF-MIRROR(S) ARE MISSING.- DETAILS SEE PL-DATA: '(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to detect the
association between the device-MNs and the VSNs of a PUBSET and
save this in metadata residing on PUBRES-/VOLRES-Disks.
The informationfunction $NKRGMN, called in addition to cover
mirrored disks has failed fully or partially.
Thus old or incomplete data on Target- or Source-Units could spoil
the full functionality.
To analyse the reason the parameter list is dumped.

### Response

PUBSET-type commands should be used for this PUBSET with caution.
The functionality for mirrored disks is not guaranteed.
At next IMPORT/EXPORT-PUBSET a retry is started.

## NDV1270

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1270 INCONSISTENT DATA FOUND DURING UPDATE OF FILE SYSDAT.APUB.<VSN> - DETAILS SEE DUMP-DATA: '(&00)'

### Meaning

To support PUBSET-type of commands BAVOLMON wants to update the
file. An inconsistency between filename and header-data is found.
To analyse the reason header-data, filename and the parameter-list
of the order are dumped.

### Response

PUBSET-type commands should not be used for this PUBSET.
At next IMPORT/EXPORT-PUBSET a retry is started.

## NDV1908

Destination: USER-TASK Routing code: Weight:

Warranty : NO

NDV1908 RELEASE-I/O FAILED - MESSAGE-PARAMETER: '(&00)' ERELDATA: '(&01)'

### Meaning

Complete set of internal Data comparable to MSG NDV0008 but more
detailed.
(&00) Parameterlist of function called
(&01) List of Errordata

### Response

same as NDV0008

©2024 Fujitsu | BS2000 System Messages