Matt,

I did something similar.  Ran an APPLY but forgot to point to my SMP/E Root and 
HFS files.  I did corrupt my live UNIX files.  Fortunately it was not severe 
enough to fix it that day.  We really do not use UNIX on the mainframe that 
much.  Only vendor required stuff.  We have no applications.  However, I did 
have to fix it that weekend by creating a new UNIX set of libraries and IPL'ing 
that system with the new set.

If you can identify all of the hfs or zfs files that were updated at the point 
of failure, you might be able to copy the information that was updated from a 
different systems UNIX environment if they are at the same level.  Otherwise 
you will need to build a new HFS or zFS file with the correct level of 
maintanence.

Maybe someone else might have a better idea.  But that is what I had to do.

Lizette



>Subject: SMPE Help
>
>Need some direction on how to correct this self inflicted wound on my z1.9 
>sand box system. I ran an smp apply for RSU maintenance and forgot to mount my 
>alternate HFS files under /service before starting. Below are some messages 
>from DD BPXPRINT and the first error msg in SMPOUT. I believe the BPX error I 
>got was a space issue but then I realized I forgot to mount the HFS files 
>under /service. 
> 
>Has my primary HFS files been compromised? Where do I go from here? Thanks Matt
> 
> 
>1BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000254.                              
>                                                      
> BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO TEXT HFS 
> FILE /usr/lpp/cpo/IBM/CPOCPREG.                          
>1BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000255.                              
>                                                      
> BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO TEXT HFS 
> FILE /usr/lpp/cpo/IBM/CPOCPSCH.                          
>1BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000256.                              
>                                                      
> BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO TEXT HFS 
> FILE /usr/lpp/cpo/IBM/CPOENV.                            
>1BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000257.                              
>                                                      
> BPXF150I MVS DATA SET WITH DDNAME SYSUT1 SUCCESSFULLY COPIED INTO BINARY HFS 
> FILE /usr/lpp/cpo/IBM/CPOHWMC.                         
>1BPXF151I BPXCOPY WAS INVOKED FOR HEAD ID 000258.                              
>                                                      
> BPXF106E RETURN CODE 00000085, REASON CODE 5B4FC005.  AN ERROR OCCURRED 
> DURING THE WRITING TO HFS FILE /usr/lpp/cpo/IBM/CPOS 
> 
> 
> 
>GIM69168E ** HFSCOPY PROCESSING TO THE SCPOHFS LIBRARY FAILED FOR HFS CPOSETUP 
>             IN SYSMOD UA39307. THE RETURN CODE (12) EXCEEDED THE ALLOWABLE    
>             VALUE. DATE 09.103 - TIME 15:46:53 - SEQUENCE NUMBER 000258.      
>GIM30216I    APPLY PROCESSING FAILED FOR SYSMOD UA39307. SYSTEM UTILITY        
>             PROCESSING FAILED FOR AN ELEMENT IN UA39307.                      
> 

----------------------------------------------------------------------
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

Reply via email to