search

RexxLA / mvstk5

Gather and structure issues around MVS TK5
0 stars 0 forks source link

IEHMOVE has a problem reading an aws tape, states "ACCESS METHOD NOT COMPATIBLE" #3

Open rvjansen opened 7 months ago

rvjansen commented 7 months ago

given this JCL:

 //AB2217#  JOB 1,1,MSGCLASS=X,REGION=512K,NOTIFY=&SYSUID                 
 //MOVE   EXEC  PGM=IEHMOVE                                               
 //TMP001   DD DSN=AB2217.SNOBOL4.LINKLIB,DISP=(NEW,CATLG),               
 //             UNIT=SYSDA,VOL=SER=TSO001,                                
 //             SPACE=(CYL,(1,1,10)),                                     
 //             DCB=SYS2.LINKLIB                                          
 //SYSPRINT DD  SYSOUT=A                                                  
 //SYSUT1   DD  UNIT=SYSDA,VOL=SER=TSO001,DISP=OLD                        
 //TAPE     DD  DSN=A,VOL=SER=SNOBOL,DISP=(NEW,KEEP),UNIT=480,            
 //             LABEL=(1,NL)                                              
 //SYSIN    DD  *                                                         
  COPY  PDS=AB2217.SNOBOL4.LINKLIB,FROM=480=SNOBOL,TO=SYSDA=TSO001,     X 
                FROMDD=TAPE                                               
 //

and a devinit 480 /home/rvjansen/snobol_iehmove_nl.aws on the hercules console, I see this job output:

IEF375I  JOB /AB2217# / START 24026.1639                                                                       
IEF376I  JOB /AB2217# / STOP  24026.1639 CPU    0MIN 00.11SEC SRB    0MIN 00.01SEC                             
SYSTEM SUPPORT UTILITIES ---- IEHMOVE                                                               PAGE    1  
 COPY  PDS=AB2217.SNOBOL4.LINKLIB,FROM=480=SNOBOL,TO=SYSDA=TSO001,     X                                       
               FROMDD=TAPE                                                                                     
THE DSCB FIELDS, RECFM AND BLKSIZE, HAVE BEEN DEFINED TO ALLOW THIS MOVE/COPY REQUEST                          
IEH411I DATA SET AB2217.SNOBOL4.LINKLIB NOT MOVED/COPIED BECAUSE                                               
 ACCESS METHOD NOT COMPATIBLE
rvjansen commented 7 months ago

Note that on advice of Mike Schwab I did the allocation of the loadlib in the same step as the utility execution, and left out the DCB statement of the original job found on Jay Moseley's site.

Tapemap tells me this:

VOL=HTAPE1                       TAPE ANALYSIS PROGRAM   (T A P E M A P)  V2.1          FRIDAY     JAN 26, 2024  (24.026)  17:05:01 

------------------------------------------------------------------------------------------------------------------------------------
RELOAD   FILE                     PSWD                   INFO                 BLOCK   BLOCK            LNTH  TOTL  CREATOR          
FORMAT   SEQ#  DATASET NAME       REQD  C-DATE  E-DATE  SOURCE  RECFM  LRECL   SIZE   COUNT  DEN  TRT  (FT)  LNTH  JOBNAME/STEPNAME 
------------------------------------------------------------------------------------------------------------------------------------
++++ NO VOL1 LABEL FOUND.  NL ANALYSIS FOLLOWS ++++                                                                                 

IEHMOVE     1                                            SCAN   F               800     155  6250         6     6                   
     *** EOV ***                                                                                                                    
NOTE:  LENGTH(S) ARE COMPUTED, (BASED ON BLKSIZE, BLKCOUNT, AND DENSITY), AND ARE THEREFORE ONLY APPROXIMATE.             6548K FREE