Please ignore my last...
yep - it was one of those 'simple basic' things.
I had a DD statement to define a temporary ISPPROF, where I'd coded
'DSORG=PS' instead of 'PO'.
(seems strange that you can code 'SPACE=(TRK,(1,1,1))' along with
'DSORG=PS' without getting at least a warning...)
Regards
Sean

On Mon, 11 Jan 2021 at 15:37, Sean Gleann <[email protected]> wrote:

> Many thanks to all who responded.
> I opted to adapt and (try to) use the REXX that Andy Styles gave, but I'm
> tripping up over something that has to be one of those 'simple, basic'
> things.
> The "ISPEXEC CONTROL ERRORS RETURN" command gives me RC(20) as a result.
> I think I've got to use an 'ADDRESS ISPEXEC' command or something like
> that at the start of the REXX, but attempts at variants of this give the
> same result.
> Any clues, anyone... please?
>
> Regards
> Sean
>
>
> On Mon, 11 Jan 2021 at 12:26, Lennie Bradshaw <
> [email protected]> wrote:
>
>> How about TSO EDIT (yes TSO, not ISPF) in batch.
>> Lennie
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List <[email protected]> On Behalf
>> Of R.S.
>> Sent: 11 January 2021 10:21
>> To: [email protected]
>> Subject: Re: Request for help with removing sequence numbers from PDS
>> members
>>
>> W dniu 11.01.2021 o 10:05, Sean Gleann pisze:
>> > This has almost certainly cropped up before but try as I might, I can't
>> > spot anything obvious in the archives.
>> >
>> > I have a need to strip sequence numbers from members in a PDS or PDSE.
>> > The input PDS(E) has DCB characteristics of REFCM=FB,LRECL-80, and
>> contains
>> > an unknown number of members. Of those members, some will have records
>> with
>> > 'old data' in character positions 73-80 (that is - sequence numbers, or
>> > whatever remains of them).
>> > I want to be able to copy this input PDS(E) to a new one with the same
>> DCB
>> > info, but all records in all members must have spaces in positions
>> 73-80.
>> >
>> > I thought that ICETOOL might be able to do this but as far as I can see,
>> > ICETOOL needs to be told which member names to process. That
>> information is
>> > readily available while developing and testing a solution, but not when
>> the
>> > result is used in a more general scenario.
>> >
>> > Can anyone point me at some sort of solution that I might adapt, please?
>> > Perhaps there is something on the CBT tape that might help...
>>
>> I don't know any tool, but I have some idea how to do it.
>> Use REXX script.
>> It's quite simple to get member list and do somethin in a loop until
>> last member is processed.
>> What to do?
>> Again, I don't know any tool, however it could be feasible to use
>> IEBGENER with non-empty SYSIN, ICEMAN, or TSO EDIT, or ISPF EDIT, or
>> something else.
>> Caution: things are simple when you just want to replace position 73-80
>> despite of its actual content, that means without checking it.
>>
>> HTH
>>
>> --
>> Radoslaw Skorupka
>> Lodz, Poland
>>
>>
>>
>>
>>
>> ======================================================================
>>
>> Jeśli nie jesteś adresatem tej wiadomości:
>>
>> - powiadom nas o tym w mailu zwrotnym (dziękujemy!),
>> - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub
>> zapisałeś na dysku).
>> Wiadomość ta może zawierać chronione prawem informacje, które może
>> wykorzystać tylko adresat. Przypominamy, że każdy, kto rozpowszechnia
>> (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania,
>> narusza prawo i może podlegać karze.
>>
>> mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,
>> www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st. Warszawy
>> XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237, NIP:
>> 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
>> 01.01.2020 r. wynosi 169.401.468 złotych.
>>
>> Jesteśmy administratorem twoich danych osobowych, które podałeś w związku
>> z prowadzoną z nami korespondencją. Przetwarzamy te dane dla celów, które
>> wynikają z przedmiotu korespondencji, w tym związanych z prowadzoną
>> działalnością bankową.
>> Więcej informacji o tym jak chroniony i przetwarzamy dane osobowe
>> znajdziesz w Pakietach RODO (w wersji polskiej i angielskiej), które są na
>> www.mbank.pl/rodo
>>
>>
>> If you are not the addressee of this message:
>>
>> - let us know by replying to this e-mail (thank you!),
>> - delete this message permanently (including all the copies which you
>> have printed out or saved).
>> This message may contain legally protected information, which may be used
>> exclusively by the addressee.Please be reminded that anyone who
>> disseminates (copies, distributes) this message or takes any similar
>> action, violates the law and may be penalised.
>>
>> mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850
>> Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the
>> Capital City of Warsaw, 12th Commercial Division of the National Court
>> Register, KRS 0000025237, NIP: 526-021-50-88. Fully paid-up share capital
>> amounting to PLN 169.401.468 as at 1 January 2020.
>>
>> We are the controller of your personal data, which you provided in
>> connection with correspondence with us. We process your data for purposes
>> resulting from the subject of correspondence, including those related to
>> the banking services.
>> More information on how we protect and process personal data can be found
>> in the GDPR Packages (in English and Polish), which are on
>> www.mbank.pl/rodo.
>>
>> ----------------------------------------------------------------------
>> 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