
{
	Software
	Release
	Announcement}
{	}
{Intelligent Datacomm Module}
{System Software (IDMSS)
Version 5.2.0
Style ID: MXB25IDM}
{To order additional copies of this document}
{	United States customers call the Unisys Customer Support Center at 18003280440.  At the prompt, enter 2776 to reach Special Services.}
{	All other customers contact your Unisys Subsidiary Librarian}
{	Unisys personnel use the Electronic Literature Ordering (ELO) system}
{	}
{Distribution lists:
SA, SN, SU, SW, PR5}
{System:	CTOS
Release	IDMSS 5.2.0}
{Part Number:	43588862001}
{NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT.  Any product and related material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly executed Program Product License or Agreement to purchase or lease equipment.  The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such License or Agreement.  Unisys cannot accept any financial or other responsibility that may be the result of your use of the information or software material, including direct, indirect, special or consequential damages.}
{You should be careful to ensure that the use of this information andor software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used.}
{The information contained herein is subject to change without notice.  Revisions may be issued to advise of such changes andor additions.}
{The names, places, andor events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise.  Any similarity or likeness of the names, places, andor events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional.}
{Copyright  1993 Unisys Corporation
All rights reserved.}
{RESTRICTED RIGHTS LEGEND.  Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 252.2277013  and FAR 52.22714 for commercial computer software}
{TRADEMARKS:
BTOS is a trademark of Unisys Corp.
XBus, and XBus+ are trademarks of Convergent Technologies, Inc.
Convergent, Convergent Technologies, CTOS,  NGEN, and SuperGen are registered trademarks of Convergent Technologies, Inc.}
{}
{Contents
Section 1	
General Description		1
1.1	Software Components		1}
{Section 2	
New Release Functionality		3
2.1	New IDM HW Support		3
2.2	Request.sys		3
2.3	Enhanced Error Reporting		4
2.3.1	IPRB Usage		4
2.3.2	Fatal Error Handling		4
2.3.2.1	Fatal Error Reporting		5
2.3.2.2	Crash Dump File		5
2.4	Commline Support for ISDN		6
2.4.1	InitCommLine		6
2.4.2	ReceiveCommLineDMA		6
2.4.3	TransmitCommLineDMA		7
2.4.4	GetCommLineDMAStatus		7
2.4.5	ReadCommLineStatus		7
2.4.6	WriteCommLineStatus		8
2.4.7	ResetCommLine		8
2.5	New Configuration Options		8
2.5.1	Configuring IMSP		9
2.5.2	Customizing ImCTOS		10
2.5.3	Configuration Guidelines		11}
{Section 3	
Product Interdependencies		13
3.1	Software		13
3.1.1	Requirement		13
3.2	Hardware		13
3.2.1	Requirement		13}
{Section 4	
Migration Requirements		15
4.1	Nationalization		15
4.2	Request Files		15}
{Section 5	
Corrections		17
5.1	UCFs Corrected in IDMSS 5.1		17
5.2	UCFs Corrected in IDMSS 5.2.0		18}
{Section 6	
Restrictions and Known Limitations		19
6.1	Restrictions		19}
{Section 7	
Customer Product Information		21
7.1	Required Product Documentation		21
7.2	ImCTOS Programming Documentation		21
7.2.1	InitCommLine		22}
{Section 8	
Support		25
8.1	Support Category		25
8.2	Support Discontinuance		25}
{Section 9	
Ordering Procedures		27}
{Section 10	
List of Files on Product Media		29
10.1	Contents of the Distribution Diskettes		29
10.2	Contents of the System Build Utilities Diskettes		31}
{Section 11	
Installation Procedure		33
11.1	Overview		33
11.2	Types of Systems		33
11.3	Required Files		33
11.4	Installing IDMSS Software		34
11.5	Installing System Build Utilities		35}
{Section 1	
General Description	
This Software Release Announcement describes Intelligent Datacomm Module System Software (IDMSS) 5.2.0.  It provides a highlevel product description and installation instructions for IDMSS.  It also provides information on how to order the product.}
{IDMSS is a software package that makes an intelligent datacommunications  module (IDM) a functional part of the CTOS system.  IDMSS downloads software onto the IDM and provides a platform for data communications gateways, such as SNA, to run on the IDM and communicate with services on the main processor.}
{}
{}
{1.1	Software Components	
}
{IDMSS consists of two major components:  the operating system and command interpreter (executive) that run on the IDM, and the system services and utilities that run on the main processor.}
{}
{The following software executes on the IDM:}
{}
{ImCTOS is a real mode, singlepartition version of the CTOS operating system.  There are three versions of ImCTOS in this release:}
{	LAN>ImCtosSp.run    for Ethernet and Token Ring modules}
{	IDM>ImCtosSp.run    for IDS and ID2 modules}
{	ISDN>ImCtosSp.run   for ISDN modules}
{}
{The ImCtos runfiles are copied onto the [Sys]<Sys> directory by the installation procedure.  They are renamed to LAN>Sysimage.sys, IDM>Sysimage.sys, and ISDN>Sysimage.sys.}
{}
{IDM>Exec.run is the 'executive' of the IDM.
}
{IDM>Request.sys is the request file that is loaded by ImCTOS.}
{}
{The following software executes on the main CPU:}
{}
{IMSP.run is the system service that provides boot and dump capabilities for the IDM and also handles the interprocessor communications between the main processor and the IDM.}
{}
{ImRun.run is a utility that provides the capability to load run files on the IDM. }
{ImBootstrap.run is a utility that provides the capability to reboot the IDM. }
{Section 2	
New Release Functionality	
IDMSS 5.2.0 is a followon to release 5.1.  It fixes several problems which are listed in section 5 below.  IDMSS 5.1 was the successor to IDMSS 4.0.603.  In that release some of the names were changed from ImBTOS to ImCTOS.}
{
2.1	New IDM HW Support	
}
{Starting with release 5.1,  IDMSS now supports the XBUS ISDN module (B25DN2) and the SuperGen XBUS+ Ethernet cartridge (SG510C) in addition to the current IDM modules:  B25EN3 Ethernet, B25TR2 Token ring, B25IDS, and B25ID2.}
{
2.2	Request.sys	
}
{ImCTOS has been enhanced to load an 'IDM only' request file on the module.  Previously, ImBTOS loaded [Sys]<Sys>Request.Sys into local IDM memory and, therefore, all request codes used by the main CPU were also loaded into the IDM.  ImCTOS will now load its own Request file,  IDM>Request.Sys, which only contains request codes used by the IDM and thereby reducing the memory requirements of ImCTOS.  If IDM>Request.Sys does not exist in the [Sys]<Sys> directory, the default file [Sys]<Sys>Request.Sys will be loaded.}
{2.3	Enhanced Error Reporting	
}
{2.3.1	IPRB Usage	

IPRBs (Inter Processor Request Block) are used to store incoming request blocks in local memory.  During normal operation, when a request is received and there are no IPRBs available, the request is queued until an IPRB is available.  The amount of time before an IPRB is available is dependent upon the application currently executing.  If the requests are being queued frequently and for long periods of time, the user may see problems such as the system hanging, or poor performance of the application program, cluster,  or network.
}
{Starting with release 5.1, ImCTOS will log the following message to the system log file:  (viewable by using PLOG)}
{}
{     Warning  IPRB exhaustion on processor X, pending queue depth Y}
{where X is the processor number and Y is the number of messages currently in the queue waiting for an IPRB.}
{
If a processor is continuously exhausting IPRBs, then customizing ImCTOS should be considered.  A timer value can be set to limit the amount of time between system log messages.  See the IDMSS Administration Guide  for  more information.}
{
2.3.2	Fatal Error Handling	

When a fatal error occurs,  IMSP will write an error message to the system log, force a crashdump of the module, and reboot the module.  }
{2.3.2.1	Fatal Error Reporting	

The errors written to the system log have been enhanced to aid the user in diagnosing the problem.  There are two categories of fatal errors:  those errors detected and reported by IMSP, and those detected by ImCTOS.}
{The following errors are reported by IMSP:}
{Unknown crash detected by IMSP   IMSP has determined that the module has crashed.  It will log an additional message which contains some of the IDM's system registers. }
{Watchdog timer expired   IMSP periodically issues a watchdog request to ImCTOS to verify that it is still running.  If ImCTOS does not respond within the specified interval, IMSP assumes that the module has hung and reports the error.  See the IDMSS Administration Guide  for  more information.}
{CycleWaitEmpty timer expired   IMSP interrupts the module when it has a request to send to the module.  If the module does not acknowledge the interrupt within the specified period, IMSP reports this fatal error.  See the IDMSS Administration Guide  for  more information.}
{The following error is reported by ImCTOS:}
{Crash Detected by ImCTOS   ImCTOS has detected a fatal condition and has notified IMSP that it can no longer continue.  The crash error code and system error buffer will be included in the system log error message.  See the CTOS Status Codes Reference Manual for more detail.}
{}
{2.3.2.2	Crash Dump File	

A crashdump file will automatically be created by IMSP if a fatal error has been encountered and the file does not already exist.   See the IDMSS Administration Guide  for more information.}
{2.4	Commline Support for ISDN	
}
{The Commline procedures of ImCTOS have been modified to support the ISDN module.  The following sections describe the new features of CommLine.}
{}
{2.4.1	InitCommLine	
InitCommLine allocates a communications channel for the caller.  Starting with ImCTOS 5.1, InitCommLine supports ISDN channels Audio, B1, B2, and D.  The full description of the procedural interface and parameters is located in Section 7 of this document.}
{}
{2.4.2	ReceiveCommLineDMA	}
{ReceiveCommLineDMA sets up the DMA controller to transfer a specified number of bytes from the communications channel to the specified memory buffer.  In ImCTOS 5.1 support was added for the 8237 DMA controller for the ISDNB1 and ISDNB2 channels.  To avoid loosing data, special care must be taken when reprogramming a DMA channel currently in use.  To reprogram a channel, mask the channel before beginning the programming sequence and unmask it when completed.}
{The 8237 DMA controller contains 4 channels (0  3).  The receive channel assignments are:}
{}
{}
{	Channel	Transfer	Mode	Direction
}
{	0	FlyBy	Single	Z16C30 to memory, ISDN 
				B1 channel}
{}
{	2	FlyBy	Single	Z16C30 to memory, ISDN 
				B2 channel}
{}
{}
{2.4.3	TransmitCommLineDMA	}
{TransmitCommLineDMA sets up the DMA controller to transfer a specified number of bytes from the specified memory buffer to the communications channel.  Support for the 8237 DMA controller for the ISDNB1 and ISDNB2 channels has been added in this release.  }
{The 8237 DMA controller contains 4 channels (0  3), and the transmit channel assignments are:}
{}
{}
{	Channel	Transfer	Mode	Direction

	1	FlyBy	Single	Memory to Z16C30, ISDN 
				B1 	channel

	3	FlyBy	Single	Memory to Z16C30, ISDN 
				B2 	channel}
{}
{}
{2.4.4	GetCommLineDMAStatus	}
{GetCommLineDMAStatus returns the number of bytes transferred during the current CommLineDMA operations (TransmitCommLineDMA or ReceiveCommLineDMA) for both the transmit and receive DMA channels.  Support has been added for the 8237 DMA controller for the ISDNB1 and ISDNB2 channels.  The changes made to this procedure allow it to read the status register of the DMA controller and return it to the caller.}
{}
{2.4.5	ReadCommLineStatus	}
{ReadCommLineStatus allows certain external signals, whose functions are not defined in the communications controller, to be queried by the application program.  This procedure will return Erc = Not Implemented for communications channels ISDNB1, ISDNB2, ISDND and ISDNAudio .}
{}
{2.4.6	WriteCommLineStatus	}
{WriteCommLineStatus allows certain external signals, whose functions are not defined in the communications controller, to be altered by the application program.  This procedure will return Erc = Not Implemented for communications channels ISDNB1, ISDNB2, ISDND and ISDNAudio.}
{}
{2.4.7	ResetCommLine	}
{ResetCommLine makes the specified communications channel available for use again after the channel has been initialized by InitCommLine.  No further interrupts will be routed to the caller of InitCommLine.  starting with ImCTOS 5.1, ResetCommLine will reset all the new chips associated with the specified channel.  For the ISDNB1 and ISDNB2 channels the chips are the relevant 8237 DMA and Z16C30 USC channel; for the ISDND the chip is the Am79C3032 and for ISDNAudio channel only the HSW (hookswitch) interrupt will be disabled.}
{
2.5	New Configuration Options	

The user has the ability to configure resources for both ImCTOS and the IMSP service.  The configurable parameters are:}
{}
{	Number of large IPRBs			number of buffers for large incoming }
{				requests from another processor
}
{	Number of sectors in large			number of 512 byte sectors in buffers
IPRB			for large IPRBs 
}
{	Number of small IPRBs			number of buffers for small incoming }
{				requests
}
{	Size of Small IPRB			size (bytes) of buffers for small }
{				IPRBs }
{	Number of rcbs			16byte structure for outgoing requests
}
{	Watchdog interval			number of 110 second intervals between 
				watchdog requests
}
{	Number of user numbers			maximum number of user numbers 
			(refer to the IDMSS Administration 
			 Guide for more information )
}
{	Number of pblinks			6byte structure for storing pbs for }
{				outgoing requests (main processor }
{				only)}
{	}
{	IPRB queue timer			interval between message logging 
			(refer to the IDMSS Administration 
			 Guide for more information )}
{}
{}
{}
{Caution:		The configuration parameters and customization parameters 
	should only be changed on the advice of Technical support.}
{}
{}
{2.5.1	Configuring IMSP	}
{The resources for the IMSP service can be configured by installing IMSP with the Run command.  The following are the parameters and the default values for this release.  The default values are sufficient for most applications.}
{}
{	 1.  [Back off timer]	(should not be modified)
	 2.  [Number of Rcbs]	(default = 200)
	 3.  [Number of Large IPRBs ]	(default = 10)
	 4.  [Sectors of each Large IPRB]	(default = 5 )
	 5.  [Number of Small IPRBs]	(default = 20)
	 6.  [Size (bytes) of Small IPRB]	(default = 170)
	 7.  [Watchdog interval]	(default = 50:  5 seconds)
	 8.  [Number of wait cycles]	(default = 0ffffh)
	 9.  [Number of Users numbers]	(default = 20)
	10. [Number of pblinks]	(default = 6 x Number of rcbs)}
{}
{}
{See the CTOS IDMSS Administration Guide for more detail.}
{2.5.2	Customizing ImCTOS	}
{
The customizable parameters for ImCTOS are included in the prefix files.  There are three prefix files in this release:}
{	LAN>ImCtosSp.asm    for Token ring and Ethernet modules}
{	IDM>ImCtosSp.asm    for IDS modules}
{	ISDN>ImCtosSp.asm   for ISDN modules}
{}
{The parameters that can be modified are:
}
{nIPRBLarge	number of large IPRBs  (default depends upon 
	ImCTOS type)}
{nSectorIPRBLarge	number of 512 byte sectors  in large 
	IPRBs  (default = 5 sectors  + 42 bytes overhead)}
{nIPRBSmall	number of small IPRBs  (default depends upon 
	ImCTOS type)}
{sIPRBSmall	size of small IPRBs  (default = 170 + 10 bytes 
	overhead)}
{nRcb	number of outgoing requests  (default = 20)}
{nUserNumMax	number of User numbers  (default = 500)}
{IPRBQueueTimer	IPRB queue timer  (default = 10)}
{}
{}
{CAUTION:  CTOS II 3.3 or higher system is required for customization.}
{}
{To customize ImCTOS, modify the parameter in the prefix file.  }
{	Example:   SET(nIPRBSmall, 100)}
{	sets the number of small IPRBs to 100}
{}
{Assemble the prefix file:}
{	Assemble
		Source files	LAN>ImCtosSp.asm}
{}
{If there are no assembler errors,  link ImCTOS using the Link ImCTOS command:}
{}
{	Link ImCtos
		Operating System type	LAN (or IDM or ISDN)
		Version	5.1.custom  (version number)}
{}
{The Link command will produce a run file, either Lan>ImCtosSp.run, ISDN>ImCtossp.run or IDM>ImCtosSp.run, depending upon the prefix file used.  This is ImCTOS image that must be copied to [Sys]<Sys>moduletype>SysImage.Sys  where moduletype is the module prefix.}
{See the CTOS IDMSS Administration Guide for more detailed information.}
{}
{2.5.3	Configuration Guidelines	}
{The default parameters for ImCTOS and IMSP have been set to optimal values for the specific modules.  In most cases, the parameters will not have to be modified.  However, their use is application dependent, and a particular application andor configuration may require the parameters to  be modified.  Consult the documentation of the data communications service.}
{The nSectorIPRBLarge and sIPRBSmall have been set to optimum values for IDM applications and should not be altered.  nIPRBLarge and nIPRBSmall are application dependent and can be modified to optimize memory utilization.}
{nUserNumMax on the main processor has been set high to resolve the  occurrence of error 31756.  However, if the user encounters this error code,  nUserNumMax should be increased.}
{nRcb should be set to the value of the sum of the small and large IPRBs on the  receiving processor.  For example, if the total number of small and large IPRBs in IMSP is 30 (on the main processor), then nRcb in ImCTOS (on the IDM) should be greater than or equal to 30.   This is also true of the IDM:  if the total number of small and large IPRBs in ImCTOS is 200, then nRcbs in IMSP should be greater than or equal to 200..}
{Section 3	
Product Interdependencies	
3.1	Software	
3.1.1	Requirement	}
{}
{IDMSS 5.2.0 requires the following levels of BTOSCTOS:}
{	  CTOS I version 3.3 or higher}
{	  CTOSVM version 2.4 or higher}
{	  CTOS II version 3.3 or higher}
{	  CTOS III version 1.0 or higher}
{	  BTOS II version 3.0.1 or higher}
{}
{NOTE:  The ISDN module (B25DN2) and the SuperGen Ethernet cartridge (SG510C)  are only supported on CTOS II version 3.3 or higher and CTOS III version 1.0 or higher.}
{}
{}
{3.2	Hardware	
3.2.1	Requirement	}
{}
{IDMSS 5.2.0 executes on XBUS and XBUS+ based workstations: B26, B28, B38, B39 and SuperGen Series 5000.}
{Section 4	
Migration Requirements	
4.1	Nationalization	
}
{To nationalize this product, the IDMSS Nationalization Build and Package Kit (LB25IDM)  is required.}
{
4.2	Request Files	
}
{The file Request.IDMSS.txt contains the request codes needed by ImCTOS and IMSP.  Request.IDMSS.txt must be merged with the current request file(s) for both the main processor and the IDM.   If the user is using the  Idm>Request.Sys file feature (see section 2.2), then Request.IDMSS.txt  must be merged into both  Request.Sys and IDM>Request.Sys.  Otherwise, Request.IDMSS.txt must be merged with Request.Sys only.  For more information on request files see the IDMSS Administration Guide and the CTOS Operating System Concepts Manual.}
{}
{Section 5	
Corrections	
This section contains a description of corrections to certain restrictions, limitations, or conditions found in preceding releases.}
{}
{5.1	UCFs Corrected in IDMSS 5.1	
UCF Number
14814787	Remote node access fails for some applications {master} 
14833641	Filename missing in nationalization guide 
14833668	Nonrequired request merged  
14833676	Token Ring LAN may fail to boot IDMSS  
14833684	GetLanAddr returns erc 31709 for TR Lan  
14833692	SNA GW fails on IDS with Erc 31751  
14833706	OS data space (ImBTOS) may be overwritten by application 
14902562	Erc 12 from LAN after configuring OS 
14941428	IMRUN fails with 31751 when loading from  sysinit.jcl 
14941541	IDS crashes when more than 20 LULU sessions are activated  
15104694	BTOS Network Controller reported erc 80 
15106093	TR2 needs more time for booting with ImBoot 
15141671	Erc 31756
15247550	APPC does not install on IDS 
15247738	Installation screens do not fit on screen 
15267747	Erc 31755: request too large for IPRBs 
15247754	Erc 22  bus timeout
15270080	Erc 31702 needs to be documented 
15270101	Erc 35 attempting to invoke IDS application from exec 
15313137	IMSP does not run on VSeries 
16863246	Two responses received for one request 
16894753	Erc 22 on B39 with IDS  
26254647	IDS crashes: MGS and 2 BMultis }
{}
{5.2	UCFs Corrected in IDMSS 5.2.0	
IMSP was unable to open a crashdump file if the system volume was protected.}
{IMSP will now accept a DWORD parameter for CycleWaitEmpty which is parameter 8.}
{Request codes 0D05C and 0D05D were omitted in Request.IDMSS.txt in the 5.1 release.  They have now been restored.}
{System registers (CS, IP, SS, SP, Flags, DS) are now logged when the WatchDog or CycleWaitEmpty timers expire.}
{An IMSP memory allocation problem which would only occur when running on CTOS III has been fixed.}
{Crashdumping on the SG5000 would always log error 31633 even though the crashdump was successful.  This has been fixed.}
{UCF 17144405  This was a bug in the ImCTOS timer code which could cause an IO to a nonexistant port.  This was fixed and should also result in a slight performance gain.}
{For SG5000 only  A request block with a response pbcb, issued from the main processor to the EN4 cartridge, with a 0 cb could result in the SG5000 crashing.  Crashes with erc 91, erc 22, erc 80, and GP faults have been observed.  This problem has been fixed and should also result in a slight performance improvement.}
{Section 6	
Restrictions and Known Limitations	
6.1	Restrictions	
}
{The Ethernet SG510 cartridge on a SG5000 will not be reset properly with versions of Boostrap.run prior to 12.1.4.  }
{}
{The IDMSS Package cannot be installed from server on systems running 12.0 Standard Software.}
{}
{ImCTOS can be customized only on systems with CTOS II 3.3 or higher and CTOS III 1.0 or higher.}
{}
{}
{Section 7	
Customer Product Information	
7.1	Required Product Documentation	
}
{Part Number	Manual Name}
{4358 72600000	CTOS Intelligent Datacomm Module System Software Administration Guide}
{This guide provides procedures for configuring and administering Intelligent Datacomm Module System Software (IDMSS) in a CTOS based cluster.}
{}
{}
{7.2	ImCTOS Programming Documentation	
}
{The following procedural interface represents modifications since the previous version of ImCtos.}
{}
{7.2.1	InitCommLine	
}
{InitCommLine allocates a communications channel for the caller. }
{}
{Procedural Interface:}
{InitCommLine (pbSpec, cbSpec, pbClcb, cbClcb, pbRet, cbRet): ercType}
{}
{where}
{pbSpec	describes the device specification string  ( see below).
cbSpec	is the size in bytes.}
{pbClcb	describes the CLCB  ( see below).
cbClcb	is the size in bytes.}
{pbRet	is the memory address of an area into which the 
	return values are written.
cbRet	is the size in bytes of the  area returned  ( see below).}
{}
{}
{pbSpeccbSpec:}
{In addition to the currently supported device specifications,  ImCTOS  5.1 will support the following:}
{}
{	Device Spec	cbSpec	Description
			}
{	A or 0A	1 or 2	ISDN Audio control channel}
{	B1	   2	ISDN B1 channel}
{	B2	   2	ISDN B2 channel
	D or 0D	1 or 2	ISDN D channel}
{}
{For a complete description of the pbSpeccbSpec, see the CTOS Procedural Interface Reference Manual.}
{For Device Spec ISDNAudio a check will be made to make sure that the module is equipped with the Am79C30A chip (voicedata capability).}
{}
{pbClcbcbClcb:}
{The following field has been added to the  Communications Line Configuration Block (CLCB):}
{}
{	Offset	Field	Size	Description}
{			(bytes)}
{	  ...}
{	  37	bISDN	  1	0: No ISDN capabilities}
{				1: D channel capability}
{				2: B channel Audio capability}
{				3: B channel Data capability}
{}
{The addresses of the ISR's will be set up by the caller, and they will have the following meaning depending on the bISDN field:}
{}
{	Offset	Field	Size	Description}
{			(bytes)}
{	  ...}
{	   4	pTxIsr	   4	bISDN = 0:	Same as 4.0  ImBTOS}
{			bISDN = 1:	D channel  interrupts (all)}
{				bISDN = 2:	NULL}
{				bISDN = 3:	B channel Transmit Data 
				  interrupt				(bit 2 in the DCCR 
				  register of 	 the Z16C30)}
{}
{	   8	pExtIsr	   4	bISDN = 0:	Same as 4.0  ImBTOS
				bISDN = 1:	NULL}
{				bISDN = 2:	NULL}
{				bISDN = 3:	B channel Transmit status 
				and device status interrupts			(bit 0 and 
				3 in the DCCR register of the Z16C30)}
{}
{	  12	pRxIsr	   4	bISDN = 0:	Same as 4.0 ImBTOS
				bISDN = 1:	NULL}
{				bISDN = 2:	NULL}
{				bISDN = 3:	B channel Receive Data 
				  interrupt 	(bit 4 in the DCCR register 
				  of the Z16C30)}
{}
{	  16	pSpRxIsr	   4	bISDN = 0:	Same as 4.0 ImBTOS
				bISDN = 1:	NULL}
{				bISDN = 2:	NULL}
{				bISDN = 3:	B channel Receive status 
				  and IO status interrupts			(bit 1 and 5 
				  in the DCCR register of the Z16C30)}
{  ...
	  24	baudXmit	  2	bISDN = 0:	Same as 4.0 ImBTOS}
{}
{	  26	baudRcv	  2	bISDN = 0:	Same as 4.0 ImBTOS
  ...
	  33	fDMA	  1	bISDN = 0:	Same as 4.0 ImBTOS}
{				bISDN = 1:	FALSE}
{				bISDN = 2:	FALSE}
{				bISDN = 3:	TRUE}
{}
{NOTE:  If fDMA = FALSE, the DMA will not be used and it will be the callers responsibility to writeread the data directly to the chip.}
{}
{}
{pbRetcbRet:}
{In addition to the return block  values supported in ImBTOS 4.0,  the following are supported in ImCTOS 5.1 :}
{For the ISDNB1, ISDNB2, ISDND and ISDNAudio channels:}
{}
{     Offset		Field	Size	Description}
{			(bytes)}
{	  ...}
{	   2	ioCommCtl	  2	If bISDN = 1 or 2, then base port 
				address to the Am79C3032 chip.}
{				If bISDN = 3, then base port address 
				of specified channel of Z16C30.}
{	   4	ioCommData	  2	Not used. Always set to 0.}
{	   6	chipType	  2	= 10h for Z16C30 chip.}
{				= 11h for Am79C30 chip.}
{				= 12h for Am79C32 chip.}
{	...10	fDMA	  2	= TRUE for ISDNB1 and ISDNB2, }
{				  otherwise  FALSE.}
{Note: It is the caller's responsibility to calculate the port address of a specific register inside a chip based on the returned base port address given in the field ioCommCtl.  The caller also has to ensure that the interrupt is disabled during access to a register which requires multiple accesses.}
{}
{Section 8	
Support	
IDMSS 5.2.0 is a warranted Unisys software product. }
{Unisys warrants that IDMSS 5.2.0, in its unaltered form, will substantially conform to Unisys current published functional specifications when used in Unisys supported configurations.  The customer is responsible for reporting suspected deviations using the User Communication Form (UCF) process within ninety (90) days following delivery.  The product is neither field repairable nor field modifiable.  Corrections to reported deviations are provided to the user via updated code files.}
{This standard warranty is not a substitute for Unisys Service Agreement offerings.}
{8.1	Support Category	
IDMSS 5.2.0 is fully supported by Unisys.}
{Support services for IDMSS 5.2.0 are offered under the SURETY (United States) or A la Carte (International) support programs and are consistent with the support services offered for the entire CTOS Hardware and Software family of products.}
{Unisys SureNet is an electronic bulletin board service, providing customers in the United States access to technical information seven days a week, 24 hours a day.  SureNet Technical Information Services are available at no additional cost to customers with a current Unisys service agreement or software license and include access to system alerts, customer technical bulletins and online UCF entry.  Registration is required.  SureNet Support Services are available on an annual subscription basis.  For more information, contact Unisys Direct at 18004481424, prompt 5.  You may register for Technical Information Services andor Support Services either online (by dialing 18008288796 (8 data bits, 1 stop bit, no parity, asynchronous, VT100 emulation) or by calling Unisys Direct.}
{If you need further assistance or information regarding support services, please contact your Unisys representative or your local Unisys office.}
{8.2	Support Discontinuance	
UNISYS supports the current release level and one level back.  Prior levels are not supported.}
{Section 9	
Ordering Procedures	
Please complete and return the attached Update Service Request form to order this product.  Media provided by Unisys Corporation may not be returned for credit.}
{To order manuals, contact your sales representative.  You can also order manuals from the following address:}
{Unisys Corporation
Publications Distribution Center
13250 Haggerty Road North
Plymouth, Michigan 48170}
{Section 10	
List of Files on Product Media	
10.1	Contents of the Distribution Diskettes	
The IDMSS distribution diskettes are your master copy and have been writeprotected.  The contents of the diskettes cannot be overwritten unless the writeprotect tabs are removed.  Do not remove the writeprotect tabs and do not use these diskettes as your working copy.}
{}
{5 inch media}
{Distribution Diskette 1 contains:}
{[B25IDM12]<Sys>IDMSS Software Diskette 1
[B25IDM12]<Sys>fdSys.version
[B25IDM12]<Sys>Install.cmds
[B25IDM12]<Sys>Install.ctrl
[B25IDM12]<Sys>Install.jcl
[B25IDM12]<Sys>Install.sub
[B25IDM12]<Sys>InstallMsg.Bin
[B25IDM12]<Sys>Request.IDMSS.txt
[B25IDM12]<Sys>XeInstall.sub
[B25IDM12]<Unisys>IDM>Exec.Run
[B25IDM12]<Unisys>IDMSS>SRA.Doc
[B25IDM12]<Unisys>IDMSS>SRA.Def
[B25IDM12]<Unisys>ImBootStrap.run
[B25IDM12]<Unisys>ImRun.run
[B25IDM12]<Unisys>IMSP.run}
{Distribution Diskette 2 contains:}
{[B25IDM22]<Sys>IDMSS Software Diskette 2
[B25IDM22]<Unisys>IDM>SysImage.Sys
[B25IDM22]<Unisys>ISDN>SysImage.Sys
[B25IDM22]<Unisys>LAN>SysImage.Sys}
{}
{3 inch media
Distribution Diskette contains:
[B25IDM11]<Sys>IDMSS Software Diskette 1
[B25IDM11]<Sys>fdSys.version
[B25IDM11]<Sys>Install.cmds
[B25IDM11]<Sys>Install.ctrl
[B25IDM11]<Sys>Install.jcl
[B25IDM11]<Sys>InstallMsg.Bin
[B25IDM11]<Sys>Request.IDMSS.txt
[B25IDM11]<Unisys>IDM>Exec.Run
[B25IDM11]<Unisys>IDMSS>SRA.Doc
[B25IDM11]<Unisys>IDMSS>SRA.Def
[B25IDM11]<Unisys>ImBootStrap.run
[B25IDM11]<Unisys>ImRun.run
[B25IDM11]<Unisys>IMSP.run
[B25IDM11]<Unisys>IDM>SysImage.Sys
[B25IDM11]<Unisys>ISDN>SysImage.Sys
[B25IDM11]<Unisys>LAN>SysImage.Sys}
{10.2	Contents of the System Build Utilities Diskettes	
The System Build Utilities diskettes are your master copy and have been writeprotected.  The contents of the diskettes cannot be overwritten unless the writeprotect tabs are removed.  Do not remove the writeprotect tabs and do not use these diskettes as your working copy.}
{}
{Distribution Diskette 1 contains:}
{[ImCTOS13]<Sys>IDMSS_BuildUtilities Software Diskette 1
[ImCTOS13]<Sys>Install.Cmds
[ImCTOS13]<Sys>Install.ctrl
[ImCTOS13]<Sys>Install.jcl
[ImCTOS13]<Sys>InstallMsg.Bin
[ImCTOS13]<Unisys>LinkImCtos.Sub
[ImCTOS13]<Unisys>IDMSS_Archive.01}
{Distribution Diskette 2 contains:}
{[ImCTOS23]<Unisys>IDMSS_Archive.02}
{Distribution Diskette 3 contains:}
{[ImCTOS33]<Unisys>IDMSS_Archive.03}
{}
{NOTE:  There is no diskette 3 for the 3 inch media.}
{Section 11	
Installation Procedure	
11.1	Overview	
The following installation procedures will install IDMSS Software on your workstation.   For details on using the Executive and its commands, see the CTOS Executive User's Guide and the CTOS Executive Reference Manual.}
{}
{11.2	Types of Systems	
The following information explains how to install IDMSS Software on the following systems:
	Standalone and cluster workstations with hard disks
	Server hard disk systems
}
{11.3	Required Files	
The files required to run IDMSS Software must reside in the [Sys]<Sys> directory.}
{   IDM>SysImage.Sys : is the ImCTOS image for IDS modules.}
{   LAN>SysImage.Sys : is the ImCTOS image for the LAN modules.}
{   ISDN>SysImage.Sys : is the ImCTOS image for the ISDN module.}
{   ImRun.Run : is a program used to install services on intelligent modules.}
{   ImBootStrap.Run : is a program to bootstrap intelligent modules.}
{   IMSP.Run : is the Intelligent Module Support Program.}
{   IDM>Exec.Run : is the executive that runs on intelligent modules.}
{11.4	Installing IDMSS Software	
}
{Use the following procedure to install IDMSS Software on standalone and cluster workstations that contain hard disks.}
{
1.	Sign on to the workstation.  Make sure the Context Manager is deinstalled.
2.	Insert the Distribution Diskette into the floppy drive.
3.	If your system has  Standard Software 12.0 (or greater) installed, use the following command to initiate the installation procedure:

   Floppy Install  <GO> 

This command will read the installation diskette, create the appropriate environment and chain on to Batch, which proceeds to do the installation.

If your system is a BTOS II 3.0 system,  from the Executive use the following command to initiate the installation procedure

   Software Install <GO>

This command will execute a chain of commands to carry out the installation.

The files are copied into the [Sys]<Sys> directory and the IDMSS requests are merged with [Sys]<Sys>Request.Sys. 
4.	During installation you will be asked if you wish to support IDS, LAN, andor ISDN modules;  depending on the response the appropriate intelligent module system image files will be copied onto the [Sys]<Sys> directory.}
{}
{}
{11.5	Installing System Build Utilities	
}
{If your application requires that ImCTOS be customized, then you will also need to install the System Build Utilities.  The same procedure described above can be used to install the System Build Utilities software on the disk.}
{CAUTION:  CTOS II 3.3 or higher or CTOS III 1.0 or higher is required for the System Build Utilities.}