System 1032
By Tym Stegner
An often-ignored or underused feature of System 1032 is the System 1032 error log. This text-based file is named S1032LOG.ERR; the S1032_ERR system logical points to it. Each process appends entries into the common error log file; a form-feed character separates the entries.
The System 1032 error log is a repository of events occurring within System 1032 sessions, such as image aborts caused by the user pressing Control-Y, and significant error events such as BUGCHK and ACCVIO. This information, written by System 1032 error handlers, is used by CCA Customer Support to assist you in determining the cause of your errors. However, much of the information recorded is also of direct use to a knowledgeable System 1032 user or administrator.
The System 1032 error log is comprised of the following sections:
This article describes each of these sections.
Heading
The heading (see Figure 1) describes the hardware and operating system environment of the event, and also serves to separate one event from another in the error log.
Items identified include the version of System 1032, date, time, process name, ID and username, terminal, process mode, node name, hardware type, operating system version, and cluster status.
Figure 1. System 1032 error log heading
Event information
Event information includes the full text of the reported event, as you would have seen it, including all system and register information. CCA Customer Support often asks for the full error message being reported.
Boot image name
The name of the program executing at the time of the event is called the boot image. S1032.EXE is the name of the system default boot image.
Process quotas and working set
You might find the process quotas and working set section the most useful section of the error log. The process quotas and working set section shows the process quotas assigned to the event process, and how much of these quotas remain at the time of the event. This data very often shows that a process quota has been reached, thus causing or contributing to the event. Keep in mind that ‘Page File’ is by far the most common limit exceeded.
BEER code
The back end execution routine (BEER) code number identifies the System 1032 command currently executing at the time of the event. For example:
Back end execution routine code number 30 active.
The code numbers can be referenced in the BEERCODES.DAT file, which is located in the directory pointed to by the S1032_LIB system logical. The previous example illustrates that 30 represents the EXIT command.
Update file list
A list of the System 1032 files currently open for update, including datasets, databases, and libraries comprises the update file list section. Each keyed attribute within the dataset is considered an updateable file. This data identifies which datasets might be damaged as part of the event.
Command group buffer
The contents of the entire current command group are held in the command group buffer, which might appear as follows:
COMMAND group buffer: <K1> <K2>U<K3>SE <K4>X<K5>; <K6><0D><K7>;<K8>
The values of <Knn> are the System 1032 parse points of the command compilation. The data identifies which command group within the current program is the source of the event. Note that this command buffer can often be lengthy.
DM_BEGIN address
The address of the startup routine for System 1032 within the executing image is the DM_BEGIN address. CCA Customer Support can use this data to determine offsets into the System 1032 executable code to track down the event location.
Internal structures
The internal structures dump is used only by System 1032 developers, and, therefore, is not covered in this article.
Managing the S1032 error log
As the error log file grows, you can accumulate months (or years!) worth of entries. New files are automatically created during System 1032 boot, if the existing file is greater than 1000 blocks.
The SCANLOG.COM tool eases the examination of large System 1032 error log files. This tool is available on the S1032 Support FTP site:
ftp:\\fox.cca-int.com\utilities
SCANLOG executes a customized SEARCH command that extracts the highlights of the error log entries. On OpenVMS V6.1 systems and above, the output of SCANLOG is paged.
Model 204
CCA is happy to announce the immediate availability of Model 204 Version 4 Release 1.1. Complete with both new and enhanced features, V4R1.1 helps you get the most out of your Model 204 investment and prepares you for the new classes of applications that you will undoubtedly be developing in the new millennium.
When you install the new version of Model 204 you receive:
Installing this version of Model 204 provides you with a fresh copy of the most up-to-date code, with previously reported problems corrected. This eliminates the need for you to manage old patches, and ensures that your system is running as efficiently as possible.
To obtain Model 204 Version 4.1.1, contact your sales representative, or fill out an upgrade request form on the CCA Web site: www.cca-int.com.
Focus on Training
by Julie Phenicie
In November, CCA will offer two classes to help Model 204 programmers become more efficient and effective in writing User Language procedures.
This newly revised course is designed for programmers who have completed the Programmer’s User Language class and have at least three months of User Language experience.
In this three-day class, learn how to:
Class Dates: November 2-4, 1998 in McLean.
Avoid runtime errors due to unsupported pattern syntax by using the $CHKPAT function. $CHKPAT returns a null string if the pattern is correct and an error message if it isn’t.
Example of $CHKPAT with incorrect syntax:
BEGIN %CHK IS STRING LEN 80 %PAT = ’JAC*-ABC+++’ %CHK = $CHKPAT(%PAT) IF %CHK = ’’ THEN FPC LASTNAME IS LIKE %PAT END FIND PRINT %PAT ELSE PRINT %PAT WITH ’ IS INCORRECT’ PRINT %CHK END IF END
Output:
JAC*-ABC+++ IS INCORRECT M204.1688: SYNTAX ERROR IN PATTERN ’JAC*-ABC+++’ NEAR CHARACTER 5
Change the previous bolded line to:
%PAT = ’JAC*,ABC+++’
You get this output:
8 JAC*,ABC+++
This course is designed for experienced programmers who want to fine-tune their programming skills to write the most efficient code possible.
Learn how to:
Class Dates: November 16-18, 1998 in McLean.
Use T(IME) REQUEST to see what resources are consumed by the application. This can help you to predict the response time that the end user will get. In the UL350 class, the statistics from the T REQUEST are explained in detail. For example:
OPENC CLIENTS xxxx BEGIN FND1: IN CLIENTS FD RECTYPE = DRIVER INCIDENT DATE IS IN RANGE - FROM 900101 TO 900229 END FIND FR FND1 PRINT POLICY NO AND FULLNAME AT 10 END FOR END T REQUEST
100340 ABBOTT, FRANKLIN G 100338 ADAMS, LEROY E 100585 ALMIREZ, PETER R . . . CPU=0.364 CNCT=512 DKRD=87 DKWR=1 - SQRD=45 SQWR=186 NTBL=1 QTBL=19 - STBL=21 TTBL=4 VTBL=5 PDL=688 CNCT=3 - CPU=12 DKRD=2 OUT=123 IN=5 FINDS=1 - RECDS=116 PCPU=2 RQTM=83 BXNEXT=15 - BXFIND=2 DKPR=288
The System 1032 community has an entirely new forum in which to share knowledge and experience. On March 28, 1999 CCA will launch the new System 1032 User Symposium, "US'99". The venue will be the Crowne Plaza hotel in Framingham, Massachusetts. There will be no registration fee for this symposium.
Because we want to hear from as many of you as possible, CCA will pay the hotel accommodations for any customers who are accepted as conference speakers.
Please submit your abstracts by mail to our Framingham office, care of Sharon Gilberti, or by e-mail to sharon_gilberti@cca-int.com. Submissions must be in by November 30, 1998.
Registration will close on January 1, 1999, but, to help us plan for a very special System 1032 event, please register with Sharon soon!
Contact CCA Webmaster Copyright 2008
