Re: Problem with $BUFFER control block

2018-05-16 Thread Jesse 1 Robinson
gt; >Date:Mon, 14 May 2018 00:12:54 + > >From:Jesse 1 Robinson > >mailto:jesse1.robin...@sce.com>> > >Subject: Re: Problem with $BUFFER control block > > >I was hopeful that the IEZIOB would include the missing fields. > >Unfortunately it does no

Re: Problem with $BUFFER control block

2018-05-13 Thread Dale R. Smith
On Mon, 14 May 2018 00:12:54 +, Jesse 1 Robinson wrote: >I was hopeful that the IEZIOB would include the missing fields. Unfortunately >it does not. Before opening an SR with IBM, I thought I'd give the List one >more shot. The $BUFFER macro changed in z/OS 2.2; we're jumping from 2.1 to

Re: Problem with $BUFFER control block

2018-05-13 Thread Jesse 1 Robinson
le 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jim Mulder Sent: Saturday, May 12, 2018 10:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Problem with $BUFFER control block

Re: Problem with $BUFFER control block

2018-05-12 Thread Jim Mulder
The $BUFFER macro contains this line: * $Z22LCKP=64BCKPT HJE77A0 140821 TJW: Use MVS IOB DSECT* So I would guess that, starting with z.OS 2.2, you need to include the SYS1.MACLIB(IEZIOB)DSECT in your program. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp

Problem with $BUFFER control block

2018-05-12 Thread Jesse 1 Robinson
I'm embarrassed to ask this question, but I've been over the same ground many times to no avail. We have carried several SMF exits from release to release without complications. In moving from z/OS 2.1 to 2.3, we suddenly get an assembly error in $BUFFER that makes no sense: