That's right.. should have remembered my own trials with FCOPY files ... as Bruce suggested -- unless the DB2 folks do something to make it fixed length (Like COPYFILE (PACK) -- this just won't work.
Ed - you should let the DB2 folks know it isn't possible to use FCOPY files when you have to download to your workstation and then upload. They should really go with a VMARC envelope instead and avoid FCOPY for something like this. Scott On Wed, Dec 9, 2009 at 2:31 PM, Kris Buelens <kris.buel...@gmail.com> wrote: > A binary file can never be transferred to a workstation and back if it is > RECFM V. Just technically impossible, unless using special transfer > programs that add the recordlength in front of each record (and strip that > back off when uploading to VM). ALMCOPY was such a beast. FTP nor IND$FILE > do that. > > 2009/12/9 Scott Rohling <scott.rohl...@gmail.com> > > Try transferring without the fixed 1024 specification... it should be >> variable when it gets to z/VM >> >> Scott >> >> >> On Wed, Dec 9, 2009 at 2:05 PM, Ed Zell <ewz...@illinoismutual.com>wrote: >> >>> I am getting DMSCPY068E Input file CLIVM740 PACKENG A1 not in packed >>> format >>> >>> >>> listfile clivm740 packeng a (all >>> >>> FILENAME FILETYPE FM FORMAT LRECL RECS BLOCKS >>> >>> CLIVM740 PACKENG A1 F 1024 204 51 >>> >>> >>> >>> This is after doing FTP with BINARY FIX 1024 >>> >>> And Roland, no, I did not receive CLIVM README file with any >>> instructions. >>> >>> I am trying to solve a -833 referenced by PQ80184 where I need to receive >>> the >>> English version of the stored procedures to load into DB2 7.4. >>> >>> If I am missing something simple, I apologize, but I can’t seem to >>> process the file >>> from support. >>> >>> Ed >>> >>> >>> >>> >>> >>> >>> ------------------------------ >>> >>> *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On >>> Behalf Of *Roland P. Chung >>> *Sent:* Wednesday, December 09, 2009 2:54 PM >>> >>> *To:* IBMVM@LISTSERV.UARK.EDU >>> *Subject:* Re: FCOPY help >>> >>> >>> >>> Ops, Bruce is correct that the FCOPY packlib files are in variable length >>> format. The FCOPY'ed file must have been COPYFILE (PACKed. >>> >>> Then you should PC transfer the file to CMS disk using Binary Fixed 1024, >>> >>> then, COPYFILE (UNP OLDD >>> then, FCOPY fn ft fm (list to find out the members in the >>> paclib (28 of them) >>> >>> then use SEL to fetch the file out to your CMS disk. >>> >>> BTW, you should have a TXT file called CLIVM README for instructions on >>> how to install it. Don't you? >>> >>> ....Roland >>> >>> --- On *Wed, 12/9/09, Bruce Hayden <bjhay...@gmail.com>* wrote: >>> >>> >>> From: Bruce Hayden <bjhay...@gmail.com> >>> Subject: Re: FCOPY help >>> To: IBMVM@LISTSERV.UARK.EDU >>> Date: Wednesday, December 9, 2009, 8:26 PM >>> >>> FCOPY packlib files are in variable length format, and you lose the >>> record structure when you upload it from a PC. I don't know how you >>> could reconstruct the file in the correct format so that FCOPY would >>> accept it. If the DB2 people would use COPYFILE (PACK on the packlib >>> first, then you could upload as Fixed 1024, use COPYFILE to unpack, >>> then extract the files using FCOPY. >>> >>> >>> >>> >>> >>> >>> >>> *Confidentiality:* This e-mail (including any attachments) may contain >>> confidential, proprietary and privileged information, and unauthorized >>> disclosure or use is prohibited. If you receive this e-mail in error, >>> please notify the sender and delete this e-mail from your system. >>> >> >> > > > -- > Kris Buelens, > IBM Belgium, VM customer support >
