I've been told by Powers That Be that this line of development is redundant
& that a different solution has been independently developed elsewhere in
the company. (*sigh* - 'twas ever thus)
But I'm still interested in discovering what I'm doing wrong.
To that end, here's the jobstream I'm using, in the hope that someone can
pin-point the problem:
(I do so hope that this comes through without being reformatted by various
e-mail servers...)

<job statement>
//RUNREXX  EXEC PGM=IKJEFT01
//SYSTSPRT DD   SYSOUT=*
//ISPMLIB  DD   DSN=ISP.SISPMENU,DISP=SHR
//ISPPLIB  DD   DSN=ISP.SISPPENU,DISP=SHR
//ISPSLIB  DD   DSN=ISP.SISPSLIB,DISP=SHR
//ISPTLIB  DD   DSN=ISP.SISPTENU,DISP=SHR
//ISPPROF  DD   DISP=(NEW,PASS),SPACE=(TRK,(1,1,1)),
//          DSORG=PO,RECFM=FB,BLKSIZE=27920,LRECL=80
//SYSEXEC  DD   DSN=<my SYSEXEC PDS>,DISP=SHR
//SYSTSIN  DD   *
ISPSTART CMD(STRIPNOS <input pds dsname>)

and here is the first part of the STRIPNOS REXX program - such as it is
right now:

/* REXX to strip line numbers in place */
/* trace i */
parse source
arg dataset
say "PDS to be modified:" dataset
"ISPEXEC CONTROL ERRORS RETURN"
"ISREDIT MACRO"
edMac = rc
"ISPEXEC CONTROL ERRORS CANCEL"
 (followed by the rest of Andy's solution, currently all commented out)


 ** Mark well that phrase 'as it is right now'. As I've already detailed,
I've tried many different variants of this code to try and get something
working, with a notable lack of success

Regards
Sean

On Mon, 11 Jan 2021 at 20:03, Lennie Dymoke-Bradshaw <
[email protected]> wrote:

> Apologies, you wanted to do a PDS member.
>
> //EDIT     EXEC  PGM=IKJEFT01
> //SYSTSPRT  DD   SYSOUT=*
> //SYSTSIN   DD   *
>    EDIT 'LEN.X.TEST.NVSAM.PDS(#ASM)' DATA
>    LIST
>    UNNUM
>    LIST
>    END SAVE
> /*
> //
>
> Note the LIST commands are optional.
> Lennie
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of Lennie Dymoke-Bradshaw
> Sent: 11 January 2021 19:48
> To: [email protected]
> Subject: Re: Request for help with removing sequence numbers from PDS
> members
>
> Here's how to do it using TSO EDIT.
>
> //EDIT     EXEC  PGM=IKJEFT01
> //SYSTSPRT  DD   SYSOUT=*
> //SYSTSIN   DD   *
>    EDIT 'LEN.X.TEST.NVSAM.FB80' DATA
>    LIST
>    UNNUM
>    LIST
>    END SAVE
> /*
> //
>
> Lennie
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of Lennie Bradshaw
> Sent: 11 January 2021 12:26
> To: [email protected]
> Subject: Re: Request for help with removing sequence numbers from PDS
> members
>
> 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
>
> ----------------------------------------------------------------------
> 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