In the general scheme of things defaults in IEASYSxx are LNKAUTH=LNKLST and for CSVLLAxx -LNKLST- And with no parms a FREEZE is done on all LNKLST. Guess I could see where updates could get out of SYNC. >From !.13 Init and Tuning ref.: <--- quote ---> -LNKLST- can be used to designate a list of data sets for this parameter, which is derived from all active LNKLST sets. When specified, LLA builds this list for you as part of its normal processing. It is a shorthand way to identify all of the data sets in the LNKLST instead of listing each of them using (-LNKLST-, non-LNKLST libname1, non-LNKLST libname2). As an example, specifying FREEZE (-LNKLST-) directs LLA to set each of the data sets in the LNKLST concatenations list in FREEZE mode. (LLA provides directories from the saved information in LLA storage for requests via JOBLIB, STEPLIB, or TASKLIB.) Specifying NOFREEZE (-LNKLST-) directs LLA to manage each of the data sets (in the LNKLST concatenations list) in NOFREEZE mode, whenever the data set is accessed outside of the LNKLST. That is, LLA provides directories by doing I/O to the DASD storage for these data sets specified via JOBLIB, STEPLIB, or TASKLIB. However, references to members via any active LNKLST concatenation are always provided from LLA storage, so NOFREEZE does not affect that request. <---end quote ---> In a message dated 5/29/2014 9:51:14 A.M. Central Daylight Time, [email protected] writes:
It has already been stated, correctly, that LLA has nothing whatsoever to do with APF authorization. So you could stop LLA and verify that you get the same result. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
