hi all, i have built?4.6.0.10941-SDL-g65c97fd6 on?Linux-5.14.0-284.25.1.el9_2.x86_64.
the hercules runs well. and i built an standalone ickdsf to initialize the cckd volume.?


INIT UNITADDRESS(52C1) NOVERIFY VTOC(300,0,600) VOLID(DCAT50)

HI,
is the data you are restoring from the same device type as you are restoring too ?
Your target is a 3390, is the source dumped from a 3390 ?

I think that DFSMSdss doesn't convert from one device type to another but expects them to be the same CC HH configuration.
It's a long time since I did dump / restore of this type, I understand it can be faster than doing it by datasets, but
restoring datasets can cross disk types and add them to the vtoc as it does it.

If the restore tape you are using contains a vtoc then the dasd is probably going to be mis-configured
because you have already configured a vtoc, and I doubt that having 2 vtoc's will work.

Regards,
Tom.

Hi Tom, thanks for your reply.? yes, the source dumped from a 3390-9.
the backup procedure is as below:

Hi,
Unfortunately you've reached the end of my knowledge, but perhaps you need to specify 3390-9 in the hercules conf file ?
I have a thought that using just 3390 defaults to a much smaller 3390-1, so you may need to run the init and restore again after changing the definition.
Regards,
Tom.

开云体育

The problem is not the dasd volume, it's the tape.? You probably reformatted the tape into AWS format, but DFDSS does not understand the record formats you are trying to install to the disk.

To copy a volume from a mainframe to Hercules, you need to upload the tape dataset to your PC in binary format and then upload that dataset to an empty DASD volume on your hercules based z/OS and restore it from there.

Alternatively, I think there is a mod somewhere that you can use on the original mainframe that causes DFDSS to create the AWS format dataset that you can use with hercules.? DFDSS expects each block to be a track image, but I think when you made the AWS tape, you changed the blocks to be quite a bit smaller, but the DFDSS you are using under hercules doesn't "know" that it needs to combine blocks to get a real track image.

There are several methods you can use to copy your data from a mainframe to hercules, but the one you are using isn't one that I have heard of previously.?

Anyway, there are several tried and true methods to transfer the data.

Brian

Hi Brian, yes i followed the step on the hercules home page. i converted the backup tape to aws format. and want to load it to the dasd inited.

after i restored the resident volume i can ipl the zos system in hercules.

Could you kindly provide some step-by-step instructions on?copy a volume from a mainframe to Hercules.

Your help is greatly appreciated. Thank you

CCKDDUMP program on actual system.

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

This procedure works 100% of the time.

On the source system, (the real mainframe in your case):

This first step uses DFdss to dump the volume to a temporary dataset that we will process with TRS to make it portable

//DUMPDASD EXEC PGM=ADRDSSU????????????????????????????????????????? ?
//SYSPRINT DD SYSOUT=*?????????????????????????????????????????????? ?
//DISK1??? DD UNIT=3390,VOL=SER=Z25PTS,DISP=SHR??????? <-- this is the volume that you want to copy to Hercules (or any system) ?????????????
//TAPE1??? DD DSN=SMSTAPE.Z25PTS.VOLUME.BACKUP,????? <-- this is the output file, which for me is on DASD, but can be on tape but the next step runs faster on DASD ??????????????
//??????????? DISP=(,CATLG,DELETE),????????????????????????????????? ?
//??????????? UNIT=3390,SPACE=(TRK,(6000,6000),RLSE)???????????????? ?
//SYSIN??? DD *????????????????????????????????????????????????????? ?
?PARALLEL??????????????????????????????????????????????????????????? ?
?DUMP FULL INDDNAME(DISK1) OUTDDNAME(TAPE1) CANCELERROR -??????????? ?
?? COMPRESS OPT(4) ADMINISTRATOR???????????????????????????????????? ?
//*???????????????????????

This step makes the temporary dataset portable.? It can be sent via FTP to anywhere in BINARY format.?
??????????????????????????????????????????
//PACK0 EXEC PGM=TRSMAIN,PARM=PACK??????????????? <-- this step compresses the data in IBM's TRS format ??????????????????
//SYSPRINT DD SYSOUT=*?????????????????????????????????????????????? ?
//INFILE DD DISP=(OLD,DELETE),DSN=SMSTAPE.Z25PTS.VOLUME.BACKUP??????? <-- this is the dataset created in the first step
//OUTFILE DD DSN=BRIANW.Z25PTS.TERSED,DISP=(NEW,CATLG),?????????????? <-- this is the output that will be FTP'ed to your PC MAKE sure to transfer in BINARY format
//??????? UNIT=TAPE,LABEL=(1,SL),RETPD=3,??????????????????????????? ?
//??????? DCB=(RECFM=FB,DSORG=PS,LRECL=1024)?????????????

The OUTFILE above needs to be FTP'ed in BINARY format to wherever you are sending it.? If to your PC, you will need to then FTP it to Hercules, but you can also FTP it directly to your hercules instance thereby removing the need to FTP it twice.? I use the FTP to the PC so that I have a copy of the dataset that I can fall back to if something happens.? ???????????

On the target Hercules system, first create a new dataset to FTP the file from the previous step into.? You need to manually create it because FTP doesn't like sending really large datsets without pre-allocation, but you could certainly use SITE commands to control the space and LRECL etc.? I jsut pre-allocate it because it's quicker for me.

That dataset on your Hercules instance should ALWAYS be created as FB lrecl=1024

You then need to run another TRSMAIN to UNPACK the dataset that you just FTPed (same as previous step, but with parm=UNPACK
make sure to use binary transfer in the FTP, preallocate as DSNTYPE=LARGE, because if you are sending 3390-9 or larger they tend to be big
Most are very big pri=4000,sec=4000 in cylinders.? Most volumes are much smaller, but I have 8 3390-54 volumes that are just for transferring volumes in one big SMS pool.? I delete them and copy the compressed CCKD 64 volumes every time I bring up hercules, so they are always empty when I start up.

//UNPACK0 EXEC PGM=TRSMAIN,PARM=UNPACK??????????????? <-- this step decompresses the data from IBM's TRS format ??????????????????
//SYSPRINT DD SYSOUT=*?????????????????????????????????????????????? ?
//INFILE DD DISP=(OLD,DELETE),DSN=BRIANW.Z25PTS.TERSED??????? <-- this is the output that will be FTP'ed to your PC
//OUTFILE DD DSN=BRIAN.Z25SYS.VOLUME,DISP=(NEW,CATLG),?????????????? <-- This is the input to the next step TRS will set the DCB back to the original in the first step
//??????? UNIT=3390,VOL=SER=TRAN01,?????????? <-- one of my 3390-54 volumes used as a temp holing area. ????????????????
//??????? SPACE=(CYL,(4000,4000)),DSNTYPE=LARGE

Then run DFDSS restore on hercules system? (if needed, this can be a SArestore):
??
//STEP1? EXEC? PGM=ADRDSSU, REGION=0M ????????????????????????????????????
//*??????????????????????????????????????????????????????????? ?
//*??????????????????????????????????????????????????????????? ?
//SYSPRINT? DD? SYSOUT=*?????????????????????????????????????? ?
//OUTDD1?? DD??? VOL=SER=G25SYS,UNIT=3390,DISP=OLD????????? <--- the volume you are making ??
//INDD1 DD DSN=BRIAN.Z25SYS.VOLUME,???????? <-- this is the dataset you ftped ??????????????????
// DISP=(OLD,KEEP,KEEP)??????????????????????????????????????? ?
//SYSIN??? DD??? *???????????????????????????????????????????? ?
?RESTORE FULL -??????????????????????????????????????????????? ?
???????? INDDNAME(INDD1) -???????????????????????????????????? ?
???????? OUTDDNAME(OUTDD1) -?????????????????????????????????? ?
???????? CANCELERROR -???????????????????????????????????????? ?
???????? WAIT(2,2) PURGE ADMIN COPYV?????????????????????????? ?
/*?????????????????

This process needs to run for each volume you want to use.? It seems like a lot of work, but actually it's very straightforward.

There are two other methods that I know of that also always work, but this is the one I use the most.

There is no limit to the volume size, I have moved terabyte EAS 3390 volumes with no issues.

Brian ????????????????????????????????????????

Hi Brian,

Thanks so much for your time and detail steps.

Two more questions per your reply:
The first? is about pre-allocate datasets on hercules. Can i use dasdinit64 command to create it? or some command else?
The second is from where can i run the unpack procedure as i don't have a z/os system up on hercules.

I have only a standalone ickdsf and a standalone dfsmsdss restore.? My dasd device is 3390-9,original z/os version is 2.2. the hardware is z15.

I need to restore the resident volume and catalog volume to hercules first so that i can ipl my system and restore the rest volumes via JCL.

Thanks again for your kindly and patient guidance.

Hi Shixinlong,

Have a look at wwwunterse, it runs on windows platforms and Linux also



There is a Download button on the web page, which will ask you for some name and email details.

You must not publish the files to any forum or public download, if you wish to tell someone
about wwunterse then please only pass the link

Regards,
Tom

Sorry, I had assumed you had a running system already.

The absolute simplest way to get a driving system up is to use Customized Offerings Driver (COD).? It's a single volume z/OS at V2.4 (or 2.3), that you can IPL direct from a USB drive.? You can order it from ShopZseries and I think there is no cost so long as you already have a mainframe and access to ShopZ. ?

It's a full fledged system, but is only meant to be used to install a new OS when you have a new box that doesn't support your old z/OS, or you have no previous z/OS to start with.? The process is actually jsut IPLing DFDSS and creating the volume, then when you are done, you IPL the single volume system you just created.? From that point you can use it to install your volume copies or install from a z/OSMF installation package.

You could also build your backup with AWSTAPE on your mainframe platform and use that tape for the stand alone install, but COD is way easier.?

There are also unterse products that run on the PC platform which would get you to where you need to be also.