The root of this problem is poorly chosen block sizes for the output data sets that contain load modules. Always, always, always use a block size of 32760 for RECFM U data sets that contain load modules and move them around using COPYMOD. Specify PARM=SPCLCMOD so you don't get warning messages about the few modules that COPYMOD won't reblock. (It will do what you want; don't worry, be happy...just use BLKSIZE=32760 and COPYMOD with PARM=SPCLCMOD.)

That will make this entire issue evaporate. As a bonus, your load libraries will likely take less space (never more) and performance might improve slightly (and will never be worse).

To partly answer what you asked: What I believe you think you want to find is the length of the longest text record, not the length of the member. Each member of a load library comprises some number of text records of variable length (up to the block size) and a number of other records. If you search the archives you will find a lengthy post I wrote some years ago that explains how the Binder and IEBCOPY write text records that will probably shed some light on what you are seeing. And, you can look up which record contains the length of the next text record and process those records to get that information if you choose to.

However, finding the length of the longest text record in a load library as a means for trying to prevent IEB188I messages or their rarer COPYMOD counterparts is, in my opinion, not a productive use of time when the best and smoothest road to improvement is paved with the right choice of block size.


ibmm...@foxmail.com (ibmmain) wrote:
Hi
   Which length do you mean?  The length of the member?

   We want to know the length of the member.

  When we copy some members in a loadlib to other one,we  received the IEB188I 
message, and only want to copy the dataset

Later we used COPYMOD instead of a COPY  to do this.

However, We want to know the length of the member in the new LOADLIB .We wonder 
wherther record with length is longer than blocksize in the new dataset

Thanks a lot!


--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
ee...@us.ibm.com

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to