Conference iosg::all-in-1_v30

1551.0. "RSD housekeeping problem" by ZPOVC::SELENACHOO () Fri Oct 02 1992 13:45

HI,

My customer just run the RSD housekeeping routine and get the following errors.


Error at "PARSE_NAME ASSIGN" with "    ACA43:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA13:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA14:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA23:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA13:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA14:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA23:":
%SYSTEM-F-IVDEVNAM, invalid device name
Error at "PARSE_NAME ASSIGN" with "    ACA43:":
%SYSTEM-F-IVDEVNAM, invalid device name

Updating SDAF master file
SDAF master file record updated for mail area A
SDAF master file record updated for mail area E
SDAF master file successfully updated
%SMJACKET-I Invoking common END_BATCH procedure
%END_BATCH-I Performing End batch job procedures for "RSD"

.....


Hence, it seems like some of the share areas are reorganized only. 
The devices which are supposed to be invalid are valid device name, referring
to different data disks. How can she prevent this from happening if she runs
RSD again? This is the first time she runs RSD after she splits the share
area to different devices.

Thanks in advance.


Selena Choo 

    Long shot, but have you checked the definition of the device logicals?
    See note #1545.3.
    
    Cheers,
    DaveT

Hi,

>> Error at "PARSE_NAME ASSIGN" with "    ACA43:":

This just tells you (or rather me! :-) at what point in RSD the error occurred,
and what data (in this case, a disk name) it was processing.

>> %SYSTEM-F-IVDEVNAM, invalid device name

This is the error that occurred, and is the return status from a SYS$ASSIGN
call: ie VMS is generating the error, not RSD.

The error means that VMS does not think that ACA43: is a valid device name.
The reason for this is that the disk name contains leading spaces, viz:

>> Error at "PARSE_NAME ASSIGN" with "    ACA43:":
                                      ^^^^

Spaces are invalid characters in disk names, so SYS$ASSIGN fails.

RSD gets the disk names from two places: SM_SDAF_MASTER and
SM_SHARED_DIR_MASTER.  It would appear that when splitting the shared areas to
different devices, the system manager entered disk names on one (or both -
I can't tell from the error which file the bad data comes from) of the above
forms with leading spaces.

So all you have to do to solve this problem is find the offending records in
SM_SDAF_MASTER and SM_SHARED_DIR_MASTER, and correct them.

Scott