I remember when I installed this that I had a lot of trouble with the ptf(s). That was due to the fact that one of the IGG modules that had to get restored had a usermod (for CA-DISK) on it. I don't remember if that module was even touched by the ptf. Restoring that usermod was a nightmare - SMPE eventually told me that it could not figure out any relationships for restore anymore and I should do it myself. I ended up accepting a just installed new PTF that fixed some PE. After that, SMP/E was able to do the restore check with CC=0. Out came about 200 ptfs. I applied the crypto stuff, then reapplied all the rest of the ptfs. And the usermod. (And I had done accept before I started that refresh.)
While it was nice to have the functionality rolled down to 2.1, the complexity was staggering and I didn't like having it forced upon me in the service stream. I was tempted to just leave the crypto ptf(s) out and wait for 2.3 which would have it in the base. I just reiterate what everybody else already told you: Backup your complete SMP/E environment including the target and DLIBs before you do any apply of that ptf. And then do real thorough testing of just about everything DFSMS. The crypto function is pretty pervasive (as it should be). Barbara Nitz ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
