CCA Customer Survey deadline extended to October 31st.
Mail in your survey today!
System 1032 FORCEX utility
By Nancy Diettrich
In every System 1032 programmer's life there comes a time when you must terminate a System 1032 application-preferably while ensuring the data integrity of your 3-million record dataset. Or, you arrive at work one morning to find that the data center considered it necessary to stop all processes for some reason. The result? Several datasets might have damage that requires rebuilding or restoring from backup.
You can avoid or minimize much of this activity by using the FORCEX utility. The FORCEX utility performs a forced exit of an image. By running the System 1032 exit handlers, it cleans up the process before terminating it. FORCEX.EXE is the preferred method of terminating a System 1032 process, as it is unlike the DCL STOP PROCESS command, which "decapitates" the process.
Look for FORCEX.EXE in the S1032_IMAGE area. By exiting in this graceful manner, you can often avoid dataset damage.
You can run FORCEX on your own process. To run FORCEX on another user's process whose UIC is in your group, you need GROUP privilege; to run FORCEX on another user's process whose UIC is outside your group, you need WORLD privilege.
Many sites have data centers whose personnel are not System 1032 users. It is worthwhile to make these folks aware of the FORCEX utility, because their first inclination might be to use the DCL STOP PROCESS command.
For more information on the FORCEX utility as well as other System 1032 utility programs, see the "Maintenance Programs" section of the System 1032 Installation and Maintenance Guide.
Model 204 Questions and Answers
Question: What is the current support status of Model 204?
Answer: Model 204 support status is as follows:
Question: Do I have to install the V4.1.0 SYSTEM (XMEMSVC) SVC and the V4.1.0 CRAM SVC?
Answer: Yes, you must install the V4.1.0 SYSTEM SVC. And, if you are a CRAM user, then you must install the V4.1.0 CRAM SVC.
Question: Are V4R1 custom zaps available for the LOGWHO and MONITOR commands?
Answer: You must use the new RESET COMMAND command to make these functions available in V4.1.0. For information on using this new command, see the Model 204 Late Breaking News, the Model 204 and Connect* Release Notes, and the Model 204 Command Reference Manual.
Question: With V4.1.0, my Online comes up and goes right down. What's wrong?
Answer: You might be experiencing the result of a tightening of the HALT command functionality. In V4.1.0, if an incorrect HALT command is encountered, the Online might terminate (EOJ) prematurely. With the tightening of the HALT functionality, make sure that you have correctly issued this command. See page 1-16 of the Model 204 and Connect* Release Notes for further details.
Question: When do I need a new CPUID zap?
Answer: You need a new CPUID zap when changing CPUs, when testing at a disaster recovery site, or when running under VM and using a virtual serial number. Allow a few days lead time to obtain a new CPUID zap from CCA.
Model 204: Restrictions when opening files
Editor's Note: This article originally appeared in the March 1997 issue of CCAPRINT. Since that time, functionality of the product has changed. This new article reflects the current functionality. The original article was removed from the Web site.
If you open a file when the SYSDATE or SYSTIME parameters are set to a future date/time, the following rules are in effect:
M204.0088: FILE FUTURE CAN NO LONGER BE OPENED BY THIS RELEASE
M204.0630: FILE OPEN COMMAND REJECTED
M204.2473: FILE SRC340 HAS A FUTURE DATE AND CANNOT BE OPENED UNTIL
01/06/2000 12:17:59
If you set the operating system clock forward and open the file with update privileges and then try to use the file in the present time, or if you set the system clock back and try to open a file updated with a present date/time, the following rules are in effect:
01/31/2007 12:17:59
If you open a file exclusively with read-only privileges, that file is not marked as having been opened at a future date/time. Therefore, this file can be shared among jobs running in different time frames.
If when running V4R1 you are also running jobs with either Model 204 V3R1 or V3R2 and files are shared among these jobs, you must contact CCA Customer Support to obtain zaps that implement this functionality for those releases.
Caution: The SYSDATE and SYSTIME parameters are for testing purposes only. Never use them with production files.
In the spirit of the Olympic Games, Winter Corporation just analyzed the results of the third annual Very Large Database (VLDB) Survey program. The official writeup appears in the September 1997 issue of Database Programming and Design magazine, a cosponsor. Of interest to CCA users are the winners in the Concurrent Users, All Environments, Transaction Processing category:
500 Old Connecticut Path, Framingham, MA 01701 webmaster@cca-int.com Copyright 2005
