Conference cookie::sls

2236.0. "SYSTEM-W-NODEVAVL, SLS-I-DEVDROPPED" by ATZIS3::PIEBER (chaos has many faces) Fri Apr 04 1997 09:18

    Hi folks,

    I stumbled across a problem I have personaly created due to omission.
    However, to locate the problem, the error message was not very helpful
    to me, nor could I find a documentation for it. So, maybe others can
    make use of this experience.

    What I did (not):

    On an ABS client I forgot to add the nodename to the drive names in
    TAPESTART.COM. My fault - no doubt.


    How this manifested itself:

    ABS:

    The logfile of the coordinator told me, that there is no drive
    available for selection:

    COORDINATOR:  Created new volume set: MCS101
    COORDINATOR:  Mounting volume set member: MCS101 RVN 1
    COORDINATOR:  Failed to mount volume set after 1 attempts
    COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable
                  tape drive via SLS
    COORDINATOR:     Line = 4404, File = RESD$:[SRC]SLS_SERVICES.C;1
    COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable
                  tape drive via SLS
    COORDINATOR:     Line = 9156, File = RESD$:[SRC]SLS_SERVICES.C;1
    COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific
                  error in diag block
    COORDINATOR:     %SYSTEM-W-NODEVAVL, no device available
    COORDINATOR:  Continuing to retry every 60 seconds...



    MDMS:

    An OPCOM message popped up for each device in each cycle the ABS SR
    performed:

	%%%%%%%%%%%  OPCOM   4-APR-1997 13:24:51.70  %%%%%%%%%%%
	Message from user SLS on ISDS01
	SLS$TAPMGRRQ, %SLS-I-DEVDROPPED, invalid device $1$MUA6: ignored 
                         during device selection


    After re-reading TAPESTART.COM over and over, I finally found, what
    caused this. Needless to say, that I worked then ;-)

    Ewald.