Using the site command is probably best for you right now.. Here is a quick description of READPRT it may be of interest because the source is available so you can change it to do anything you like. * MODULE NAME : READPRT * * * * FUNCTION : READ THE FIRST PRINTER FILE FOUND IN THE VIRTUAL CARD * * READER, WRITE IT TO A CMS DISK UNDER THE SPECIFIED FILE * * NAME AND FILETYPE, RECREATING THE ASA CARRIAGE CONTROL * * AS THE FIRST CHARACTER IN EACH LOGICAL RECORD. * It's only about 200 instructions .
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Wakser, David Sent: Tuesday, January 22, 2008 11:40 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: RECEIVE question What do your programs do? Alan answered that, by default, VM's FTP set the files to "V". I added a SITE command, and it fixed the problem. David Wakser _____ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Huegel, Thomas Sent: Tuesday, January 22, 2008 12:26 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: RECEIVE question Or if you are adventuress I have two programs you can have. 1) READPRT I think this is an old program that was available for download. I have the source. 2) READLIST I only have the module, don't know where it came from, there is no doc, there doesn't appear to be any copyright notes in the module. It works. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Wakser, David Sent: Tuesday, January 22, 2008 10:54 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: RECEIVE question No, the files are NOT sent by SENDFILE but by FTP from a VSE POWER queue. David Wakser _____ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, January 22, 2008 11:46 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: RECEIVE question IIRC, SENDFILE (or TRANSMIT {synonym = XMIT} on TSO) sends files in NETDATA format (making everything F 80 and including lots of control information). When you RECEIVE a file sent in NETDATA (by SENDFILE or XMIT) format, the file attributes are built to match what was sent. That's is likely what Dave is seeing, assuming that the system sending the files to his reader is using SENDFILE. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Fran Hensler" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 01/22/2008 10:26 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: RECEIVE question That's funny David because I have often wished for exactly the opposite. When I RECEIVE PRT files from a VSE virtual 3800 they are always RECFM 'F' and 205 bytes even if the longest print line is 10 bytes. If they were received as 'V' it would save a lot of space. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 44 years [EMAIL PROTECTED] +1.724.738.2153 "Yes, Virginia, there is a Slippery Rock" On Tue, 22 Jan 2008 08:38:33 -0700 Wakser, David said: >All: > > I am issuing a RECEIVE from within an EXEC to receive a lot of >files onto a minidisk. However, RECEIVE sets them up as record format >"V" - and I want them to be "F". I see no options for this on the >RECEIVE command itself. Is there any way around this? > >David Wakser >InfoCrossing _____ The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.
