10.Verify the job output to ensure that the IOCDS was written without error and to the correct IOCDS. You receive the following messages: 

ICP057I IOCP JOB WIOCP SUCCESSFUL. LEVEL A3 IOCDS REPLACED. Sev Msgid Message Text  I CBDA674I IOCP successfully completed for A3.ARIES. 

11.Now if you return to HCD option 2.11 and view the IOCDS, notice that the SNA Address remains at IBM390PS.CETUS  (Figure 5-15). 

Processor Cluster List Row 1 of 4 Command ===> _______________________________________________ Scroll ===> CSR Select one or more CPCs, then press Enter. --------------CPC-------------- IODF / SNA Address Type Model Processor ID # IBM390PS.ARIES 8561 T01 _ IBM390PS.CETUS 3906 M04 ARIES _ IBM390PS.LEPUS 2965 N20 LEPUS _ IBM390PS.MUSCA 3907 ZR1 MUSCA 

12.Also, when you select IBM390PS.CETUS , notice that IOCDS A3 (to which you wrote the upgrade IODF) has a status of Invalid  (Figure 5-16).This error occurs because you specified Yes  for the Write IOCDS in preparation for upgrade field, and the IOCDS contains IOCP statements and code relevant only for a 8561 processor. 

The status switches when this processor is upgraded to a 8561. The 3906 IOCDS status changes to Alternate  and the 8561 IOCDSs changes to Invalid . 

Tip:  Generally, rewrite the IOCDS written in preparation for the upgrade at your earliest convenience. Subsequent MESs might cause an IOCDS written in preparation for an upgrade to become invalid. 

IOCDS List Row 1 of 4 More: > Command ===> _______________________________________________ Scroll ===> CSR Select one or a group of IOCDSs, then press Enter. -----Token Match----- Write / IOCDS Name Type Status IOCDS/HSA IOCDS/Proc. Protect _ A0.ARIES IODF65 LPAR Alternate No No No _ A1.ARIES IODF66 LPAR POR Yes No Yes-POR _ A2.ARIES IODF62 LPAR Alternate No No No _ A3.ARIES IODF67 LPAR Invalid No Yes No ******************************* Bottom of data ******************************* 

