On Sun, 21 Jun 2009 17:26:57 +0300, Binyamin Dissen wrote:
>On Sun, 21 Jun 2009 14:58:58 +0100 Terry Sambrooks wrote:
>
>:>As to the question of "How, then, does the utility determine DSORG by
>:>opening for input?" My suspicion here would be a combination OPEN,TYPE=J
>:>plus READJFCB. The fact that this is necessary is further evidence that it
>:>is all too easy to corrupt the DSCB whether it is by program, JCL or a
>:>combination of the two.
>
>More likely that an OBTAIN is needed. I don't know if the JFCB would always
>have the information.
>
FWIW, the utility was GIMDTS. And the behavior has changed: it now
operates successfully with SYSUT2 allocated write-only. But I
archived the PMR, in which I reported:
18 *-* RC = BPXWDYN('alloc dd(SYSUT2) pathopts(OWRONLY)' ,
'recfm(F,B) lrecl(80) blksize(6000)' ,
'filedata(TEXT) path(''/dev/fd'stdout''') reuse msg(2)')
>>> "0"
22 *-* address 'ATTCHMVS' 'GIMDTS'
>>> "GIMDTS"
IEC104I 0000000A,user ,STEP1 ,SYSUT2 -000,BPX1OPN ,0079,0562003F
IEC141I 013-C0,IGG0199G,user,STEP1,SYSUT2
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=013 REASON CODE=000000C0
TIME=13.05.23 SEQ=00419 CPU=0000 ASID=003B
PSW AT TIME OF ERROR 075C1000 80ACCA5A ILC 2 INTC 0D
... the error message is not "self-explanatory", and M&C was
little help.
-- gil
----------------------------------------------------------------------
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
