Dave,
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.
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
If you then look at the actual source for TMSUX2E you will see the
following.
* 00052000
* PLACE USER CODE HERE 00053000 <== this line will be replaced
* 00054000
B RETURN 00055000
SPACE 2 00056000
NEWSTYLE DS 0H 00057000
What IEBUPDTE does is to replace or insert lines based on the line sequence
numbers (column 73-80). Why do this instead of simply replacing the entire
module? Because we (CA-1 support) might be forced to make some changes to
the entry or exit logic, or some USING in the middle of the sample exit and
then you would have to re-write the exit. Using IEBUPDTE with the same
sequence numbers (and we try very hard not to modify those sequence numbers
though accidents do happen) allows an existing exit to be applied, and
re-applied over and over and over again without having to go and re-write
any code. Many clients are running with CA-1 exits that haven't been touched
in many-many years (read decades). So, if you want to insert code starting
at sequence 00053000; then simply have sequence 00053001, 00053002,
00053003, as your sequence numbers in the CL05205 member of PPOPTION. Then,
only those lines would be inserted.
Now, that being said you also need to remember that since we added the new
TMSXTEND utility with r11.0 the need to maintain exits U&E (TMSUX2U and
TMSUX2E) has been eliminated. You are still able to use them, but if you are
able to use TMSXTEND to define and add ranges these exits will be
eliminated.
Lastly, regarding your z/OS 1.7 problems. Normally I have the highest regard
for the folks at Innovation, and am very interested in this intermittant
0C4. Do you have a dump, and have you open'ed a helpdesk issue? I know of no
outstanding 0C4 abends within the product at this time. For z/OS 1.7, at
CA-1 r11.5 you only need QO73756 to be applied. This does correct a 0C4, but
only if using our TMSTPNIT to initialize a tape. No other requirements to
CA-1 r11.5 are known to support either z/OS 1.7 or z/OS 1.8. Are the 0C4
abends in TMSTPNIT?
If you haven't yet open'ed a helpdesk issue for the intermittant 0C4, please
do so. Especially if you have some dump to look at (which I assume you do,
or the folks at Innovation wouldn't be pointing fingers).
Russell Witt
CA-1 Level-2 Support Manager
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of O'Brien, David W. (NIH/CIT) [C]
Sent: Monday, June 11, 2007 9:32 AM
To: [email protected]
Subject: Re: CA-1 install - user exits?
Hi Sam,
Generally speaking I agree that CA-1 runs as designed and Russell is helpful
to users of this list. However since upgrading to Zos 1.7 we have been
experiencing intermittant 0c4 errors which FDR support attributed to CA-1.
Having a question about iebupdte and having CA support refuse to comment on
it, despite the fact that is used in the install doc, is what I found
unacceptable.
Regards,
Dave O'Brien
________________________________
----------------------------------------------------------------------
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
