This document explains the functions and screens which can be invoked from the "SNADS Administration Menu" in the order of their appearance in the menu. For a description of how to invoke this menu and the most frequently used commands, see Navigating Through SNADS Administration.
This document covers the following topics:
Select the Queue Maintenance function from the "SNADS Administration Menu". The "Queue Maintenance" screen is displayed. All queue maintenance activities begin from this screen.
8:49 AM * * * C o n - n e c t 3 * * * 19.Sep.2005
Cabinet LS SNADS - Queue Maintenance X-FMQ-03
Cmd Queue ID Items Last Active I O R Time Description
--- -------- ------ -------------------- - - - ---- -----------------------
__ ***INB** 0 5.Oct.2004 4:54 PM A E E 0 `
__ ***DMY** 0 31.Dec.2003 5:35 AM A E E 0
__ CNT312CO 0 12.Feb.2004 4:15 PM A E E 0
Position to Queue: ________
Cmd:
DI Display Items DQ Display Queue MO Modify Queue EI Erase Items
EQ Erase Queue
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Add
Mark item(s) from the list above with a command or press a PF-key |
The following information is shown on the "Queue Maintenance" screen:
- Queue ID
The name of the queue. "***INB**" is reserved as the identifier for the inbound queue; while "***DMY**" is reserved as the identifier for the dummy queue. All other queues are outbound queues.
- Items
The number of DIUs in a queue.
If the queue contains more than 9999 items, "!>9999" is shown in this column. It is recommended that you do not keep so many items in a queue and that you delete items in time.
- Time Last Active
The date and time of the queue's last activity. Con-nect SNADS records the last date and time that a Con-nect SNADS queue server program was scheduled, activated or deactivated.
- I
Input status. Possible queue statuses are: A (active) and D (queue being drained).
When a queue drains, all items currently in the queue can be processed but new items cannot be received.
- O
Output status. The output status for timer-driven queues can have the following values: reset, scheduled and active. If the output status is T, the timer is not activated. However, after repeated or serious errors, the output status is Held.
- R
Reset status. The reset status is the initial value of the output status and describes the scheduling method which applies to that queue. Possible queue statuses are: I (inactive; only through administrator intervention), T (timer driven scheduling), E (event driven scheduling) and H (queue held).
Notes:
- If your system runs in batch mode, the reset status must be either I (inactive) or H (held). It must not be set to T (timer driven) or E (event driven).
- The scheduling method for the dummy queue is always timer driven with a time interval of one minute regardless whether I (inactive), T (timerdriven) or E (event driven) has been specified.
- Time
The timer interval in minutes. If your system runs in batch mode, this field must not be specified.
- Description
Optional - a description of the queue.
- Position to Queue
If the displayed list is longer than one page, enter the name of the queue which you want to scroll to the top of the display.
The Con-nect SNADS administrator must ensure that the appropriate mechanisms for scheduling the Con-nect SNADS queue server programs have been established and activated.
For further information regarding scheduling, see Scheduling the Con-nect SNADS Queue Servers.
For each node in the SNADS network that is directly adjacent to the local Con-nect system, an outbound queue must be defined as a temporary repository for the DIUs that are destined for transmission to those nodes. You can define as many queues as are required for the current environment.
If you mark an item with DQ (Display Queue) on the "Queue Maintenance" screen, the "SNADS - Display Queue" screen which displays information concerning a single queue appears:
12:28 * * * C o n - n e c t 3 * * * 8.Mar.04
Cabinet LS SNADS - Display Queue X-FMQ-03
------------------------------------------------------------------------
Queue ID: YORK-Q__ Description: NEW YORK______________
Connection ID: NYRK_____________ Mode Name: MOY_____
------------------------------------------------------------------------
Time Last Active: 12.Feb.04 16:15
Time Last Deactivated: 12.Feb.04 16:15
Time Last Scheduled: 12.Feb.04 16:15
------------------------------------------------------------------------
Reset Status (I, T, E, H): T Time Interval: 10___ Min
Input Status (A, D): A
Output Status: T
------------------------------------------------------------------------
Queue Status:
A : Queue Active H : Queue Held ' ' : Scheduled
D : Queue being Drained T : Timer Wait
I : Queue Inactive E : Event Wait
------------------------------------------------------------------------
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Modif
Press a PF-key |
To add a queue, press PF4 on the "Queue Maintenance" screen. The "SNADS - Add/Modify Queue" screen is displayed and the highlighted fields can be specified. See Outbound Queues.
If you want to modify a queue, press PF6 on the "SNADS - Display Queue" screen, the "SNADS - Add/Modify Queue" screen is displayed and the highlighted fields can be modified.
The following information is displayed in the above mentioned screens when you add, modify or display a SNADS queue.
- Queue ID
The name of the queue.
- Connection ID
This and the "Mode Name" field, identifies the SNA LU6.2 link used to send SNADS distributions from the queue.
If your system uses Software AG's EntireX Broker Services (LU6.2 API), you must enter the fully qualified LU name which was used to define the adjacent node to the SNA network.
For systems running CICS, this field must match the name this connection used in CICS (TCT entry). You can obtain this information from your network administrator or system programmer.
- Description
Optional - a description of the queue.
- Mode Name
This and the "Connection ID" field, identifies the SNA LU6.2 link used to send SNADS distributions from the queue.
If your system uses EntireX Broker Services (LU6.2 API), you must enter the VTAM log mode name which can be used for the APPC definition for the current node. You can obtain this information from your VTAM system programmer.
For systems running CICS, you must enter the VTAM log mode name which can be used for an APPC connection with the appropriate adjacent node and which was entered in the TCT of CICS for the appropriate connection. In the case of a dummy queue, you must enter the name of an appropriate VTAM log mode which the adjacent SNADS nodes must use to create the connection with the local system. You can obtain this information from your network administrator or system programmer.
For each of the queues, the system keeps three time stamp values:
- Time Last Active
The time when the queue's server program was last activated.
- Time Last Deactivated
The time when the queue's server program was last deactivated.
- Time Last Scheduled
The time when the queue was last scheduled.
For each of the queues, the administrator can select one of the following scheduling mechanisms as appropriate:
I inactive status - scheduling only at explicit operator intervention T timer driven scheduling (does not apply to systems which run in batch mode) E event driven scheduling H hold status - no scheduling at all (the respective queue will not be serviced) - Reset Status
Possible values for the queue status are: I (inactive), T (timer driven), E (event driven) and H (hold).
- Input Status
Possible values for the queue status are: A (active) and D (queue being drained).
- Output Status
On the "Modify" as well as on the "Add" screen, you can mark the required action: either Start (activate), Stop (deactivate) or Reset (sets the output status to the value of the Reset Status) the Queue Server (the programs which actually deliver the SNADS DIUs).
- Time Interval
Only applicable for timer driven scheduling: the time interval (in minutes) in which the respective Con-nect SNADS server program (for DIU transmission or for routing and directing) is scheduled.
If the event-controlled scheduling is active, the appropriate server program is started each time a DIU is appended to the respective queue.
Note:
The scheduling mechanism for the inbound queue can be
event-controlled only if all Con-nect end-users invoke Con-nect uniformly in a
Com-plete (with EntireX Broker Services (LU6.2 API)) or CICS environment in
which also runs the non-interactive server tasks for Con-nect SNADS. This
restriction does not apply to the other queues.
If you mark an item with DI for "Display Items" on the "Queue Maintenance" screen, the following screen listing the items in a queue - the SNADS DIUs - appears:
3:19 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Items in Queue: YORK-Q Friday
Cmd Origin Name Origin Node Priori Origin Date and Time SeqNo
--- ----------------- ----------------- ------- ---------------------- -----
__ CONNECT1 HSC MINNE SOTA DATA-8 14.Feb.94 12:27 PM 4
__ CONNECT1 HSC MINNE SOTA DATA-8 14.Feb.94 12:29 PM 6
__ CONNECT1 HSC MINNE SOTA DATA-8 14.Feb.94 12:31 PM 7
Cmds are 2 characters from the list below:
DI Display MO Modify RE Recipients ER Erase
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit
Mark item(s) from the list above with a command or press a PF-key
|
The following information is shown on the "Items in Queue" screen:
- Origin Name
The SNADS user (DUN) who sent this DIU.
- Origin Node
The SNADS node (DSUN) from which this DIU originated.
- Priori
The priority options: FAST (highest), STATUS, DATA-16 to DATA-1 (lowest).
- Origin Date and Time
The date and time when the DIU was created.
- SeqNo
The sequence number of the DIU.
If you mark an item with DI for Display on the "Items in Queue" screen, the following screen appears:
3:21 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS DATA Distribution Interchange Unit Friday
________________________________________________________________________
Distribution ID
Origin Node: MINNE SOTA Origin Date Time: 1994021412220200
Origin Name: CONNECT1HSC Origin Sequence No: 4
Origin Correlation: ORIGINATED BY CON-NECT
________________________________________________________________________
Distribution Info
Priority: DATA-8 Distr Object Count: 1
Protection: YES Feedback: Error Feedback
Capacity: INDF Hop Count: 16
________________________________________________________________________
DIA Info I Queue Info
I
Reply: COD I
Personal: NO I Queue ID: YORK-Q
Priority: NO I Queued At: 14.Feb.94 12:43 PM
________________________________I_______________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Modif Recip
Please press a PF-key
|
The above screen pertains to the DIU data. Similar information is displayed for the DIU status.
To modify the DIU data, you can either mark an item with MO for Modify on the "Items in Queue" screen and press ENTER, or press PF6 in the above screen. Either the "DATA Distribution Interchange Unit" screen or the "STATUS Distribution Interchange Unit" screen is displayed and you can modify the highlighted fields.
The following information is displayed on the "DATA Distribution Interchange Unit" and "STATUS Distribution Interchange Unit" screens:
| Origin Node | The name of the SNADS node (DSUN) from which the DIU originated. |
| Origin Name | The name of the SNADS user (DUN) who sent the DIU. |
| Origin Correlation | Part of the DIU identification (supplied by the SNADS application transactions which created the DIU). |
| Origin Date Time | The sender's local date and time when the DIU was created. |
| Origin Sequence No | The sequence number of the DIU. |
| Priority |
The options are: FAST (highest), DATA-16 to DATA-1 (lowest). Modifications of this value only influence the local mail node |
| Protection |
The DIU is to be stored on a non-volatile medium such as a disk file. The options are: YES and NO. This valuecannot be modified. |
| Capacity |
A value giving the maximum size of the DIU's distribution object. The options are: 0K, 4K and INDF (indefinite). This value cannot be modified. |
| Distr Object Count |
The number of distribution objects contained in the DIU. |
| Feedback |
Indicates whether SNADS is to generate feedback for the DIU in case of an error (e.g. if the hop count value is 0 and the DIU has not reached its destination node). Possible feedback values are: "Error Feedback" and "No Feedback". |
| Hop Count |
The SNADS architecture uses the concept of a hop count so that distributions do not wander endlessly through the network due to routing tables specified inconsistently. The hop count defines an upper limit for the number of connections in the path along which a DIU can travel. Each hop taken by a DIU decrements the hop count value by one. Con-nect SNADS uses the value that was specified on the "Control Info" screen during the Con-nect SNADS installation process. This value, which can be modified, is used as a limit for all DIUs that originate from the local Con-nect system. Provided the system has been properly set up, it should not be necessary to modify this field. However, if the hop count value of an incoming DIU is 0, you can modify this field if, for example, additional hops are needed for the DIU to reach its destination node. |
Note:
SNADS uses the values for the parameters "priority", "protection"
and "capacity" to route distributions through DSUs which provide only the
requested service. See Routing
Entries.
The "DIA Info" refers to IBM's "Document Interchange Architecture".
Con-nect SNADS distributions are assigned a series of service level parameters in the form of a DIA attribute list. DIA attributes are set automatically for distributions which originate from Con-nect . Unlike the SNADS service levels, they are not used for routing, and hence do not occur on the "Routing Entry" screen.
| Reply |
Is confirmation of delivery (COD) requested? Will the distribution object not to be appended to the document library upon receipt (COD/NAPP); i.e. is it to be handled as a note rather than as a document? Values: COD, NO COD, COD/NAPP Values generated by Con-nect SNADS: COD, COD/NAPP Con-nect SNADS generates a confirmation of delivery for the document units for which COD or COD/NAPP is requested. If a Con-nect user sends a document, Con-nect SNADS automatically generates the value COD. However, if a document is in final format (Con-nect format Txt) and contains no cover note, Con-nect SNADS generates the value COD/NAPP. The Con-nect user can avoid the generation of a COD/NAPP by entering "DOCU" or "DOKU" - this can be either in upper case or lower case - as the first four characters in the "Subject" line of the "Send" screen; now Con-nect SNADS generates the value COD. |
| Personal |
Is the distribution intended as personal? Values: YES, NO Value generated by Con-nect SNADS: NO Document units with the attribute "personal" are only delivered to users, standalone and private cabinets; not to the distribution lists, external mail nodes or nicknames. |
| Priority |
Does the distribution have urgent priority? Values: YES (for urgent messages), NO Value generated by Con-nect SNADS: NO This is not used by Con-nect SNADS. |
| Queue ID |
The name of the respective outbound queue. You can modify this field to move the DIU to another queue. |
| Queued At |
The time when the DIU was added to this queue. |
If you want to display a list of all addressees of a single DIU, either press PF8 on the "DATA Distribution Interchange Unit" or "STATUS Distribution Interchange Unit" screens or mark an item on the "Items in Queue" screen with RE for Recipients and press ENTER. The following screen appears:
3:22 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Recipients Friday
Origin Name: CONNECT1HSC
Origin Node: MINNE SOTA
No Recipient Name Recipient Node
---- ---------------- ----------------
1 ESHBERRYJOHN NEW YORK
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit
Please press a PF-key
|
The following information is shown on the "Recipients" screen:
- Origin Name
The originator (DUN) of this DIU.
- Origin Node
The node (DSUN) at which this DIU was originated.
- No
The recipients are sequentially numbered.
- Recipient Name
The recipient's DUN.
- Recipient Node
The recipient's DSUN.
Choose the Control Maintenance function from the "SNADS Administration Menu". The "Control Maintenance" screen which lists the contents of the control record - an enumeration of the SNADS DSUNs that have been assigned to the local Con-nect system is displayed:
11:24 * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Control Maintenance Friday
Hop Count: 16 Max Retries: 3
Status Save: 99 Days Retry Delay: 2
Log Level: 0 NPR Node: 123
Local Language: ENGLISH_ Com-plete Receive: **NA**
MRU Orig Seq No: 10 Com-plete Send: CPSEND
Local Node Name CON-NECT System DB-ID FNR Status (A: Active
-------------------- --------------- ----- ---- ------ N: Not Acces-
MINNE___ SOTA____ CONNECT1 180 37 A sible
U: Unknown )
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Add Modif Erase
Press a PF-key
|
This information shows how the local node names (DSUNs) are to be correlated with Con-nect (s) and underlying Adabas database IDs and file numbers. A single Con-nect SNADS driver can serve more than one Con-nect system on more than one Adabas file.
The following information is shown on the "Control Maintenance" screen:
- Hop Count
The initial hop count value. This is the maximum path length for any SNADS DIU that originates from this node. The hop count mechanism is intended to prevent DIUs from being relayed endlessly between the various nodes of a SNADS network as a result of an inconsistent setup of routing directives.
Con-nect SNADS requests error feedback if the hop count value reaches 0.
- Status Save
The number of days Con-nect SNADS waits for status DIUs to be returned in reply to messages sent from Con-nect . After this period, the relevant messages awaiting confirmation (see Messages Awaiting Confirmation of Delivery) should be deleted by the administrator. Any status DIUs that are returned after the messages have been deleted are ignored.
- Log Level
The amount of log information to be recorded.
- Local Language
The local language identifier which selects the required character conversion for text data. The identifier refers to the specifications made in the translation table (CONDTR1) used for the Con-form-to-DCA conversion facility.
- MRU Orig Seq No
Most recently used origin sequence number. This value is generated automatically. It is part of an identifier for distributions sent by Con-nect SNADS.
- Max Retries, Retry Delay
The maximum number of attempts that are made to establish a connection to an adjacent SNADS node before that connection is internally marked as out of service, and the interval (in minutes) between attempts. The DIUs that have been queued for transmission across that connection are held until explicit operator intervention restarts efforts to establish that connection. Timer-driven queues use the defined interval value.
- NPR Node
The Natural PROCESS ID with which the desired EntireX Broker Services (LU6.2 API) nucleus address can be identified.
- Com-plete Receive
Currently not evaluated.
- Com-plete Send
Only for EntireX Broker Services (LU6.2 API) environments with Com-plete. The name which is assigned to the Com-plete application program CPSEND (used to invoke Con-nect SNADS).
- Local Node Name
The SNADS DSUN. These are the names by which Con-nect is known in the SNADS network.
- Con-nect System
The name of the corresponding Con-nect system.
The next three fields are determined by the DS_ROUTER_DIRECTOR task at the start of each run and cannot be modified:
- DB-ID
The database number where the Con-nect system files are stored.
- FNR
The file numbers of the Con-nect system files.
- Status
The current status of the Con-nect system file. For example, if the DS_ROUTER_DIRECTOR cannot find or cannot access the specified database and/or file number, it returns the status N (not accessible) or U (unknown).
Con-nect SNADS requires information about the configuration of the SNADS network. Choose the Routing Entry Maintenance function from the "SNADS Administration Menu". The "Routing Entry Maintenance" screen is displayed. This screen lists all routing entries for the nodes with which you want to communicate (for an explanation of indirect routing, see Routing Entries):
3:28 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Routing Entry Maintenance Friday
Cmd Recipient Node Priority Prot Cap St Queue Description
--- ----------------- -------- ---- ---- -- -------- ----------------------
__ DAKOTA NORTH DATA-8 NO INDF A DAKOTA-N NORTH DAKOTA
__ DAKOTA SOUTH DATA-16 YES INDF A DAKOTA-S SOUTH DAKOTA
__ NEW MEXICO DATA-8 YES INDF A MEXICO-Q NEW MEXICO
__ NEW YORK DATA-8 YES INDF A YORK-Q NEW YORK
Position to Recipient Node: ________________
Cmds are 2 characters from the list below:
MO Modify ER Erase
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Add
Mark item(s) from the list above with a command or press a PF-key
|
The following information is shown on the "Routing Entry Maintenance" screen:
- Recipient Node
The DSUN consisting of the RGN and the REN. Each routing table entry refers to a fully or partially qualified SNADS DSUN. In case of partial qualification, either the REN portion or both the RGN and the REN portions of the DSUN can be replaced by an asterisk (*).
- Priority
The priority options are: FAST (highest), STATUS, DATA-16 to DATA-1 (lowest).
- Prot
DIUs must be stored on a non-volatile storage medium at relay or target nodes. The protection options are: YES and NO.
- Cap
The maximum size of a SNADS DIU. The capacity options are: 0K, 4K and INDF (indefinite).
- St
The status of the queue. Possible values for the queue status are: A (active) and I (inactive).
- Queue
The name of the queue.
- Description
Optional - a description of the routing entry.
- Position to Recipient Node
If the displayed list is longer than one page, enter the name of the recipient node which you want to scroll to the top of the display.
If you want to add a routing entry, press PF4 on the "Routing Entry Maintenance" screen to display the following screen (a similar screen is shown if you mark an item on the "Routing Entry Maintenance" screen with MO for Modify and press ENTER):
3:16 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Routing Entry Friday
_________________________________________________________________________
Recipient Node: ________ ________
Priority: DATA-8_ (FAST,STATUS, DATA-16 .. DATA-1)
Protection: YES (YES, NO)
Capacity: INDF (0K, 4K, INDF: indefinite)
Status: A (A: active, I: inactive)
Next Queue: ________
Description: ______________________________
_________________________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Conf
Add routing entry
|
Specify the following information on the "Routing Entry" screen:
- Recipient Node
The name of the recipient node (the DSUN consisting of RGN and REN).
See Routing Entries.
Note:
Priority, protection and capacity are SNADS service level parameters
(see Service
Levels); values other than those recommended (see default
values in the above screen) should be used only when an administrator
understands the significance of the SNADS settings.
- Status
The options are: A (active) and I (inactive). An inactive status allows the SNADS administrator to disable a route temporarily without having to add the routing entry again when it is re-activated.
- Next Queue
The name of the queue to which a DIU is to be transmitted.
- Description
Optional - a description of the routing entry.
After you have completed your specifications, press PF5 to confirm the addition of the routing entry.
Notes:
This function comprises a set of specifications which link a SNADS DUN to a user of a local Con-nect system, thus allowing that user to be specified as a recipient of a SNADS DIU.
It is not mandatory, however, to link a SNADS DUN to a user. If an assignment cannot be found for the DUN of a local recipient and if the DGN is equal to one of the multi-node identifiers of the local Con-nect system, the system performs a lookup in the respective user directory of the Con-nect system file, and tries to locate a user ID or a unique user name that is equal to the DEN. If a user is found, that user is assumed to be the intended recipient.
Choose the Local User Maintenance function from the "SNADS Administration Menu". The "Local User Maintenance" screen which lists all local user assignments is displayed:
3:36 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Local User Maintenance Friday
Cmd SNADS User Name CON-NECT System User ID
--- ----------------- ---------------- --------
__ BOHANNON MARC CONNECT1 MBO
__ DENT IAN CONNECT1 IDE
__ MILLER JOAN CONNECT1 JMI
__ PETERSON PAUL CONNECT1 PPA
__ PINTER MIRIAM CONNECT1 MPI
Position to SNADS User Name: ________________
Cmds are 2 characters from the list below:
MO Modify ER Erase
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Add
Mark item(s) from the list above with a command or press a PF-key
|
The following information is shown on the "Local User Maintenance" screen:
- SNADS User Name
The SNADS name which has been assigned to a Con-nect user by the administrator (the DUN, consisting of DGN and DEN).
- Con-nect System
The local Con-nect system of the local Con-nect user.
- User ID
The user ID of the local Con-nect user.
- Position to SNADS User Name
If the displayed list is longer than one page, enter the name of the SNADS user which you want to scroll to the top of the display.
By default, Con-nect SNADS assigns a SNADS DUN to all local Con-nect users who are not specified in the local user table. The DUN is made up of the local Con-nect system ID (DGN) and the local Con-nect user ID (DEN).
Note:
If you mark an item with ER for Erase in this screen, the
marked item is erased immediately. You are not asked to confirm the
deletion.
If you want to add a local user entry, press PF4 on the "Local User Maintenance" screen to display the following screen (a similar screen appears if you mark an item with MO for Modify on the "Local User Maintenance" screen and press ENTER):
3:39 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Local User Entry Friday
____________________________________________
SNADS User Name: ________ ________
CON-NECT System: ________
CON-NECT User ID: ________
____________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Conf
Add user entry
|
Note:
See Local
SNADS Addresses (DUNs) for additional information on local
SNADS addresses (DUNs).
Enter the following information on the "Local User Entry" screen:
- SNADS User Name
The SNADS name which has been assigned to a Con-nect user by the administrator (the DUN, consisting of DGN and DEN).
- Con-nect System
The local Con-nect system of the local Con-nect user.
- Con-nect User ID
The user ID of the local Con-nect user.
After you have completed your specifications, press PF5 to confirm the addition of a local user entry.
Upon receipt of a SNADS status DIU that references a SNADS DIU which originated from the local Con-nect system, Con-nect SNADS appends delivery and error notifications to the address list of the respective Con-nect Outbasket entry.
Choose the Messages Awaiting Confirmation of Delivery function from the "SNADS Administration Menu". The following screen which lists all users of the local system who are still waiting for SNADS status DIUs is displayed:
2:28 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Messages Awaiting Confirmation of Delivery Friday
Cmd Origin Name Origin Node Origin Date and Time
--- ----------------- ----------------- ----------------------
__ CONNECT1 HSC MINNE SOTA 14.Feb.94 1:46 PM
__ CONNECT1 HSC MINNE SOTA 14.Feb.94 1:58 PM
__ CONNECT1 HSC MINNE SOTA 14.Feb.94 2:01 PM
__ CONNECT1 HSC MINNE SOTA 14.Feb.94 2:02 PM
Cmds are 2 character from the list below:
AD Recipients ER Erase
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit Erall
Mark item(s) from the list above or press a PF-key
|
The following information is shown on the "Messages Awaiting Confirmation of Delivery" screen:
- Origin Name
The name of the originator of the DIU.
- Origin Node
The name of the local Con-nect system where this DIU originated.
- Origin Date and Time
The date and time when the DIU was sent.
Note:
If you mark an item with ER for Erase in this screen, the marked item
is erased immediately. You are not asked to confirm the deletion.
A DIU can be sent to more than one recipient. For a list of all recipients of a DIU for whom confirmation of delivery is missing, mark the respective item on the "Messages Awaiting Confirmation of Delivery" screen with AD for Recipients to display the following screen:
2:25 PM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet LS Recipients Friday
Origin Name: CONNECT1HSC
Origin Node: MINNE SOTA
No Recipient Name Recipient Node
---- ---------------- ----------------
1 LONG SONYA DAKOTA SOUTH
2 LONG WILLIAM DAKOTA SOUTH
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit
Please press a PF-key
|
The following information is shown on the "Recipients" screen:
- Origin Name
The originator (DUN) of this DIU.
- Origin Node
The node (DSUN) at which this DIU originated.
- No
The recipients are sequentially numbered.
- Recipient Name
The name of the recipient (the DUN consisting of DGN and DEN).
- Recipient Node
The name of the system to which the message was sent (the DSUN consisting of RGN and REN).
When confirmation of delivery arrives from one recipient, the respective item is erased from the above list. When confirmation of delivery has arrived for all items, the respective entry is erased from the "Messages Awaiting Confirmation of Delivery" screen.
Each significant event that occurs during the execution of Con-nect SNADS routines is recorded in a section of the Con-nect spool file, which is made up of Con-nect SNADS log records. Significant events are: originating, routing, sending, receiving and directing of SNADS DIUs, as well as any kind of Natural or SNA exceptional conditions.
Con-nect SNADS retains log information for each significant action in order to facilitate problem determination and general supervision by a Con-nect administrator. To avoid excessive disk space usage, a Con-nect administrator should occasionally purge obsolete log data from the Con-nect spool file.
Choose the Log Information Maintenance function from the "SNADS Administration Menu" to display the following screen:
3:32 PM * * * C O N - N E C T 3 * * * 5.Feb.98
Cabinet LS SNADS - Log Information Maintenance X-FLG-M
Cmd Actor Program Log Time Ty Log Message
--- -------- -------- ------------------- -- ---------------------------------
__ X-FWTCH 1998-01-22 09:52:18 02 CSL WATCH DOG STOPPING ***DMY**
__ RECEIVER X-FDEM 1998-01-22 10:10:48 02 STARTING RECEIVE E
__ RECEIVER X-FIN000 1998-01-22 10:10:50 96 3COMPLETECNT312CO
__ RECEIVER X-FIN000 1998-01-22 10:10:50 96 1COMPLETECNT312COCNT312COXSISKU
__ ROUTER X-FR 1998-01-22 10:10:52 98 3COMPLETECNT312CO
__ DIRECTOR X-FT-N5 1998-01-22 10:10:52 98 3COMPLETECNT312CO
__ ROUTER X-FR 1998-01-22 10:10:52 98 1COMPLETECNT312COCNT312COXSISKU
__ DIRECTOR X-FT-N3 1998-01-22 10:10:53 98 1COMPLETECNT312COCNT312COXSISKU
__ SNADS-SE X-FN1-1 1998-01-22 10:10:55 98 3COMPLETECNT32
__ ROUTER X-FR 1998-01-22 10:10:55 98 3COMPLETECNT32
__ DS-SEND X-FON000 1998-01-22 10:11:01 96 3COMPLETECNT32
__ RECEIVER X-FDEM 1998-01-22 10:39:45 02 STARTING RECEIVE E
__ RECEIVER X-FIN000 1998-01-22 10:39:46 96 1COMPLETECNT312COCNT312COXSISKU
__ ROUTER X-FR 1998-01-22 10:39:47 98 1COMPLETECNT312COCNT312COXSISKU
Cmd: Position to Log Time: ______________
DI Display ER Erase TO Top (YYYYMMDDHHMMSS)
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit ErAll - + -- ++
Mark item(s) from the list above with a command or press a PF-key
|
The following information is displayed:
- Actor
The name of the server program. See Con-nect as a SNADS Node.
- Program
The name of the program which generated the log record.
- Log Time
The time the log record was created.
- Ty
Type. These values are used internally by Con-nect SNADS.
- Log Message
Information used for tracing.
- Position to Log Time
If the list is longer than one page, you can enter a date and time in this line to scroll the list to the specified date and time.
Note:
If you mark an item with ER for Erase in this screen, the
marked item is erased immediately. You are not asked to confirm the
deletion.
You can use the following PF-keys to page through the list of log records:
| PF8 | Display the previous page (-). |
| PF9 | Display the next page (+). |
| PF10 | Display the first page (--). |
| PF11 | Display the last page (++). |
You can also mark an item with TO for Top and press ENTER to scroll the marked item to the top of the list.
The following screen displays information which help the Software AG staff when problems occur.
Mark any item with DI for Display on the "Log Information Maintenance" screen to obtain extended information about this item. The following screen appears which contains coded information about events or exceptional conditions:
10:25 AM * * * C O N - N E C T 3 * * * 14.Feb.94
Cabinet Extended Information about Marked Friday
Log Record
Program: X-FS-N2 Actor: SNADS-SEND
Log Time: 199402131119147 Msg Type: 98
Message:
DIU Type : DATA Result : OK
Origin DSUN : EBER CICS1 Origin DUN : FCT1 LS
Origin TIME : 1994021311171070 Origin SEQ : 176
Xaddr1 : Xaddr2 : FCT1
Xaddr3 : LS
Fdbk DSUN : Fdbk DUN :
Fdbk TIME : Fdbk SEQ :
NCODE1 : 1 NCODE2 :
ACODE1 : ACODE2 :
Applic Text :
Applic Content:
Message :
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Menu Quit
Press a PF-key
|
Program XF-GETH is delivered as a source program. It can be set up to delete obsolete SNADS service log records.
When you define the parameters #HOURS and #LOGSETNUMBER and stow your modifications, this program is run each time a queue server program is activated.
When XF-GETH is run, it checks the SNADS log records for records older than the value defined in parameter #HOURS. If any records are found, they are deleted. If the total number of old records is more than the value defined in parameter #LOGSETNUMBER, only the number of records defined in this parameter are deleted. The remaining records will be deleted the next time XF-GETH is run. If log records exist but are not older than the value in parameter #LOGSETNUMBER, they are not deleted.
To edit XF-GETH, enter the following at the Natural Next prompt:
E XF-GETH
0060 DEFINE DATA 0070 PARAMETER 0080 1 #HOURS (N6) 0090 1 #LOGSETNUMBER (N5) 0100 END-DEFINE 0110 * 0120 * Value defined for #LOGSETNUMBER determines the number of logs 0130 * erased if they are older than #HOURS 0140 * 0150 COMPUTE #HOURS = 24 0160 COMPUTE #LOGSETNUMBER = 100 0170 * 0180 END
You can modify the following parameters:
- #HOURS
Default is 24 hours. Defines the frequency, in hours, the log records are erased.
- #LOGSETNUMBER
Default is 100 records. Determines the total number of records deleted at one time. If the current number of log records is greater than this value, they are deleted the next time XF-GETH is activated.
See Initialization of the Con-nect Spool File for a description of how to initialize the Con-nect SNADS control information.
When you choose this function from the "SNADS Administration Menu" and the control informaiton has been initialized, a message is displayed indicating that the control information already exists.
Con-nect SNADS retains information for each SNADS distribution that originates locally. Incoming SNADS delivery and error notification are correlated with the outbasket entries of a local Con-nect system and the appropriate messages are inserted there. Part of the normal procedure performed by Con-nect SNADS is the deletion of correlation data as soon as the SNADS feedback notification has been received and processed. However, if feedback notifications are lost (e.g. due to an external system failure), the respective correlation data are not deleted automatically. The Con-nect administrator should regularly purge obsolete correlation data from the Con-nect spool file. See Messages Awaiting Confirmation of Delivery.
Con-nect SNADS internally employs standard multi-node Con-nect routines to convey information between the Con-nect spool file and the Con-nect system file(s). It is important to note that Con-nect SNADS records that have been marked as "logically purged" remain in the Con-nect spool file. This means that the Con-nect administrator must occasionally purge these records from the Con-nect spool file with the Delete Spool File Entries function. See Delete Spool File Entries.
Log records must be periodically deleted from the spool file with the Log Information Maintenance function.
X-0INIT can be used to set all defaults for the call or driver:
- #ERROR-TA
Error transaction.
- #DEF-MINUTES
Start program X-0INIT every nnn minutes. If this value is 0 or batch job, the job is run one time only.
- #DEF-CABINET
Cabinet to be used if no cabinet is entered in address data.
- #TXT
Name of driver to be started.
- #ZTXT
Name of driver to be started to process external mail created by subprogram Z-MAILA.
- #DEF-INPUT
Terminal I/O with SET CONTROL "N" 0 = no.
Note:
#DEF-MINUTES and #DEF-INPUT are only valid in online mode.
In the case of external mail items (e.g. SNADS) created with the API subprogram Z-MAILA, it is imperative that X-0INIT is called after Z-MAILA is executed. Thus, X-0INIT will automatically invoke X-FZ, which is used to transmit external mail items onto the recipient nodes.