APS Alpha Pawn Software
Following are the steps to modify programs and then eventually update users.
1. Modify the latest version / edit number
2. Modify / enhance programs in DSK6:[101,101]
3. Test new programs AND update release notes and manual tasks.
4. Copy new/RUN programs to [27,*] distribution
5. On the user’s system transfer files
6. Distribute update to the user’s run accounts
Note, the AMOS format for a folder is DSK?:[Project, programmer] or just [PPn], in this document it is referred to as a folder, account, storage location. It will be documented as DSK6:[101,101], and in the PC format it is listed as ...>DSK6\101101\...
1. Modify the latest version / edit number
Defining the release and edit number, in the format M.Na(###) they are:
The M is a super major release
The N is a minor release, typically a bunch of new enhancements
The “a” letter increasing means that a file record layout has changed or been added and that a conversion routine must be run to update to this release.
The ### is the edit release, saying that something is changed / read the release notes to be aware of it.
For example, one of the options in the store setup routine might have a new value
an option did have two values: Yes or No, now it has three: Y, N, O.
The release notes are ordered in two sections, the first section starting from the latest release just describes the changes/enhancements in the release. The second section is the Manual changes needed to be done to install the release.
NOTE when updating a user always look on the Master Menu display screen (program PWN110) to know what their current release is. Then when going through the manual changes required make all changes after that release up to the latest.
First log into the [101,101] Ppn
LOG 101,101
To start a new edit number of a new release, modify the file:
VUE PROGRM.MAP
and change the current
MAP1 PVER ,S,13,"Ver 6.3B(234)"
MAP1 PROGMM ,B,2,60
PROGRAM P,6.3B(234)
from (234) to (235) in the two places. Further down add a new edit line and describe what is being modified. Follow the pattern on the new edit line for 234, put in today’s date as the date it was released.
Always recompile PWN110, the master menu display screen. It shows the new release number.
There are four Ppns where programs *.BAS, file variable definitions *.MAP, and *.SUB subroutines are stored. They are:
[101,101] all latest BAS, MAP, and SUB files
the following three libraries have the file types with an edit number
that was used BEFORE a change was made.
[101,102] previous versions of the BAS programs
[101,103] previous versions of the MAP files
[101,104] previous versions of the SUB files
In the examples below, the sample program will be PWN150.BAS and the MAP or SUB file
will be named SPRINT.MAP and SPRINT.SUB
PWN150 will have some major changes made to it. First find out the version that PWN150 is currently running with:
DIR PWN150.RUN[]/V
The display will respond with a version and edit number in DSK6:[101,0]
6.1A(215)
Note the current edit is going from (234) to (235), so this program has not been modified in a long time. So copy the BAS version to the library with the 215 edit number:
COPY *.215[101,102]=PWN140.BAS
In prepareing to make a major change to a MAP or SUB, note there is not a version
associated with it, use the old edit number in the copy statement to each library:
COPY *.234[101,103]=SPRINT.MAP
COPY *.234[101,104]=SPRINT.SUB
2. Modify / enhance programs in DSK6:[101,101]
Create a new program or enhance an existing one as needed in a specific program. Typically this is done withVUE, when exiting VUE the G exit will compile the program.
3. Test new programs then update release notes and manual tasks
Log to [101,201] Texas jurisdiction, or [101,2??] other jurisdictions and execute the program:
RUN PWN150[101,101]
Continue on steps 2 and 3 until testing is complete, then use the MR (move runs) command to move all the new RUN programs to [101,0]:
MR
4. Copy new/RUN programs to [27,*] distribution
When all enhancements have been made and the new release is ready to be distributed, use X from any menu and then enter the command:
COPY APSRUN:*.*=APSLIB:*.RUN
then run the following command to make a directory of hash totals for each file:
MAKDIR
This creates the file RUN.DIR, it will be looked at on the user system to verify that the programs have been copied to the user system correctly.
5. On the user’s system transfer files.
Using Team Viewer transfer to the user’s system:
all the [27,*] folders and files, c:\vm\miame\dsk0\027000\
the user documentation in c:\users\owner\documents\sbc business\APS ver 6 user docs
to the user’s documentation folder c:\……….\documents\APS Docs\
Click on the APS icon, this will bring up the APS master menu. In the upper right corner of the screen will be the current release number. Write it down here _______
Then from the menu enter the letter “X”, this will exit the program and display the Ashell prompt, typically it is “APS.”. Log to [27,0] and verify that the programs go loaded correctly:
LOG 27,0
enter the command:
VERIFY RUN.DIR
This will check that each program got loaded correctly. If any errors are displayed at the end and the screen displayed too fast, re-run with:
PAGE VERIFY RUN.DIR
this will stop at each screen full to allow a visual check to see which file had an error.
Figure out why there is an error and repeat the download and verification until no errors are displayed.
6. Distribute update to the user’s run accounts
Log to the run account load the new programs and make any manual changes:
LOG APSLIB:
Rename the old programs to save them:
RENAME .OLD = *.RUN
Then copy the new programs:
COPY APSLIB:*.* = APSLOD:*.RUN
Open the release notes and in the manual tasks section, find the place that is the release/edit number of the current user. Read up from there doing each task necessary to bring the user up to the release just loaded.
Edit the document:
APS System 04 Users APS version and date
Update the user’s information with the APS release number and date
*** End of APS System 21 programming and update ***
