The only problem I’ve had with SMS this was years ago that it kept extending a 
data set over 137 volumes and it took a little while to get that archived off 
because they didn’t want it deleted so SMS is a good thing but it can also bite 
you



Sent from my iPhone

No one said I could type with one thumb 

> On Aug 2, 2025, at 10:01, Jack Zukt 
> <[email protected]> wrote:
> 
> Hi,
> SMS can do a lot based on your dataset name but that does not mean that the
> result is what you need or want. When coding Rexx I usually do the
> allocations from within instead of relying in the JCL. However, be it with
> JCL, be it from within the exec, I always specify the RECFM, the LRECL, the
> space units and the amount to allocate. I just leave to SMS to decide where
> to allocate it.
> 
> Regards
> Jack
> 
>> On Sat, Aug 2, 2025, 15:13 Clement Clarke <
>> [email protected]> wrote:
>> 
>> I am writing a simple EXEC command so that running Z/OS programs can be
>> executed in much the same way that Linux and Windows programs are
>> executed.  For example:
>> 
>>     EXEC PAYROLL1 Payroll.Input.dets Payroll.validated.dets;
>> 
>> where the program Payroll1  inputs and outputs a file after validating the
>> transactions.
>> 
>> ----------------
>> I asked Google's AI (gemini.Google.com) the following question:
>> 
>> "These days, with SMS what does a typical JCL statement look like for
>> allocating new data sets? Does one code Space, Unit and Recfm, or leave it
>> off the JCL and rely on SMS?"
>> 
>> Google gave a long answer (try it yourself?) but in essence it said:
>> 
>> "With SMS, the JCL becomes much cleaner. The system handles the allocation
>> details based on its policy. A typical DD statement for a new dataset now
>> looks more like this:
>> 
>> "Code snippet
>> 
>> //NEWDS DD DSN=MY.TEST.FILE,
>> //         DISP=(NEW,CATLG,DELETE)
>> 
>> ----------------------------
>> 
>> Is this correct, or does most JCL still have SPACE etc coded for new data
>> sets?
>> 
>> Many thanks,
>> 
>> Clem Clarke
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN

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

Reply via email to