Skip to main content

Discussion posted 3/28/08 by Serenity Thompson
Details:


supportadmin

Topic: bas lib search order changes after admin update. (1 of 2), Read 79 times
Conf: ZMF
From: Rick Behee Richard.Behee@commercebank.com
Date: Wednesday, August 23, 2006 03:28 PM
Has any one had issues in v552 with the compile process after changing or adding library types to an application. Currently when i select or view an application baseline the search order changes in cmn$$syc.
Topic: bas lib search order changes after admin update. (2 of 2), Read 49 times
Conf: ZMF
From: Sandy Karlin Sandra.Karlin@gwl.com
Date: Tuesday, December 05, 2006 01:03 PM
We just ran into the same issue, but with only one of many applications. To make a long story short, specifying sequence numbers for the library-type definitions in both Global and Application Administration should solve the problem. The sequence numbers apply to like-source, like-copy, and like-load library types. Starting in 5.5.1 or 5.5.2, if SEQ NO. is not specified, the SYSLIB concatenation pulls a RANDOM order of datasets based on the location in the package master (not from the order on the screens). Hope this helps . . .



#posta4360ea95e
#oldforumpost
#ChangeManZMF

Discussion posted 3/28/08 by Serenity Thompson
Details:


supportadmin

Topic: bas lib search order changes after admin update. (1 of 2), Read 79 times
Conf: ZMF
From: Rick Behee Richard.Behee@commercebank.com
Date: Wednesday, August 23, 2006 03:28 PM
Has any one had issues in v552 with the compile process after changing or adding library types to an application. Currently when i select or view an application baseline the search order changes in cmn$$syc.
Topic: bas lib search order changes after admin update. (2 of 2), Read 49 times
Conf: ZMF
From: Sandy Karlin Sandra.Karlin@gwl.com
Date: Tuesday, December 05, 2006 01:03 PM
We just ran into the same issue, but with only one of many applications. To make a long story short, specifying sequence numbers for the library-type definitions in both Global and Application Administration should solve the problem. The sequence numbers apply to like-source, like-copy, and like-load library types. Starting in 5.5.1 or 5.5.2, if SEQ NO. is not specified, the SYSLIB concatenation pulls a RANDOM order of datasets based on the location in the package master (not from the order on the screens). Hope this helps . . .



#posta4360ea95e
#oldforumpost
#ChangeManZMF

This is an old migrated post that has been assigned status Complete.