On Tue, 22 Oct 2013 11:21:16 +0300, ��� �� ��� <[email protected]> wrote:

>Hi,
>I added a few consoles, and the operators are complaining that the output from 
>$DI is not displayed on the console.
>When I issue the $DI command I see this in the syslog, but nothing is 
>displayed on the console:
>T064     00000290  $DI
>STC09092 00000290  $DI,CLASS,STATUS,JOBNAME
>INTERNAL 00000090  $HASP892 INIT(1)    CLASS=KQ1B,STATUS=INACTIVE
>INTERNAL 00000090  $HASP892 INIT(2)    CLASS=Q,STATUS=INACTIVE
-snip-

Based on SYSLOG, the command was issued by some console named T064 (EMCS, maybe 
SDSF or some other tool). 

T064 cannot be one of your MCS consoles (all of which are unnamed, given that 
they bear their console ids) based on your D C command below:

>IEE889I 07.33.49 CONSOLE DISPLAY 689
>MSG: CURR=0    LIM=9000 RPLY:CURR=0    LIM=50   SYS=BOIA      PFK=28
>CONSOLE/ALT        ID  --------------- SPECIFICATIONS ---------------
>SYSLOG                 COND=H      AUTH=CMDS         NBUF=0    UD=N
>                        ROUTCDE=ALL
>01/02              01  COND=M      AUTH=MASTER       NBUF=0    UD=Y
>  04A0                  AREA=Z          MFORM=J
>  BOIA                  DEL=R    RTME=1      RNUM=16   SEG=20    CON=N
>                        USE=FC   LEVEL=ALL             PFKTAB=PFKTAB1
>                        ROUTCDE=ALL
>                        MONITOR=JOBNAMES,SESS
>09/10              09  COND=A      AUTH=ALL          NBUF=0    UD=N
>  1000                  AREA=Z          MFORM=J
>  BOIA                  DEL=R    RTME=1      RNUM=16   SEG=20    CON=N
>                        USE=FC   LEVEL=ALL             PFKTAB=PFKTAB1
>                        ROUTCDE=ALL
>                        MONITOR=JOBNAMES,SESS
>10/09              10  COND=A      AUTH=ALL          NBUF=0    UD=N
>  1001                  AREA=Z          MFORM=J
>  BOIA                  DEL=RD   RTME=1      RNUM=18   SEG=9     CON=N
>                        USE=FC   LEVEL=ALL             PFKTAB=PFKTAB1
>                        ROUTCDE=ALL
>                        MONITOR=JOBNAMES,SESS

You could probably figure out what's happening by GTF tracing the pertinent SSI 
control blocks (SSIB, SSOB, SSCM) before/after the command processing SSI (code 
10).  I'm pretty sure that IBM documents how to do this somewhere because "who 
the frack screwed up my control blocks" is a frequent SSI problem.

Forensically, it would appear that someone(s) on the SSI are changing the 
command text (augmenting the command) and changing the issuing console id to 
zero (I don't believe you can alter the console name to INTERNAL).

It's not clear to me why you'd expect a command response to show up on a 
different console from the one issuing the command (other than by MSGROUT, as 
pointed out elsewhere).  A way that you might capitalize on this behavior is to 
assign the "INTIDS" attribute to the consoles where you want the output to go.  
Using INTIDS says, "I want all messages routed to console id 0 to come to 
here."  Have a look here (mind any wrap):  
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2g370/3.4.7?ACTION=MATCHES&REQUEST=intids&TYPE=FUZZY&SHELF=EZ2ZO10I

Scott Fagen
Chief Architect - System z
CA Technologies

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to