Cecil
A couple of points:
1 - you indicate that you will have 18 million records, you file
equation says 10 million
2 - a look at the IMB JCL would be valuable, how are those records
blocked - you would only need that may 'blocks' on the HP side.
3 - specifying a file as ASCII does no translation, the file will still
be EBCIDIC unless the IBM converted it.
4 - On data conversion, is all of your data in DISPLAY format, that is
no BINARY or PACKED-DECIMAL fields
5 - FCOPY is a compatibility mode program, and as such will use FOPEN,
not HPFOPEN to open any new files. It will be
bound by the limitations of that intrinsic. I believe this also
applies to the BUILD command. You may need to write
a small native mode program that calls 'HPFOPEN' with the file
parameters you need to establish the file.
6 - Can you have the IBM folks send the file in smaller, more manageable
pieces. You can do this if you cannot write the
program mentioned above.
Hope this helps some, any questions please feel free to email or call
Bob Schlosser
Harris Corporation
Melbourne, FL.
(407) 727-5893
-----Original Message-----
From: Ceceil Barbarino [SMTP:[log in to unmask]]
Sent: Thursday, May 27, 1999 10: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:
|
