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. Poughkeepsie NY > > 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: > > 9476 $BUFFER > 000018 9935+BUFIOBST DS XL(IOBLENG) Defin > ASMA068S Length error - L(IOBLENG) > ASMA435I Record 484 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 9941+TPBMXREC EQU IOBINCAM, > 1,C'C' Max R > ASMA044E Undefined symbol - IOBINCAM > ASMA435I Record 490 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 9942+IOBECBSV EQU IOBINCAM+1,1 I/O C > ASMA044E Undefined symbol - IOBINCAM > ASMA435I Record 491 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 9943+TPBLCCC EQU IOBXTENT, > 1,C'C' Last > ASMA044E Undefined symbol - IOBXTENT > ASMA435I Record 492 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 9944+TPBLCCAD EQU IOBXTENT, > 4,C'A' Addr > ASMA044E Undefined symbol - IOBXTENT > ASMA435I Record 493 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 9945+IOBXTENT EQU IOBM,1,C'C' DEB e > ASMA044E Undefined symbol - IOBM > ASMA435I Record 494 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 9952+ ORG BUFIOBST+ > (IOBSEEK-IOBDSEC > ASMA080E Statement is unresolvable > ASMA435I Record 501 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 10013+ ORG BUFIOBST+ > (IOBSEEK-IOBDSEC > ASMA080E Statement is unresolvable > ASMA435I Record 563 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > 000050 10085+HDBID DS CL4'HDB' Eyecatche > 0000D8 10257+ DC 0S((BUFSTART- > BFPDSECT)-(B > ASMA028E Invalid displacement > ASMA435I Record 809 in SYS1.SHASMAC($BUFFER) on volume: R23DLB > Assembler Done 9 Statements Flagged / 12 was Highest Severity Code > > I can't understand the undefined symbols. I'm able to recreate the > 2.1 exit code using the 2.1 release libraries. Symbol IOBLENG for > example simply is not defined in the 2.3 release even though the > symbol is used. Am I missing something transparently obvious? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
