Selecting Session Opercoms (option O) from the displays the menu:
13:59:43 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
- Session Opercoms - PACI002
Code Service Code Service
---- ------------------------------ ---- ------------------------------
A Allocate/Deallocate CLOG/PLOG S Stop user(s)
C Issue reactivate CLOG command T Termination Commands
E Extended Error Recovery U Manage Online Utilities
F Force CLOG or PLOG switch V User Table Maintenance
L Lock or unlock files X Replicator Management
R Reset ONLINE-DUMP-Status Z Cluster operator commands
. Exit ? Help
---- ------------------------------ ---- ------------------------------
Code ........... _
Userid(ETID) ... ________
CLOG/PLOG Ind .. _ Global.. _
Database ID .... 1955 (WIS1955) NucID .. 1021
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Menu |
Note:
A zero value in the NucID field indicates that the command
applies to all nuclei in the cluster (global). A non-zero value for NucID
indicates that the command applies only to the cluster nucleus specified.
System operator command functions you can perform are accessed from the Session Opercoms menu by entering the appropriate code, as follows:
| Option | Function |
|---|---|
| A | Allocating/Deallocating CLOG and PLOG Data Sets |
| C | Reactivating Command Logging |
| E | Extended Error Recovery Functions |
| F | Forcing Dual/Multiple CLOG/PLOG Switch |
| L | Locking / Unlocking files |
| R | Resetting Online Dump Status |
| S | Stopping Users |
| T | Termination Commands |
| U | Managing Online Utilities |
| V | Maintaining the User Table (nucleus cluster environments only) |
| X | Displays the menu, which allows you to access the Adabas Event
Replicator Subsystem (SYSRPTR) as well as to activate and deactivate subsystem
definitions, run the RPLCHECK, RPLCLEANUP, or RPLREFRESH utilities, and display
subsystem parameters and definitions.
Note: For more information about the Adabas Event Replicator Subsystem or any of the functions you can perform from the Replication Management menu, refer to your Event Replicator for Adabas documentation. |
| Z | Running Cluster Operator Commands |
Option (Allocate/Deallocate CLOG/PLOG) on the menu is used to dynamically add and delete CLOG and PLOG data sets without terminating your current nucleus session. Using this function, you can specify up to eight CLOG or PLOG data sets. This will reduce the chances of a wait condition in the nucleus, when the nucleus waits for an available CLOG or PLOG. You might find this particularly useful during busier times of the month or year.
This function corresponds to the utility functions ADADBS ADDCLOG, ADDPLOG, DELCLOG, and DELPLOG.
When you select option , the menu appears.
To add a CLOG or PLOG data set dynamically, the nucleus must know about its JCL at startup time. To use this functionality in AOS, you must set up your Adabas nucleus startup jobs to include definition statements for the maximum number of CLOG and PLOG data sets as you plan to use, but limit the actual usage of the PLOGs using the ADARUN NCLOG and NPLOG parameters. For example, you might start a nucleus with eight PLOG definitions in the Adabas startup JCL, but limit the number of PLOGs actually used during nucleus processing to three PLOGs by setting the NPLOG parameter to "3". When the nucleus starts up, only three PLOGs will be opened and logged in the PPT, even though eight are defined in the JCL. The additional PLOG data sets can then be dynamically added using this ADADBS ADDPLOG utility or the functions provided on the AOS menu.
Note:
Any CLOG or PLOG data sets you add dynamically will not be
retained once you recycle your Adabas nucleus. To retain these new data sets
when Adabas is stopped and restarted, alter the Adabas startup JCL as well,
ensuring that the number of PLOG definition statements in the JCL matches the
increased number of PLOG data sets and that the NPLOG ADARUN parameter setting
includes the new PLOG data sets.
15:13:17 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
- Allocate/Deallocate CLOG/PLOG - PACIA02
Code Service
---- ---------------
A Allocate CLOG
D Deallocate CLOG
P Allocate PLOG
S Deallocate PLOG
? Help
. Exit
---- ---------------
Code ........... _
Dataset number . _
Dataset Name ... ____________________________________________
Database ID .... 1955 (WIS1955) NucID .. 1021
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help PPT Exit Menu |
This section covers the following topics:
Option (Allocate CLOG) on the menu is used to dynamically add CLOG data sets without terminating your current nucleus session.
This function corresponds to the utility function ADADBS ADDCLOG.
To allocate a CLOG data set:
Select option on the menu.
In the Dataset number field, specify the number of the CLOG data set, as defined in your Adabas startup JCL.
In the Dataset Name field, specify the data set name of the CLOG data set, as defined in your Adabas startup JCL.
Press Enter.
The CLOG data set is allocated and can immediately be used.
When you select option , the menu appears.
Option (Deallocate CLOG) on the menu is used to dynamically delete CLOG data sets without terminating your current nucleus session.
This function corresponds to the utility function ADADBS DELCLOG.
To deallocate a CLOG data set:
Select option on the menu.
In the Dataset number field, specify the number of the CLOG data set, as defined in your Adabas startup JCL.
In the Dataset Name field, specify the data set name of the CLOG data set, as defined in your Adabas startup JCL.
Press Enter.
The CLOG data set is deallocated and can no longer be used.
Option (Allocate PLOG) on the menu is used to dynamically add PLOG data sets without terminating your current nucleus session.
This function corresponds to the utility function ADADBS ADDPLOG.
To allocate a PLOG data set:
Select option on the menu.
In the Dataset number field, specify the number of the PLOG data set, as defined in your Adabas startup JCL.
In the Dataset Name field, specify the data set name of the PLOG data set, as defined in your Adabas startup JCL.
Press Enter.
The PLOG data set is allocated and can immediately be used.
Option (Deallocate PLOG) on the menu is used to dynamically delete PLOG data sets without terminating your current nucleus session.
This function corresponds to the utility function ADADBS DELPLOG.
To deallocate a PLOG data set:
Select option on the menu.
In the Dataset number field, specify the number of the PLOG data set, as defined in your Adabas startup JCL.
In the Dataset Name field, specify the data set name of the PLOG data set, as defined in your Adabas startup JCL.
Press Enter.
The PLOG data set is deallocated and can no longer be used.
Option (Issue reactivate CLOG command) on the menu is used to reactivate command logging in an active nucleus where it had been disabled previously as a result of an I/O error. The cause of the I/O error needs to be corrected before running this function or command logging will simply fail again and will not be reactivated.
This function corresponds to the utility function ADADBS REACTLOG.
When you select option , a request to reactivate command logging is issued.
Selecting option E (Extended Error Recovery) on the menu displays the menu:
15:21:46 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
- Extended Error Recovery - PACIE02
Code Service
---- ----------------------------------
B Display message buffer
D Display/modify environment
E Display/modify Exit routines
M Add/Delete PIN modules
P Display/modify PIN routines
R Refresh threshold and alert exits
S SNAP a nucleus dump
? Help
. Exit
---- ----------------------------------
Code ........... _
Start Address .. ________ End Address ... ________
Database ID .... 1955 (WIS1955) NUCID .. 1021
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Menu |
Note:
Option (Refresh threshold and
alert exits) is no longer a functional option.
From this menu you can:
display the message buffer
display or modify the parameters controlling the extended error handling environment;
display or modify parameters for invoking the error handling exits;
add or delete PIN modules;
display, activate, or deactivate specific PIN routines;
SNAP a dump image of nucleus memory.
This section covers the following topics:
Selecting option (Display Message Buffer) on the menu displays the contents of the message buffer on the Display Message Buffer screen.
These functions are the same as the error handling operator commands:
SMGT,DISPLAY=MSGBUF
15:19:47 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - Display Message Buffer - PACIEB2
NUCID .. 1021
Select starting message ________
Msg Num Time Msg ID Message
---------- -------- ------ ---------------------------------------------------
2307 10584254+00E0 00000000 00000000 00000000 00000000 *..........
2308 10584264+00F0 00000000 00000000 00000000 00000000 *..........
2309 10584274+0100 00000000 10584284 1058428C 10584284 *.......d..
2310
2311
2312 Snap Basic System Status flags:
2313
2314 00067746+0000 00000004 00000000 00000001 00000027 *..........
2315
2316 11:09:49 ADAH51 Dump format completed
2317 11:09:49 ADANX1 ********End P I N R S P Output *******
2318 11:09:49
Command ===>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Latest -- - + Menu |
Press PF4 to refresh the screen and show the latest messages added to the buffer.
The Msg Num column contains the sequential record number for each item in the message buffer. Enter a record number in the field Select starting message to position the display to a particular record.
Selecting option (Display/modify environment) on the menu displays the current setting of several extended error handling parameters on the Display/Modify Environment screen.
The functions on this screen mirror the error handling operator commands:
SMGT,{ON | OFF}
SMGT,ABNORMALTERM={ON | OFF}
SMGT,DUMP={ON | OFF}
SMGT,MSGBUF={ON | OFF}
SMGT,DISPLAY=LAST
15:22:18 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - Display/Modify Environment - PACIED2
NUCID .. 1021
------- Parameters ----------- Status - Executions -
Extended Error Recovery (SMGT) ON 0
Message Buffering ............ ON
Abnormal Term. Handler ....... ON 0
Response Code Handler ........ ON 0
Full System Dump (DUMP) ...... OFF
----------- Most Recent Recovery Action -----------
Last error occurred at: 2014-05-02 11:09:49
Condition: Rsp 009 Location: * N/A *
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help MsgBuf Exit Menu |
The parameters with "ON"/"OFF" values in the Status column can be activated and deactivated by changing the value.
Selecting option (Display/modify Exit routines) on the menu displays the status of the exits currently loaded on the List/Modify Exit Routines screen.
These functions are the same as the error handling operator commands
SMGT,DISPLAY=EXITS
SMGT,{XACTIVATE | XDEACTIVATE}=exit-code
SMGT,XLOAD=exit-code
SMGT,XLOAD=(exit-code,module-name)
SMGT,{XCRITICAL | XNOTCRITICAL}=exit-code
15:22:42 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - List/Modify Exit Routines - PACIEE2
NUCID .. 1021
Mark with 'A' Activate, 'D' Deactivate, 'L' Load, 'C' Critical, 'N' Not Crit
M Exit Program Status Critical M Exit Program Status Critical
- ---- -------- -------- -------- - ---- -------- -------- --------
_ UX08 UX8ST Active Critical _
_ _
_ _
_ _
_ _
_ _
_ _
_ _
_ _
_ _
_ _
_ _
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Refr -- - + Menu |
The exit code, the name of the program invoked by the exit, the current status, and the criticality are listed for each exit. You can change the status and criticality of the exit from this screen.
To change the status and criticality of the exit, enter one of the following codes in the M column next to the selected exit:
| Code | Description |
|---|---|
| A | Activates the exit |
| D | Deactivates the exit |
| L | Reloads the exit program in memory or to loads a new exit |
| C | Makes the exit critical |
| N | Makes the exit noncritical |
After changes have been made, use PF4 to refresh this screen.
Selecting option (Add/Delete PIN modules) on the menu displays a list of currently available PIN modules on the Add/Delete PIN Modules screen.
These functions are the same as the error handling operator commands
SMGT,{ADDPIN | DELPIN}=module-name
15:27:27 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - Add/Delete PIN Modules - PACIEM2
NUCID .. 1021
Mark entries with 'A' to Add or 'D' to Delete:
M Module Description Message
- -------- ------------------------------ -------
_ ADAMXY Standard Nucleus PIN Routines
PINAAF SAF Security
PINAFP Adabas Fastpath
PINATM Adabas Transaction Manager
PINAVI Adabas Vista
_ PINRSP Adabas Response Code Handler
_ PINUES Universal Encoding Support
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Menu |
To load a PIN module into memory:
Enter "A" in the M column next to the module name.
This command is successful only if the exit module exists in a library accessible to the Adabas nucleus.
To remove a PIN module from memory:
Enter a "D" in the M column next to the module name.
When deleting a PIN module from memory, all related PIN routines are also removed.
Selecting option (Display/modify PIN routines ) on the menu displays a list of PINs currently loaded in memory on the List/Modify PIN Routines screen.
These functions are the same as the error handling operator commands
SMGT,DISPLAY=PINS
SMGT,{ACTPIN | DEACTPIN}=pin-number
15:28:01 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - List/Modify PIN Routines - PACIEP2
NUCID .. 1021
Mark entries with 'A' Activate, or 'D' Deactivate: Total Pins: 267
M Condition Error Location Status Uses Module Message
- --------- ---------------------------- ------- ---- -------- -----------
_ 000C1000 All Locations Active 0 ADAMXY
_ 000C2000 All Locations Active 0 ADAMXY
_ 000C3000 All Locations Active 0 ADAMXY
_ 000C4000 All Locations Active 0 ADAMXY
_ 000C5000 All Locations Active 0 ADAMXY
_ 000C6000 All Locations Active 0 ADAMXY
_ 000C7000 All Locations Active 0 ADAMXY
_ 000C8000 All Locations Active 0 ADAMXY
_ 000C9000 All Locations Active 0 ADAMXY
_ 000CB000 All Locations Active 0 ADAMXY
_ 000CF000 All Locations Active 0 ADAMXY
_ 00047000 All Locations Active 0 ADAMXY
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Refr -- - + Menu |
For all PIN routines on the list, the screen indicates the conditions that cause them to be executed, the current status, the number of times they have been used, and the module in which they are located.
To change the status of the PINs from this screen, enter one of the following codes in the M column next to the PIN number:
| Code | Description |
|---|---|
| A | Activates a PIN |
| D | Deactivates a PIN |
After changes have been made, use PF4 to refresh the screen.
Selecting option "R" (Refresh Threshold and Alert Exits) from the Extended Error Recovery menu is no longer a functional option.
Selecting option (SNAP a nucleus dump) on the menu generates a formatted dump of the nucleus without error diagnostics.
This function is the same as the error handling operator command
SMGT,SNAP[=(start,end)]
To generate a dump of the whole nucleus:
Leave the Start Address and End Address fields on the menu blank.
Or:
To generate a SNAP dump of only a range of addresses,
enter hexadecimal addresses in the Start Address and
End Address fields on the menu.
Press Enter.
The formatted dump is written to the DDPRINT data set specified in the nucleus.
Option (Force CLOG or PLOG switch) on the menu allows you to immediately switch (by forcing an end-of-file) between dual or multiple command log (CLOG) or protection log (PLOG) files. Switching (that is, "toggling") changes from one CLOG or PLOG file to another.
Equivalent direct commands are:
FORCE CLOGSWITCH
FORCE PLOGSWITCH
Option (Lock or unlock files) on the menu is used to lock, unlock, or display locked files. Files can be locked or unlocked for all users or for all but utility or EXF users. Once locked for all users, a file cannot be unlocked for utility users only.
Locking is immediate; a transaction in process whose file becomes locked will be backed out.
Unlocking makes the file available again for normal use.
Equivalent direct commands are:
LOCK FILE
UNLOCK FILE
Selecting option displays the menu.
15:28:48 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
- Lock / Unlock Files - PACIL02
Code Service
---- ----------------------------------
D Display locked files
F Lock file for all users
K Advance lock file
L Lock file except for UTI/EXF users
N Unlock file from general lock
R Release an advance lock
U Unlock file from UTI/EXF lock
? Help
. Exit
---- -----------------------------------
Code ......... _
File Number ..
UTI/EXF Ind .. U
Database ID .. 1955 (WIS1955)
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Menu |
For the most part, the options on this menu perform locking or unlocking functions without the use of additional AOS screens.
| Option | Description |
|---|---|
| D | Displays locked files and allows you to modify their locked status on the Display Locked Files screen, as described later in this section. |
| F | Locks the file identified in the File Number field for all users. |
| K | Performs an advance lock on the file identified in the File Number field. |
| L | Locks the file identified in the File Number field for either utility functions (UTI) or EXF users, as specified in the UTI/EXF Ind field. |
| N | Unlocks the file identified in the File Number field for all users. |
| R | Releases an advance lock on the file identified in the File Number field. |
| U | Unlocks the file identified in the File Number field for either utility functions (UTI) or EXF users, as specified in the UTI/EXF Ind field. |
To list and modify the locked status of files using the Display
Locked Files screen:
Select option (Display locked files) on the menu..
The Display Locked Files screen appears:
15:32:10 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - Display Locked Files - PACID02
Mark entries with 'U' to unlock:
M Fnr. Lock Status M Fnr. Lock Status
- ----- ------------------------- - ----- -------------------------
_ 1 Locked for ALL users
_ 29 Locked except for UTI
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit -- - + Menu |
To unlock a file on the Display Locked Files, enter a "U" in the M column to the left of the file number on this screen.
Multiple files may be unlocked at the same time.
Option (Reset ONLINE-DUMP-Status) on the menu is used to reset the online dump status for use when an ADASAV online dump operation has abended.
An equivalent direct command is:
RESET ONLINESTATUS
Selecting option (Stop user(s)) on the menu displays the menu.
19:43:12 ***** A D A B A S BASIC SERVICES ***** 2015-05-19
- Stop Users - PACIS12
Code Service Code Service
---- ------------------------------ ---- ------------------------------
F Stop users using file S Stop all selected Secuid
I Stop inactive users U Stop a selected user
J Stop users by jobname
? Help . Exit
---- ------------------------------ ---- ------------------------------
Code ............. _
File Number ...... _____
Last Activity .... ________ (elapsed time in seconds)
Job Name ......... ________
Purge UQE(s) ..... N
With Resp 22/54 .. N
Selected Secuid .. Selected Userid ..
Database ID ...... 1955 (WIS1955)
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Disp UQ Exit Clear UID Menu |
You can stop a specific user, all users from a specific job, all users using a specific file, or all inactive users. Any open transactions of the stopped users are backed out. When the Purge UQE(s) field is set to "Y", the stopped users are also deleted. Note that EXF and UTI users are not stopped or deleted.
The following table describes what each of the screen options allows you to do and how to use them effectively:
| Option | Description |
|---|---|
| F | Stops all users who are using a
specific file. When you use this option, specify the file number in the
File Number field. This is the equivalent of
running the Adabas STOPF operator command.
The nucleus backs out all open transactions of any users of the file. If the Purge UQE(s) field is set to "Y", the stopped users are also deleted. If the Purge UQE(s) field is set to "N" or Adabas is running with ADARUN OPENRQ=YES, a stopped user who returns (by sending a command) will receive response code 9. Caution: |
| I | Stops all users who have not executed a
command during a specific time interval. When you use this option, specify the
inactivity time (in seconds) in the Last
Activity field. This is the equivalent of running the Adabas STOPI
operator command.
The nucleus backs out all open transactions of the affected users. If the Purge UQE(s) field is set to "Y", the stopped users are also deleted. If the Purge UQE(s) field is set to "N" or Adabas is running with ADARUN OPENRQ=YES, a stopped user who returns (by sending a command) will receive response code 9. Caution: |
| J | Stops and deletes all users from a
specific job. When you use this option, specify the job name in the
Job Name field. This is the equivalent of
running the Adabas STOPU operator command with a job name specified.
The nucleus backs out any open transactions from the job and deletes the users (purges their user queue elements), regardless of the setting of the Purge UQE(s) field. No response code is issued, when the field With Resp 22/54 is set to "N"; the next time a stopped user issues a command, a new user queue element (UQE) is created. If the field With Resp 22/54 is set to "Y", this is the equivalent of running the Adabas STOPUR operator command with a job name specified. The nucleus backs out any open transactions from the job and deletes the users (purges their user queue elements), regardless of the setting of the Purge UQE(s) field. However, the stopped users are only deleted after they have issued a subsequent command and response code 22 (ADARSP22), subcode 54 has been issued in response to that command. This response code/subcode combination is used to notify users that their Adabas activity has been halted and their user session resources have been freed. Only after the response code/subcode combination has been issued will the user queue element of the stopped users be deleted. Caution: |
| S | Stops and deletes all specific security
user IDs. When you use this option, specify the security user ID (secuid) of
the user you want to stop in the Selected
Userid field. You can do this by selecting a user from the current
user queue (select PF2 on this screen) and specifying
"N" in the With Resp
22/54 field. This is the equivalent of running the Adabas STOPSU
operator command with a security user ID specified.
The nucleus backs out any open transaction of the user and deletes the user (purges the user queue element), regardless of the setting of the Purge UQE(s) field. No response code is issued; the next time a stopped user issues a command, a new user queue element (UQE) is created. If the field With Resp 22/54 is set to "Y", this is the equivalent of running the Adabas STOPSUR operator command with a security user ID specified. The nucleus backs out any open transactions from the job and deletes the users (purges their user queue elements), regardless of the setting of the Purge UQE(s) field. However, the stopped users are only deleted after they have issued a subsequent command and response code 22 (ADARSP22), subcode 54 has been issued in response to that command. This response code/subcode combination is used to notify users that their Adabas activity has been halted and their user session resources have been freed. Only after the response code/subcode combination has been issued will the user queue element of the stopped users be deleted. Caution: |
| U | Stops and deletes a specific ET-ID
user. When you use this option, specify the user ID (ET-ID) of the user you
want to stop in the Selected Userid field. You
can do this by selecting a user from the current user queue (select
PF2 on this screen and then press PF6 to show ET-ID).
The nucleus backs out any open transaction of the user and deletes the user (purges the user queue element), regardless of the setting of the Purge UQE(s) field. However, the stopped user is only deleted after they have issued a subsequent command and response code 22 (ADARSP22), subcode 54 has been issued in response to that command. This response code/subcode combination is used to notify users that their Adabas activity has been halted and their user session resources have been freed. Only after the response code/subcode combination has been issued will the user queue element of the stopped user be deleted. Caution: |
| ? | access online help for this screen. |
| . | exit this screen. |
The following table describes the use of the fields on this screen:
| Field | Description |
|---|---|
| Code | Specify the code of the function you wish to perform, as described in the table above. |
| File Number | When selecting the option (stop users of a specific file), specify the file number; all users of the file will be stopped. |
| Last Activity | When selecting the option (stop inactive users), specify the inactivity time of the users (in seconds); users who have not executed a command during the specified time interval will be stopped. |
| Job Name | When selecting the option (stop and delete users from a specific job), specify the job name; all users from that job will be stopped and deleted. |
| Purge UQE(s) | When selecting the
or options specify
(with "Y" or "N") whether
the user queue elements (UQEs) of the stopped users should be purged. Users
stopped via the or
options are always purged.
Caution: |
| With Resp 22/54 | When selecting the , , or options specify (with "Y" or "N") whether the user queue elements (UQEs) of the stopped users should be purged or have a response 22, subcode 54, returned. |
| Selected Secuid | Lists the selected security user ID. To change the security user ID, press the PF2 key and select a new security user ID from the current user queue. To clear a security user ID from this field, press the PF4 key. If no specific user is listed in this field, all users are assumed. This field is used only when the Code (stop a specific secuid) is selected. |
| Selected Userid | Lists the selected user ID. To change the user ID, press the PF2 key (and PF6 for ET-ID) and select a new user ID from the current user queue. To clear a user ID from this field, press the PF4 key. If no specific user is listed in this field, all users are assumed. This field is used only when the Code (stop a specific user) is selected. |
| Database ID | Specify the database ID of the database for which the users are stopped. |
The following special function keys are also available for use on this screen:
Press PF2 (Disp UQ) to display the current user queue. You can select a user from the current user queue list.
Press PF4 (Clear UID) to clear the Selected Userid field.
An equivalent direct command is:
STOP USERS
Selecting option (Termination Commands) on the menu invokes the menu from which you can choose to terminate a session normally (ADAEND), cancel a session immediately (CANCEL), or stop a session (HALT).
15:56:48 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
- Session Termination - PACT002
Code Service
---- -----------------------------------
A Normal session termination (ADAEND)
C Cancel session immediately (CANCEL)
H Stop session (HALT)
? Help
. Exit
---- -----------------------------------
Code ......... _
Database ID .. 1955 (WIS1955) NUCID .. 1021
Global.. _
Current nr. of users in User Queue ... 1
Nr. of users with open transactions .. 0
Nr. of active nucs in Plex cluster ... 1
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Menu |
In all cases, you are prompted to confirm your termination request before the action is taken.
An equivalent direct command is:
TERMINATE SESSION
Selecting option (Manage Online Utilities) on the menu displays the Manage Online Processes screen:
15:58:02 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
DBID 1955 - Manage Online Processes - PACIP02
Total Processes...
Mark entries with 'S' (Suspend), 'R' (Resume), or 'X' (Stop):
I I Process I Sort I Current I Throw- I Process I I
M I FNR I Type I Seq I RABN/ISN I Backs I ID I Status I
-----------------------------------------------------------------------------
_ I 50 I Reor Data I Phy I 3345 I 6 I 000003FC I Active I
_ I 61 I Invert DE I AA I 286 I 1 I 000003FF I Suspended I
_ I 101 I Reor Asso I BJ I I 1 I 000000C2 I Active I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
_ I I I I I I I I
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Refresh -- - + Menu |
From this screen, you can manage (that is, monitor, suspend, resume, and stop) online utility processes.
All online processes currently in the database nucleus are listed, up to a maximum of 40. You can use PF6 (back to the start of the list), PF7 (back one screen), and PF8 (forward one screen) to scroll among the processes.
The equivalent direct command is:
DISPLAY PROCESS
To maintain the processes, enter one of the following maintenance codes in the M column to the left of the process named in the Process Type column:
| Code | Description |
|---|---|
| S | Suspends an active process |
| R | Resumes a suspended process |
| P | Stops a process |
You can maintain multiple processes at the same time.
The equivalent direct command is
MANAGE PROCESS
The sort sequence used by a process is indicated in the Sort Seq column:
| For process type . . . | Sort Seq. contains the descriptor currently being . . . |
|---|---|
| reorder Data Storage | reordered* |
| invert descriptor | inverted |
| reorder Associator | reordered |
* When reordering Data Storage for a file, the default sort sequence is physical sequence or "PHY". Other possible options include "ISN" if the file is to be sorted in ISN order, or the two character descriptor name to sort the file according to the value of the specified descriptor.
The Current RABN/ISN column shows the progress of work:
| For process type . . . | Current RABN/ISN displays the current . . . |
|---|---|
| reorder Data Storage | RABN being processed |
| invert descriptor | ISN, as this function works in ISN sequence |
| reorder Associator | (left blank) |
Note:
This option is available in Adabas nucleus cluster environments
only.
When option (User Table Maintenance) is selected on the menu, the menu appears:
15:58:04 ***** A D A B A S BASIC SERVICES ***** 2014-05-02
- User Table Maintenance - PACIV02
Code Service
---- -------------------------
C Begin CLUFREEUSER process
? Help
. Exit
---- -------------------------
Code ......... _
TNA .......... 0______
UID .......... ___________________
Force ........ _
Global ....... _
Database ID .. 1955 (WIS1955) NucID .. 1021
Command ==>
PF1----- PF2------ PF3------ PF4------ PF6----- PF7----- PF8----- PF12-----
Help Exit Menu |
The CLUFREEUSER command is only valid
in cluster environments. It can be issued against the local nucleus only or,
with the Global option, against all active and inactive nuclei in the
cluster.
The command is used to delete leftover user table elements (UTEs) in common storage that are no longer associated with user queue elements (UQEs) in a nucleus where:
| Screen Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| TNA | A decimal number specifying the timeout value in seconds. UTEs that are not used during the time specified may be deleted if other conditions are fulfilled. If TNA is not specified, UTEs may be deleted without regard to their recent use. | ||||||
| UID | A character string or hexadecimal byte
string as follows:
A character string must be enclosed in apostrophes if it contains characters other than letter, digits, or embedded '-' signs. If a specified character string is less than 8 characters long, it is implicitly padded with blanks. If a specified hexadecimal string is shorter than 16 hexadecimal digits, it is implicitly padded with binary zeros. If the last 8 bytes of a user's 28-byte communication ID match a specific user ID or user ID prefix, that user's UTE may be deleted if other conditions are fulfilled. If UID not specified, UTEs may be deleted regardless of their user IDs. |
||||||
| FORCE | Indicates whether leftover UTEs should be deleted even if the users are due a response code 9, subcode 20. If FORCE is not specified, such UTEs are not deleted. Before using the FORCE parameter, ensure that the users owning the UTEs to be deleted will not expect any of their transactions to remain open. Specify FORCE on this screen by marking the Force field with any character. | ||||||
| GLOBAL | Indicates whether leftover UTEs should be deleted throughout the Adabas cluster if they are no longer associated with UQEs and are eligible according to the other specified parameters. Additionally and subject to the other rules, delete leftover UTEs if their assigned nuclei have terminated since their last use. If GLOBAL is not specified, only UTEs assigned to the local nucleus and used since the nucleus start are eligible for deletion. Specify GLOBAL on this screen by marking the Global field with any character. |