1. ****************************************************************************
* IBM eNetwork Personal Communications V4.30
*
* for Windows 95, Windows 98, and Windows NT
*
*
*
* Read Me - Please !
*
* (README.TXT)
*
****************************************************************************
First Edition
-------------
This document contains information supplementary to the online Help and the
Publications; it includes such things as newly-added function, hints, tips,
restrictions and corrections.
For information on installing Personal Communications, please refer to
the online Help for the INSTALL program.
Thank you for choosing Personal Communications V4.3!
============
* Contents
============
* IBM 3270 and 5250 Credit Card Adapters on PC with TI PCI-1130 in Windows 98
* IBM Personal Communications Internet Home Page
* Installation problems with MS NT V4.0
* Telnet 5250 Session Hang when Using IPX/SPX Sockets
* Installation problems on machines with IBM AntiVirus Program
* DBCS IME auto-start hidden switch (DBCS only)
* Migrated PCOMM Windows 16 twinaxial configurations don't always work
* SNA Node Verification Utility caution
* Client install considerations for AS/400 Network Drives
* Performance considerations for AS/400 Network Drives
* How to keep AS/400 Network Drives (Shared Folders) from starting
* Removing the IBM LLC2 Protocol Interface
* Configuration considerations for IBM Wide Area PCI Adapters
* IBM Communications Manager/2 configuration migration
* ISDN PPP limitation
* Starting PCOMM sessions while running Visual Basic Script loops
* NOTES.RIP files
* Requirement for .WS file when using embedded COAX sessions
* Icon problems when using Excel 7.0 and PCOMM as an out-of-place object
* COM Port/X.25 COM Port considerations
* IBM selected PC code point support in Japanese 943 PC code page.(Japan
only)
* Japan Postal bar code support. (Japan only)
* Old JIS sequence printer support (Japan only)
* NT V4.0 limitation for Old JIS sequence printer (Japan only)
* Limitations of PCOMM Macro to VBScript macro conversion
* Tivoli Plus Module Limitation
* Maximum Macro File Size
* Sort limitation in Log Viewer
* LLC2 install and uninstall
* Drawing errors within the Terminal Bean's PS running in IE4
* Recovery from Secure Sockets Layer (SSL) Installation Failure
* Sockets over SNA support only available via custom install
* New default code page
* DB2 Connect for Personal Communications

2. * Epson printer raster fonts with Windows 95 and Windows 98 (Taiwan Only)
* Split DBCS characters do not print correctly (3270 DBCS Only)
* Chinese Star support on Windows 95 OSR2 (PRC Only)
* GDI mode host print using SCS TRN/ATRN control codes
* SCS Control Code default in 5250 Print Session
* PCSMincho and PCSGothic not selectable for display on Windows NT (Japan
Only)
* Support for Win2000 Professional Beta 3 (CSD1)
* Support for Windows Terminal Server (CSD1)
* Network Drives over IP (CSD1)
* Virtual Terminal History Window (CSD1)
* Virtual Terminal Screen Size of Greater than 24 lines (CSD1)
* Open Host Interface Objects (OHIO) API (CSD1)
* Support for entering lower case letters in CAPS LOCK state (CSD1)
* Support for specifying multiple PCSPD.DAT files (CSD1)
* Network Drives Configuration (CSD1)
* Launch Application from VBScript (CSD1)
==============================================================================
* IBM 3270 and 5250 Credit Card Adapters on PC with TI PCI-1130 in Windows 98
==============================================================================
The Texas Instruments PCI-1130 CardBus controller has a restriction that it
can only map all memory windows for TI PCI-1130 and PC cards into a single
16MB frame. In Windows 98, PC cards listed below are affected by this
restriction:
- IBM 3270 Emulation Credit Card Adapter ID#0933390
- IBM 5250 Emulation Credit Card Adapter (Asia-Pacific) ID#35G3850
In Windows 98, TI PCI-1130's memory windows are mapped into the top of 16MB
frame of system RAM although the above PC card's memory window is mapped into
the first 16MB of system RAM. As a result, this PC card cannot be configured
correctly.
If you use this PC card on the PC with TI PCI-1130 CardBus controller in
Windows 98, please apply the following work around:
Add the following registry DWORD value
"IBMForceLow" = 2
to the registry subkey
[HKEY_LOCAL_MACHINESystemCurrentControlSetServicesVxDCBSSHacks]
This registry subkey may not exist and therefore needs to be created.
Then re-boot the system.
This special registry flag forces the CardBus support driver of Windows 98
to always map all memory windows into the first 16MB of system RAM.
You can determine which CardBus controller is installed on your PC in the
following way:
1. Open the Device Manager Panel. (Select My Computer Icon, Control Panel
Icon, System Icon, and Device Manager Tab)
2. Select PCMCIA Socket.
You will find PCMCIA controller's name here.
CAUTION:
You should not apply this work around:
- In Windows 95 environment.
- To the PC with any CardBus controller other than TI PC-1130.
- If you do not use PC card listed above.
For additional assistance with this, visit the PCOMM Support Web Page
(http://www.software.ibm.com/eNetwork/pcomm/support) or contact IBM Support.

3. ==================================================
* IBM Personal Communications Internet Home Page
==================================================
Find out the latest information regarding the IBM Personal Communications
family of products by visiting the Personal Communications home page on
the internet:
http://www.raleigh.ibm.com/pcf/pcfprod.html
This home page provides information or links to headline information,
specification sheets, commonly asked questions and answers, maintenance
information and much more!
=========================================
* Installation problems with MS NT V4.0
=========================================
If you are installing to a machine which has Microsoft Windows NT Version
4.0 without any Service Packs, you should apply a later Service Pack
available from Microsoft BEFORE you install PCOMM. For more information on
obtaining the latest service pack, query on SERVPACK in the Microsoft
Knowledge Base or contact Microsoft directly.
Without applying the latest Service Pack, Microsoft maintains that under
certain circumstances installing third party applications can lead to
problems which will not allow your computer to reboot after installation.
Further information can be obtained by referencing Microsoft Knowledge Base
articles Q148485, Q160658 and Q149857.
=======================================================
* Telnet 5250 Session Hang when Using IPX/SPX Sockets
=======================================================
While running a telnet 5250 session over IPX/SPX sockets, if someone pulls
the network interface cable (token-ring, ethernet, etc...), from the back
of the machine, the session will hang and the process for that session
will not get properly cleaned up. The rest of the system processes should
not be affected by this at all. At the time of release, the problem seemed
to be related to the tcp/ip stack underneath PCOMM. Future fixes to the
underlying stack may resolve this problem.
================================================================
* Installation problems on machines with IBM AntiVirus Program
================================================================
It has been noted that PCOMM fails to create all icons on Windows 95
and Windows NT computers if certain levels of the IBM AntiVirus program
are installed. If you see this problem, then you should uninstall the
IBM AntiVirus program, reinstall PCOMM and then reinstall the IBM AntiVirus
program.
=================================================
* DBCS IME auto-start hidden switch (DBCS only)
=================================================
For DBCS sessions, by default, IME will be invoked
automatically when the cursor moves into a DBCS field.
To disable the function you may add the following lines
to your PCSWIN.INI file:
[DBCS]
IME_AUTO_START=N
When N is selected (as shown above) the user will have
to manually invoke the IME editor using the defined
sequence of keystrokes.
========================================================================

4. * Migrated PCOMM Windows 16 twinaxial configurations don't always work
========================================================================
PCOMM is unable to always successfully migrate 5250 twinaxial configurations
which were originally created using PCOMM for Windows 16. Because of this
you may find that the configurations fail to connect after migration to
PCOMM V4.3 for Windows 95, Windows 98 and Windows NT. Most of the time,
restoring these configurations is a simple matter of invoking the
configuration utility and selecting the correct adapter.
=========================================
* SNA Node Verification Utility caution
=========================================
Personal Communications now stores its SNA Node configuration in text files
(*.ACG) which can be viewed or edited with an ASCII text editor. This
allows system administrators to perform minor modifications or
customizations to end user configurations without requiring the system
administrator to use the SNA Node Configuration or the SNA Node
Configuration Wizard utilities. While the SNA Node Verification utility
has been provided to assist the system administrator, it should be noted
that the SNA Node Verification utility is only intended to provide a quick
check of the resulting changes. It is not intended to provide the same
level of verification that is provided by the SNA Node Configuration
utility or the SNA Node Configuration Wizard.
===========================================================
* Client install considerations for AS/400 Network Drives
===========================================================
If you choose to run PCOMM from a server, as a client, and you want to
reconnect at logon to AS/400 Network Drives, then you must map the PCOMM
server drive with a letter earlier in the alphabet than the AS/400 drive.
When the computer reboots drives are reconnected in alphabetic order. The
client must reattach the PCOMM server drive in order to access files needed
to reattach the user's AS/400 Network Drives.
This consideration should be taken into account prior to installing PCOMM.
========================================================
* Performance considerations for AS/400 Network Drives
========================================================
If you are experiencing performance problems while using AS/400 Network
Drives, you should change the Receive Window count value to match the
window size on the AS/400 (typically 2). This value is set with SNA Node
Configuration on the Performance page for LAN Devices.
====================================================================
* How to keep AS/400 Network Drives (Shared Folders) from starting
====================================================================
If you would like to manually disable the AS/400 Network Drives (Shared
Folders) function, you may do so by performing the following actions
(depending upon the operating system). Always save your registry prior to
making any changes. Please read the complete set of steps before you start
this process. If you are unsure about anything related to these steps you
should not attempt the process.
* If you are using Windows NT 4.0:
Use REGEDIT or REGEDT32 to:
---------------------------
- Remove the following key from the registry
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicespcssfnpn
- Remove the string 'pcssfnpn' from value name 'ProviderOrder' in
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlNetworkProviderOrder

5. - Remove the string 'pcssfrrx' from the value name 'Userinit' in
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon
Use the Control Panel -> Devices application
--------------------------------------------
- Select 'Network Drives' then press the 'Startup' button, select the
'Disabled' radio button and finally the 'OK' button.
* If you are using Windows 95 and Windows 98:
Use REGEDIT to:
---------------
- Remove the following key from the registry
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicespcssfnp9
- Remove the string 'pcssfnp9' from the value name 'ProviderOrder' in
HKEY_LOCAL_MACHINESystemCurrentControlSetControlNetworkProviderOrder
- Remove the string 'pcssfrrx' from any value names in
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRunServices
============================================
* Removing the IBM LLC2 Protocol Interface
============================================
Removing the IBM LLC2 Protocol Interface currently cannot be automatically
performed. This section describes how to manually remove the IBM LLC2
Protocol Interface.
Windows 95 and Windows 98 Instructions
1.Open the "Network" application which resides in the "Control Panel" folder.
2.Select the "Protocols" tab in the "Network" notebook.
3.Select the entry "IBM Personal Communications LLC2 Driver" in the "The
following network protocols are installed" window and click on the
"Remove" button.
4.Click on the "OK" button on the "Network" dialog.
5.Click on the "Yes" button on the "System Settings Change" dialog to
restart the computer.
Windows NT 4.0 Instructions
1.Open the "Network" application which resides in the "Control Panel" folder.
2.Select the "Protocols" tab in the "Network" notebook.
3.Select the entry "IBM LLC2 Protocol" in the "Network Protocols" window and
click on the "Remove" button.
4.Click on the "Yes" button on the pop-up "Warning" dialog asking you if you
wish to continue removing the component from the system.
5.Click on the "Close" button on the "Network" notebook.
6.Click on the "Yes" button on the "Network Settings Change" dialog to
restart the computer.
===============================================================
* Configuration considerations for IBM Wide Area PCI Adapters
===============================================================
If you are using an IBM Wide Area Connector PCI Adapter, you need to select
"OEM" as an Interface when configuring an emulator session or "OEM-SYNgate"
as a DLC when configuring a Device or Connection in SNA Node Configuration.
========================================================
* IBM Communications Manager/2 configuration migration
========================================================

6. If you are trying to migrate existing CM/2 V1.11 SNA node configurations to
PCOMM V4.3 for Windows 95, Windows 98 and Windows NT, it is recommended
that you consult the PCOMM internet home page referenced above in this
readme file. At the time of this release, a utility was being developed
to assist in this migration process. It is anticipated that a US English
version of this utility will be made available as a link from the PCOMM
family internet web page.
=======================
* ISDN PPP limitation
=======================
Personal Communications V4.3 does not support PPP between the DTE (PC) and
the DCE (modem). If your modem provides the Link Control Protocol (LCP)
independently of the application support, then PCOMM should work. PCOMM as
an application does not provide the LCP required to support a PPP
connection over ISDN.
===================================================================
* Starting PCOMM sessions while running Visual Basic Script loops
===================================================================
If you have a PCOMM Visual Basic Script which runs in a tight loop (for
instance, waiting for a certain change on the screen), you may not be able
start other PCOMM sessions. The work-around is to have your VB Script
update the WindowTitle, for example:
WinTtl = autECLSession.autECLWinMetrics.WindowTitle
do
autECLSession.autECLPS.Wait(1000)
autECLSession.autECLWinMetrics.WindowTitle = WinTtl
...<code that checks for specific screen>...
loop until ...<event you were looking for>...
===================
* NOTES.RIP files
===================
After installation of Lotus Notes 4.0 or later you may notice "NOTES.RIP"
files being generated. This can happen with or without Notes running and
can also happen on other versions of Notes. These files are generated by
Quincy, a just-in-time debugger. Quincy will generate these files when it
believes it has detected an application failure. Unfortunately it can be
triggered falsely by an application such as PCOMM when certain conditions
occur.
You can turn off Quincy by renaming it or by typing "qnc -u". To restore
Quincy, simply rename the file back to QNC.EXE or type "qnc -i".
=============================================================
* Requirement for .WS file when using embedded COAX sessions
=============================================================
You must always use a workstation profile (.WS) file when embedding a
Personal Communication session in a compound (OLE) document, even when
using a Coax attachment that does not otherwise need a profile.
==========================================================================
* Icon problems when using Excel 7.0 and PCOMM as an out-of-place object
==========================================================================
This readme item applies to customers who answer YES to all of the
following questions:
- Are you using Excel 7.0 (version included in Office 95)?
- Was PCOMM installed a path which contains spaces in one or more of the
directory names?
- Are you trying to imbed a PCOMM session into an Excel spreadsheet and
display it as an ICON? (i.e. Did you select the "Display as Icon"

7. option on the "Insert Object" dialog?)
If you answered YES to all three of the above questions, you may have
noticed one of the following conditions:
- No icon display on "Insert Object" dialog (and therefore you cannot
change it at this time, but can change the icon later using normal PCOMM
methods).
- If you exit PCOMM before you save the Excel document, you do not
see the PCOMM icon.
You can prevent these problems by performing one of the following actions:
- Always save the Excel document before exiting a newly created,
out-of-place PCOMM session.
- Edit the registry entry documented below to use the short file name
variation of the path.
HKEY_CLASSES_ROOT/CLSID/{F9EEDE0-1B9D-11D0-C1B-0004AC35D17B}/DefaultIcon
EXAMPLE:
Change the value of the DefaultIcon key documented above from
C:Program FilesPersonal Communicationspcsws.exe,1
to
C:Progra~1Person~1pcsws.exe,1
Please note that these problems are not found when using Excel 8.0 (version
included in Office 97).
=========================================
* COM Port/X.25 COM Port considerations
=========================================
If you are going to be using both COM Port and X.25 COM Port on the same
machine please be aware of the following two restrictions.
1) You cannot define a COM Port connection and an X.25 COM Port
using the same port name (i.e. COM1) in the same *.ACG file.
Attempting to do so, may leave the configuration file in an
undefined state.
2) If you have a either a COM Port or an X.25 COM Port defined
in the active *.ACG file, you must stop the node prior to
attempting to start an *.ACG file with the other type of
connection. You can stop the node using CSSTOP command from
the DOS command prompt or by using the SNA Node Operations
utility.
================================================================================
* IBM selected PC code point support in Japanese 943 PC code page (Japan
only)
================================================================================
In Windows, there are several duplicate DBCS-PC code points mapping to the
same DBCS-Host code. Duplicate PC-code points are supported both IBM-select
and NEC-select in uploading. However, while downloading, the default DBCS-Host
is mapped to NEC-select; If you would like to map to IBM-select, please create
the [DBCS] stanza in PCSWIN.INI and add the line, "CP943_IBM=Y" to it.
Following is a list of code mapping relationship in hexadecimal and
example of PCSWIN.INI.
DBCS-Host NEC-select IBM-select
========= ========== ==========
41F1 8754 FA4A

8. 41F2 8755 FA4B
41F3 8756 FA4C
41F4 8757 FA4D
41F5 8758 FA4E
41F6 8759 FA4F
41F7 875A FA50
41F8 875B FA51
41F9 875C FA52
41FA 875D FA53
446D 878A FA58
446E 8782 FA59
446F 8784 FA5A
Example of PCSWIN.INI,
...
[DBCS]
CP943_IBM=Y
...
==============================================
* Japan Postal bar code support.(Japan Only)
==============================================
To print Postal Bar Code data from AS/400, following PDF/PDT - printers are
supported by PCOMM.
NPPAGES.PDF -- PDF file for IBM Network Printer with PAGES option
NPPAGES.PDT -- PDT file for IBM Network Printer with PAGES option
IBM5577B.PDF -- PDF file for IBM 5577-S02/T02 Printer
IBM5577B.PDT -- PDT file for IBM 5577-S02/T02 Printer
Please note that the function is also supported on both printers by non-PDT
mode with the automatically installed JPNPBARC.TTF (Japan Postal Bar
Code) font file.
=================================================
* Old JIS sequence printer support (Japan only)
=================================================
Personal Communications uses new JIS sequence(JIS X 0208-1990) for Japanese
DBCS (Kanji) code point. So that if the printer only supports old JIS
sequence(JIS C 6226-1978), some DBCS characters which code points were
changed by this JIS standard modification may not be printed correctly.
In this case, please add the following line to [printers] stanza of
Workstation Profile(.ws file).
OldJIS=Y
================================================================
* NT V4.0 limitation for Old JIS sequence printer (Japan only)
================================================================
The following characters are not printed on old JIS sequence printer
with non-PDT mode.
A. Duplicated between NEC selected and IBM selected (13 characters)
DBCS-Host NEC-select IBM-select
========= ========== ==========
41F1 8754 FA4A
41F2 8755 FA4B
41F3 8756 FA4C
41F4 8757 FA4D
41F5 8758 FA4E
41F6 8759 FA4F
41F7 875A FA50
41F8 875B FA51

9. 41F9 875C FA52
41FA 875D FA53
446D 878A FA58
446E 8782 FA59
446F 8784 FA5A
B. Triply duplicated (2 characters)
DBCS-Host JIS-NonKANJI NEC-select IBM-select
========= ============ ========== ==========
4478 81E6 879A FA5B
DBCS-Host JIS-NonKANJI NEC's IBM-select IBM-select
========= ============ ================ ==========
425F 81CA EEF9 FA54
This is because NT uses uni-code internally, these characters are always
mapped to NEC-selected (for 13 characters) and JIS-NonKANJI (2 characters).
However, these characters are not defined in old JIS sequence.
Workaround:
1. If the printer supports both new JIS sequence and old JIS sequence, use
new JIS sequence.
2. If the printer driver has the function to send real image not text, use it.
Or, if the printer driver has the function not to use printer font, use it.
3. Use PDT mode.
===========================================================
* Limitations of PCOMM macro to VBScript macro conversion
===========================================================
When converting existing PCOMM macros to VBScript macros, be aware that
VBScript, unlike VBA, does not support branching via GOTO statements.
However, if your PCOMM macro uses the GOTO statement to construct a simple
loop, you could alter your converted VBScript macro to substitute a
DO...LOOP structure for the :LABEL....GOTO LABEL structure.
=================================
* Tivoli Plus Module Limitation
=================================
The Tivoli Framework cannot successfully run two or more tasks concurrently
against the same PC managed node. Therefore, when you start a task (by
double clicking the task icon), allow that task to complete before you
start another task that involves the same PC managed node.
===========================
* Maximum Macro File Size
===========================
The macro editor included with PCOMM is capable of editing macros up to
32K bytes in size. (It is very unusual for macros to exceed this size.) If
you need a macro which is bigger than this, it is recommended that you split
the file into two files and have the first file call the second file.
Alternatively, you may utilize a simple text editor to perform the editing
actions.
=================================
* Sort limitation in Log Viewer
=================================
Due to a known problem in the pre-IE4.01 version of the COMCTL32.DLL, as
supplied by Microsoft, the sort function accessed from the right mouse
click in the summary view will not work properly for systems that do

10. not have IE4.01 or greater installed. This problem has been corrected
by Microsoft in IE4.01.
==============================
* LLC2 install and uninstall
==============================
During the installation or uninstallation of the LLC2 protocol driver
supplied with IBM Personal Communications, Windows 95, Windows 98, or
Windows NT4.0 may ask for their respective CD-ROMs to be inserted.
This is normal and may or may not occur.
===============================================================
* Drawing errors within the Terminal Bean's PS running in IE4
===============================================================
There is a known problem with graphical host characters being displayed
incorrectly. For example, the main screen in ISPF has host box characters
that will display as letters.
=================================================================
* Recovery from Secure Sockets Layer (SSL) Installation Failure
=================================================================
The failure codes for the install of the Secure Sockets Layer (SSL)
mean the following:
1 = Error in launching the SSL install.
This is usually caused by copying the install image from the CD without
the SSL subdirectory. Check that the install source directory contains
an SSL subdirectory with various setup*.* files in it.
2 = Error in writing to the SSL response file.
see 1.
10 = Timeout.
This is usually caused by network problems or another processor-
intensive application running in the background.
less than 0 = unsuccessful silent install of SSL.
All of these are documented in the Reference Guide, Appendix J.
If the SSL install failed and you wish to install it after a succesful
installation of Personal Communication, you need to follow these steps:
1)invoke SSL's install from the cd-rom or equivalent server path
<cd-rom>:win32installalldisk1sslsetupssl.exe PCOMM <langID>
where
<cd-rom> is your cd-rom drive
<langID> is the language for which you purchased for Personal
Communications
language langID
---------------------------
Chinese-Simplified zh_CN
Chinese-Traditional zh_TW
Czech cs_CZ
Danish da_DK
German de_DE
English en_US
Spanish es_ES
Finish fi_FI
French fr_FR
Hungarian hu_HU
Italian it_IT

11. Japanese ja_JP
Korean ko_KR
Dutch nl_NL
Norwegian no_NO
Polish pl_PL
Brazilian Portuguese pt_BR
Russina ru_RU
Slovenian sl_SI
Swedish sv_SE
Turkish tr_TR
2) respond to SSL's install panels. It should install successfully.
If you receive a failure message that the parameters were incorrect,
repeat step 1. If you receive other failure messages, take note of
them and report them to IBM service.
==============================================================
* Sockets over SNA support only available via custom install
==============================================================
Sockets over SNA support is no longer automatically installed with the IBM
SNA protocols or full install options. If this support is required. please
perform a custom install and select the Sockets over SNA checkbox.
=========================
* New default code page
=========================
The new default code page is the Windows code page for each country, rather
than the MS-DOS code page.
===========================================
* DB2 Connect for Personal Communications
===========================================
During installation of DB2 Connect, the country, code page, and regional
settings are established. These can be overridden by changing the system
environment variables DB2CODEPAGE and/or DB2COUNTRY. When a new
connection to a database is made, the database manager uses these new
values. For additional information, please refer to Appendix B of the
Quick Beginnings for DB2 connect Personal Edition.
===========================================================================
* Epson printer raster fonts with Windows 95 and Windows 98 (Taiwan Only)
===========================================================================
If you choose a nonexistent font size of a raster font (i.e. 10CPI in Song or
Black fonts), the printed results will be incorrect. Please use a font size
supported by the particular font selected. If the font size is necessary,
use a printer driver that does not have ROM fonts to avoid this problem.
For example, you could use the Epson 1060 driver instead of the Epson
1060C driver.
=================================================================
* Split DBCS characters do not print correctly (3270 DBCS Only)
=================================================================
If there are split DBCS characters on the screen, [Print Screen] will not
split the characters due to printer limitations. If you desire WYSIWYG
output, then use [Print Graphics] instead.
======================================================
* Chinese Star support on Windows 95 OSR2 (PRC Only)
======================================================
Some older versions of Chines Star under Windows 95 OSR2 do not work properly.
Please ensure that you version of Chinese Star is 2.97 or newer.
========================================================
* GDI mode host print using SCS TRN/ATRN control codes

12. ========================================================
When using GDI print mode, print data which is sent from host application
using SCS TRN (Transparent) and ATRN (Ascii Transparent) control codes are
sent to the printer by the Windows Escape function. However, the remaining
data is printed by the Windows GDI function.
To bypass this problem, do not mix the two forms of output or use PDT mode.
==================================================
* SCS Control Code default in 5250 Print Session
==================================================
If MPP(MaximumPrinterPosition), MPL(MaximumPrinterLine),
CPI(CharacterPerinch), and LPI(LinesPerInch) are not transfered
from AS/400, it means that the default value is different from the
"UseDefault" specification in the Work Station (*.ws) profile's [Printers]
section.
If "UseDefault" does not exist, or if "UseDefault=N", then the SCS
value sent from AS/400, will be used. However, if the above control codes
are not specified in SCS, the PDT file's default will be used.
If "UseDefault=Y" is specified, then the value defined in PDT file
will be used as default.
In this case, please note that if you run printing continuously from the
AS/400, from the second print job on, incorrect output may occur due to
the AS/400 not sending SCS Control Codes that are used to set MPL, MPP,
CPI, or LPI.
====================================================================
* PCSMincho and PCSGothic not selectable for display on Windows NT
* (Japan Only)
====================================================================
On Windows NT, PCSMincho and PCSGothic will not appear in the select font
dialog because Windows NT does not perform the font merging that is done by
Windows 95 and Windows 98. Therefore, if either of these fonts were to be
selected, then the DBCS characters would not displayed.
This is a limitation of Windows NT.
==================================================
* Support for Win2000 Professional Beta 3 (CSD1)
==================================================
Personal Communications has been tested on Win2000 Professional NT 5.0
beta 3 (build 2031)and has the following restrictions:
- Support is provided for any LAN adapter(s)
- Support is provided for legacy adapters (no PCI) IBM WAC ISA, IBM MPA ISA,
IBM 3270 emulation ISA and IBM 5250 emulation ISA
- Support is not provided for PCMCIA credit card adapter
- Network Drives is not supported on WIN2000 and is being resolved with
MicroSoft support.
If you attempt to use this function, avoid using the Network Neighborhood.
If you experience hangs trying to connect to the subdirectories, try
connecting at the root instead. Once a drive letter is assigned, this
function is enabled.
==============================================
* Support for Windows Terminal Server (CSD1)
==============================================
Personal Communications provides limited support for Microsoft's Windows NT
4.0 Enterprise Server - Terminal Server Edition platform. Support is limited
to the host connectivities of Telnet and IBM's LLC2 LAN protocol.
Metaframe by Citrix, a product installed to supplement Microsoft's WTS
operating system is supported and the ICA protocol provided for the

13. clients will replace Microsoft's RDP protocol.
Known restrictions in this environment:
- If Microsoft's RDP protocol is used, the RDP client software the default
key for the CLEAR key does not work. The RDP client does not map the key
correctly to the server. If the RDP protocol is used the user must either
remap the CLEAR key or use the pop-up mouse pad.
- ONLY IBMs LLC2 LAN protocol is supported along with TELNET connectivity.
- PCSWIN.INI, an initialization file which contains window sizes, locations
etc. is shared by all users. If one user moves a window, any subsequent
user will see the same update.
- When using the IBM LLC2 and Personal Communication SNA protocol stack, the
administrator must create a default configuration file and initially start
the SNA node via the command line utility CSSTART.EXE with the -a option
and reboot the system. This action will update the system registry to
always start the SNA node at system boot time and will allow the SNA stack
to remain active when a user logs off the sytem. Otherwise, other active
user(s) would lose the SNA host connection(s).
=============================================
* Support for Network Drives over IP (CSD1)
=============================================
Personal Communications provides support for the configuration and use of
Network Drives over IP. Previously, this had been limited to SNA protocols
only. This will allow Shared Folders to execute using the IP protocol.
Configuration support is available to allow the selection of the IP protocol
in addition to the SNA selection.
=======================================================
* Support for Virtual Terminal History Window (CSD1)
=======================================================
Virtual Terminal display supports the ability to scroll the display by one or
more rows. If an ASCII host sends more than one screens worth of data, data
at the top of the display will scroll off and not be viewable by the user.
Personal Communications configuration enables the users to specify the size
of a "History" buffer (or window) to display data that may have been lost by
the host update.
============================================================================
* Support for Virtual Terminal Screen Size of Greater than 24 lines (CSD1)
============================================================================
Personal Communications provides for the configuration of the following
screen size specifications for Virtual Terminal Emulation:
- 36 x 80
- 36 x 132
- 48 x 80
- 48 x 132
- 72 x 80
- 72 x 132
- 144 x 80
- 144 x 132
=============================================================
* Support for Open Host Interface Objects (OHIO) API (CSD1)
=============================================================
Prototype code is provided to support the OHIO specification. This prototype
code is an implementation of the draft (Version 01) Open Host Integration
Objects (OHIO) Application Programming Interface and provided as org.ohio.*
objects in <Personal Communications>pcseclj.jar and documented in the
docohio directory. IBM will provide no Program Services or other support

14. for the prototype code.
=====================================================================
* Support for entering lower case letters in CAPS LOCK state (CSD1)
=====================================================================
The keyword CapsLockOverride=YES specified in the keyboard section of the .WS
file will allow the user to enter lower case letters by using the shift key.
Currently, when CAPS LOCK is enabled, the shift key will not change the key
case mode to lower case.
==========================================================
* Support for specifying multiple PCSPD.DAT files (CSD1)
==========================================================
To support the use of a font mapping table (AS/400 to PC) on a session basis,
the keyword DATFILE=(Fully qualified file name of the additional PCSPD.DAT
file) is added to the printers section of the .WS file. This allows the use
of multiple PCSPD.DAT files for 5250 printing and the user should use the
default PCSPD.DAT file as a template for creating additional files.
=======================================
* Network Drives Configuration (CSD1)
=======================================
A utility, the AS/400 Connection Configuration, located in the Utilities
folder provides configuration support for creating a Network Drives
configuration file. This utility allows the configuration of both IP
and SNA hosts and provides a method for migrating previous Network
Drive configuration information. Previous configuration data contained
in the .ACG file will not be used and must be converted to the new format
prior to starting the Network Drives function. See the online help
documentation for this utility for details on performing this migration
step.
===========================================
* Launch Application from VBScript (CSD1)
===========================================
Personal Communications now supports starting an application file from
within a VBScript. To accomplish this a new automation object has been
introduced. autSystem is the new object and Shell is the new method.
The prototype is as follows:
function autSystem.Shell "ExeName",["Parameters"],[WindowStyle] as long
Parameters :
ExeName - String; the path and filename to the executable file.
Parameters - String, optional; any parameters you wish to pass on to
the application
WindowStyle - Integer, optional; the window style that you want the
application started as.
The valid values are:
AUTSYS_SHOW = 1 - show normal with focus
AUTSYS_SHOWMINIMIZED = 2 - show minimized with focus
AUTSYS_MAXIMIZE = 3 - show maximized
AUTSYS_SHOWNA = 4 - show normal without focus
AUTSYS_MINIMIZE = 5 - show minimized without focus
The default is AUTSYS_SHOW.
Return:
long - If the value is less than 32 it indicates an error has occured.
example: to run notepad from within a VBScript
autSystem.Shell "Notepad.exe", "c:test.txt" , 1
This will start notepad with the file c:test.txt loaded in a Normal window

15. with focus.
****************************************************************************
Items below this line may not be translated and therefore may be included
in US English only.
****************************************************************************
----------------------------------------------------------------------------