Re: CMS Files to XMIT compatible datastream
On Friday, 08/08/2008 at 12:25 EDT, Thomas Kern <[EMAIL PROTECTED]> wrote: > The CMS Files to TSO XMIT is one part of the overall process. The other > parts are CMS Files to VMARC, CMS Files to ZIP and CMS Files to TAR. The > VMARC option is for people (like me) who would use these files on other z/VM > systems. The ZIP option is for people who would only use these files on > their Windows PC. The TAR option is for the people who would use the files > on Linux/SUN/AIX systems. The XMIT option is necessary for those people who > would use them on z/OS systems. If folks feel that CMS and TSO netdata-style communications needs to be beefed up, please work with your fave user group to get those requirements open. If you don't tell us, we don't know. Alan Altmark z/VM Development IBM Endicott
Re: CMS Files to XMIT compatible datastream
The CMS Files to TSO XMIT is one part of the overall process. The other parts are CMS Files to VMARC, CMS Files to ZIP and CMS Files to TAR. The VMARC option is for people (like me) who would use these files on other z /VM systems. The ZIP option is for people who would only use these files on their Windows PC. The TAR option is for the people who would use the file s on Linux/SUN/AIX systems. The XMIT option is necessary for those people w ho would use them on z/OS systems. On Fri, 8 Aug 2008 09:15:20 -0700, Lionel B. Dyck <[EMAIL PROTECTED]> wrote: >How about using VMARC to collect the files into a single transportable >file and then on the PC you can use VMA from Leland Lucius > >VMA can be found at http://homerow.net/zvm/vma.htm > >The description is: > >VMA Utility >VMA is a utility that allows you to list and/or extract subfiles from >VMARC files. It consists of a command line version that should run just >about anywhere and a GUI version that should run whereever wxWidgets is >supported. > >Lionel B. Dyck, Consultant/Specialist >
Re: CMS Files to XMIT compatible datastream
How about using VMARC to collect the files into a single transportable file and then on the PC you can use VMA from Leland Lucius VMA can be found at http://homerow.net/zvm/vma.htm The description is: VMA Utility VMA is a utility that allows you to list and/or extract subfiles from VMARC files. It consists of a command line version that should run just about anywhere and a GUI version that should run whereever wxWidgets is supported. Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: "Our cause is health. Our passion is service. We're here to make lives better." I never guess. It is a capital mistake to theorize before one has data. Insensibly one begins to twist facts to suit theories, instead of theories to suit facts. - Sir Arthur Conan Doyle NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. <>
Re: CMS Files to XMIT compatible datastream
Two problems with this solution. I need to get the XMIT file down to a PC. I don't have ISPF on this IFL. /Tom Kern /301-903-2211 On Fri, 8 Aug 2008 00:51:48 -0600, Roger Bolan <[EMAIL PROTECTED]> wrote: >If you have ISPF on VM you can use option 3.6 the SPOOL utility XM optio n >to send a whole set of files with the same lrecl and recfm to TSO as a >PDS. >For example, If I have a set of JCL files on VM I can send the whole se t >as * JCL with XM, and it arrives as an xmitted PDS on TSO. I get these >messages: >INMR901I Dataset A.ASTERISK.JCL from RBOLAN on BLDVMB >INMR906A Enter restore parameters or 'DELETE' or 'END' + > >Roger Bolan
Re: CMS Files to XMIT compatible datastream
If you have ISPF on VM you can use option 3.6 the SPOOL utility XM option to send a whole set of files with the same lrecl and recfm to TSO as a PDS. For example, If I have a set of JCL files on VM I can send the whole set as * JCL with XM, and it arrives as an xmitted PDS on TSO. I get these messages: INMR901I Dataset A.ASTERISK.JCL from RBOLAN on BLDVMB INMR906A Enter restore parameters or 'DELETE' or 'END' + Roger Bolan The IBM z/VM Operating System wrote on 08/07/2008 09:22:33 AM: > What I would like to do is take a list of CMS files and package them > together as a single data file compatible with the TSO XMIT and Windows > XMIT-Manager programs. I have looked at the PIPELINES BLOCK NETDATA (I am > > not that good a plumber) and at stacking NETDATA output files together > (SPOOL PUN CONT, NETDATA ... (NOSPOOL, SP PUN NOCONT CLOSE), but this doe > s > not produce a usable XMIT file. > > Does anyone have a procedure for combining multiple CMS files into a sing > le > XMIT data file? > > /Tom Kern > /301-903-2211
Re: CMS Files to XMIT compatible datastream
The TAPPDS and TAPEMAC programs only read IEBPTPCH, IEBUPDTE and IEHMOVE
data files.
The IEBCOPY program that I have is from a VM/SP 2 version of the Waterloo
Mods tape. It is M0091. It is also included in File 05 of the CBTTape whi
ch
is a REXX program (with assembler helper programs) to load the CBTTape to
CMS files.
The OSPDS REXX and the XMITINFO EXEC (from PlanetMVS) are the most useful
as
examples of decoding the IEBCOPY directory and data. I noticed that PIPEL
INE
has an IEBCOPY built-in stage to decode the directory and data. I wonder
if
the old DECODE operand to it was removed because people hoped there would
be
an ENCODE operand someday?
/Tom Kern
/301-903-2211
On Thu, 7 Aug 2008 14:27:35 EDT, A. Harry Williams <[EMAIL PROTECTED]>
wrote:
>OSPDS is a rexx stage for Pipelines that breaks apart a IEBCOPY file.
>http://www2.marist.edu/~pipeline/ospds.rexx
>
>I use it as:
>
>PIPE(name PDSREC)|',
> 'reader file' splid '|',
> 'find' '41'x '|',
> 'spec 2-* 1.80|',
> 'deblock netdata|',
> 'find {|' ,
> 'spec 2-* 1|' ,
> 'ospds' ft fm
>
>
>You may also find http://www.planetmvs.com/unxmit/index.html useful for
>some additional details.
>
Re: CMS Files to XMIT compatible datastream
On Thu, 7 Aug 2008 14:22:38 -0400 David Boyes said:
>TAPPDS and TAPEMAC can reassemble unloaded PDSes on CMS. In looking
>around, also look for INMR123 REXX on your S disk. That seems to do
>something like what you might want.
OSPDS is a rexx stage for Pipelines that breaks apart a IEBCOPY file.
http://www2.marist.edu/~pipeline/ospds.rexx
I use it as:
PIPE(name PDSREC)|',
'reader file' splid '|',
'find' '41'x '|',
'spec 2-* 1.80|',
'deblock netdata|',
'find {|' ,
'spec 2-* 1|' ,
'ospds' ft fm
You may also find http://www.planetmvs.com/unxmit/index.html useful for
some additional details.
>> I suspect that the 'some data' is an IEBCOPY unloaded PDS. Now I have
>an
>> assembler program that reads an IEBCOPY unloaded PDS but no program to
>wr
>> ite
>> one. I will have to break open the IEBCOPY program to see how a
>datastrea
>> m
>> is constructed. Maybe I can get a pipeline to create a compatible
>datastr
>> eam.
Re: CMS Files to XMIT compatible datastream
TAPPDS and TAPEMAC can reassemble unloaded PDSes on CMS. In looking around, also look for INMR123 REXX on your S disk. That seems to do something like what you might want. > I suspect that the 'some data' is an IEBCOPY unloaded PDS. Now I have an > assembler program that reads an IEBCOPY unloaded PDS but no program to wr > ite > one. I will have to break open the IEBCOPY program to see how a datastrea > m > is constructed. Maybe I can get a pipeline to create a compatible datastr > eam.
Re: CMS Files to XMIT compatible datastream
More information: An example of an XMIT file, taken from the CBTTAPE website contains 5 INM R control records. 1) INMR01 with fromnode fromuser tonode touser information 2) INMR02 with an eyecatcher of IEBCOPY 3) INMR02 with an eyecatcher of INMCOPY 4) INMR03 with some original file information some data 5) INMR06 to terminate the datastream I suspect that the 'some data' is an IEBCOPY unloaded PDS. Now I have an assembler program that reads an IEBCOPY unloaded PDS but no program to wr ite one. I will have to break open the IEBCOPY program to see how a datastrea m is constructed. Maybe I can get a pipeline to create a compatible datastr eam. /Tom Kern /301-903-2211
Re: CMS Files to XMIT compatible datastream
That alternative, I will keep in my back pocket for a last resort. /Tom Kern /301-903-2211 On Thu, 7 Aug 2008 11:52:37 -0500, McKown, John <[EMAIL PROTECTED]> wrote: >Just as an aside, the Java "jar" command can be used to create or >"explode" ZIP type files. Most z/OS shops should have Java. It's free. > >jar xf some.file.zip > >will eXtract the files from soe.file.zip > >jar cf some.other.zip file1 file2 file3 ... > >Will create a ZIP file containing the files. > >I don't think it supports "legacy" z/OS datasets, only z/OS UNIX files. > >-- >John McKown
Re: CMS Files to XMIT compatible datastream
> -Original Message- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern > Sent: Thursday, August 07, 2008 11:43 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMS Files to XMIT compatible datastream > > The purpose is to have a datafile that can be transferred to a PC for > archival to a CD/DVD and viewed with the XMIT Manager program > under Windo= > ws > and when the user gets a new job at a z/OS installation, the > file can be > uploaded to that system and properly used by the TSO RECEIVE command. > > I cannot guarantee that the user will have an UNZIP at a new > z/OS job. = > > > /Tom Kern Just as an aside, the Java "jar" command can be used to create or "explode" ZIP type files. Most z/OS shops should have Java. It's free. jar xf some.file.zip will eXtract the files from soe.file.zip jar cf some.other.zip file1 file2 file3 ... Will create a ZIP file containing the files. I don't think it supports "legacy" z/OS datasets, only z/OS UNIX files. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it.
Re: CMS Files to XMIT compatible datastream
> What I would like to do is take a list of CMS files and package them > together as a single data file compatible with the TSO XMIT and Windows > XMIT-Manager programs. I have looked at the PIPELINES BLOCK NETDATA (I > am not that good a plumber) and at stacking NETDATA output files > together (SPOOL PUN CONT, NETDATA ... (NOSPOOL, SP PUN NOCONT CLOSE), > but this does not produce a usable XMIT file. > Does anyone have a procedure for combining multiple CMS files into a > single XMIT data file? Some combination of FILEDEF and MOVEFILE to make a PDS, then XMIT _that_, perhaps? De
Re: CMS Files to XMIT compatible datastream
The purpose is to have a datafile that can be transferred to a PC for archival to a CD/DVD and viewed with the XMIT Manager program under Windo ws and when the user gets a new job at a z/OS installation, the file can be uploaded to that system and properly used by the TSO RECEIVE command. I cannot guarantee that the user will have an UNZIP at a new z/OS job. /Tom Kern /301-903-2211 On Thu, 7 Aug 2008 09:13:58 -0700, Schuh, Richard <[EMAIL PROTECTED]> wrote : >How about PKZIP? > >Regards, >Richard Schuh > >> -Original Message- >> From: The IBM z/VM Operating System >> [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern >> Sent: Thursday, August 07, 2008 8:23 AM >> To: IBMVM@LISTSERV.UARK.EDU >> Subject: CMS Files to XMIT compatible datastream >> >> What I would like to do is take a list of CMS files and >> package them together as a single data file compatible with >> the TSO XMIT and Windows XMIT-Manager programs. I have looked >> at the PIPELINES BLOCK NETDATA (I am= >> >> not that good a plumber) and at stacking NETDATA output files >> together (SPOOL PUN CONT, NETDATA ... (NOSPOOL, SP PUN NOCONT >> CLOSE), but this doe= s not produce a usable XMIT file. >> >> Does anyone have a procedure for combining multiple CMS files >> into a sing= le XMIT data file? >> >> /Tom Kern >> /301-903-2211 >> > = ===
Re: CMS Files to XMIT compatible datastream
Kris, I'd be interested in that even if the OP isn't. Jerry Whitteridge Safeway Inc 925 951 4184 > -Original Message- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens > Sent: Thursday, August 07, 2008 9:29 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CMS Files to XMIT compatible datastream > > I sending the files in one MVS job that receives them automatically an > option? If yes, I've got a solution, I wrote such code for my former > client to transfer accounting and alike to MVS; punched some JCL to > call IKJEFT01 (that is TSO) with RECEIVE commands, and finally punched > the wanted CMS files using PIPE's NETDATA stage. > > 2008/8/7 Thomas Kern <[EMAIL PROTECTED]>: > > What I would like to do is take a list of CMS files and package them > > together as a single data file compatible with the TSO XMIT > and Windows > > XMIT-Manager programs. I have looked at the PIPELINES BLOCK > NETDATA (I am > > not that good a plumber) and at stacking NETDATA output > files together > > (SPOOL PUN CONT, NETDATA ... (NOSPOOL, SP PUN NOCONT > CLOSE), but this does > > not produce a usable XMIT file. > > > > Does anyone have a procedure for combining multiple CMS > files into a single > > XMIT data file? > > > > /Tom Kern > > /301-903-2211 > > > > > > -- > Kris Buelens, > IBM Belgium, VM customer support > > "Email Firewall" made the following annotations. -- Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ==
Re: CMS Files to XMIT compatible datastream
Hmm. If the package passes through RSCS, since RSCS doesn't support NETDATA with multiple datasets, won't the package get exploded on transmission? > Does anyone have a procedure for combining multiple CMS files into a sing > le > XMIT data file? > > /Tom Kern > /301-903-2211
Re: CMS Files to XMIT compatible datastream
I sending the files in one MVS job that receives them automatically an option? If yes, I've got a solution, I wrote such code for my former client to transfer accounting and alike to MVS; punched some JCL to call IKJEFT01 (that is TSO) with RECEIVE commands, and finally punched the wanted CMS files using PIPE's NETDATA stage. 2008/8/7 Thomas Kern <[EMAIL PROTECTED]>: > What I would like to do is take a list of CMS files and package them > together as a single data file compatible with the TSO XMIT and Windows > XMIT-Manager programs. I have looked at the PIPELINES BLOCK NETDATA (I am > not that good a plumber) and at stacking NETDATA output files together > (SPOOL PUN CONT, NETDATA ... (NOSPOOL, SP PUN NOCONT CLOSE), but this does > not produce a usable XMIT file. > > Does anyone have a procedure for combining multiple CMS files into a single > XMIT data file? > > /Tom Kern > /301-903-2211 > -- Kris Buelens, IBM Belgium, VM customer support
Re: CMS Files to XMIT compatible datastream
How about PKZIP? Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern > Sent: Thursday, August 07, 2008 8:23 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: CMS Files to XMIT compatible datastream > > What I would like to do is take a list of CMS files and > package them together as a single data file compatible with > the TSO XMIT and Windows XMIT-Manager programs. I have looked > at the PIPELINES BLOCK NETDATA (I am= > > not that good a plumber) and at stacking NETDATA output files > together (SPOOL PUN CONT, NETDATA ... (NOSPOOL, SP PUN NOCONT > CLOSE), but this doe= s not produce a usable XMIT file. > > Does anyone have a procedure for combining multiple CMS files > into a sing= le XMIT data file? > > /Tom Kern > /301-903-2211 >
