I have been using my target VM system as the client. If I use my pc as a 
stepping stone, I prefer to use it as an FTP client to upload to my VM system.

Have the VMARC files been updated with the latest and greatest?

Regards, 
Richard Schuh 

 

> -----Original Message-----
> From: CMSTSO Pipelines Discussion List 
> [mailto:[email protected]] On Behalf Of Paul Gilmartin
> Sent: Wednesday, July 14, 2010 3:12 PM
> To: [email protected]
> Subject: Re: CMS Pipelines 1.1.12/0006 and manual available
> 
> On 07/14/10 14:46, Rob van der Heij wrote:
> > On Wed, Jul 14, 2010 at 10:28 PM, Schuh, Richard 
> <[email protected]> wrote:
> >
> >
> >> The MODE B doesn't seem to work for me. I get a message 
> saying that it isn't supported.
> >>
> >
> > That only works among adults... VM (or MVS) on the client 
> side. If you 
> > need to use your PC as stepping stone, you download "bin" and then 
> > upload as "FIX 1024" (you may need "quote site fix 1024" 
> with FTP, or 
> > specify that in your termulator when using IND$FILE). If 
> you forget, 
> > it can be repaired with "fblock 1024"
> >
> >
> Or, a trick.  Connect to Marist and issue:
> 
>     ftp> binary
>     200 Representation type is IMAGE.
>     ftp> quote type e
>     200 Representation type is EBCDIC.
>     ftp> quote mode b
>     200 Data transfer mode is Block.
> 
>     get what.ever
> 
> Then connect to your target VM system and issue the same 
> binary; type; mode,
> then:
> 
>     put what.ever
> 
> >> 550 Command failed: SFS system error; DMSEXIDI rc 8 reason 74000
> >>
> >
> > And that's "file not found" - it's PIPELINE.MODULE, no VMARC.
> >
> >
> Ummm... I see:
> 
> ftp> pwd
> 257 "ACADEM:PIPELINE.EWEB" is working directory
> ftp>
> ftp> dir *.vmarc
> 200 Port request OK.
> 125 List started OK
> ANYOF    VMARC    F         80        110          3 
> 2003-11-01 02:44:28 -
> DATECONV VMARC    F         80       1406         28 
> 1998-08-24 17:44:33 -
> DJONES   VMARC    F         80        279          6 
> 1998-07-15 11:55:26 -
> JPH50    VMARC    F         80     113997       2227 
> 1996-08-13 15:34:20 -
> LP3820   VMARC    F         80       5184        102 
> 1997-03-01 16:09:24 -
> MTREXX   VMARC    F         80        344          7 
> 1997-10-21 17:31:52 -
> NXPIPE   VMARC    F         80       7791        153 
> 2010-07-12 07:32:35 -
> PDUPDT   VMARC    F         80        184          4 
> 1997-11-12 09:32:35 -
> PICKPIPE VMARC    F         80        421          9 
> 1997-11-10 18:45:24 -
> PIPAPERS VMARC    F         80      65903       1288 
> 2000-10-31 18:08:33 -
> PIPDIAG  VMARC    F         80       7853        154 
> 2010-02-11 06:18:56 -
> PIPEDEMO VMARC    F         80        504         10 
> 1996-07-07 13:48:02 -
> PIPESERV VMARC    F         80      10252        201 
> 2002-05-16 12:40:15 -
> POPEN    VMARC    F         80        788         16 
> 2002-09-18 11:01:55 -
> PWB      VMARC    F         80       4024         79 
> 1998-04-06 06:49:31 -
> PX3270   VMARC    F         80        366          8 
> 1996-06-19 05:51:39 -
> RMHLUP   VMARC    F         80        109          3 
> 2000-06-07 07:07:22 -
> RTDOC    VMARC    F         80      68069       1330 
> 2010-07-03 05:36:21 -
> RUNTIME  VMARC    F         80      25926        507 
> 2010-07-03 05:36:15 -
> SPAWNER  VMARC    F         80         98          2 
> 1998-10-01 12:02:05 -
> WEENYWEB VMARC    F         80        154          3 
> 2000-06-11 06:57:06 -
> 250 List completed successfully.
> 
> ... and when the VMARC exists I prefer to get it and unpack 
> it because it restores the original timestamp.  One more bit 
> of audit trail.
> 
> And:
> 
> ftp> get nxpipe.vmarc
> 200 Port request OK.
> 550 Command failed: SFS system error; DMSEXIDI rc   8 reason  74000
> ftp>
> ftp> get none.such
> 200 Port request OK.
> 550 File 'none such'  not found
> 
> ... the SFS system error seems to quite different from "file 
> not found".
> 
> -- gil
> 

Reply via email to