Category: Programming

I copied the web- and development environment to Daphne. There were a few things I needed to solve before the projects (WGLIB and WGCMS) compiled, but once that was done, I could start testing the bunch again, with the adapted file specifications. First, emulate the CGI interface and that seemed fine. Next accessing it via the web: In itself it did work properly, just not as a webpage….

No way to understand what was wrong: typing the template was no problem:

$ type cmsdata:wwwheader.txt
HEADER_ID=WWWHEADER
DESCRIPTION=HEADER for HTML - main page
LINES=26
Status: 200
X-Powered-By: WG_WEBPAGE 0.3
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Content-type: text/html; charset=UTF-8

< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

www.grootersnet.nl


ENDHEADER
$

the first three and last line are used by the library routines – the ‘real’ part is lines 4..29, and I would expect see the rendering of line:

www.grootersnet.nl

but in stead, it showed me:

Status: 200
X-Powered-By: WG_WEBPAGE 0.3
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Content-type: text/html; charset=UTF-8

< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

www.grootersnet.nl

as text….

But why? This should be a copy of what is on Diana and Dione. Well, there IS a difference:

$ type cmsdata:wwwheader.txt
HEADER_ID=WWWHEADER
DESCRIPTION=HEADER for HTML - main page
LINES=26
Status: 200
X-Powered-By: WG_WEBPAGE 0.3
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Content-type: text/html; charset=UTF-8
..
..
< !DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


What are these dots?

Dump showed the difference:


50206C6D 74682045 50595443 4F44213C 00790000 00000000 0000382D 4654553D =UTF-8........y.< !DOCTYPE html P 0000E0                                         ^^^^ ^^^^^^^^ ^^^^^                   ^^^^^^^^

where it should read:

50206C6D 74682045 50595443 4F44213C 00790A0D 00020A0D 0002382D 4654553D =UTF-8........y.< !DOCTYPE html P 0000E0                                         ^^^^ ^^^^^^^^ ^^^^                    ^^^^^^^^

Simply <RETURN> to create an 'empty' line is not enough! CRLF (0A0D) muts be added EXPLICITELY (CTRL-V + CTRL-M, CTRL-V + CTRL-J) before <RETURN> - on VMS. be aware if you edit these files on PC and copy them to VMS, be sure to use BINARY - because ASCII will remove the required CRLF. I couldn't test this with VMS-IDE; though I could edit the files (not sure whether it worked..) but I don't upload .txt files....

To prevent problems during further development I moved all development to Daphne – the 512Mb PWS. It contained just a 4Gb system disk, but I added two IDE disks left over from
older PC’s: one of 14Gb and one of 120Gb. The development environment from Diana has been copied to this 14Gb disk. Of course I had to make some adjustments to the startup procedure of Daphne to facilitate the environment and made a few changes to the procedures that set all logicals – and ran into Job-table restrictions: JTQuota were just 4096 bytes and needed to be raised to 10.000 for both SYSTEM and user. And I had to play with security to be able to edit files.
In the end, it turned out that just one (system) file was located on a different location, but that is easily tackled by setting the logical referring to this file to the right location. Added clean-up procedure for WGIB (and recreate the object libraries), and now the program compiles. To run it, protection still needed some adjustments: on Diana the user I use is member of the SYSTEM group, on Daphne it is a normal user (as it should be) so some files could not be accessed – but the same file resides in the development environment: just edit the configuration file, and the program can be run as a normal user. so I can now get on with development and testing without interfering with the production environment.

With some last changes: error trapping and handling, conditional logging and basic documentation, the new version of the CMS-presenter has been activated, including some changes to the template: Cleaned HTML, removed obsolete functionality (display of currrent date and time: For some reason these didn’t show up anymore).
Next step is an easier adding of new content (first adding data written to a text file, a web-based version after an FMS-based local one?), adding title to the configuration file and reading links from a file. Once that is done, the next stap is using the latest file definitions: it is not that much different, but will offer more flexibility: reading next and previous post, and link post to category and tags.