What release of Attachmate? Have you tried to change your Attachmate
session to use ftp instead of IND$FILE? For example, click on Options,
then Session Type, then select FTP for File transfer protocol.
Craig
-Original Message-
From: IBM Mainframe Discussion List
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
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
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
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
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
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
7 matches
Mail list logo
