RE: Bulk update of CL source fil

Another tip that was mentioned a little while back in a different thread.  If
you create a source file with an index (CRTSRCPF ACCPTH(*KEYED) ), then you
can add records to the file, using the sequence number to position where you
want new source statements to appear within the existing source.  Next time
you call the member up in SEU, the source statements you added to the end of
the physical source file will appear by sequence number.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
D.Bale@Handleman.com
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-------------------------- Original Message --------------------------
You might be able to automate at least a piece of the code maintenance.  If
you create a source member NEWCODE in QGPL/QCLSRC:

9999.00 /*  these are important lines of code */
9999.01              MONMSG     MSGID(CPF1002) EXEC(DO)  /*whatever code you
really need*/
9999.02              DLYJOB     DLY(120)
9999.03              GOTO       CMDLBL(ALC)
9999.04 /*  this is where they end            */

and save it on the way out, renumbering the source statements from 9999.00
in increments of .01 you can easily drop it in to your modified members
using PDM.  Just create a PDM User-Defined Option like this:

XX    CPYF QGPL/QCLSRC &L/&F NEWCODE &N MBROPT(*ADD)

to copy the added lines to the bottom of each source member requiring the
changes.  It might be easier to copy the lines in then pull the members up
in SEU to move the lines to where they need to go.

I've done this in the past when faced with a similar chore.  I pulled up my
PDM source member list on two 5250 sessions.  On one session I ran the 25 to
scan and change lines, then as I exit each member I would flop over to the
other session, copy in the added lines using the user defined option, edit,
drop to the bottom of the member and move lines around.

-----Original Message-----
From: Richard Reeve [mailto:richreeve@yahoo.com]
Sent: Wednesday, April 04, 2001 8:27 AM
To: MIDRANGE-L@midrange.com
Subject: Re: Bulk update of CL source file


DCL will need to be added.

--- "James W. Kilgore" <eMail@James-W-Kilgore.com>
wrote:
> Just a stupid question ...
>
> Sure you can scan/replace, but does each member need
> to be visited to
> add a DCL For the variable or is it going to be
> replaced with *LIBL?
>
> Mike Naughton wrote:
> >
> > I agree this wouldn't be too hard to write.
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to
> MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to
> MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list
> owner/operator: david@midrange.com
> +---


=====


__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---