I don't think the problem is a generated or temporary dataset name but may
be with the way you coded your HSC definitions.
Try coding your HSC TAPEREQ parms adding .** as follows:
TAPEREQ DSN(PRODSTN.BFS.**) MEDIA(LONG)
You probably have something like this which looks right but isn't:
TAPEREQ DSN(PRODSTN.BFS) MEDIA(LONG)
I ran into a problem which sounds like yours, basically it looked like HSC
wasn't picking up my
TAPEREQ parm and standard tape was mounted. According to the HSC systems
reference a dataset name specified as A.B.** would be a match for datasets
named A.B, A.B.C,
A.B.C.D, A.B.C.D.E, and so forth.
You will also need a VOLATTR Statement to define a volser range as "long"
you probably have done. Ours is as follows:
VOLATTR SER(070000-095480) MEDIA(LONG) RECTECH(36)
If you have any more questions drop me a line.
Niagara Mohawk Power Corp
jphinney AT HUMANA DOT COM
12/04/97 12:51 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Jeffrey P Connor)
Subject: ADSM on MVS
We have a software pkg called HSC that runs on MVS and manages tapes. We
want to use extended tapes for ADSM. You can tell HSC to use extended
tapes for all tapes with a particular dataset name (in our case,
PRODSTN.BFS). HSC doesn't see that dataset name, though, apparently it's
seeing a temporary dataset name that is used prior to the actual name... so
THAT's the name we need to key off of. Does anyone know what that
temporary name is? Someone had opened up a problem record with HSC and
ADSM, and indicated they got around it by specifying ADSM.* .* or
something along those lines. Does ADSM use the started task name in
that temporary name?
If you do know what the temporary name is, do you know if it's the same
name for all storage pools?
JPHINNEY AT HUMANA DOT COM