TSO XMIT/RECEIVE (How does it work??!!)
Sam Butters - ATCX
have forwarded to this list for possible discussion...
========================================================================
> Its been a while since I transmitted datasets between JES nodes, so please
> bear with my question.
>
> I'm trying to transmit a PDS to another LPAR, which I have JES
> connectivity to, via the TSO TRANSMIT command. For example, I issue the
> following command:
>
> XMIT (OS27.$TSSSB2) DSNAME('$TSSSB1.CICS.MAINTLIB.JCL') PDS NOTIFY(ALL)
>
> My problem is this. I want to use the TSO RECEIVE command on the OS27
> node to get the dataset which I transmitted. But, what I see happening is
> that on the OS27 SYSLOG, I get the following message:
>
> $HASP540 $TSSSB2 ON L3.SR1 FROM $TSSSB2 AT TEST 887
> RECORDS
>
> And I get a "TSU" sysout for job $TSSSB2. This SYSOUT contains what
> appears to be the raw contents of the PDS I am transmitting.
>
> When I attempt to use the RECEIVE command on the OS27 node, I get the
> following message:
>
> INMR003I You have no messages or data sets to receive.
>
> Now, what the heck is going on here?? At a previous site, I was able to
> transmit a PDS and then receive it on the target node. Am I missing
> something here??
>
> Anybody got an answer for this?? BTW, our MVS systems programmer seems to
> think its because we don't have a PUNCH class defined in JES parms; could
> that be the problem??
>
> Thanks,
> Sam Butters
> Maricopa County - ATC, Arizona USA
> CICS - Technical Services
> 602-506-7782
>
Dan McLaughlin
TSO XMIT Node.Userid da('fully.qualified.name')
On the receiving end:
Receive DA('fully qualified.name')
You may get asked if you want to replace, etc. It is even possible to send a
single member of a PDS...
Daniel A. McLaughlin
Sr. Tech Analyst/OS390
Cotton States Insurance Co.
Atlanta, GA
Sam Butters - ATCX
Simon Wheeler
I assume that your userid is the same on both lpars. Can you see the data queued
on the output queue in SDSF?
Cheers,
Simon.
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric and Southern Electric are trading names of
Scottish and Southern Energy Group
**********************************************************************
Kalinich, John
priviledge.
Jeremy C B Nicoll
> > I'm trying to transmit a PDS to another LPAR, which I have JES
> > connectivity to, via the TSO TRANSMIT command. For example, I issue the
> > following command:
> >
> > XMIT (OS27.$TSSSB2) DSNAME('$TSSSB1.CICS.MAINTLIB.JCL') PDS NOTIFY(ALL)
> >
> > My problem is this. I want to use the TSO RECEIVE command on the OS27
> > node to get the dataset which I transmitted. But, what I see happening is
> > that on the OS27 SYSLOG, I get the following message:
> >
> > $HASP540 $TSSSB2 ON L3.SR1 FROM $TSSSB2 AT TEST 887
> > RECORDS
That means the target jes is receiving a sysout dataset on line 3's
first-defined sysout receiver, and that's as you'd expect.
> >
> > And I get a "TSU" sysout for job $TSSSB2. This SYSOUT contains what
> > appears to be the raw contents of the PDS I am transmitting.
Yes. That's how tx/rx works - a transmit creates an iebcopy unload
version of the pds in a sysout file which has a DEST value of the target
node/userid.
> > When I attempt to use the RECEIVE command on the OS27 node, I get the
> > following message:
> >
> > INMR003I You have no messages or data sets to receive.
> >
> > Now, what the heck is going on here?? At a previous site, I was able to
> > transmit a PDS and then receive it on the target node. Am I missing
> > something here??
Possibly. Are you logged onto that node as tso userid $TSSSB2 ? If not
you need to use RECEIVE USER($TSSSB2) to specifu whose files you want to
receive (and that's a restricted command - you need OPER authority to do
that).
> > Anybody got an answer for this?? BTW, our MVS systems programmer
> > seems to think its because we don't have a PUNCH class defined in JES
> > parms; could that be the problem??
Don't think so.
--
Jeremy C B Nicoll - my opinions are my own.
BUDBILL, GENE
output before they noticed it and punched it.
By default, TRANSMIT sends it's output as SYSOUT CLASS B. Does your
receiving system (OS27) have SYSOUT=B assigned to a printer? If not, double
check what class is being used for the TRANSMIT. Check the SYS1.PARMLIB
member IKJTSO00 for any TRANSREC parameters, particularly SPOOLCL, which
defines the class for the outgoing data. Is that class defined on the
receiving system to a printer?
Hope this helps.
Gene
Sam Butters - ATCX
XMIT/RECEIVE. One is that you must have a PUNCH class defined to your
JES's. The other requirement is that IKJTSOxx must be modified to use that
PUNCH class).
After these changes were made, the XMIT/RECEIVE worked as advertised.
Thanks to all who responded!
> -----Original Message-----
> From: Simon Wheeler [SMTP:Simon....@SCOTTISH-SOUTHERN.CO.UK]
> Sent: Wednesday, March 15, 2000 8:50 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: TSO XMIT/RECEIVE (How does it work??!!)
>
Dan McLaughlin
the receive side and usually fumble with it until I hit
the right combination.
Dan McLaughlin
user on SDSF and can see anything. It was pointed out
that I had the wrong receive syntax, so check on that.