Nomad and HTTP and CGI, Oh My!

Part II: Installation

There are at least 3 methods of installing these packages

The Official Method
The Quick and Dirty Method
The "Gee, I'm not sure I'm supposed to do this" Method

I'm not going to cover the official method. There is plenty of information included in the VMARC files for each of these products. Additional information may be available at the various products' homepages.

I am going to provide a Quick and Dirty installation method because the purpose of this series is to show how easy all this stuff is and if I got bogged down in shared segment mapping then it would start to look complex.

I'll also cover some "Gee, I've only got a class G userid" installation tips, but if you bring down an International Banking System, I had nothing to do with it! Honestly, if you're hesitant, I'm the last guy you want to take systems advice from.

A word about the author

I work for a small company with a small VM system. Working on a small system allows me great freedom in experimenting with new technologies. Unfortunately, it also means I have no concept of large systems issues such as product/project ownership. Also, spending a lot of time working with new technologies often means I have no idea what I'm doing. Keep this in mind when deciding if you really want to install a rogue webserver under your individual Class G userid. You really should have the blessings of your system administrator. On the other hand, since it can be installed from a Class G ID and it will run from a Class G ID, you know it's pretty safe.

I assume TCP/IP for VM is installed and that you have access to a web-capable workstation that has a TCP/IP connection to the VM system.

You'll need to create a standard CMS userid with class G privileges and a 191 minidisk of 10 3380-cylinders (or equivalent) . If you don't have the ability to create userids you can release your 191 disk and bring in 10 cylinders of T-Disk as your A disk (but that means you're starting to look like installation method #3 above.)

Use your favorite PC-to-VM transfer method to upload VMARC MODPACK to the new 191 disk as a binary file with RECFM F LRECL 1024.

Copy VMARC MODPACK to VMARC MODULE using the "unpack" option.
	COPY VMARC MODPACK A VMARC MODULE A (UNPACK

Again use your PC-to-VM transfer method to upload RXSOCKET VMARC (Rexx Sockets) to the new 191 as a binary file with RECFM F LRECL 80.

Use VMARC to extract the various parts of RXSOCKET to the new 191
	VMARC UNPK RXSOCKET VMARC A = = A

Upload RUNTIME VMARC (CMS Pipelines) to the 191 as binary, RECFM F LRECL 80.

Again use VMARC to extract the various parts of CMS Pipelines to the 191
	VMARC UNPK RUNTIME VMARC A = = A

Upload CMSHTTPD VMARC (Webshare) also as binary, RECFM F LRECL 80.

Use VMARC to extract Webshare to the 191
	VMARC UNPK CMSHTTPD VMARC A = = A

That's it! You've just installed a VM web server!

Back	Next... Testing and Configuring
Feel free to send questions or other feedback to me, also drop me a line if you'd like e-mail notification of new installments in this series.

Nomad and HTTP and CGI, Oh My!

©1997 Don DeCosta, All Rights Reserved