take a look at it?
Thanks
Scott
--
*From:* The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] *On
Behalf Of *Kris Buelens
*Sent:* Tuesday, March 08, 2011 3:47 PM
*To:* IBMVM@LISTSERV.UARK.EDU
*Subject:* Re: Sending files to JES
On our VM systems
SPOOL PUN TO RSCS
TAG DEV PUN zos SYSTEM
PUNCH fn ft fm ( NOH
Explanation:
SP PUN TO RSCS sets the destination of the PUNCH command on the VM side. RSCS
knows to look at the tag data of the incoming files to decide what to do with
them. TAG DEV PUN zos SYSTEM sets the tag data destination
Alternatively, the TCPNJE add-on-extra to RSCS will allow submission through
NJE.
Neale
On 3/8/11 12:34 PM, David Boyes dbo...@sinenomine.net wrote:
SPOOL PUN TO RSCS
TAG DEV PUN zos SYSTEM
PUNCH fn ft fm ( NOH
Explanation:
SP PUN TO RSCS sets the destination of the PUNCH command on the VM
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf
Of Neale Ferguson
Sent: Tuesday, March 08, 2011 9:44 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Sending files to JES
Alternatively, the TCPNJE add-on-extra to RSCS will allow submission
Alternatively, the TCPNJE add-on-extra to RSCS will allow submission through
NJE.
The user part of the process is the same, though. In both cases, the file has
to end up in RSCS' virtual reader; the transport between VM and z/OS is
transparent to that process.
If the z/OS system was
He didn't specify it was a job. That opens a whole new can of worms: JCL, pswd
etc.
Les
David Boyes wrote:
Alternatively, the TCPNJE add-on-extra to RSCS will allow submission through
NJE.
The user part of the process is the same, though. In both cases, the file has
to end up in RSCS'
On 3/8/11 1:00 PM, Les Koehler vmr...@tampabay.rr.com wrote:
He didn't specify it was a job. That opens a whole new can of worms: JCL,
pswd etc.
Not the problem of the NJE transport. It's just got to get the file from
system A to system B. Content and payload correctness are left as an
exercise
[mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of David Boyes
Sent: Tuesday, March 08, 2011 12:34 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Sending files to JES
SPOOL PUN TO RSCS
TAG DEV PUN zos SYSTEM
PUNCH fn ft fm ( NOH
Explanation:
SP PUN TO RSCS sets the destination of the PUNCH command
On Tuesday, 03/08/2011 at 02:00 EST, Shumate, Scott
scshum...@bbandt.com wrote:
That works great.
Now I'm running into a new problem. The file I'm sending is too big.
I get
the following message.
DMSPUN044E Record exceeds allowable maximum
Any ideas how I can get around
/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU]
*On Behalf Of *David Boyes
*Sent:* Tuesday, March 08, 2011 12:34 PM
*To:* IBMVM@LISTSERV.UARK.EDU
*Subject:* Re: Sending files to JES
SPOOL PUN TO RSCS
TAG DEV PUN zos SYSTEM
PUNCH fn ft fm ( NOH
Explanation:
SP PUN TO RSCS sets
detail.
Thanks
Scott
-Original Message-
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of Alan Altmark
Sent: Tuesday, March 08, 2011 2:06 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Sending files to JES
On Tuesday, 03/08/2011 at 02:00 EST, Shumate
Why not FTP it?
-Original Message-
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of Shumate, Scott
Sent: Tuesday, March 08, 2011 1:16 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Sending files to JES
I have 130 lrecl log file that is stored on operator's
.
Shumate, Scott scshum...@bbandt.com
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
03/08/2011 01:15 PM
Please respond to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Sending files to JES
I have 130 lrecl log file
Use the VM SENDFILE command: SENDFILE fn ft fm TO user AT zos
On the z.OS side, use the TSO RECEIVE command to receive the file.
SENDFILE takes the original file and encodes it to fit into a series of 80 byte
cards, carrying enough metadata to reassemble the file in it's original form on
the
On 3/8/11 2:21 PM, Ward, Mike S mw...@ssfcu.org wrote:
Why not FTP it?
Simple enough: Automating NJE transfer is trivial -- NJE is
fire-and-forget in that the system daemons handle routing, retries, and
guaranteed delivery (short of someone clearing spool for some stupid
reason). If you've got
On our VM systems, we had some processes that sent a CMS file embedded in an
MVS job. The MVS job started TSO in batch to receive the file. At last
that single job could carry multiple CMS files. As a result, the REXX code
became less than easy to read for beginners. I can dig that up, on
That would be great. Can I take a look at it?
Thanks
Scott
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of Kris Buelens
Sent: Tuesday, March 08, 2011 3:47 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Sending files to JES
@LISTSERV.UARK.EDU
Subject: Re: Sending files to JES
Eventually you are going to find that files contain so many records
(perhaps some with very large LRECLs) that using SENDFILE is no longer
productive.
Not only that, but SENDFILE (aka TRANSMIT or XMIT on TSO) and RECEIVE
have significant CPU overhead
18 matches
Mail list logo