--- On Thu, 3/19/09, Rick Fochtman <[email protected]> wrote:
---------------SNIP-------------------------
> Putting the DEST= information in the proc is fine for 3-4
> destinations. When it gets to several thousand, your procs
> get to be rather large, and size, in my experience, leads to
> confusion and errors. Not to mention various limits that
> might be imposed by z/OS or JES2/JES3.
>
> PDS8.x, STARTOOL or my freebee PDSSCAN utility from the
> CBTTAPE sight can be used to find references to parmlibs or
> proclibs, or members therein, to help find all the
> references when changes are made. There are also other
> tools, I'm sure, that will also accomplish the same tasks.
>
-----------SNIP------------------------
Yes you are right there are a few tools out there to do this. the side issue I
think is that this works with with a few destinations. A LONG time ago and far
far away a company I worked for had symbolics for just about everything in a
proc and it was at times confusing, but surprisingly nice to have when its 0000
something and you are trying to get something fixed fast. At first I was
against the idea but working with it a little it did have its advantages. I
will leave it up to the person reading this as to whether it is a good idea or
not. THE KISS methodology works here as well, as I can see both sides.
The thing to remember though for thoroughness if you go the route of a card
image way is that you should keep it in the same library (PDS or PDSe) as the
procedure. Then scans will pick it up and there will not be any surprises.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
