Thanks Don, will pass this on to the maintainer, much obliged.

cheers,
Peter

On Fri, 18 Oct 2019 06:42:00 -0400, Don Poitras <[email protected]> wrote:

>The current CBT 183 has a fix for this. See SWAREQ22 (it was z/OS 2.2
>where the breaking change was introduced.) It works on pre-2.2 as
>well, so there's no need to hold on to the original SWAREQ.
>
>In article <[email protected]> you wrote:
>> Bad form to reply to myself, but I should have added this.
>> This gave me a hint:  
>> https://www.ibm.com/support/pages/abend0c4-or-other-problems-retrieving-dataset-names-cobol
>> This gave me the answer:  
>> https://www-01.ibm.com/support/docview.wss?uid=swg1PI58751
>> We're moving to z/OS 2.3 which was the source of the environment change.
>> best regards,
>> Peter
>> On Thu, 17 Oct 2019 22:34:44 -0500, Peter Bishop <[email protected]> wrote:
>> >Hi,
>> >
>> >in case anyone else is having failures using the old SWAREQ REXX that is 
>> >floating around (originally from Gilbert Saint Flour), in our case as part 
>> >of a REXX that compares catalogues via the IGGCSI00 program and various 
>> >other methods, you will need to change your job class to SWA=BELOW to get 
>> >it to work.
>> >
>> >After I did that, the mysterious errors relating to rubbish dataset names 
>> >that SWAREQ was returning vanished, and normal processing resumed.
>> >
>> >Hope this saves some time for others.
>> >
>> >best regards,
>> >Peter
>
>
>--
>Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
>[email protected]           (919) 531-5637                Cary, NC 27513
>
>----------------------------------------------------------------------
>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