| View previous topic :: View next topic |
| Author |
Message |
sudhaa
Beginner
Joined: 05 Apr 2006
Posts: 2
Topics: 1
|
 Posted: Wed Apr 05, 2006 4:07 am Post subject: SNAP Command in ADSO |
 |
|
| Did anyone have used the SNAP command in ADSO to display the values of the record?If so can anyone explain that command in detail? |
|
| Back to top |
|
 |
Jaya
Beginner
Joined: 02 Sep 2005
Posts: 77
Topics: 10
Location: Cincinnati
|
| Posted: Tue Apr 11, 2006 12:45 am Post subject: |
|
|
Sudha,
You can code the SNAP command in the premap or response processes to request for a dump.
U can either either print the dump using PRINT LOG utility or see them online through OLP ( Online PLOG). U can invoke Online PLOG by typing
OLP in DC/UCF. I.e in ENTER NEXT TASK CODE .
For complete syntax of SNAP, Please refer the following information.
| Quote: | Purpose: Request a snap dump of the contents of one or more areas maintained in memory for CA-ADS. The dump produced by a SNAP command can be used to assess the use of system resources by an executing dialog.
Syntax:
______________________________________________
>>____ SNAP ___v_________ ALL ________________________________|_______________>
| | | |
| | ____________ | |
| |_v___ OCB ___|__| |
| |_ OWA -_| |
| |_ OTB _| |
| |_ OTBX _| |
| |_ FDB _| |
| |_ VDB _| |
| |_ RBB _| |
| |_ ADB _| |
| |_ TAT _| |
| _______________ |
|_ RECORDs - ( _v_ record-name _|_ ) _|
>_________________________________________________ . ________________________><_>> For information on PRINT LOG, refer to CA-IDMS Utilities.
|
Regards,
Jaya.
_________________
"Great spirits have always encountered violent opposition from mediocre minds."
-Albert Einstein |
|
| Back to top |
|
|
Jaya
Beginner
Joined: 02 Sep 2005
Posts: 77
Topics: 10
Location: Cincinnati
|
| Posted: Tue Apr 11, 2006 12:49 am Post subject: |
|
|
| Quote: | Parameters
ALL
Writes all areas of memory maintained for the issuing dialog to the SNAP dump.
OCB
Keyword which requests the CA-ADS control block. The OCB contains CA-ADS system parameters specified in the system generation ADSO statement.
OWA
Keyword which specifies the CA-ADS online work area. The OWA is maintained as a temporary storage buffer for application and dialog information used during CA-ADS runtime processing. The OWA is not maintained across tasks.
OTB
Keyword which specifies the CA-ADS terminal block. The OTB contains information about the current CA-ADS session. The OTB is maintained across tasks.
OTBX
Keyword which specifies the CA-ADS terminal block extension. The OTBX is an extension of the OTB and contains pointers to the TAT, the ADSO-APPLICATION-GLOBAL-RECORD record buffer, the RBB, and the ADB for the currently executing application. The OTBX exists only for applications defined using the application compiler (ADSA).
FDB
Keyword which specifies the fixed dialog block. The FDB is the dialog load module created by the dialog compiler (ADSC). Information in the FDB includes executable process code and parameters required to execute the dialog, and information on the maps and records associated with the dialog.
VDB
Keyword which specifies the variable dialog block. One VDB exists for each operative dialog. A VDB contains runtime variable information about a dialog, such as the status of map fields, information concerning flow of control, addresses of records used by the dialog, and the address of the executing command.
The VDB is created dynamically for the issuing dialog at runtime.
RBB
Keyword which specifies the record buffer block. The RBB contains header information and buffers for all records associated with the current application.
ADB
Keyword which specifies the application definition block. The ADB is the application load module created by the CA/ADS online application compiler. The ADB contains the application information supplied on the definition screens during an application compiler session. The ADB exists only if the application is defined using the application compiler.
TAT
Keyword which specifies the task application table. The TAT contains the names of task codes used to initiate applications and the names of the applications (ADBs) thus initiated. The TAT exists only if there are applications on the system that are defined using the application compiler.
RECORDS record-name
Includes information associated with the specified subschema, map, or work records in the SNAP dump. The information is taken from the RBB; it includes data, but no headers, from the buffers for the named records.
Record-name must be associated with the issuing dialog.
TITLE is 'title-text'
Specifies a title for the SNAP dump.
Title-text is a 1- to 90-character string enclosed in single quotation marks. The specified title is printed on the hard-copy listing of the SNAP dump.
|
_________________
"Great spirits have always encountered violent opposition from mediocre minds."
-Albert Einstein |
|
| Back to top |
|
|
sudhaa
Beginner
Joined: 05 Apr 2006
Posts: 2
Topics: 1
|
| Posted: Tue Apr 11, 2006 1:09 am Post subject: |
|
|
| Thank you jaya for your reply.I 'll use the command and let you know in case of any concerns. |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
