Integrating Context Manager into your BTOS application
920608-elp01
INTRODUCTION:
=============
This Technical Support Knowledgebase entry describes how to
integrate your application with Context Manager in the BTOS/CTOS
environment.
WHY YOU NEED TO DO THIS:
========================
Context Manager provides a convenient tool for building "hot-key"
toggles among various applications and software utilities for BTOS/
CTOS users. Rather than just providing an Executive session for
the operating system to get to PROGRESS, and rather than just
providing a toggle hot-key into PROGRESS, building a true Context
Manager command allows the system administrator to provide all
the startup options a user needs to access a particular
database and pass in the desired startup parameters.
PROCEDURAL APPROACH:
====================
There are several steps you need to follow to
set up a Context Manager configuration to start a PROGRESS
client session, connect to a specific database, and use the
intended startup options.
First, you need to build a parameter file for PROGRESS. Second, you
need to build a SUBMIT file that invokes the PROGRESS command
and uses that startup parameter file. Third, you need to
configure Context Manager to run your submit file. Each step
should be tested thoroughly before moving on to the next one.
This Knowledgebase entry assumes that you are already configured
to use Context Manager.
The following sections provide detials on how to perform these steps.
CREATING A PARAMETER FILE. Execute the PROGRESS 4GL command
to get into PROGRESS. From the Dictionary, select Utilities,
and from there, select Editor for Parameter Files. Enter the
name of the parameter file when prompted. It is generally a
good idea to put the parameter file in the same volume and
directory as the database, e.g., [sys]<dlc>demo.pf. The editor
guides you through the available startup options and writes
them to an ASCII file in the correct format. Include the
name of the database, fully qualified with volume and directory
(but do not use the ".db" extention). Include all the CLIENT
startup options you need, such as Editor Buffer (-e) and Local
Buffer Size (-l).
CREATING A SUBMIT FILE. Use the RECORD command at the Executive
to log your keystrokes in a submit file. This submit file must
reside in the [sys]<sys> directory for Context Manager to find it.
Record
File to record on [sys]<sys>Start4GL.SUB
<GO>
Next, type in the command to start a PROGRESS session manually,
and include the name of your parameter file.
PROGRESS 4GL
[Parameter File List -pf] [sys]<dlc>demo.pf
<GO>
This tests the validity of the entries in your parameter file.
Once you get into the PROGRESS editor for your application,
QUIT out immediately and get back to the Executive. Then
enter the command:
STOP RECORD
<GO>
Use the BTOS/CTOS EDITOR command to view your submit file:
EDITOR
[File name(s)] [sys]<sys>Start4GL.SUB
[Read only?]
[Alternate user name]
[Starting line number]
Remove the tail end of the submit file, which shows your
"STOP RECORD<GO>" keystrokes, and save the changes.
Test your submit file by using the Executive SUBMIT command
and passing in the name of the submit file you just created. If
you can again get in to PROGRESS for your database, you are
ready for the next step.
EDITING THE CONTEXT MANAGER CONFIGURATION FILE. Use the
CM Editor to edit your Context Manager configuration file. The
default filename is: [sys]<sys>cmconfig.sys.
Enter the name of the submit file as the name of the Context
Command, e.g., "Start4GL". Create a new Context definition (F5)
and give it the Run file name of [sys]<sys>SubCmd.Run, and the
amount of memory required to run PROGRESS with your startup
options (see note below for memory amount guidelines). Other
parameters for the command, such as a command key, are optional.
Save the changes to the cmconfig.sys file and reboot your system.
Start the server for your database, and run the Install Context
Manager command. You will then see your new Context, and
invoking it will get you right into PROGRESS with just the
press of a keystroke!
OTHER NOTES:
============
- PROGRESS SERVERS MUST BE STARTED BEFORE YOU INSTALL CONTEXT MANAGER
ON THE MASTER WORKSTATION. YOU WILL RECEIVE A
SYSTEM ERROR IF YOU TRY TO START A SERVER ON A PROCESSOR THAT
ALREADY HAS CONTEXT MANAGER INSTALLED. You can start the
server either automatically in the [sys]<sys>sysinit.jcl file
at boot up time, or manually from the Executive command line.
If you also want to have Context Manager installed automatically,
make sure it follows the PROGRESS command, [sys]<dlc>proserv.run,
in the sysinit.jcl file.
- Context Manager IS REQUIRED to run operating system utilities
(other than the CTOS OS commands) from within PROGRESS, such
as running QUOTER, which is used in the Dictionary/Admin/
Import (foreign data formats) function.
- When defining a partition to run PROGRESS in, it must be large
enough to execute PROGRESS with all of your client startup
parameters. Check the size of your partition for the
Executive itself. If the partition is large enough that you can
manually execute PROGRESS, then it is large enough for PROGRESS to
be invoked by the submit file.
- Maintaining the startup is easily done by modifying the
parameter file called by the SUBMIT routine. You do not
need to re-define the Context in order to modify performance
startup parameters, for example.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
See System Administration II: General, section 2.3.1.
See also PROGRESS CTOS System Administration Seminar Student Guide.
See also Unisys' System Administration documentation
for Context Manager.
Progress Software Technical Support Note # 5175