94
© 2002. Xephon UK telephone 01635 33848, fax 01635 38345. USA telephone (303) 410 9344, fax (303) 438 0290.
ISPF SCREENS – THE CASE FOR NEW ONES
Let’s face it: IBM doesn’t appear to have put a whole lot of thought
or planning into its ISPF screens for RACF. Installation data input is
free-format, so you’ve got to count how far along you are if you want
to have the List User, List Group, List Dataset, etc looking correct.
And IBM, while we’re at it, what possessed you to change the
installation data format for all of these items? I mean, 45 characters per
line for groups, 50 for users, 79 for datasets and general resource
profiles, etc – a little standardization would’ve been more convenient.
But be that as it may, we’re stuck with IBM’s ISPF screens. Or are we?
If your Technical Support team is of sufficient quality (and I’m betting
that it is) and of sufficient intestinal fortitude, new ISPF screens can
be designed which will allow for better, more logical, and more
efficient input of RACF data by your administrative team. This can
keep your installation data formats up to date without having to resort
to JCL every time you want to add or change a user, group, or dataset
profile.
I’m not going to go into the specific coding requirements of the ISPF
screens here for a variety of reasons. First and foremost, I’m not a
programmer capable of creating such code. Second, when it comes
right down to it, each site must come up with the screens which will
fit their desired use of the installation data field – formatting and
content issues are quite individual and must conform to your own
security requirements. Finally, Technical Support people love a good
challenge. Developing new ISPF screens for RACF, with sufficient
controls to ensure security of data and continuity of naming standards,
will give them quite a lot of enjoyment.
“HERE’S YOUR LPAR – WHERE ARE THE DOUGHNUTS?”
Well, you’ve got the JCL all neat and tidy in your text files on your PC.
You’ve developed all your group structures, recreated your CICS
region profiles, copied the dataset profiles, made all new user IDs, all
tucked away in ASCII character sets on your hard drive. You’ve spent
a lot of time and effort getting this ready. But it’s not doing you much
good in a Windows environment. You need a test LPAR to do the
initial builds and tests.
Kommentare zu diesen Handbüchern