Got something back from IBM, not direct quote, but my summary
If zOS 1.08 and OA20831 applied (PTF UA36918 Y may be sup'd by
UA38734) AND the following patch in your DFSMShsm startup parmlib member
ARCCMDnn (PATCH .MCVT.+433 X'FF'), this may be causing your problem. I
got it WIHTHOUT the patch. This APAR and PATCH allow you to invoke
DFSMSdss in cross-memory mode for all HSM functions except recall. This
code has had many problems and we are recommending to clients to turn this
function off. If you have this patch applied you can turn it off by
putting the following patch in your ARCCMDnn member (PATCH .MCVT.+433
x'00'). You will have to stop and restart DFSMShsm.
IF zos 1.09 APAR is OA23236 PTF UA39499 which creates new Keyword
DSSXMMODE(Y|N) the default is already OFF.
So, Now why this came up for me on 1.08 after UA38734 and no
pacth? Still to come. I am putting in the "UN"PATCH X'00' to see if that
stops the problem in 1.08.
For those of you on 1.09, try DSSXMMODE(Y) at your risk. Just be
ready for irate ops managers asking where all their scratch tapes went.
For Ted MacNeil, I (most) always add an extra zero to releases 0
thru 9 'cuz I hate it when things do not collate sensibly in dsname lists,
members, etc etc. Yeah, I'm excessive compulsive about this kind of
order, but I do not think this will cause much confusion.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
