Update for MCP 63

When the Resolver lookup of the TCPIP Hostname fails, error messages now displays the Host Name being looked up.

Recorder will now handle problems connecting to resolver in a more controlled manner. When sending SNMP traps attempts to establish the Source IP adddress will now retry for each sent trap. Resolver errors are now more clearly identified and logged.

This change introduces logging to Recorder. Most displays may now be logged to the Supervisor Log. Logging is controlled by the TT REC LOGging command. TT REC LOG or TT REC LOGGING with report whether logging is active or inactive. TT REC LOG + or TT REC LOGGING + will enable logging. TT REC LOG - or TT REC LOGGING - will disable logging. All entries are stored with an identifier of REC so can be seen using TT LOG REC. The first time the new version of Recorder runs it will turn on the logging option.

If Recorder was thawed then any task trying to link to the library would hang until Recorder quit. This could on rare occasions cause Supervisor to hang (DSing Recorder would correct this). This change forces Recorder to quit if a Thaw command is entered.

Some versions of the Algol compiler had a bug which gives bad results for some expressions involving numeric constants. This change avoids the bug.

Internal change only.

Record mnemonics passed to the exported procedure HOTLINE_MSG are now upcased.

The value of MaxMessage is now used to calculate the number of octet string required in a trap. Previously only Maxpacket and MaxOctet were used.

Ex. MaxMessage=450 Maxoctet=450 MaxPacket=700 now correctly calculates that only one octet string is required instead of two in the previous version.

In the Mib extension #SUMMARY a space has been added after '%s of %s:'.

It was possible for the first SNMP trap, after Recorder has started, to cause Recorder to fault with an IO error on the UDP port. The cause of this error has been fixed and any subsequent IO errors will write debug info to the taskfile , rather than causing a fault.

The Mib extensions generated in the REC SNMP MIB command will now match those required by the SNMP-Server (CA Unicenter NSM). To generate extensions for Tivoli use REC SNMP MIB TIVOLI <file name>.

An Mib extension is now generated for Severity. The Severity value is taken for the Record Name. SO REC NAMES + WARNING SNMP will have a Mib entry with --#SEVERITY=WARNING. If SNMP Record names do not match valid severity values then the Mib files should be edited before importing into your SNMP Server.

The REC SNMP DEST command has been changed.

-- REC -+- CLOSE -+--- <Mnem> ------+---------------------------+-|
|         +--- <Intgr> -----+                             |
+- NAMES -+-----------------------------------------------+
|         +--- <Mnem> ---- = <Intgr> --+---------------+--+
|         |                            +-- <File map>--+  |
|         +- + <Mnem> --+-------------+--- <File map>-----+
|         |             +- = <Intgr> -+                   |
|         +- - <Mnem> ------------------------------------+
+- QUIT --------------------------------------------------+
+- TCPIP --+------------+---------------------------------+
|          +- <Intgr> --+                                 |
+- SNMP -+------------------------------------------------|
|        +- MIB -- <File Title> --------------------------|
|        +- DESTination -+-----+ <IP and Community> ------|
|        +- MAXPacket -- <integer> -----------------------|
|        +- MAXOctet --- <integer> -----------------------|
|        +- MaxMessage - <integer> -----------------------|
+- VER ---------------------------------------------------+

<IP and Community>

---- <IP address> -- " -- <String> -- " ----------------------I

The DESTination option is to add an addrress and community string where Traps should be sent. If there are no addresses specified then no SNMP TRAPS can be sent. To delete a specific Ip/Community the - prefix is used and both IP and community must be specified. Ex. REC SNMP DEST 10.0.0.35 "supervisor"

REC SNMP DEST - 10.0.0.1 "public"

A new option MaxMessage has been added to REC SNMP. The MAXMessage option is the maximum size of text which will be sent for a single Record. If this value is greater than 0 then messages will be truncated to this size before being split into packets.

Using the UNISYS SNMP implementation restricted strings in SNMP traps to 258 characters. A UCF requesting that this be fixed, prompted the limit to be reduced to 255 characters. This change allows Recorder to generate SNMP traps without using the Unisys SNMP interfaces.

A new SMNP variant has been added to the TT REC command.

--+- SNMP -+------------------------------------------------!
+- MIB -- <File Title> --------------------------!
+- DESTination -- <IP address list>--------------!
+- MAXPacket -- <integer> -----------------------!
+- MAXOctet --- <integer> -----------------------!

The SNMP variant is used to control SNMP traps sent by Recorder when a RECORD statement, which maps onto type SNMP, is performed. SNMP traps no longer require UNISYS SNMP to be configured. Four options can follow the SNMP variant.

If no option is specified then the SNMP settings are reported.

The MIB option creates an SNMP Mib file to match any Name Mnemonic set to send an SNMP trap. Ensure that the title passed has a Usercode and Family and that any level with a dot character is quoted. The generated file should be transferred to any system used to monitor SNMP traps, and be compiled into the MIB database. Note that if MAXOctet or MAXPacket are changed then the MIB file should be regenerated as the number of variables in a Trap could change. The MIB file contains extensions which can be used by the Tivoli mib2trap utility.

Ex. REC SNMP MIB (BOB)SNMP/"""META.MIB""" ON DEV

The DESTination option is to provide a list of IP addresses where Traps should be sent. If there are no addresses specified then no SNMP TRAPS can be sent. At present the Trap community is hard coded as 'public'. If this is not suitable , please contact Metalogic.

Ex. REC SNMP DEST 10.0.0.35,10.0.0.4$"

The SUPERVISOR implementation of the RECORDER program has been changed. RECORDER is now initiated by SUPERVISOR using a library linkage instead of direct initiation. SUPERVISOR links to the RECORDER library via the SL RECORDERLIB which will be automatically established by the INSTALL utility. The USE TASK.. FOR RECORDER command will be deimplemented.

This change allows RECORDER to be more freely available for other Metalogic software; FLEX Inquiry has now been extended to support its own version of the OPAL RECORD statement. Please see FLEX LIBRARY DNote 510.22 for more details.

Recording a message of more than 868 characters to an SNMP destination would cause recorder to fault. The correct limit in Unisys *SYSTEM/SNMPAGENT is 258 characters. Messages longer than 258 characters will be truncated.

Version 510.03 included debug code which caused a delay in the response to a TT REC VER command. The debug code has now been removed.

Version 510.03 was an incomplete patch. Responses to TT REC commands were no longer returned. This problem has now been corrected.

If the TT REC CLOSE command is used for a mnemonic which maps on to a disk or byte file, it will now return a message which includes the file title.

tt rec close tmp
Closed *SUPERVISOR/RECORD/TMP/"THURSDAY.TXT" ON DISK
or
tt rec close tmp
Closed_Already *SUPERVISOR/RECORD/TMP/"THURSDAY.TXT" ON DISK

The Opal code:
$FTitle:=Keyin("TT REC CLOSE TMP"); If Not($Rslt:=$Ftitle.Split(" ") HdIs "Closed") Then Begin $FTitle:=Empty; SHow("Error ",$Rslt,,$Ftitle); End;

could be used to store the title on the 'TMP' record file in $FTitle

Prevent SEG ARRAY ERROR with long messages.

This change updates RECORDER's internal version to reflect MCP 51.1 compatibility.

This change corrects the formatting of SNMP Traps. Previously every trap was reported as Trap 1 no matter which value was passed in the RECORD statement.

The MIB file generated by the REC MIB command is now compatible with the Tivoli MIB2TRAP utility.

Ex. TT REC MIB (BOB)"RECORDER.MIB" ON DEV
Transfer the file to the PC where tivoli is running
From the command promt on the PC
MIB2TRAP RECORDER.MIB TRAPS.BAT
generates a batch file to configure the traps in Tivoli
Executing TRAPS.BAT will configre the traps.

The REC NAMES command has been extended to allow SNMP as a file type mnemonic. If SNMP is set on a Names Mnemonic then when a Record of that type is done Recorder will attempt to send an SNMP trap with the text of the Record statement as a parameter. The UNISYS SNMP AGENT must be active (See NW SNMP command response) and the TRAPCOMMUNITY must be set up to direct traps to the PC running your SNMP manager. (See NW SNMP TRAPCOMMUNITY response).

The REC MIB <File Title> command will generate a MIB file which can be loaded into you SNMP Manager to interpret the Recorder Traps.

Ex.
If Rec Names Returned

--- RECORDER File Mapping Mnemonics ---
--- 0 of 18 Disk Files currently open ---
RECORD [01] mapped to SNMP BYTE,SNMP
RECORD [02] mapped to IPP BYTE,PORT
RECORD [04] mapped to TEST BYTE
RECORD [12] mapped to HEROIX PORT=10.0.0.26
RECORD [13] mapped to CRITCL BYTE,SNMP
RECORD [14] mapped to BOBC PORT
RECORD [15] mapped to BOB PORT
RECORD [16] mapped to STATUS PORT
RECORD [17] mapped to META_MIN PORT
RECORD [18] mapped to META_FULL PORT
RECORD [19] mapped to META_STATUS PORT
RECORD [20] mapped to META_WARN PORT
RECORD [21] mapped to DEBUG PORT
RECORD [23] mapped to ALERT BYTE
RECORD [24] mapped to RSVP BYTE,PORT,SNMP
RECORD [63] mapped to FRED

Default DISK files NOT mapped 0,3,5,11
Default PORT files NOT mapped 6,7,8,9,10,11,47
Default VAR files NOT mapped 50,51,52,53
.....

Then REC MIB (BOB)SNMP/"META.MIB" ON DEV
would create a MIB like:
METALOGIC-MIB DEFINITIONS ::= BEGIN
-- Title: Metalogic MIBs
-- By : Metalogic SaRL Luxembourg
IMPORTS
enterprises
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
DisplayString
FROM RFC-1213
unisys,a-series,sms,a-snmp
FROM UNISYS-MIB ;
metaRecorder OBJECT IDENTIFIER ::= {a-snmp 255}
-- the Recorder group
-- Recorder generates SNMP traps based on
-- data received from Supervisor.
metaRecTrapText OBJECT-TYPE
SYNTAX DisplayString
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"Text sent in Recorder SNMP traps."
::= {metaRecorder 1}
metaTrap_SNMP TRAP-TYPE
ENTERPRISE metaRecorder
VARIABLES {
metaRecTrapText
}
DESCRIPTION
"This enterprise specific trap is sent when Recorder receives a message with mnemonic SNMP, from Supervisor."
::=1
metaTrap_CRITCL TRAP-TYPE
ENTERPRISE metaRecorder
VARIABLES {
metaRecTrapText
}
DESCRIPTION
"This enterprise specific trap is sent when Recorder receives a message with mnemonic CRITCL, from Supervisor."
::=13
metaTrap_RSVP TRAP-TYPE
ENTERPRISE metaRecorder
VARIABLES {
metaRecTrapText
}
DESCRIPTION
"This enterprise specific trap is sent when Recorder receives a message with mnemonic RSVP, from Supervisor."
::=24
END
Note that the standard UNISYS MIB must be loaded before the generated MIB.

This change is intended to simplify direct connections between Recorder and Hotline programs running on PCs.

A series of commands are accepted from the PC to determine the form of text to be sent to the PC. Each command must be prefixed by the literal PCHOT: All responses are in Ascii and are prefixed by a string in the form vvyyyydddsssss:<hostname> where vv is a version number for the response format, yyyyddd is todays date in Julain format, sssss is the current time of day in seconds and <hostname> is the host name of the system sending the message.

Ex. 01200414931535POWEREDGE:

Two commands are user to determine the messages which will be sent to the PC and their format.

The Headings command accepts one of more of TIME, MNEMONIC, HOSTNAME as parameters. The parameters determine if any prefix is to be added to the messages from Supervisor via Recorder. The order of the parameters determines the order in which they appear in the message.

TIME causes a timestamp in the form hh:mm:ss to be added. MNEMONIC causes the Mnemonic used in the Record statement to be added. Hostname causes the Hostname where the Record was done to be added.

Ex.
PCHOT:headings mnemonic hostname time would give a response of
01200414934101POWEREDGE: Headings Mnemonic, Hostname, Time and
subsequent record message would look like: META_FULL POWEREDGE
09:44:50:C 8227/8227 OK (IPP)OBJ/LIBSELECTOR

The REQUEST command is used to specify which RECORD messages are to be sent to the PC. It expects a list of or Recorder Mnemonics or Numbers.

Ex. PCHOT:Request 6,meta_full returns 

01200414937098POWEREDGE:6 set META_FULL(24)set

HEADING and REQUEST commands can be combined by separating the two commands by a ; (semi-colon). A separate response is generated for each command.

Ex. PCHOT:Heading time hostname mnemonic;Request 6,meta_full returns
01200414937218POWEREDGE: Headings Time, Hostname, Mnemonic
01200414937218POWEREDGE:6 set META_FULL(24)set

Two other command are available. The NAMES command returns a list of valid mnemonics or port numbers.

Ex. PCHOT:names returns 01200414937661POWEREDGE:CRITCL EOJ RSVP EOT CONFIG
SECERR SYSMON 9 10

The TT command can be used pass commands to Supervisor. A response acknowledging the command is returned. Any Supervisor responses are sent with a mnemonic of TT.

Ex. PCHOT:TT WS

Returns

01200414938656POWEREDGE:Sent TT WS
10:44:17 POWEREDGE TT: ------- METALOGIC SUPERVISOR Mix 15431 --...
10:44:17 POWEREDGE TT:SUPERVISOR Version 50.500.13 Compiled at 14:35 ..
10:44:17 POWEREDGE TT:Attributes Version 50.500.07 Modified at 11:50 ..
10:44:17 POWEREDGE TT:OPAL Version 50.500.10 Compiled at 14:29 ..
10:44:17 POWEREDGE TT:MAGUS Version 50.500.02
10:44:17 POWEREDGE TT:MCPs from Version 46.0 to 50.999 are compatible..
10:44:17 POWEREDGE TT:
10:44:17 POWEREDGE TT: ---- LICENSE DETAILS ----
10:44:17 POWEREDGE TT:Installed modules : SUPERVISOR Permanent
10:44:17 POWEREDGE TT: LOG CONTEXTS Permanent
10:44:17 POWEREDGE TT: TRIM Permanent
10:44:17 POWEREDGE TT: ODT CONTROL Permanent
10:44:17 POWEREDGE TT:
10:44:17 POWEREDGE TT: ---- RUN-TIME DETAILS ----
10:44:17 POWEREDGE TT:Maximum WHEN slots : 40
10:44:17 POWEREDGE TT:Task PRIORITY : 50
10:44:17 POWEREDGE TT:Monitor session : Inactive
10:44:17 POWEREDGE TT:Compile-time option DEBUG is SET

RECORDER will now correctly update the REC_FILEMAP config variable when any '=DATE' modifier was used (implemented in Dnote 490.02). Previously, any date assignments were lost when RECORDER or SUPERVISOR was restarted; this problem is now fixed.

Also, the REC NAMES command did not correctly process valid input after any '=DATE' modifier e.g.

REC NAMES TEST BYTE=DATE,PORT

In the above case, the PORT assignment would be ignored unless it preceded the BYTE=DATE text string. This problem is also resolved.

By using a '=DATE' modifier in a TT REC command it is now possible to have a date as the last level of a RECORDER disk file.

See TT HELP REC for full details.

The internal version of RECORDER has been updated to reflect MCP 49.1 compatibility.

The UnderScore character is now allowed in Record names.

Code was added to support the PC Hotline program.

When the Recorder Names are changed using a TT REC NAMES command, a Recorder Message with the Category RcdRefresh (27) is issued to Recorder Connection Block Clients.

Prevent Invalid Index with long record.

Prevent Invalid Index in Note_Change due to global array conflict.

RECORDER was not correctly handling all HOTLINE file state changes, in particular for TCPIP connections to PCs, where the changed state became CLOSEREQUESTRECEIVED or CLOSREQUESTED. In effect, RECORDER ignored this file state leaving the subfile in a closed or closing state and effectively unusable.

For regular CLOSEREQUESTRECEIVED transitions, this would eventually use all of RECORDER's subfiles, requiring a TT REC QUIT to resolve. This problem is now fixed.

A Record Category greater than 47 would cause a fault if Filters were installed. If the NAME Task Attribute contained non alpha characters the Filter HandShake would loop.

If a RECORDER port mnemonic name had more than 6 characters, HOTLINE would truncate the name length to 6 and, also, it was possible for the HOTLINE program to fault with a SEG ARRAY error at sequence 897000. RECORDER and HOTLINE handshake will now correctly handle long mnemonic names.

The TT REC NAMES command will now disallow mapped mnemonic names with more than 17 characters.

In certain circumstances it was possible for a port file connection to be closed without internal flags for that port being reset. This would cause subsequent RECORDs to that port to fail with an IO error. The flags are now reset no matter how the port is closed.

Recorder now supports a Port file to a nominated IP address. The REC NAME syntax has been extended to allow the specification of an IP address. Ex:
TT REC NAME + HEROIX PORT=10.0.0.26

A TT REC QUIT should be done after setting or changing any PORT mappings.

Record messages passed to this port have no additional data added to (i.e. Not timestamp or Hostname). The port is closed after each write.

This change was made to enable Supervisor to create HEROIX ROBOEDA events. The layout of the events is controlled by Opal routines. Metalogic have a suite of example Opals available to anyone interested in passing events to ROBOEDA.

The TT REC TCPIP command is used to specify the PORT number to be used. (2919 is the default value for ROBOEDA).

Recorder now freezes as a Library and exports the procedure

PROCEDURE HOTLINE_MSG(TEXT);
EBCDIC ARRAY TEXT[*];

This procedure will pass a message to Recorder as if an OPAL Record statement had been done.
The Text of the message may start with a control sequence to determine the Record parameter.
Ex. passing "[WAIT]THIS IS A TEST"
Is equivalent to RECORD[WAIT]("THIS IS A TEST")
passing "[6]YET ANOTHER TEST"

If the prefix does not map onto a valid 'REC NAME' or number, then the prefix is not stripped from the text and the default record value is used.
If the NAME DEFLIB has been defined then that name is used for the default Record. If DEFLIB is not defined then [0] is used as the default.

A TT REC QUIT will return a warning if users are linked to Recorder. A subsequent TT REC QUIT will force RECORDER to quit killing any tasks which are linked.

A TT REC VERSION will show how many tasks are linked and also shows the mix number of recorder. A <recorder mix number>Y command will list all of the linked tasks. The TT REC VERSION command resets the 'pending quit' flag so that if tasks are still linked it will again require two Quit commands to terminate.

This patch is only to change the version to 48. Version 470.04 is valid for MCP 48.

If the HOTLINE program was run under the * Usercode, remote BNAv2 host connections would show two spurious error messages e.g.

USERDATA ERROR  35 - no alias for *ANYUSER OF NX4200MCP
USERDATA ERROR 35 getting alias of  OF NX4200MCP

These messages have now been removed.

Also, some anomalies and formatting issues have been resolved when using some variants of the TT REC command.

RECORDER will now correctly handle multi-line messages, where lines are delimited by CR or nul characters, when writing to all disk file types. Previously, RECORDER would only write the first line of the message.

The changes implemented by patch 470.01 had the unwanted side-effect of not closing RECORD files after a date change. Normally, the first RECORD statement after midnight would close any existing disk files and, when required, open new files with the appropriate day name in the file title. This problem meant that, although no data would be lost, the same RECORD files would always be used be used until a RECORDER restart.

This problem is now fixed.

Further, the prefixing of a timestamp at the beginning of each RECORD that is written to Supervisor's fixed DISK files (i.e. not variable or byte) can be inhibited by setting the following Magus config variable:

U META/INSTALL RECORDER_NOTS=TRUE

A restart of RECORDER is required after making this change and RECORDER will display an appropriate message during its start-up.

The REC NAMES command has been considerably modified to allow more flexibility with the assignment of mnemonics to specific file numbers. New or existing file mappings can be mapped to user-selected file numbers as long as the number is not already mapped. For example:

TT REC NAMES RSVP=3 PORT
TT REC NAMES + TEST=25 BYTE

In example 1, the existing mnemonic RSVP is being re-mapped to file number #3; any existing assignment for RSVP is deleted and its prior file number is returned. In example 2, the new mapping TEST is assigned a file number #25 and is assigned a kind of PORT. More information on the complete syntax can be found by examining the response to a TT REC HELP command.

A new REC modifier, TCPIP, has been added which allows the user to easily control if RECORDER should be using TCPIP or BNAv2 services for its port files. The current status is always shown in the response to a TT REC VER command.

For example:

TT REC TCPIP -
TT REC TCPIP 22222

Using the '-' modifier will cancel a TCPIP assignment to a BNAv2 setting. Using the <port> modifier will cause force RECORDER to use TCPIP, with socket number assigned by <port>, instead of BNAV2. Both of these changes are applied only after the next RECORDER restart.

Previously, RECORDER was susceptible to problems when the critical MCP Independent Runner OLAYSCOUT was waiting for available sectors on disk. This was because of RECORDER's extensive use of local arrays which has now been eliminated. Although we cannot guarantee that any of our software will continue to function normally when OLAYSCOUT is waiting, the problems caused for RECORDER have been greatly minimised.

Version 450.08 introduced a problem when two different Record disk (Jobsymbol) files were open at the same time. Corruption two both files could occur, with spurious data from previous files on disk appearing.

This problem has now been corrected.

Previously, RECORDER was not correctly closing all his offered port subfiles during an orderly termination. This could have caused warning messages about lost data during a close down as well as misleading HOTLINE write errors when a HOTLINE client had terminated.

Further, if RECORDER was restarted by a RECORD message from a SUPERVISOR WHEN, any waiting HOTLINE clients eligible to pick up the message *may* have failed to receive it. This patch allows 15 seconds for RECORDER to reconnect to other HOTLINEs, in the event of a restart, before handling any queued RECORDs. However, if any HOTLINES fail to connect during this period, these queued messages will be discarded.

This change fixes an invalid index which could happen when adding new mappings using the REC NAME command.

This change corrects a problem where VAR type files had a timestamp added, and were not correctly recovered after an interruption.

A new Record type has been added. BYTE will create a character stream file suitable for access via NXSERVICES. Adding 60:STATS=BYTE/ to the config variable REC_FILEMAP would allow a RECORD[STATS] to write to character stream file SUPERVISOR/RECORD/<dayname>/STATS.

The TT REC command has been extended with two new modifiers.

TT REC CLOSE <mnemonic<
Is used to close the disk file associated with the Mnemonic.

TT REC NAME - <mnemonic<
Removes the mapping for the supplied mnemonic.

This command maps a mnemonic to recorder Actions. The mnemonic can then be used in RECORD statements and is used is the title of Disk, Byte and Var files. Any disk files created by a RECORD[<mnemonic>] will be on the DL Backup family and have a title of the form:

*SUPERVISOR/RECORD/<mnemonic</<dayname>

or for Byte files:

*SUPERVISOR/RECORD/<mnemonic</<dayname>.txt

Specifying PORT will pass the message to any Hotline program requesting this message type.

DISK means that messages will be written to a Jobsymbol file. The same format as RECORD[1].

DISK and HDR or HDR on its own means messages will be written to a Jobsymbol file, with each message preceded by a header line. The same format as for Record[0].

Var means that messages will be written to a variable length record data file. The same format as Record[50].

Byte means that the message will be written to an ASCII byte stream file, suitable for reading via NX/Services.

Ex. TT REC NAME + ALERTS BYTE PORT

would allow a RECORD[ALERTS] which would write to a file like *SUPERVISOR/RECORD/ALERTS/"MONDAY.TXT" and pass the message to any Hotline program which requested 'ALERTS'.

Previously RECORDER would fault when an IPADDRESS of maximum length (15 characters) was encountered.

This problem has now been corrected.

This change ensures that the Subfile Message Type mask held within RECORDER is cleared when a Subfile is first opened. This prevents unsolicited messages being sent before the initial RECORDER / HOTLINE dialogue has been established.

The previous change 450.04 to enable TCPIP connectivity introduced a change to the message formats used by RECORDER and HOTLINE by appending a CRLF (Carriage Return / Line Feed) to the end of each message. It has been reported that this change has affected Users with their own locally produced 'Hotline' programs - most of whom are still using BNA connectivity.

This change removes the additional CRLF message delimiters when BNA is used as the Transport mechanism. Message delimiters will still be used under TCPIP.

This change together with an associated change to HOTLINE version 450.03 enable these two programs to communicate using TCPIP.

BNA communication is still supported and no changes to the User environment are required if BNA connectivity is used BUT this version of RECORDER will NOT function with earlier versions of HOTLINE as the message formats used for intercommunication have been changed.

To run RECORDER / HOTLINE in a TCPIP environment the User must specify file on the System on which RECORDER will run and on the System that will run HOTLINE. The Socket number can be in the range 0 to 65535 and should be chosen to avoid conflicts with any existing numbers.

The variable RECORDER_SKTNO can be set up using META/INSTALL as follows:-

U META/INSTALL RECORDER_SKTNO=33333

which, in this example, will establish a Socket number of 33333.

Both RECORDER and HOTLINE attempt to retrieve this variable when they initialise and will, if the variable is present, attempt to communicate using TCPIP. Thus, if BNA connectivity is available and is to be used the RECORDER_SKTNO Variables should NOT be set up.

If TCPIP is to be used a TCPIP Hostname Mapping must be set up on the System that is to run the HOTLINE. This enables HOTLINE to continue to establish connections by Hostname as it has done previously in BNA environments. A TCPIP Hostname can be established as follows:-

     NW TCPIP MAP + METAHOST TO 10.17.6.22

where, in this example, METAHOST is the Hostname to be used by HOTLINE to communicate with RECORDER running on a System with an IPADDRESS of 10.17.6.22

Due to the way in which TCPIP operates the HOTLINE STATUS response will now show a Host state of 'Pending OPEN' while HOTLINE is attempting to establish communication with a TCPIP Host. This is equivalent to the 'OFFERED' state when running in a BNA environment.