> -----Original Message----- > From: IBM Mainframe Assembler List > [mailto:[email protected]] On Behalf Of Paul Gilmartin > Sent: Thursday, December 22, 2011 9:08 AM > To: [email protected] > Subject: Re: HLASM macros in z/OS UNIX subdirectories. > > On Dec 20, 2011, at 08:29, McKown, John wrote: > <snip> > An off-list discussion has prompted a question: How does BPAM > implement NOTE and POINT for UNIX files? If we create copybook > members with vi, emacs, nedit, jedit, ... and allocate SYSLIB > with FILEDATA=TEXT,RECFM=FB,LRECL=80,PATH=..., the (emulated) > BPAM will pad lines with 0x40 to 80 byte records. Then a nested > COPY causes a NOTE; copies in the nested member and POINTs back > to the previous position. I'd expect POINT to use fseek() > internally. But how does it calculate the fseek() argument, > not knowing how many padding bytes were added previously? > Or does BPAM keep a journal? > > Years ago I had a PMR on failure of this operation. IBM fixed > it. I have no idea how. > > John and I would never tolerate being required to pad lines in > all our UNIX files to 79 characters plus <NL>. > > -- gil
Why wouldn't it just use ftell() to record the actual position in the UNIX file, independant of its reformatting of the data placed into the user's buffer? Then fseek() back to that. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM
