I have created the text file Qhtmlsrc. But my subprocedure gets a
compilation error because it doesn't see the text file external description.
Is there some way of compiling the text file??


----- Original Message -----
From: "Mark A. Manske" <mmanske@minter-weisman.com>
To: <web400@midrange.com>
Sent: Tuesday, April 23, 2002 3:55 PM
Subject: RE: [WEB400] Writing Source Member to Web Page


> It is just a source physical file, they have many records for each member,
> or can have one record,
> but you read in by member for the file - here is a code snippet.
>
> C                   eval      Library   = '*LIBL     '
> C                   eval      TheFile   = 'QHTMLSRC  '
> C                   eval      SrcMembr  = 'SIGNINERR '
> C                   CALLP     #WrtSrcMbr(Library:TheFile:SrcMembr)
>
> I use a procedure to do the writing - here is a snippet of the source in
> that memeber -
> keep in mind I have a large source physical file, so these are "cut-off"
>
> but I hope this gives you the genearal idea
>
>
> 0001.00 <html>
> 0002.00
> 0003.00 <head>
> 0004.00 <meta http-equiv="Content-Type" content="text/html;
>
> 0025.00 <p>
> 0026.00   <a href="http://www.minter-weisman.com/";>
> 0027.00    <img src="/_derived/home_cmp_minter110_gbtn.gif" width="95
> 0028.00     align="middle"></a>
> 0029.00 </p>
> 0030.00
> 0031.00 <p> <img src="/_derived/signon.htm_cmp_minter110_bnr.gif" wid
> 0032.00  </p>
>
> Here too is a "picture of that source physical file as seen through the
> eyes of pdm:
>
>
>  File  . . . . . .   QHTMLSRC
>    Library . . . .     CGIDEV               Position to  . . . . .
>
>  Type options, press Enter.
>   2=Edit         3=Copy  4=Delete 5=Display       6=Print     7=Rename
>   8=Display description  9=Save  13=Change text  14=Compile  15=Create
modu
>
>  Opt  Member      Type        Text
>       SIGNINERR   TXT         sign in error HTML
>       SR_ORDER    TXT         Sales Rep/order status inquiry HTML
>       SR_ORDERXX  TXT_DEAD    Sales Rep/order status inquiry HTML
>       SRP         TXT         SRP password menu HTML
>       SRP_C       TXT         SRP ITEM Selection menu HTML
>       SRP_C_B     TXT         SRP ITEM Selection menu HTML
>       SRP_C_B_NO  TXT         SRP ITEM Selection menu HTML
>       SRP_C_B_NX  TXT         SRP ITEM Selection menu HTML (no mass
button)
>
> HTH
> Mark
>
> -----Original Message-----
> From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On
> Behalf Of Justin Houchin
> Sent: Tuesday, April 23, 2002 3:35 PM
> To: web400@midrange.com
> Subject: Re: [WEB400] Writing Source Member to Web Page
>
>
> Does the file have a record? I am still confused.
>
> Justin
> ----- Original Message -----
> From: "Mark A. Manske" <mmanske@minter-weisman.com>
> To: <web400@midrange.com>
> Sent: Tuesday, April 23, 2002 2:41 PM
> Subject: RE: [WEB400] Writing Source Member to Web Page
>
>
> > As for myself, without looking back at the book, I placed my source
stuff
> > in a member of source physical file qhtmlsrc which I built as 240 bytes
> > "wide"
> > I placed that source file in both of my libraries (I have one for
> > development
> > and one for live web serving) on two separate ports.  This has worked
out
> > very
> > nicely to test new things, and to test changes before I roll them out to
> the
> > rest of the world.
> >
> > HTH
> > Mark
> >
> > -----Original Message-----
> > From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On
> > Behalf Of Justin Houchin
> > Sent: Tuesday, April 23, 2002 2:30 PM
> > To: web400@midrange.com
> > Subject: [WEB400] Writing Source Member to Web Page
> >
> >
> > This is a multi-part message in MIME format.
> > --
> > [ Picked text/plain from multipart/alternative ]
> > Hi Everyone,
> >     I am trying to use Brad Stone's Write to Source Member Procedure and
> am
> > having some problems. Is the file I am supposed to be storing the
> JavaScript
> > or HTML data a PF or text?
> >
> > Thanks,
> >
> > Justin Houchin
> > Programmer
> > Reliatek, Inc
> > jhouchin9@charter.net
> > _______________________________________________
> > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> > To post a message email: WEB400@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> > or email: WEB400-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/web400.
> >
> >
> > _______________________________________________
> > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> > To post a message email: WEB400@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> > or email: WEB400-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/web400.
> >
> >
>
>
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
>
>
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.
>
>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.