|
View previous topic :: View next topic
|
| Author |
Message |
Janos Molnar
New User
Joined: 29 May 2023
Posts: 1
Location: Romania
|
|
|
|
Hello,
Would like to ask your help regarding the following case.
Several modules have been copied from a destination library to a target library using ISPF options . The target library is in LINKLIST.
The modules which were already existing in the target library were replaced OK, but for any new module it showed *NO-DATA and it wasn't viewable/browsable.
After this dataset was renamed and removed from Linklist the modules were accessible.
There is no such issue when copying with a job using IEBCOPY.
We suspect that the issue is related to LLA caching the directory entries and for new the modules it wouldn't contain the correct entries. LLA refresh wasn't done.
But how is a browse from ISPF 3.4 related to the LLA entries ?
Also why no such issue with IEBCOPY. Is there a behavioral difference in this regard between IEBCOPY and the ulility used by ISPF?
Thanks for your answers in advance |
|
| Back to top |
|
 |
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1328
Location: Bamberg, Germany
|
|
|
|
| It is never a good idea to copy Load Modules with the ISPF dialog. IEBCOPY w/ COPYMOD/CM is the way to go. As you have mentioned, LLA is kind of a Caching mechanism. When you update/add/create additional info in the DSN, a LLA REFRESH is needed. Also avoid any additional extents to the DSN in the LNKLST, it's limited, and can also cause you trouble. |
|
| Back to top |
|
|
|
|
