There is an (closed) apar about it. IBM promissed to fix in 36 month. don't remember when count starts... \BTW, never tested that, but how about TSO CONSOLE command in SYSTEM Rexx? did you try that?
ITschak ITschak Mugzach Z/OS, ISV Products and Application Security & Risk Assessments Professional On Tue, Dec 20, 2016 at 3:13 PM, John McKown <[email protected]> wrote: > I use the AXRCMD() function in my System REXX console automation to issue > z/OS operator commands. The commands run as user AXRUSER because that's how > I have them set up. But the console names are "bad"; for example *AXT01H1 . > The "H1" at the end appears to be my &SYSCLONE value. The "01" seems to be > a sequence number. But where is the "*AXT" coming from? This name is > causing me a problem with CICS autoinstall for terminals. I get a message > similar to: > > DFHAC2032 T6CH CICS autoinstall for console *AXT01H1 has failed. > > I cannot create a DEFINE a console, as I have for the actual consoles, > because CICS complains about the leading asterisk in the name. > > > -- > Heisenberg may have been here. > > http://xkcd.com/1770/ > > Maranatha! <>< > John McKown > > ---------------------------------------------------------------------- > 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
