Author |
Message |
Topic: DFSORT FILSZ Ennn Required Accuracy |
twb
Replies: 3
Views: 2126
|
Forum: Utilities Posted: Mon Aug 28, 2017 4:56 pm Subject: DFSORT FILSZ Ennn Required Accuracy |
If I coded FILSZ=Unnn, then I would expect an abend if available storage was insufficient. If I code FILSZ=Ennn, I still expect to fail if I exceed available resources, but I also expect to fail simp ... |
Topic: DFSORT FILSZ Ennn Required Accuracy |
twb
Replies: 3
Views: 2126
|
Forum: Utilities Posted: Mon Aug 28, 2017 2:56 pm Subject: DFSORT FILSZ Ennn Required Accuracy |
Does anyone know how wrong a DFSORT FILSZ=Ennn value can be before the sort abends? Is it a number, a percentage, something else? Are the upper and lower limits the same?
The manuals recommend a ... |
Topic: How to Avoid Replacing Existing Dataset with DISP=(NEW ? |
twb
Replies: 22
Views: 17219
|
Forum: Job Control Language(JCL) Posted: Tue Jul 11, 2006 10:47 am Subject: DISP=(NEW for Existing |
"Dedpending on what is coded in the ALLOCxx member of PARMLIB depends on what course of action will taken"
/********************************************************************/
/* ... |
Topic: How to Avoid Replacing Existing Dataset with DISP=(NEW ? |
twb
Replies: 22
Views: 17219
|
Forum: Job Control Language(JCL) Posted: Thu Jul 06, 2006 5:48 pm Subject: How to Avoid Replacing Existing Dataset with DISP=(NEW ? |
or type TSO ISRDDN ; PARMLIB
Cool feature.
Unfortunately, I do not have TSS READ access to SYS1.PARMLIB (I'll probably get a message from my VP asking why he is getting all of these TSS violat ... |
Topic: How to Avoid Replacing Existing Dataset with DISP=(NEW ? |
twb
Replies: 22
Views: 17219
|
Forum: Job Control Language(JCL) Posted: Wed Jul 05, 2006 2:18 pm Subject: How to Avoid Replacing Existing Dataset with DISP=(NEW ? |
Long ago, if one coded DISP=(NEW,CATLG,DELETE) for an existing dataset, the job failed. It seems now (with SMS), DISP=(NEW,CATLG,DELETE) will uncatalog an existing dataset and allocate and catalog a ... |
|