W dniu 2016-04-29 o 22:30, Paul Gilmartin pisze:
On 2016-04-29, at 09:58, R.S. wrote:
That deserves an SR.  Works in JCL; works everywhere else.  The statement is
patently false.
No, it isn't. MOD is not allowed for *member* od PDS or PDSE.
MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DELETE

Try IEBGENER  //SYSUT2 DD DSN=HLQ.SOME.PO(MEMBER),DISP=(MOD,CATLG)

My test job step:
//STEP  EXEC  PGM=IEBGENER
//SYSUT2 DD DSN=&SYSUID..SOME.PO(MEMBER),DISP=(MOD,CATLG),
//  UNIT=SYSALLDA,SPACE=(500,(500,,5))
//SYSUT1 DD *
    Test Data
//SYSPRINT  DD  SYSOUT=(,)
//SYSIN     DD  *
//*

And log output:

14.10.00 JOB00158  -                                      -----TIMINGS 
(MINS.)------                          -----PAGING COUNTS----
14.10.00 JOB00158  -STEPNAME PROCSTEP    RC   EXCP   CONN       TCB       SRB  
CLOCK          SERV  WORKLOAD  PAGE  SWAP   VIO SWAPS
14.10.00 JOB00158  -STEP                 00     47     22       .00       .00   
  .0           116  BATCH        0     0     0     0
14.10.00 JOB00158  IEF404I PDSMOD - ENDED - TIME=14.10.00
14.10.00 JOB00158  -PDSMOD   ENDED.  NAME-Paul Gilmartin       TOTAL TCB CPU 
TIME=      .00 TOTAL ELAPSED TIME=    .0
14.10.00 JOB00158  $HASP395 PDSMOD   ENDED - RC=0000

Works for me.
You are right. Please rerun the job. I bet you'll get SB214 abend.
My description was innacurate (I'm sorry for that!), however I meant MOD as appending existing memebr. It is not possible. BTW: simple JCL workaound is to copy member to a PS, append it and then overwrite the member (overwrite is possible, despite of PDS vs PDSE internal processing, I mean what enduser see).

Regarding SDSF, the forbiden DISP and DSORG combination can be result of SDSF dialog logic, not the access method restriction.

Unfortunately, it is possible to overwrite a member by mistake using the dialog

Regards
--
Radoslaw Skorupka
Lodz, Poland






--
Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku 
przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie 
jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem 
niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania 
adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by 
karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie 
zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo 
wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: [email protected]
Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru 
Sdowego, nr rejestru przedsibiorców KRS 0000025237, NIP: 526-021-50-88. 
Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci 
wpacony) wynosi 168.955.696 zotych.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to