The characters may be coming from a default environment file for the
printer. When I send
output to an http server I bypass the spooler with the following JCL:


!JOB jobhttp,MANAGER.ACCT
:SETVAR PRE,"PRE"
:SETVAR LT, "<"
:SETVAR GT, ">"
:PURGE HTTPFILE
:BUILD HTTPFILE;REC=-132,,F,ASCII;DISC=100000
:FILE PRINTER=HTTPFILE,OLD;DEV=DISC;ACC=APPEND
:ECHO !!!LT!PRE!!!GT >*PRINTER
:ECHO !hpdatef >*PRINTER
:RUN RPTXYZ
:LISTF HTTPFILE,2
!ftp.arpa.sys
open 1.0.1.4
user HP3000JOBS
PASS3K
cd d:\SERVER\PUBLIC\WWW\HTML\ROOT
del XYZRPT.htm
put HTTPFILE XYZRPT.htm
quit
!EOJ

----------
> From: Edie Houston <[log in to unmask]>
> Subject:      A strange one.........
> To: [log in to unmask]
>
> I hope someone out there has some experience with this....
>
> We have nightly reports that run on our HP3000/949 (using IX5.5).  These
> are a mixture
> of CA/Manman canned reports and Powerhouse Quiz.  We have been making
them
> available to users through the Maui Online Reporting System.  We want to
> port them (or I should say some of them) to our Intranet which is housed
on
> an NT box (NT4.0). The reports will be viewed using (the dreaded) IE3.0.
>
> I am transferring the files from the HP to NT via FTP in ASCII mode.  The
> transfer happens fine.  I can access the files via the network and read
> them just fine.  When we try to access them using IE3.0 we get an error
> message "IE is unable to open this file".  We thought that it was a
> security issue but that does not prove to be the case.  There is
"garbage"
> (about 10 characters) in front of each line of the file so IE doesn't
> recognize it as a text file.  This garbage is not visible in Edit3000,
nor
> is it visible in Notepad (or any other text editor) on the local PC, it
is
> only visible in Notepad on the NT Server.  I have tried transferring the
> report as a spoolfile and as a disc file.  I have tried transferring as
> type ASCII and type binary.  I have also tried transferring as "nocctl".
> Depending on which way I transfer I either end up with a file that
includes
> "garbage" or a file that is one long continuous line of characters.  In
> either case the file isn't usable by the end user.
> The only thing I haven't tried is "buildparms" because I am advised NT
> doesn't accept them.  I am only just starting to learn NT so I accept
this
> for now.
>
> Has anyone out there had any experience with this type of transfer?  How
> have you overcome the problems?  My supervisor insists there must be a
way
> to do it, and I am
> inclined to agree.