[H390-MVS] How to install recv370?

['Matthew R. Wilson' [e-mail] [H390-MVS]]

Howdy,

Probably a really basic question, but I'm trying to figure out MVS
basics from scratch. I've played around with TK4-, but am now trying
to understand a bit more of the 'under the hood' mechanics, so I've
followed Jay Moseley's great tutorial for installing MVS and now have
a basic system up and running.

Next I'd like to install recv370 to be able to deal with XMIT
packages. I've successfully installed IND$FILE so I can get the XMIT
files up to my system, but once there I need recv370 to receive them.

I've downloaded the tape it's supposed to be on from
http://cbttape.org/~jmorrison/mvs38j/index.html, but I'm stuck as to
what I'm supposed to do with that.

From searching, it sounds like that tape has datasets copied to it
with IEBCOPY. Using hetmap to try to determine something about the
contents of the tape, I see:

---
$ hetmap xv0005-beta02.het
Hercules HET and AWS tape map program Version 3.13
(c)Copyright 1999-2015 by Roger Bowler, Jan Jaeger, and others
---------------------
Filename : xv0005-beta02.het
---------------------
Label : 'VOL1'
Volume Serial : 'XV0005'
Improved Data Rec. : ' '
Owner Code : 'N9GTM '
---------------------
Label : 'HDR1'
Dataset ID : '.V0005.BETA02.CBT'
Volume Serial : 'XV0005'
....
---

I was hoping that "dataset ID" would be a clue as to the dataset on the tape.

I put together the following JCL, but I know it's missing something
and IEBCOPY abends with S813, which a google search says that means
the data set name in the JCL wasn't on the tape.

Here's the JCL I've cobbled together:

//TPLOAD02 JOB (SYS),'LOAD TAPE',CLASS=S,MSGCLASS=A
//STEP1 EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=V0005.BETA02.CBT,DISP=(OLD,KEEP),
// UNIT=TAPE,VOL=SER=XV0005,LABEL=1
//SYSUT2 DD DSN=MWILSON.FOO,DISP=(,CATLG),
// VOL=SER=PUB001,UNIT=SYSDA,SPACE=(CYL,(2,0,20),RLSE)
//SYSIN DD DUMMY
//

So... a couple of questions:

1. Am I on the right track in identifying the abend code as indicating
my DSN is wrong? If so, how do I know what DSN to use from a tape that
I know nothing about other? Overall, is my SYSUT1 DD to point to the
tape anywhere close to being correct?

2. Even if I correctly define SYSUT1, I feel like my SYSUT2 DD for the
output is missing the DCB section...again, without knowing anything
about the source tape, how do I know how to set up my target dataset?

Thank you,
Matthew

[[e-mail] [H390-MVS]]

... okay, quick follow-up: I now discovered that recv370 is available in the compiler pack DASD that Jay Moseley includes in his system installation instructions under SYSC.LINKLIB.

But, for the purposes of learning, if that weren't the case, I'd still appreciate pointers to where I can learn about how to handle my original questions.

Thanks,
Matthew

[Dave Kreiss [e-mail] [H390-MVS]]

Mathew

The tape label has a limit of 17 characters for the dataset name so only the last 17 characters are stored in the tape label. If you look carefully at the data set name on the tape it starts with a period. Simple trick is to add any high level qualifier to the DSN parameter like DSN=HERC01.V0005.BETA02.CBT. The system matches only on last 17 characters.

And you are correct abend S813 is an error caused by OPEN (SVC 13) on a mismatch between tape label and your DSN in this case.

Dave

[[e-mail] [H390-MVS]]

The tape label has a limit of 17 characters for the dataset name [...]
Simple trick is to add any high level qualifier to the DSN parameter

Ah, thank you Dave! That did the trick. I ended up having to increase the SPACE parameters in my JCL, but otherwise adding extra characters to the beginning of the DSN worked and the PDS is now restored to disk.

Thanks again,
Matthew