Re: TSSO issuing command to CICS

2008-12-08 Thread Kittendorf, Craig X.
I solved the problem by turning on console autoinstall.

Thanks

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Westerman
Sent: Saturday, December 06, 2008 1:56 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSSO issuing command to CICS

It works okay for me, what CICS/TS level are you running?

Looking at the OSCMD code, I don't see any obvious areas that would
cause
any problems.  

Brian

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

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


Re: TSSO issuing command to CICS

2008-12-05 Thread Kittendorf, Craig X.
TSSO is defined to use 3 subsystem consoles.  The subsystem consoles are
defined to CICS.  Commands from JCL used to enter as console # 000 but
now enter as console name INSTREAM and this is defined to CICS.

OSCMD issued by TSSO works ok. OSCMD issued by me in my ISPF session
works  ok.  It's OSCMD issued from a batch tso job which is failing.

Thanks,
   Craig

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Westerman
Sent: Friday, December 05, 2008 12:47 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSSO issuing command to CICS

Did you set up consoles for TSSO at installation time?

Brian

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

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


FW: TSSO issuing command to CICS

2008-12-05 Thread Kittendorf, Craig X.
I solved the problem with TSSO's OSCMD from batch by setting up CICS 
autoinstall for consoles. The console gets installed with one of those odd 
termids:

DFHZC5966 I 12/05/2008 14:24:44 AJD1JDCC INSTALL started for TERMINAL (  ¬AAA)
DFHSN1800 12/05/2008 14:24:44 AJD1JDCC Signon at console  by preset user 
JSYSCXK in group OMVSSYS is complete.
DFHZC6935 I 12/05/2008 14:24:44 AJD1JDCC Autoinstall for console ¬AAA with 
consolename  using model or template @CONS successful. 

Thanks to all who replied,
   Craig
_
From: Kittendorf, Craig X. 
Sent: Wednesday, December 03, 2008 3:28 PM
To: 'IBM-MAIN@bama.ua.edu'
Subject: TSSO issuing command to CICS

Hi,

We are using TSSO with z/OS 1.9 and have the patches applied for v1.9.  
Everything is working fine except trying to send a command to CICS/TS 3.1 from 
a batch job, for example:

// EXEC BATCHTMP
//SYSINDD *
OSCMD F CICS,tran
/*

The CICS log shows:

DFHAC2015 11/24/2008 11:28:24 AJD1DCTE Console 000 has not been defined to CICS.

Has anyone found and fixed this problem?

Thanks, 
   Craig

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


Re: TSSO issuing command to CICS

2008-12-04 Thread Kittendorf, Craig X.
I have defined consoles including Internal, subsystem, etc.  Apparently
TSSO is using console number 000 and not a console name.  With CICS 3.1
you can not define a console by number.  Issuing commands thru TSSO to
CICS 3.1 worked fine until upgrading to z/OS 1.9.

Craig

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Westerman
Sent: Thursday, December 04, 2008 2:34 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: TSSO issuing command to CICS

You have to define the console ID you are issuing the commands from to
CICS.
 The procedure for doing that is outlined in the CICS systems guide.

Brian

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

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


Re: TSSO issuing command to CICS

2008-12-04 Thread Brian Westerman
Did you set up consoles for TSSO at installation time?

Brian

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


TSSO issuing command to CICS

2008-12-03 Thread Kittendorf, Craig X.
Hi,

We are using TSSO with z/OS 1.9 and have the patches applied for v1.9.
Everything is working fine except trying to send a command to CICS/TS
3.1 from a batch job, for example:

// EXEC BATCHTMP
//SYSINDD *
OSCMD F CICS,tran
/*

The CICS log shows:

DFHAC2015 11/24/2008 11:28:24 AJD1DCTE Console 000 has not been defined
to CICS.

Has anyone found and fixed this problem?

Thanks, 
   Craig

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


Re: TSSO issuing command to CICS

2008-12-03 Thread Brian Westerman
You have to define the console ID you are issuing the commands from to CICS.
 The procedure for doing that is outlined in the CICS systems guide.

Brian

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


TSSO issuing command to CICS

2008-11-24 Thread Kittendorf, Craig X.
Hi,

We are using TSSO with z/OS 1.9 and have the patches applied for v1.9.
Everything is working fine except trying to send a command to CICS/TS
3.1 from a batch job, for example:

// EXEC BATCHTMP
//SYSINDD *
OSCMD F CICS,tran
/*

The CICS log shows:

DFHAC2015 11/24/2008 11:28:24 AJD1DCTE Console 000 has not been defined
to CICS.

Has anyone found and fixed this problem?

Thanks, 
   Craig

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