TSSO and z/OS 1.11.

[Richbourg, Claude]

Good morning all,

I am uploading the 'new' TSSO that I pulled down from the CBT updates
page. Does anyone know if it Is

ready to go for z/OS 1.11?

Thanks up front .

Regards,

Claude

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Brian Westerman]

It had to be re-assembled, but appears to work correctly.

Brian

[Richbourg, Claude]

Hello Brian,

I downloaded TSSO from the UPDATES section and it assembled fine. When
TSSO traps a message on the syslog and fires off a command, I now get
this from TSSO:

TSSA305E TSSO COMMANDS MAY NOT BE ISSUED FROM THIS ENVIRONMENT

Any ideas on what I may have missed or need to do? I do not really
understand what TSSO is fussing about unless it is console related..

Here is a snippet from a 'D C' command;
CDCUSYSA TYPE=SUBSYS STATUS=ACT-CDCU COMPID=TSSO ASID=0020
DEFINED=(*ALL)
MATCHED=(*ALL)
ATTRIBUTES ON CDCU
AUTH=(MASTER)
CDCUSYS1 TYPE=SUBSYS STATUS=ACT-CDCU COMPID=TSSO ASID=0020
DEFINED=(*ALL)
MATCHED=(*ALL)
ATTRIBUTES ON CDCU
AUTH=(MASTER)
CDCUSYS2 TYPE=SUBSYS STATUS=ACT-CDCU COMPID=TSSO ASID=0020
DEFINED=(*ALL)
MATCHED=(*ALL)
ATTRIBUTES ON CDCU
AUTH=(MASTER)

Any and all help would be much appreciated by you or someone you know
who may have the key.

Regards,
Claude

[Brian Westerman]

Hi,

This is related to issues with your consolXX member (normally it has been
because of a syntax error and/or purposly done for another product) and
certain types of commands issued by TSSO (normally only REXX or CLISTS
because if you were to just issue a console command it should work fine).
When TSSO attempts to issue the REXX command it grabs the consoleID from the
originating message (the one that drove him), and in your case it's getting
a empty one. If you have consoles with no assigned names they are built
differently and you run into this problem because you can end up with the
SSCMCNID set to zeros. There are two fixes, one, fix your consoleXX member
so that everyone gets a name, (this is not always possible for some people
to do), the second method is to change the TSSOSS10 member at line 02283006

FROM

BNE STAT4 EEJ1102 02283006

TO

B STAT4 yourname EEJ1102 02283006

then reassemble/link and recycle TSSO, and you will be good to go.

If your version of TSSOSS10 doesn't have the EEJ1102 on that line, then
don't make the change because you have the wrong version of the module (pre
1.8) and you will end up in a loop. You will have to get the newest version
and use it (in fact, you will want to re-assemble everything if you have to
get the new version because you need it to support z/OS 1.8 and up:).

I will have to put some replacement code together to handle this since more
people seem to be setting up their consolXX member without names, but right
now the above fix will resolve it for you.

If you have any questions please contact me offline and I can discuss them
with you.

Brian Westerman

[Richbourg, Claude]

Hello Brian,

Many thanks on the fix. This worked great and now we are in business
with 1.11.

Regards,
Claude

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On
Behalf Of Brian Westerman
Sent: Tuesday, January 05, 2010 2:11 AM
To: IBM-...@bama.ua.edu
Subject: Re: TSSO and z/OS 1.11.

[Brian Westerman]

No Problem,

I think I have the issues worked out now, there are some sites that are
running only with the HMC console and those with the OSA attached consoles
that have not defined them with names.

Brian