On Jun 13, 2007, at 11:35 AM, Paul Gilmartin wrote:
On Tue, 12 Jun 2007 06:55:29 -0500, Russell Witt wrote:
The entire question of how well should we document IBM utilities and
procedures was discussed just today regarding GDG's. We have some
utilities
(such as TMSCOPY to backup the TMC) were we recommend creating
GDG's to keep
some number of backup copies. It was asked if we should give
examples of how
to define GDG's in our manuals for those system-programmers that
have never
defined a GDG. This morning, I stood on the "NO" side but am
starting to
wonder if that was correct.
Stick to your knitting. As an example, it's tedious how the Rexx RM
repeatedly steps outside its jurisdiction to document the syntax of
TSO commands.
To answer your question about IEBUPDTE; to apply the CL05205
USERMOD you
concatenate two members together. Barry sent the CL05205S member
from our
PPOPTION PDS which is the SMP/e control statements; you also have the
CL05205 member of PPOPTION. By default, the CL05205 member
contains the
following IEBUPDTE control statements;
./ CHANGE NAME=TMSUX2E
SSI=CL05205 CL05205 00038000
* PLACE USER CODE HERE CL05205 00053000 <== this will
replace
the existing line
This appears to be a skeleton, to be customized by the customer. I'd
suggest a few things when a supplier does this sort of thing:
o Supply a couple lines of context, before and after, so the customer
can readily spot what ISPF/PDF autonumbering does, and perhaps
to guide ISPF concerning what numbers to use:
./ CHANGE NAME=TMSUX2E
SSI=CL05205 00038000
* 00052000
* PLACE USER CODE HERE 00053000 <== this line will be replaced
* 00054000
o Given ISPF's technique of using 79-80, this only allows 19 lines of
insertions before a line number collision happens. I'd suggest
that the initial development (too late now) insert several dozen
dummy lines; renumber the file, then delete the dummies to leave a
wide number gap.
Gil,
Its an idea but a suggestion might be in order here. Wouldn't it be a
little clearer if comments were inserted (perhaps in an asterisks in
a box format saying inset code below this box.
Of course there are many ways to do this my suggestion is a common
sense one I believe, but there are others. I personally find it hard
to believe that a typical sysprog would not know about IEBUPDTE so a
guiding hand in this area is a little condescending.
Ed
----------------------------------------------------------------------
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
