Almost sounds like there's a spurious ISFPARMS in LNKLST or LOGON proc. IRSDDN should ferret it out. In a message dated 4/10/2016 6:18:50 P.M. Central Daylight Time, [email protected] writes:
Just too crazy. It's behaving like an old version. Removed our file name from ISFPRMxx, then it wanted ancient default ISF.HASPINDX. Put in a new name and created one with that name. Now LOG works, but ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
