HP3000-L Archives

May 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Peckham, Brenda" <[log in to unmask]>
Reply To:
Peckham, Brenda
Date:
Thu, 27 May 1999 10:27:11 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
Cecil,
   Are your IBM people SURE there are no FTP capabilities available?
We are doing transfers to an IBM mainframe from an HP3000 and visa
versa.  (This is a fairly recent development however, the IBM FTP
implementation is fairly new).
   Most operating systems now have FTP implementations, including IBM.
If you can get FTP for IBM, you can install a 100MB network card on your
HP3000 and go for it!

> Brenda Peckham
Pacific Life
My opinions are my own and in no way reflect those of Pacific Life.

> -----Original Message-----
> From: Ceceil Barbarino [SMTP:[log in to unmask]]
> Sent: Thursday, May 27, 1999 7:44 AM
> To:   [log in to unmask]
> Subject:      File transfer between Mainframe & HP3000
>
> Hello (this is a long one please bare with me):
>
> Is anyone out there familiar with a Bus-Tech Datablaster??? We
> currently
> have this set up between our Mainframe and HP 3000/997/500 when we do
> a
> 'blast' from the Mainframe to the HP it is painfully slow - we are in
> a
> quandry we have to pass a 18,000,000 record file from the Mainframe to
> the
> HP and we are looking for ways to get this process to work faster.
> Unfortunately there are no FTP capabilities on the Mainframe.  So we
> are
> stuck with the datablaster.
>
> I have been trying a multitude of options, and my mainframe people
> keep
> telling me if I can increase my 'blocking factor' the process should
> go
> faster, I keep explaining to them that the HP doesn't really care
> about
> blocking factor. After more discussion, I was told to set my REC= to
> the
> blocking factor on the Mainframe; ok, I can do that, of course what
> happens
> next is 'EXTENT SIZE EXCEEDS MAXIMUM'  if I don't use the DISC= on my
> FCOPY
> the command works, but defaults to the 1023 file size.
>
> I've included the JCL from the job that runs on the HP, this runs
> simultaneously with a job on the Mainframe to get the file
> transferred. If
> anyone knows anything, well you will be helping a truly frazzled human
> being!
>
> Thanks,  Ceceil Barbarino
>
> HP Job:
> !JOB CBCONV2,MGR.SGAII;OUTCLASS=LP,1
> !COMMENT   ***  ONE SHOT CONVERSION FILE BLAST ROUTINE ****
> !COMMENT   TRANSFER OF FILES AS IT IS BEING TRANSLATED
> !COMMENT   FROM EBCDIC TO ASCII
> !COMMENT   This process is using the mainframe block size
> !COMMENT   as the record length.
> !TELLOP
> !TELLOP MAKE SURE THE MAINFRAME PROCESS IS STARTED
> !TELLOP
> !TELLOP
> !PURGE CBCONV3.CBARBAR1
> !FILE BLAST;DEV=40;REC=-32618,1,F,ASCII
> !BUILD CBCONV3.CBARBAR1;REC=-32618,1,F,ASCII;DISC=10000000
> !FCOPY FROM=*BLAST;TO=CBCONV3.CBARBAR1
> !TELLOP
> !TELLOP  BLAST PROCESS COMPLETE.
> !TELLOP
> !EOJ
> ______________
>
> Mainframe:

ATOM RSS1 RSS2