Hi Willie, its not as simple as getting it recalled to the same volume. I believe it's still the case that at jes startup it maps the dataset extents so you would need to get it back to exactly the same place(s) on the pack. The best solution is to make all your jes proclibs non migrateable. A simple alter mgmtclas to something suitable will do the job.
Dave *********************************************************************************************** >Good Day Readers, >Several jobs are failing due to the following : >IEC143I 213-2C,IFG0194D,JES2,JES2,SYS00035-0009,9987,SMTP01,SYS2.HESP.BPROCLIB >IEF196I IEC143I 213-2C,IFG0194D,JES2,JES2,SYS00035-0009,9987,SMTP01, >IEF196I SYS2.HESP.BPROCLIB >$HASP307 HESPD01 UNABLE TO OPEN PROC02 >IEFC452I HESPD01 - JOB NOT RUN - JCL ERROR >The problem was caused by the library which was migrated by HSM was recalled >to another volume - SMTP03. The >volumes in this Storage Group are SMS >managed. >I was able to get our MVS support folks to refresh the JES2 proc which >rectified the problem (jobs were rerun >successsfully). >My question is should a problem of this nature occur again (pds migrated) how >can I force HSM to recall the dsn to the >original volume? In this case the >dsn was recalled to another volume other than the orginal. >Thanks. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN