Hi, Scott.
The file you are trying to send is not too big, its record length
exceeds what the PUNCH command supports. The maximum record length for
the PUNCH command is 80 bytes. If what you are trying to send to z/OS
(via RSCS) is a JCL file, make sure its lrecl is 80 and its recfm is fixed.
Have a good one.
DJ
On 3/8/2011 12:56 PM, Shumate, Scott 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 this?
Thanks
Scott
*From:* The IBM z/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 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
fields to node zos (replace with the NJE name of your zos system)
SYSTEM, which is normally the JES input processor (SYSTEM is a magic
word for NJE). PUNCH fn ft fm (NOH takes your virtual card deck stored
in fn ft fm (must be RECFM F, LRECL 80) and punches it to RSCS without
any special headers (the NOHeader parm). CP tags the virtual card deck
with the information from the TAG command, and it ends up in RSCS'
virtual reader. RSCS looks at the tag data, slurps up the file and sends
it to zOS.
All this is covered in the RSCS Users' Guide, albeit somewhat opaquely.
Feel free to ask if you have more questions.
