Back in the day, I had to write a DYNALC() external function for PL/I (because BPXWDYN hadn't been released yet) and then ask forgiveness/justify it after the fact--all I was told was that the DSNAME was a field in an ISPF panel and PL/I was preferred to assembly.
I wish now I'd had the guts to include a Text Unit option for anything I hadn't predicted as a requirement :-) As a result, I remember that for SVC 99, R1 -> fullword with high bit on->list of fullword pointers to TUs, the last with the high bit on (i.e. VL parameter list). Wish I could remember yesterday's new password... Roops --- "Mundus sine Caesaribus" On Thu, 28 Aug 2025, 21:36 Tony Harminc, <[email protected]> wrote: > On Thu, 28 Aug 2025 at 16:02, Jon Perryman <[email protected]> wrote: > > > On Thu, 28 Aug 2025 21:14:35 +0200, salva <[email protected]> wrote: > > > > >call bpxwdyn "alloc fi(myterm) tu(0028)" > > > > DSN(*) should have work because of SVC screening but I'm guessing the op > > tried it and it failed. > > > How does SVC screening come into this picture? > > Using SVC99 DALTERM is the obvious answer. > > > Was it obvious to you before someone else made the point that bpxwdyn > allows explicit text units to be specified? > > > > Out of curiosity, I had a quick chat with claude.ai about svc99 instead > > of BPXWDYN. It happily generated the correct assembler code and offered > > DSN(*) as an alternative. AI knows about DALTERM which caused the leap to > > TERMINAL https://claude.ai/share/b9da7da8-f0ef-454a-be99-bed0c54091f2 > > > It also seems to believe that issuing DYNALLOC instead of SVC 99 avoids the > need to set up the SVC 99 arguments. > > Tony H. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
