Random HIS Tips from Steve Smaller (HIS PM) and Andrew McLaren (MSFT AU HIS PSS)

Last week I did 2 days of training in Sydney with Steve Smaller (a HIS TI PM) and Andrew McLaren (a HIS specialist from PSS) on HIS2004. The course was interesting for reasons not directly related to the course material - many of the attendees were “old hands” from mainframe days and there were a great deal of interesting “war stories”. Here are a couple of random tips from the course. 

<?xml:namespace prefix = o ns = “urn:schemas-microsoft-com:office:office” /> /o:p

<?xml:namespace prefix = st1 ns = “urn:schemas-microsoft-com:office:smarttags” />Enterprise/st1:place/st1:City SSO/o:p

If you are installing your first HIS machine and want ESSO – go ahead and do it

If you are installing another HIS machine you want to JOIN an existing ESSO db

If you are installing an HIS machine and you have ESSO already installed from Biztalk then UPGRADE

If you are installing an HIS machine and you have ESSO already installed from Biztalk and you don’t want to use ESSO then UPGRADE ANYWAY or else your ESSO install is toast.


HIS Printing Stuff/o:p

HIS printing can either use GDI (which is necessary for rich documents with lots of formatting, but slow) or a PDT file (which is better for bulk-printing “plain text” files). To create a PDT file for a specific printer (if you have to do it) you create a plain text file called a .pdf (there is a demo one in the HIS directory). You may need to put printer-specific parameters (read from your printer manual) in the pdf file. Then you use a utility called pdfcomp to “compile” the pdf file to a pdt file, which you can then use when defining a 3270 or APPC print session in HIS SNA manager.

TI Tips
For TI Perf use COM on the client over IPDLC (‘cause it’s fast) and you can also do 2PC with it.

If you turn off anon access in IIS (when you host a TI component in IIS - the default) you need to make sure the user who makes the call to the component has the required rights to access the HIS TI runtime. Signs that this problem is occurring is that you get an amorphous HTTP 50x error, and you don’t get any information in a trace. To get around this you either need to grant the appropriate rights to ALL the users who might need to use your application OR turn off impersonation in IIS.