ADSM-L

[no subject]

2015-10-04 17:36:16

Sam,

     I specified the first volume in the export as the first volume on the
import.  You're right, of course, about the 813-04 and the dataset name is
ADSM.EXP.  I'm sure it has to do with the security aspects of either the dataset
name or the 'job' accessing it - both of which are different on the two servers.

                         Ginny
---------------------- Forwarded by Virginia L Hysock/GIS/CSC on 12/15/99 02:24
PM ---------------------------
PM ---------------------------

       (Embedded image moved to file: pic24381.pcx)


Virginia L Hysock/GIS/CSC
12/15/99 12:12 PM

To:   Virginia L Hysock/GIS/CSC@CSC
cc:
Subject:  IMPORT NODE TO A DIFFERENT SERVER

Date:    Tue, 14 Dec 1999 11:42:09 PST
From:    Sam Sheppard <SHS AT SDDPC.SANNET DOT GOV>
Subject: IMPORT NODE TO A DIFFEREN


---------------------------- Top of message ----------------------------
>>--> 12-14-99  11:39  S.SHEPPARD     (SHS)    IMPORT NODE TO A DIFFEREN
>>--> 12-14-99  11:39  S.SHEPPARD     (SHS)    IMPORT NODE TO A DIFFEREN

Ginny:  Abend 813-04 indicates that the dsname on the tape label doesn't
match what ADSM is expecting, usually something like ADSM.EXPORT.  Make
sure you have specified the correct volser in the import.

Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668


<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=