home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
wr0605.zip
/
WR0605.DOC
Wrap
Text File
|
1993-08-23
|
88KB
|
1,794 lines
IBM COMMUNICATIONS MANAGER/2 VERSION 1.01
Communications Manager/2 Information APARs
------------------------------------------
The following Communications Manager/2 Information APARs have been written
since the initial release of the product.
If you have access to CompuServe, check the OS/2 Developers Forum 2 (OS2DF2)
library for the file CMINFO.ZIP. This contains the latest information APARs.
+-------------------------------------------------------------+
|II06001 |
| COMMUNICATIONS MANAGER INFORMATION APAR |
| |
| HOW TO SEND PROBLEM DOCUMENTATION TO |
| COMMUNICATIONS MANGER LEVEL 2 SUPPORT |
| |
|LAST UPDATE: 05/26/93 BY: RHB |
| |
|PURPOSE: THIS INFORMATION APAR PROVIDES INSTRUCTIONS ON HOW |
| TO SEND THE PROBLEM DOCUMENTATION (TRACES AND |
| FILES) REQUESTED BY A COMMUNICATIONS MANAGER |
| LEVEL 2 SPECIALIST TO THE IBM SUPPORT CENTER. |
+-------------------------------------------------------------+
|
| AT THIS POINT, A LEVEL 2 SPECIALIST HAS REQUESTED THAT
| PROBLEM DOCUMENTATION BE SENT TO LEVEL 2 FOR PROBLEM
| ANALYSIS. THERE ARE FOUR METHODS TO CHOSE FROM:
|
| 0. ELECTRONICALLY VIA IBMMAIL OR IBMLink
| 1. ELECTRONICALLY THRU THE NETWORK BY THE SE
| 2. FAX
| 3. EXPRESS COURIER
| 4. U.S. MAIL
|
| BEFORE SENDING ANY INFORMATION A PROBLEM RECORD (PMR)
| MUST BE OPEN WITH THE IBM SUPPORT CENTER.
|
| After sending the information please call
| the IBM Support Center at 1-800-237-5511 to
| inform IBM Communications Manager Level 2 that
| the information has been sent and the
| method of transport.
|
+-------------------------------------------------------------+
| 0. ELECTRONICALLY VIA IBMMAIL or IBMLink |
+-------------------------------------------------------------+
|02/26/93
| If you have an IBMMAIL or IBMLink id, then you may send
| problem information electronically to Level 2.
|
| The filename must be the PMR number. The
| extension should identify the files. For example,
| MESSAGE.DAT would be 9x999.msg, where 9x999 is the
| PMR number. All files should be submitted as
| binary files. Reference Information APAR II06459
|
| THE IBM MAIL ADDRESS IS: USIB4J5S at IBMMAIL
| THE IBMLink ADDRESS IS: DEFECT AT RALVM5
|
| THE IBMLink and IBMMAIL
| addresses are not monitored for notes. Please call
| the IBM Support Center to update the PMR at phone number,
| 1-800-237-5511, or update the Electronic PMR. If you
| would like to send additional information with
| the problem information files, please create a separate
| file called: 'pmrnumber TXT'.
|
|
|
|
+-------------------------------------------------------------+
| 1. ELECTRONICALLY THRU THE NETWORK BY THE SE, |
+-------------------------------------------------------------+
|05/26/92
| AN IBM SE can transmit files from a Customer's diskette to
| Level 2 as follows:
|
| Send the files from the diskette to your PROFS or VMID,
| using Communications Manager:
|
| Logon to your PROFS or VMID.
|
| In an OS/2 Window for each file enter:
|
| SEND A:filename.extension A:fn ft fm ( RECFM V
| | |
| +---> disk drive +---> Short Session ID
|
| The filename should be the PMR number. The
| extension should identify the files. For example,
| MESSAGE.DAT would be 9x999.msg, where 9x999 is the
| PMR number. All files should be submitted as
| binary files.
|
| On your PROFS or VMID, send the files to DEFECT at RALVM5.
|
| For example: SENDFILE 9x999.MSG TO DEFECT AT RALVM5.
|
|
| DEFECT AT RALVM5 is not monitored for PROFS notes. If you
| would like to send additional information, create a CMS file
| called 'PMR number' TXT. For example: XEDIT 9x999 TXT.
| Please send this file to DEFECT at RALVM5
| instead of a PROFS NOTE.
|
+-------------------------------------------------------------+
| 2. FAX |
+-------------------------------------------------------------+
|12/17/92
| The following phone numbers are available to receive
| FAX transmissions:
|
|
|
| (919) 543-1013 or 8/441/1013
|
| Remember to place the PMR number and the L2 Programmer's
| name on the FAX cover sheet.
|
+-------------------------------------------------------------+
| 3. EXPRESS COURIER |
+-------------------------------------------------------------+
|12/17/92
|
| IBM Corporation
| 3039 Cornwallis Road.
| Research Triangle Park, NC, USA 27709
| ATTN: "L2 Programmer's Name"
| DC08/B062/Room "office number" RE:"APAR or PMR Number"
|
+-------------------------------------------------------------+
| 4. U.S. MAIL |
+-------------------------------------------------------------+
|12/17/92
| IBM CORPORATION
| P.O. BOX 12195
| RESEARCH TRIANGLE PARK, NC, USA 27709
| ATTN: "L2 Programmer's Name"
| DC08/B062 RE:"APAR or PMR number"
|
|
+-------------------------------------------------------------+
|KEYWORDS: CMINFO 562121301 R100 566933602 R130 CM |
| 0964110 FAX TRANSMIT TRANSMISSION SEND SENDING |
| COM MGR APAR APARS COMMGR 562125400 100 0964137 |
| Communications Manager/2 ES EE |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II06875 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| 122-Key Keyboard Support (HOST KEYBOARD) |
| |
| Tips, Techniques, Questions and Answers |
| |
|LAST UPDATE: 05/26/93 BY: RHB |
| |
+-------------------------------------------------------------+
|
| 1. 04/08/93 The 122-key keyboard can be utilized for
| 5250 emulation sessions as well as for 3270 emulation.
|
| The 122 keyboard is configurable for 5250 emulation
| sessions and all twenty-four (24) Function keys
| will be recognized. However, the keyboard mapping
| can only address keys defined for the 101-key Enhanced
| Keyboard and does not include keys for specific 5250
| function. One will need to remap the
| required keys to provide specific 5250 functions.
|
| Communications Manager /2 Information and Planning
| SC317007 Guide page 4-16 is incorrect
| in stating that the 122 keyboard is not supported for
| 5250 Emulation.
|
|
+-------------------------------------------------------------+
|KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
| 5250WSF 122KEY 122 key keyboard board host |
| IBM Connected #6400 6400 PFKEYS |
| PFKEY 3270EM EXTRA EMULATION 3270 EMULATOR KEYS |
| Feature |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II06894 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| Starting a Communications Manager/2 Trace |
| |
| |
|LAST UPDATE: 05/26/93 BY: RHB |
| |
+-------------------------------------------------------------+
|
| 1. 05/26/93 Starting a Communications Manager/2 trace.
|
| 1. Select the Communications Manager/2 ICON folder
| from the Desktop.
| 2. Select the PROBLEM DETERMINATION AID - TRACE ICON.
| 3. On the PROBLEM DETERMINATIONS AIDS - TRACE SERVICES
| panel:
| 3.1 For Product, select COMMUNICATIONS MANAGER
| 3.2 Under APIs, DLCs, Events, select the options as
| directed by IBM Level 2 Support.
| 3.3 Select Options on the Action Bar
| 3.4 Select Trace Buffer Details
| 3.5 Set TRACE BUFFER SIZE (x64KB) to 16
| 3.6 Set TRACE RECORD LENGTH (bytes) to 144
| unless directed otherwise by IBM Level 2 Support
| 3.7 Click on OK.
| 4. Click on START, Trace Status shows ACTIVE
| 5. Click on TOGGLE VIEW, to verify that the selected
| traces were started.
| 6. Recreate the problem.
| 7. Return to the PROBLEM DETERMINATIONS AID - TRACE
| SERVICES PANEL.
| 7.1 Click on STOP ALL, trace status shows INACTIVE
| 7.2 Click on SAVE. The FILENAME SELECTION panel is
| displayed.
| 8. On the FILENAME SELECTION panel,
| 8.1 For FILENAME, enter <pmrnumber>.trc
| Note: pmrnumber is Problem number open to IBM.
| 8.2 The default selections will place the file
| in CMLIB for pickup by CMPD processing.
| From an OS/2 command prompt, issue the command
| CMPD <pmrnumber> d1: d2: where d1 is the disk
| where CM is installed, and d2 is the disk where
| NTS/2 (LAPS) is installed (optional), both
| usually being C: C: , and press Enter.
| 8.3 A compressed file called <pmrnumber>.RAM will be
| generated containing configuration, error, message,
| ini, and other related files, followed by a listing
| of all the files contained therein...this takes a
| little while to do all that, so please be patient!
| 8.4 Copy CMLIB <pmrnumber>.RAM to a diskette for
| analysis by the service personnel requesting
| the information.
| 9. Click on OK, Verification notice pop-up is presented.
| 10. Close the FILENAME SELECTION Window.
| 11. Close the PROBLEM DETERMINATIONS AIDS - TRACE SERVICES
| window.
|
+-------------------------------------------------------------+
|KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
| CMDOC CMPD CMPSI PD PSI PD PSI ERRORS PROBLEMS |
| MESSAGE MESSAGES LOG LOGS ALERTS |
| |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II06895 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| Management Services |
| |
| Tips, Techniques, Questions and Answers |
| |
|LAST UPDATE: 04/16/93 BY: RHB |
| |
+-------------------------------------------------------------+
|
| 1. 04/16/93 Information on Communications Manager/2
| Management Services.
|
| Network Administration and Subsystem Management
| Guide SC316168
| Chapter 1 Communications Manager Features
| Chapter 2 Communications Manager and SNA
| Chapter 16 System Management Programming Capabilities
| System Management Programming Reference SC316173
| Chapter 1 Introduction, under Management Services Verbs
| Chapter 2 The Display Verb
| Chapter 5 Configuration Verbs
| Chapter 6 Management Services Verbs
| Appendix D Management Services (MS) Support
| Appendix E MDS-MUs for Requesting and Reporting
| System Data
| Communications Manager/2 Version 1.0 New Features GG243958
| Chapter 9 SNA Management Services
|
| 2. 04/16/93 CMSETUP Installation/Configuration panels and CID
| do not support the following verbs:
|
| DEFINE_DEFAULT_SOC
| DEFINE_EXPLICIT_SOC
| DEFINE_REMOTE_FP
| These verbs and associated parameters will need to be
| added via editing the <your configuration name>.NDF file,
| then verifying the changed .NDF file via CMVERIFY.
| See Chapter 1 Communications Manager Features under
| Communications Manager Configuration Methods
| in the Network Administration and Subsystem Management
| guide SC316168 and Chapter 5 Configuration Verbs
| in the System Management Programming Reference, SC316173.
| The APPNV.CTL file in the CMLIB sub-directory also shows
| the syntax for these verbs.
|
| 3. 04/16/93 Why are my Alerts not getting to NetView?
|
| a. Verify in error log that Alert (type 0017-00000002) is
| received correctly by Communications Manager/2.
| Check for correct Alert formatting of subvectors.
| Alert dump formatter (EPWALERT.DMP) may help.
| b. Use PMDSPLAY to display FP status for Alert
| if FP status = ACTIVE, check that
| EPWROUT is started and set properly (EPWROUT 1).
| Then start a Communications Manager/2 Trace
| to insure Alert is sent.
| Check for NetView filters that keep Alert from
| being displayed, See NetView Operation book--DFILTER
| to display, SRFILTER to set.
|
| c. If FP status is INACTIVE &
| If using SSCP-PU session (NMVT Alerts),
| DEFINE_LOCAL_CP host_fp_support must be (YES)
| AND SSCP-PU session must be active
|
| d. If FP status is INACTIVE &
| If using LU 6.2 session (MDS-MU Alerts) then
| check one of the following 3 items:
| 1. FOCALPT CHANGE FPCAT=ALERT TARGET=cpname must be
| issued and accepted at NetView. If not accepted,
| check that links are active and that NetView
| LU or implicit inbound PLU
| support is on at Communication Manager/2.
| NetView will not reissue the command.
| 2. DEFINE_REMOTE_FP must be issued at Communication
| Manager/2.
| 3. This may be due to delay in acquisition.
| - 30 seconds after link comes active.
| - 30 minute automatic retry in case of non-APPN links
| or unknown time if Communications Manager/2
| is not responsible for acquisition.
|
| 4. 04/16/93 Why am I not a focal point for entry
| point xxxxxxxx?
|
| a. Use PMDSPLAY to display MS information for local
| focal points.
| b. Must use .NDF file verbs, SOC program, or entry
| point definition to establish relationship.
| d. Focal FP application must be currently registered.
| e. Session may not be active (inactive links, no
| LU definitions).
| f. EP may have higher rank FP.
| g. Check error log for revoke received (type 0055 ), then
| EP may have been acquired by another FP
| or FP loop may have been detected and broken.
| h. Entry point product may not accept focal point
| AS/400 pre V2R2 only accepts Alert category.
| NetView does not accept higher Alert FP (and some
| other categories).
| i. May be due to delay in acquisition, as previously stated.
|
|
| 5. 04/16/93 Why do I keep getting xxxxxxxx as my FP?
|
| a. Use PMDSPLAY to check retry responsibility and rank
| for category.
| b. If FP has retry responsibility,
| Remove this node from FPs SOC.
| (Does not have immediate effect) and
| issue REVOKE_REMOTE_FP for this category
| (no user interface supplied).
| c. If EP (local Communications Manager/2 node)
| has retry responsibility,
| remove DEFINE_REMOTE_FP from the .NDF file,
| if it is present. Stop Communications Manager/2 and
| erase APPCMS.DAT (will remove all categories).
| Issue REVOKE_REMOTE_FP for this category.
| If host rank, set DEFINE_LOCAL_CP HOST_FP_SUPPORT (NO).
|
|
+-------------------------------------------------------------+
|KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
| FOCAL POINT ENABLEMENT MS APPLICATION |
| NMVT MS ALERTS ALERT DEFINEREMOTEFP |
| DEFINEDEFAULTSOC DEFINELOCALCP HOSTFPSUPPORT |
| DEFINEEXPLICITSOC REVOKEREMOTEFP |
| DEFINEREMOTEFP |
| |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II06915 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| Finding the cause of problems when |
| using Communications Manager/2 |
| |
|LAST UPDATE: 05/26/93 BY: RHB |
| |
+-------------------------------------------------------------+
|
| 1. 04/22/93 Finding the cause of INSTALLATION problems.
| 1.1. Check if CM.LOG in OS2 CMLIB exists. If it
| does then edit or type this file to see the
| error messages produced during installation.
| You may need to also check "Communications Manager/2
| Message Reference" SC316159.
| 1.2. Check if CMRINST.LOG in OS2 CMLIB exists. If it
| does then edit or type this file to see the
| error messages produced during CID processing.
| 1.3. Check if CM.LOG in CMLIB exists. If it
| does then edit or type this file to see the
| error messages, or view this file from the OPTION
| pulldown of CMSETUP.
| 1.4. Check the FFST/2 Message log for errors.
| If FFST/2 was operational at the time of the
| error. See 6. Checking the FFST/2 Message log.
| 1.5. Consult the "Communications Manager/2 Workstation
| Installation Guide" SC316169.
| 1.6. Consult the README for Communications Manager/2
| under "OPTIMAL ERROR REPORTING".
|
| 2. 04/22/93 Finding the cause of Configuration problems.
| 2.1. If errors occurred during the verification of
| the Communications Manager/2 configuration you
| will be prompted to view the VERIFY.LOG
| 2.2. Use the CMRECORD command to produce an ASCII
| file showing the Communications Manager/2
| Configuration. You can print this file or display
| it in an OS/2 window while you review error messages
| CMRECORD <configuration filename>
| 2.3. Check the FFST/2 Message log for errors.
| See 6. Checking the FFST/2 Message log.
| 2.4. Use the Help available on the Configuration
| panels. Help is available via PF1 in a
| field or put focus on the field and click
| on the help button. This will present help
| for the field. PF2 from a HELP window
| or HELP in a window will produce general
| help for the window.
| 2.5. Consult the IBM "Communications Manager/2
| Configuration Guide" SC316171.
|
| 3. 04/22/93 Finding the cause of problems when
| migrating a configuration from a
| previous release to Communications Manager/2.
| 3.1. Check UPGRADE.LOG using the FFST/2
| Message Log Formatter to view this file.
| See 6. Checking the FFST/2 Message log.
| 3.2. Check the FFST/2 Message log for errors.
| See 6. Checking the FFST/2 Message log.
|
| 4. 04/22/93 Finding the cause of CID problems.
| 4.1. Check CMRINST.LOG in OS2 CMLIB or CMLIB.
| Edit or type this file to see the
| error messages produced.
| 4.2. Check the FFST/2 Message log for errors.
| See 6. Checking the FFST/2 Message log.
|
| 5. 04/22/93 Finding the cause of other Communications
| Manager/2 problems.
| 5.1. Use the CMRECORD command to produce an ASCII file
| showing the Communications Manager/2 Configuration.
| You can print this file or display it in an OS/2
| window while you review error messages.
| CMRECORD <configuration filename>
| 5.2. Check the FFST/2 Message log for errors.
| See 6. Checking the FFST/2 Message log.
| 5.3. ONLINE help is available. See 9. Checking the
| ONLINE MESSAGE REFERENCE.
| 5.4. If you are receiving a OIA MACH___ or COMM
| error message, press ALT-Q
| while in an emulator window
| or chose Emulator Help from the
| Emulator window pull down in upper left hand
| corner.
|
| 6. 05/26/93 Checking the FFST/2 message log.
| 6.1. Locate the FFST/2 folder on the OS/2 desk top.
| 6.2. In the FFST/2 folder, Chose the MESSAGE LOG
| FORMATTER ICON.
| If the FFST/2 folder is not on the desktop you may
| enter MSGLOGF to invoke the Message Log Formatter
| in an OS/2 window.
| 6.3. On the OPEN panel,
| Select the message log you are currently using.
| The default message log is OS2 SYSTEM OS2MLOG.DAT
| (on the boot drive). Errors which
| occurred during Verify or Upgrade of your
| configuration may be viewed by selecting either
| VERIFY.LOG or UPGRADE.LOG in the CMLIB directory.
| Select the desired directory and log, then
| click on OPEN.
| 6.4. On the MESSAGE LOG FORMATTER panel, the current
| System and Communications Manager/2 messages are
| displayed. Review the message details and
| then message help for each message.
| The message at the top is the most recent message.
| Help can be selected as follows:
| Place the cursor on the line of the message you
| would like to see help for, from options pull down
| select DETAIL ENTRY (or double click on the line).
| Note the scroll bars, the next button and the
| previous button, to move the displayed information
| The message may direct you to other sources of
| information, such as the System Error Log, FFST/2
| DUMP formatter, or the Communications
| Manager/2 Publications, make a note of the
| PROBE ID, PROBLEM ID, DATE, and TIME.
|
| 7. 04/22/93 Checking the SYSTEM ERROR LOG.
| 7.1 In the FFST/2 folder, chose the SYSTEM ERROR
| LOG ICON or from the command prompt enter
| "START SYSLOG".
| 7.2 ON THE OS/2 ERROR LOG FORMATTER, the most recent
| error log record is displayed. Chose the error
| record that matches the PROBLEM ID, PROBE ID, DATE
| and TIME. Follow the instructions for the message
| that directed you here. All system error log
| entries should have a corresponding
| message entry.
|
| 8. 04/22/93 Checking the FFST/2 DUMP FORMATTER.
| 8.1. In the FFST/2 folder, choose the DUMP
| FORMATTER ICON or from a command prompt
| enter "START EPWDF".
| 8.2 On DUMP FORMATTER/OPEN panel, choose the
| dump file to open as directed
| by the message. EPWALERT.DMP is the
| most common dump file, containing all the
| alerts for Communications Manager/2.
| Choose the dump record that matches the
| PROBE ID, the PROBLEM ID, DATE and TIME.
| Follow the instructions for the message that
| directed you here.
|
| 9. 04/22/93 Checking the ONLINE MESSAGE REFERENCE.
| 9.1. In the Communications Manager/2 ICON VIEW folder,
| choose the MESSAGE REFERENCE ICON,
| or from a command prompt enter "VIEW CMMSGREF".
| 9.2. SELECT the message prefix for the message you are
| interested in or chose SERVICES, SEARCH and enter
| the message number. Press enter or double
| click on the messages.
| This is an ONLINE version of the
| Communications Manager/2 Message
| Reference SC316159.
| 9.3. Or enter HELP <message number> (HELP ACS0619)
| to have the message information displayed.
| The Help command will not display messages
| that end with an I. The I indicates Information
| Messages. Messages ending with E, Error
| and ending with W, Warning, are displayed.
|
|10. 04/22/93 Other References
| Check the "Communications Manager/2 Problem
| Determination Guide" SC316156, especially
| Chapter 1 "Problem Determination Procedures".
|
+-------------------------------------------------------------+
|KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
| CMDOC CMPD CMPSI PD PSI PD PSI ERRORS PROBLEMS |
| MESSAGE MESSAGES LOG LOGS ALERTS |
| |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II06984 |
| |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| USING HOST FILE TRANSFER WITH COMMUNICATIONS MANAGER/2 |
| |
| |
| LAST UPDATE: 05/26/93 BY: RHB |
| |
| PURPOSE: THIS INFORMATION APAR PROVIDES SOLUTIONS TO |
| POSSIBLE PROBLEMS THAT MAY BE ENCOUNTERED |
| WHEN USING HOST FILE TRANSFER WITH COMMUNICATIONS |
| MANAGER/2. |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| A. FREQUENT PROBLEMS AND SOLUTIONS |
+-------------------------------------------------------------+
| |
| 1. 05/26/93 |
| TRANS010 - Listed below are various possible causes |
| and solutions to the TRANS010 error. |
| |
| a. IND$FILE is not at the correct level. To determine |
| whether IND$FILE is at the correct level. At the host |
| prompt type IND$FILE. If you get a panel stating the |
| program and version, the level is fine, if nothing, |
| then IND$FILE is downlevel. The correct level for |
| IND$FILE IS 1.1.1. Until PC FILE TRANSFER can be |
| upgraded on the host, set BUFFERSIZE OVERRIDE=2K. |
| CMSETUP > 3270 EMULATION > Select session and open |
| it, then under OPTIONS select DATA TRANSFER BUFFER |
| SIZE OVERRIDE, then select the radio button SPECIFIC |
| and change to 2K. |
| |
| b. A TRANS010 can also imply that the SEND/RECEIVE syntax |
| is wrong. Refer to the Command Reference publication |
| or the OS/2 Online Help. |
| |
| c. Recreate the failure and jump to the host session. |
| Is the cursor in the lower right hand corner of the |
| screen? This placement of the cursor indicates that |
| the query bit, extended data streaming is not on. |
| The PSERVIC statement has been defined incorrectly |
| in the VTAM logmode table. In an LU2 environment, |
| the 3rd character in the PSERVIC statement should |
| be an eight(8). |
| |
| d. TRANS010 on file transfer to/from MVS/TSO host. |
| When performing a file transfer with a MVS/TSO host |
| it is very important that the host session be at a |
| TSO READY prompt. ISPF/PDF or TSO Session Manager |
| cannot be running. |
| |
| e. TRANS010 and keyboard locked in the middle of file |
| transfer. Problem occurs when the one is in a |
| protected screen application on the host session, a |
| clear is issued prior to the IND$FILE command which |
| resets the cursor location in the host session. In |
| some cases, this problem can be caused by a field |
| that is too small for the file transfer to process |
| a command on the host. One should enlarge the |
| unprotected space or use native TSO,CMS,etc... |
| |
| f. TRANS010 on file transfer to/from VSE/CICS host. |
| Verify that the PTF for VSE APAR PN01653 is applied |
| on the host. The VSE equivalent to IND$FILE is |
| INWPCCOM and apar PN01653 modified it. For further |
| information regarding file transfer and a VSE host |
| please reference information APAR II06554. |
| |
| g. TRANS010 and TSO displays three asterisks (***): |
| at the TSO Ready; prompt enter PROFILE NOINTERCOM |
| then enter TERM NOBREAK. This will insure "native" |
| TSO mode. |
| |
| 2. 05/26/93 |
| TRANS013 |
| The problem may be that the BUFFER SIZE OVERRIDE |
| is incorrect. Try 2K, if left to the default of |
| zero, Communications Manager/2 |
| will try to compute a default. To |
| change this go into CMSETUP, 3270 EMULATION and |
| select a session and open it, under OPTIONS select |
| DATA TRANSFER BUFFER SIZE OVERRIDE, then select the |
| radio button SPECIFIC and enter 2K. |
| |
| 3. 05/26/93 |
| TYPE 0022 SUBTYPE 00009008 in the FFST/2 logs. Check |
| the system for other SEND/RECEIVE commands. If there |
| are others, check PATH statements in CONFIG.SYS to see |
| if the directories that contain SEND/RECEIVE commands |
| follow CMLIB, if not, change the PATH statement so |
| that CMLIB precedes the other directory. The subtype |
| 00009008 identifies DosExecPgm as the OS/2 function |
| call that was attempted. |
| Communications Manager's SEND and RECEIVE does |
| not use the DosExecPgm OS/2 function call. |
| |
| 4. 05/26/93 |
| CHARACTERS NOT TRANSLATED CORRECTLY. Transferring files |
| and translating from ASCII to EBCDIC or vice versa and |
| the characters do not translate properly. The most |
| common is the "begin braces" and the "end braces" |
| in C programs (Reference JR01104). |
| One may create their own code page. See the |
| Configuration Guide, SC316171, Appendix A. One |
| will have to send a copy of the IND$FILE to a local |
| disk and change the translation tables there. |
| |
| 5. 05/26/93 |
| One is able to perform file transfers on small files |
| but receives IKT00405I and PROG727 on transferring |
| LARGE files. |
| |
| Change the PSERVIC as indicated in the Host Connection |
| Reference manual, on page 1-5, under 3270 Display (LU2) |
| |
| Another solution is to change the 3270 profile |
| Data Buffer from '0' to '2K' bytes. |
| |
| 6. 05/26/93 |
| Transferring files to a CICS host (MVS): CICS requires |
| that the data transfer buffer size override be set to |
| 2K. Otherwise, some files will be corrupted. |
| No messages are received including the FILE TRANSFER |
| COMPLETE message. |
| See item 2 above. |
| |
+-------------------------------------------------------------+
| B. REFERENCE DOCUMENTATION |
+-------------------------------------------------------------+
| |
|1. 05/25/93 |
| Host Connection Reference Manual : SC31-6170-00 |
|2. 05/25/93 |
| The Message Reference : SC31-6159-00 documents |
| TRANS messages. TRANS messages can also be accessed |
| by selecting the Message Reference icon under the |
| Communications Manager Icon View. |
+-------------------------------------------------------------+
| |
| |
| KEYWORDS: FILEXFER TRANS010 TRANS10 TRANS013 TRANS13 |
| 0022 00009008 DOSEXECPGM SEND RECEIVE CMINFO |
| IND$FILE 562125400 R100 CM2INFO TSO ISPF PDF |
| PROG727 IKT00405I CM/2 CM2 0964137 |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II06996 |
| |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| USING 3270 HOST PRINT WITH COMMUNICATIONS MANAGER/2 |
| |
| |
| LAST UPDATE: 05/26/93 BY: RHB |
| |
| PURPOSE: THIS INFORMATION APAR PROVIDES SOLUTIONS TO |
| POSSIBLE PROBLEMS THAT MAY BE ENCOUNTERED |
| WHEN USING HOST PRINT WITH COMMUNICATIONS |
| MANAGER/2 |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| A. FREQUENT PROBLEMS AND SOLUTIONS |
+-------------------------------------------------------------+
| |
| 1. 05/26/93 |
| Host Print and 3270 Screen Print problems after the |
| OS/2 V2.0 ServicePak (XR06055) is applied. Some symptoms |
| are: First page of host print job is missing. |
| Blank first page of host print job. |
| Error PMVxxxx indicating corrupt metafile. |
| |
| Solution: |
| In the Printer Object Settings select the Queue Options |
| tab then select Printer Specific Format. A raw data file |
| will be created instead of a metafile. Reference APAR |
| PJ06608. |
| |
| 2. 05/26/93 |
| 3270 Print Screen (SHIFT+PRINT SCREEN) fails with SYSTEM |
| ERROR in Emulator Print Control when attempting to print |
| to the Print Server after the OS/2 V2.0 ServicePak |
| (XR06055) has been applied. |
| |
| Solution: |
| This problem has been documented in APAR IC04859 |
| for the LAN product. |
| |
| 3. 05/24/93 |
| Print Server fails with 0044 0000C003 while attempting |
| to print host file. The Print Server is running the |
| LEXMARK SPOOL UTILITY which routes output to remote |
| printers attached to 4033 devices on the LAN. VTAM was |
| generating a SNA return code of 081C for this failure. |
| |
| Solution: |
| This problem was resolved by installing the latest |
| LEXMARK SPOOL UTILITY and changing the Network Adapter |
| Print Utility Timeout parameter from 60 to 90. As of |
| 05/21/93, the latest level of 4033 code available on |
| the LEXMARK BBS (606/232-5238 or T/L 445-5238) is v1.2. |
| Download file 4033V12.EXE from the BBS (about 200K bytes)|
| |
| 4. 05/26/93 |
| Host Print job wraps at column 80 on HP Laserjet printer |
| even though PM_Q_RAW is used. |
| |
| Solution: |
| A possible circumvention is to check the CPI setting in |
| Emulator Print Control, Print Style. If it is set to 10 |
| change it to 17 CPI. The emulator uses an algorithm that |
| looks at the print line coming down in the job stream |
| compares it with the space allocated for it to print in, |
| which is limited by print density (CPI) and page size |
| (job properties). This plus the margins (which are fixed |
| on the HP) determine how many characters per line are |
| printed. |
| |
+-------------------------------------------------------------+
| B. REFERENCE DOCUMENTATION |
+-------------------------------------------------------------+
|1. 05/26/93 |
| The Communications Manager: 3270 Host Print publication |
| by the NTSC will assist in configuring and |
| utilizing some of the print features provided by |
| Communications Manager. This document is available on |
| MKTTOOLS as CMHOSTP, or order Technical Bulletin |
| GG663241. |
+-------------------------------------------------------------+
| KEYWORDS: HOSTPRNT HOSTPRINT CMINFO CM2INFO 562125400 R100 |
| 0964137 PMV6011 3270EM 3270 EMULATION SCRNPRNT CM/2 CM2 |
| SHIFTPRINT |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II07001 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| SNA GATEWAY |
| |
| Tips, Techniques, and Frequent Problems |
| |
|LAST UPDATE: 05/26/93 BY: RHB |
| |
+-------------------------------------------------------------+
|RECOMMENDED READING
| 1. 05/26/93 Communications Manager/2 Configuration
| Guide, SC316171, Chapter 11.
| This book provides Configuration information and
| instructions for the product.
|
| 2. 05/26/93 Communications Manager/2 Network Administration
| and Subsystem Management Guide, SC316168, Chapter 7.
| This book also defines concepts and planning procedures
| for configuration, installation, and networking
| considerations. Shipped with this book is a
| diskette that contains SAMPLE RESPONSE FILES.
|
| 3. 05/26/93 Communications Manager/2
| New Features, GG243958, Chapter 5.
| This book provides an overview of the new and
| enhanced features of Communications Manager/2.
|
|CONFIGURATION DIFFERENCES
|
| 1. 05/26/93 There are now two (2) SNA Gateway definition
| verbs located in the .NDF file which can occur
| multiple times. They are:
|
| DEFINE_GATEWAY_HOST :
| This parameter defines LU POOLS for a specified host
| link and optionally, their AUTO-LOGOFF timers.
|
| DEFINE_GATEWAY_WORKSTATION :
| This parameter defines which HOST LU's will be
| allocated to which workstation, and whether the LU's
| will be POOLED or DEDICATED. Only POOLED LU's are
| given to IMPLICIT workstations. Keep in mind that
| the gateway never contacts an IMPLICIT workstation.
|
| 2. 05/26/93 SNA Gateways can now support up to 3
| MULTIPLE PU's which can all be active at the same
| time. This means that there will be 2
| or more DEFINE_LOGICAL_LINK commands in the .NDF
| that specify SOLICIT_SSCP_SESSION(YES). This signifies
| that APPC is expecting ACTPU's and ACTLU's from the
| other end of the link.
|
| 3. 05/26/93 When configuring a connection to a
| host or logical link through the panels,
| a HOST LINK will have SOLICIT_SSCP_SESSION(YES)
| and ACTIVATE_AT_STARTUP(YES).
|
| 4. 05/26/93 All defined links must specify the following:
| o ADAPTER_NUMBER
| o DLC_NAME
| o Destination ID
|
| The destination ID can be defined in 3 ways:
| o DESTINATION_ADDRESS
| o FQ_ADJACENT_CP_NAME
| o ADJACENT_NODE_ID
|
| DESTINATION_ADDRESS can be specified through either
| the Communications Manager Configuration panels or
| by editing the .NDF file.
|
| FQ_ADJACENT_CP_NAME is specified in the panels by the
| Partner network ID and Partner node name on the
| CONNECTIONS PANEL, but this panel forces one to put in a
| destination address and adds a DEFINE_PARTNER_LU
| LOCATION verb.
|
| ADJACENT_NODE_ID can only be specified by editing the
| .NDF file.
|
| Links defined through FQ_ADJACENT_CP_NAME and ADJACENT
| NODE_ID only work with links that perform XID exchanges.
| These links must also have ACTIVATE_at_STARTUP(NO).
| Keep in mind that the remote node must activate the link.
|
| FQ_ADJACENT_CP_NAME only works for XID3 exchange, not
| XID0.
|
| After changing the .NDF file the configuration will
| need to be verified. See Item 3, under
| Configuration Problems section.
|
| 5. 05/26/93 With Multiple PU (MPU), one link is
| designated as the control point link and:
| o it's PU_NAME is either the same as the CP_NAME
| or is not specified.
| o It is used as the HOST_FOCAL_POINT so all NMVT's
| will be sent to it.
|
|
|CONFIGURATION PROBLEMS
|
| 1. 05/26/93 Many fields that were in HEX in prior releases
| are now in DECIMAL. This is especially true for
| NAU ADDRESSES. If you are upgrading from EE or ES,
| this conversion will be done for you.
|
| 2. 05/26/93 In the .NDF file, but not in the panels,
| all numbers are assumed to be in DECIMAL
| unless preceded by 'X' and enclosed in SINGLE QUOTES.
|
| 3. 05/26/93 After the .NDF file is updated, the file
| must be verified. Use CMSETUP or CMVERIFY.
| See Chapter 1 Communications Manager Features under
| Communications Manager Configuration Methods
| in the Network Administration and Subsystem Management
| guide SC316168 and Chapter 5 Configuration Verbs
| in the System Management Programming Reference, SC316173.
| The APPNV.CTL file in the CMLIB sub-directory also shows
| the syntax for these verbs.
|
| 4. 05/26/93 POOL NAMES in the GW configuration are
| CASE SENSITIVE but, SNA NAMES (LU names, PU names,
| link names etc) are not.
|
| 5. 05/26/93 If "2B?" or "2B " is received in the OIA
| of the downstream workstations then check
| the following:
| -That link between the SNA Gateway
| and the host is active.
| -That if the workstation is explicitly defined, and
| the LAN Destination Address is specified,
| then make sure the local address of the
| downstream workstation matches the defined
| address in the SNA Gateway.
| -That the NAU addresses match between the
| downstream workstation configuration and the
| SNA Gateway workstation configuration.
|
|MISCELLANEOUS PROBLEMS
|
| 1. 05/26/93 Various Symptoms on Downstream Token-Ring
| workstations attached to the SNA Gateway.
| -COMM695 on Downstream Workstations.
| -ACS1231 on Downstream Workstations.
| -XID failure
| -Only some Downstream Workstations Connect.
| -RANDOM COMM695 on Downstream Workstations.
| -Message LT20030 on the SNA Gateway Workstation
| in the LANTRAN.LOG.
| -Cannot establish sessions with more than
| a certain or set number of workstations.
| On the SNA GATEWAY workstation, change
| the following configuration items for the
| Token-ring card connecting the Downstream
| workstations:
| - Use the REFERENCE DISKETTE and set the
| Token-Ring card to use a shared RAM SIZE
| OF 64K, If the workstation is not
| executing LAN Server via this Card.
| - In the configuration for the Token-Ring
| Data Link Control increase the max number
| of link stations from to 128.
| - In the configuration for the LAN Adapter
| and Protocol support, make sure the Max.
| number of link stations is 255.
| - In the LAN adapter and protocol support (LAPS)
| IEEE 802.2 profile increase the Timer Control
| Blocks setting to 128.
|
| 2. 05/26/93 If the GATEWAY reports an error, it will be
| logged in the OS2 SYSTEM OS2MLOG.DAT. Reference
| II06915 Finding the cause of problems when using
| Communications Manager/2.
| Types of messages logged are
| o Negative responses to an ACTPU/DACTPU, BIND/UNBIND,
| or NOTIFY.
| o Frame out of sequence.
| o Workstation requests an ACTPU, but no associated
| definition for it.
|
| 3. 05/26/93 Message ACS2008 (the gateway is unable to
| create a session) can be logged when nothing is wrong.
| (This does not apply to Communications Manager/2 1.0
| at WR06050.)
|
| 4. 05/26/93 If you are having problems with Alerts not
| getting to NETVIEW, please review the Management
| Services information APAR II06895.
|
|SNA GATEWAY APARS RESOLVED IN WR06050
|
| 1. 05/26/93 JR06942 Does not produce a distinct
| message indicating that the maximum number of
| link stations defined have been exceeded.
|
| 2. 05/26/93 JR07121 The SSCP-PU session between VTAM
| and a SNA Gateway is taking longer than expected.
|
| 3. 05/26/93 JR07123 Downstream workstations unable to
| re-connect to ES/1 server after a link failure.
|
| 4. 05/26/93 JR07126 SNA Gateway does not reactivate the
| DLC after VTAM is recycled.
|
| 5. 05/26/93 JR07128 On X25 NETWORK, Generates call
| indefinitely responding to clear 00.
| No way to eliminate or stop the retries.
|
|ADDITIONAL READING
|
|There are several books that can be ordered separately
|which provides additional planning and installation
|information.
|
| 1. 05/26/93 Host Connection Reference, SC316170.
| Contains parameter matching and sample system
| generations for connections to System 370 and
| OS/400 hosts.
|
| 2. 05/26/93 Scenarios, SC316174.
| Contains sample scenarios with steps to install
| and configure several types of networks with
| attached workstations.
|
|
+-------------------------------------------------------------+
|KEYWORDS: CMINFO 562125400 R100 MPU |
| GATEWAY SNAGATE COMM695 COM695 COM 695 |
| WORKSTATIONS NOT CONNECTING. |
| ACS1231 MSGACS1231 CM2INFO |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II07003 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| Installing Communications Manager/2 1.0 |
| |
| Tips, Techniques, Questions and Answers |
| |
|LAST UPDATE: 05/25/93 BY: RHB |
| |
+-------------------------------------------------------------+
|
|A. The following information is applicable to
| SYSLEVEL WR06000, and WR06050.
|
| 1. 05/25/93 README Highlites:
| This file contains last minute information and corrections
| to publications which were discovered after the
| publications had been printed. It also contains technical
| information about restrictions, compatibility, and
| coexistence with other products.
|
| You can find the "README" file on diskette 1.
| or once installed you can select the README
| ICON from the Communications Manager/2 Folder to
| review this on-line.
|
| SOME OF THE TOPICS DISCUSSED ARE:
| Access to Extended Services Icons
| AS/400 PC Support Text Assist feature
| Compatibility and Coexistence
| Disk Space Requirements
| Enhancements
| Extended Services Database Manager
| Hints and Tips
| Installation
| Installing from CD-ROM or Optical Disks
| ISDN Users and NTS/2
| Optimal Error Reporting
| PNA
| Prerequisite Product Fixes
| Productivity Aids
| Programmatic Configuration
| Restrictions
| Upgrading from Extended Edition 1.3 or Extended Services
|
| 2. 05/25/93 Quick Installation
| The Communications Manager/2 package contains a
| Quick Installation Card, SX75008500. Reference this
| information to quickly install and setup
| 3270 or 5250 terminal emulation sessions.
|
| 3. 05/25/93 Installation information
| The Communications Manager/2 package contains
| the following publications to assist you when
| installing and configuring Communications Manager/2:
| Start Here, SC31610400
| Workstation Installation Guide, SC31616900
|
| 4. 05/25/93 LAPS or NTS/2 is required.
| If you plan to install Communications Manager/2
| on a Local Area Network (LAN), or if you are
| using integrated services digital network (ISDN)
| then LAN Adapter and Protocal Support (LAPS) is
| required. The level of LAPS shipped with
| Network Transport Services/2 (NTS/2)
| Version 1.0 or LAN Server Version 3.0
| is recommended; however Communications
| Manager also supports the levels of LAPS
| available with LAN Server Version 2.0 and Extended
| Services for OS/2.
| Reference: Communications Manager/2 Workstation
| Installation Guide Version 1.0, SC31616900
| under Upgrade Considerations.
|
|
| 5. 05/25/93 OS/2 BASE PREREQUISITE PRODUCT FIXES
| If you are using OS/2 2.0 with the Service Pak applied,
| OS/2 Base APAR PJ06671 should be applied.
|
| Otherwise:
|
| - The Communications Manager Setup ( CMSETUP )
| and Keyboard REMAP push buttons may not work and
| the CMSETUP graphic displays (METAFILES)
| may not be displayed. Unexpected return code
| from WMS (Window Management System) messages
| and other various messages are produced.
|
| - A possible system hang condition may occur
| after issuing the CMSETUP command when
| the following options are chosen: After
| issuing the CMSETUP command using
| Communications Manager/2, the
| COMMUNICATIONS MANAGER CONFIGURATION
| DEFINITION window appears. At this window
| a WORKSTATION CONNECTION TYPE and a FEATURE OR
| APPLICATION is entered. The error occurs here when
| the system clock appears and stops but the screen does
| not change and you cannot go any further.
|
|
|
| 6. 05/25/93 OTHER PREREQUISITE PRODUCT FIXES
|
| - ISDN users who are using NTS/2 must apply the fix for
| NTS/2 APAR IC04997.
|
| - Coexistence with PNA requires the application of
| the fix provided as a part of the PNA APAR IC04781.
| Without this fix, Communications Manager/2 will report
| a command syntax error.
|
| 7. 05/25/93 Corrupted or Missing Group Boxes, ICONs or Folders
| Use Communications Manager/2's CMSETUP command or
| select the SETUP ICON in the Communications Manager/2
| Folder, select OPTIONS, then RECREATE FOLDERS
| This rebuilds all group box, or folder
| entries for all features and functions installed
| on the workstation. If you have moved icons
| to other folders, they will be recreated in the
| Communications Manager/2 folder. If you deleted
| the folder it will be recreated.
|
| 8. 05/25/93 Lost or corrupted Communications Manager/2
| CONFIG.SYS entries.
| Use Communications Manager/2's CMSETUP command or
| select the SETUP ICON in the Communications Manager/2
| Folder, select INSTALL, then select the correct
| directory and configuration file to
| reinstall the same configuration. This will reset
| the CONFIG.SYS entries. This updates PATH, DPATH
| and LIBPATH statements in CONFIG.SYS. It will also
| add all necessary device drivers to support the default
| configuration and any installed additional functions.
| UPM and FFST/2 statements are only updated when
| executing CMSETUP from the diskette or
| diskette images.
|
|
| 9. 05/25/93 Reinstalling OS/2 when Communications Manager/2
| is already installed
| OS/2 install will not retain all Communications
| Manager/2 CONFIG.SYS entries.
| The PATH, DPATH, and LIBPATH will be retained.
| The device drivers will NOT be retained,
| but will be commented out (REM ...).
| Reinstalling the same Communications Manager/2
| configuration will restore CONFIG.SYS, etc.
| UPM and FFST/2 statements are only updated when
| executing CMSETUP from the diskette or
| diskette images.
|
|10. 05/25/93 FFST/2 and UPM
| If FFST/2 SYSLEVEL says a newer version of FFST is on
| the workstation Communications Manager/2 1.0 will NOT
| install FFST/2. If UPM (User Profile Management) SYSLEVEL
| says a newer version of UPM is on the workstation
| Communications Manager/2 1.0 will NOT install UPM.
| Communications Manager/2 will use the newer
| versions that are already installed.
|
|11. 05/25/93 XCOPY or COPY *.* of files from an Installed
| Communications Manager/2 will fail.
| Communications Manager/2 must be installed
| using Communications Manager/2's CMSETUP command or
| selecting the SETUP ICON in Communications Manager/2's
| Folder, selecting INSTALL.
| You can install Communications Manager from a
| redirected drive. Reference Communications
| Manager/2 Network Administration and
| Subsystem Management Guide, SC31616800,
| under "Communications Manager Configuration
| Methods" in Chapter 1.
|
|
|12. 05/25/93 .CF2 file cannot be found when upgrading from
| Communications Manager Extended Services
| This can occur during CMSETUP processing when the
| diskette containing the ES 1.0 Communications Manager
| configuration does not contain the .CF2 file. To
| upgrade you will need the following Communications
| Manager ES 1.0 files from the following ES 1.0
| directories
| CMLIB <your>.cfg
| CMLIB APPN <your>.CF2
| CMLIB APPN <your>.NDF
| CMLIB APPN <your>.SEC
|
| This can also occur when trying to use an
| ES 1.0 Communications Manager
| configuration to upgrade to Communications
| Manager/2 1.0, but install Communications Manager/2 1.0
| on a different drive than where ES 1.0 Communications
| Manager was installed. Communications Manager/2 1.0
| requires that all the configuration files be located
| in the same directory on the ES 1.0 Communications
| Manager, copy:
| CMLIB APPN <your>.CF2 to CMLIB *.*
| CMLIB APPN <your>.NDF to CMLIB *.*
| CMLIB APPN <your>.SEC to CMLIB *.*
| This is not a problem when installing Communications
| Manager/2 1.0 on the same drive over ES 1.0 Communications
| Manager, because Communications Manager/2 1.0 Install
| collapses the ES 1.0 Communications Manager APPN
| sub-directory into CMLIB.
|
|B. The following information is applicable only to
| SYSLEVEL WR06000.
|
| 1. 05/25/93 Installing Communications Manager/2 with
| less than 32K free on the boot drive.
| This will return you to the command line
| with no messages displayed and no messages
| logged. You will need to free enough space
| on the boot drive for Communications
| Manager to install. Reference the README file on
| diskette one for more information.
|
| 2. 05/25/93 Missing DLL when attempting to use REINST to
| add or remove ES 1.0 Database Manager.
| The update to REINST was not installed.
| This update is only applied when you install
| a configuration. Therefore, running CMSETUP from
| diskette, selecting Close on the main window,
| selecting YES to install the setup code, will NOT
| install the REINST update. The REINST update will be
| installed when the first configuration is installed.
| Consult the README on diskette 1 under
| "Extended Services Database Manager".
|
+-------------------------------------------------------------+
|KEYWORDS: CM2INFO CMINFO 562125400 100 |
| INSTALL INSTALLATION CMSETUP |
| PCSUPPORT |
| |
| |
| |
+-------------------------------------------------------------+
+-------------------------------------------------------------+
| II07005 |
| COMMUNICATIONS MANAGER/2 1.0 562125400 |
| |
| SDLC |
| |
| Tips, Techniques, Questions and Answers |
| |
|LAST UPDATE: 05/26/93 BY: TLG |
| |
+-------------------------------------------------------------+
|
| 1. 05/26/93 AS/400 to Communications Manager/2 using SDLC
| for 5250WSF on a MULTIDROP TRIBUTARY LEASED
| NON-SWITCHED line.
|
| When connecting in this manner,
|
| You must choose: Line type Non-Switched
| Link station role Secondary
|
| and for ADDITIONAL PARAMETERS...MODEM PARAMETERS
| LINE MODE Half-duplex.
|
| When using a MODEM SHARE DEVICE you must also change
| the device driver entry in CONFIG.SYS to use
| the #Y parameter.
|
| Example: DEVICE=C: CMLIB SDLCDD.SYS #Y
|
| One of the symptoms is that when SDLC is setup
| as FULL DUPLEX, none of the other devices on the
| multi drop line can get a poll and will be hung.
|
| You may also see the following message
| ACS2363 ALERT: The local node has detected
| an inactive link condition and has deactivated
| the SDLC communication link.
|
| When LINE MODE Half-duplex is used, it allows Line
| Turnaround to occur and will toggle the RTS line to
| allow other stations to communicate.
| When LINE MODE Full-duplex is used. Request To Send
| will stay high all the time and no other
| devices will communicate.
|
| The SDLC adapter and MPCA adapter supported by
| Communications Manager/2 do not support
| full-duplex data transfer. However, by
| selecting Full-duplex, an SDLC adapter can be configured
| to operate efficiently on a full-duplex line. If the
| line is full-duplex and is multi point or multi drop,
| you must set up Communications Manager/2
| MODEM PARAMETERS LINE MODE
+-------------------------------------------------------------+
|KEYWORDS: CM2INFO CMINFO 562125400 0964137 100 |
| SDLC AS/400 5250EM MULTIDROP LEASED |
| AS400 CM CM2 OS/400 DLC FULL DUPLEX MULTIPLE |
| POINT DROP |
| |
+-------------------------------------------------------------+
Communications Manager/2 APARs
------------------------------
The following Communications Manager/2 APARs have been written since the initial
release of the product and are corrected in this version.
JR06865: ACS2454 While TP1/TP2 Running Over X.25 Using ISDN
While TP1/TP2 is running over ISDN X.25 D-channel, TP2 machine stops and
displays alert "ACS2454: X.25 line failure". The X.25 physical link status on
SSM is changed to "Error Level 2".
JR06941: Trap 000D Occurs at the Re-activate SNA Logical Link
A trap 000D may occur at X25DD.SYS when the SNA logical link is re-activated.
JR06881: Trap 000D Performing Host Redirected Print
A trap 000D (SYS1943) may occur while performing host redirected 3270 print.
JR06982: NAU Address Values Modified
When upgrading a configuration during install, upgrading a configuration after
installation, or modifying a current configuration, the values of the NAU
addresses for non-DFT 3270 terminal emulation sessions MAY be changed to
arbitrary values.
JR06992: Cannot Open COM Port
Cannot open COM Port when configuration file name is 8 characters or more.
Symptoms include: ACS3138E, ACS3138, 00000022, 0022, 0000108d.
JR06994: Activatable_on_Demand Link not Updated
If an activatable_on_demand link (link defined with activate_at_startup(no)
and adjacent_node_type(LEARN)) is activated between two Communications Manager
NNs, then the topology database is properly updated to show that CP-CP sessions
are active. However, when the link is deactivated, the topology database is
not updated to show that there are no longer CP-CP sessions between these two
NNs on this link.
JR07004: Code Page Field in 3270 Emulator Not Updated
Changing to a user defined code page for 3270 in advanced configuration works
correctly but the display continues to show 037 (the default).
JR07008: SYS3175 Saving New REMAP 122 Key Keyboard
Hang and SYS3175 in ACS3EMCF.DLL while attempting to save new remap of 122 key
keyboard profile.
JR07019: Unpack Function for the *.H Files Fails
The Communications Manager Samples diskette contains header (*.H) files that
use externalized API's. The unpack function for the *.H files fails.
JR07034: ACS0608W, 0653W, 3100E for 5250 Printer Session
Communications Manager 5250 printer session do notalways come up and the
following messages are issued:
ACS0608W, ACS0653W, and ACS3100E
Communications Manager is imbedding nulls in the Message Queue and Message
library fields if the names are not the defaults of QSYSOPR and *LIBL or the
names do not completely fill the field.
JR07037: SYS3175 in CMINST.DLL During Install
SYS3175 trap can occur in CMINST.DLL during installation. The error occurs
during processing of Diskette 1. A program generated an access violation at
1510f1cd CMINST.DLL 0003:08a4c4ab.
JR07044: Empty OS/2 Window When Communications Manager Started
When Communications Manager is started an empty OS/2 window is created that is
entitled "Communications Manager". This is an extraneous window. Closing it
can result in terminating emulator sessions or other unpredictable results.
This does not occur on all systems.
JR07046: 3270 Emulation Fails for 24x80 Mode
When 3270 device emulation, STREML3270, is started from a 5250 logical terminal
session which is configured as 24x80 mode, the AS/400 displays an error message
and terminates the 3270 device emulation.
JR07047: S/36 Subconsole Mode Not Working in Communications Manager 5250
Communications Manager/2 5250 emulator S/36 LT session cannot enter subconsole
mode even if the session is specified as a subconsole of a S/36 LP session.
JR07056: Changes on Emulator Print Control Panel Don't Work in Real Time
After starting a 5250 LP session, changes on the Emulator Print Control window,
such as "Spooler Queue Name" and "Job Change Prompt Level", do not take effect
immediately.
JR07073: During Keyboard Remap, Using <ALT> and Digits on Number Pad Gives
Incorrect Results
During Keyboard Remap, directly entering ASCII characters by using the <ALT>
key in combination with the number pad on the keyboard is not working
correctly.
JR07099: Alt + Home Key Combination (PA2) is not Working Correctly
When rapidly pressing the Alt + Home key combination (PA2) many times,
intermittently the PA2 AID code does not get sent to the host. The PA2 always
gets sent if the Alt key is held down while hitting the Home key, but if the
Alt key is released, the next Alt + Home key sequence may not send a PA2.
JR07085: Activatable_on_Demand Link Reported Incorrectly
If a link is defined as an activatable_on_demand link (with
activate_at_startup=NO and fq_adjacent_node_type=LEN or NN) and is also defined
as CP_CP_SESS_SUPPORT=YES, this link is being reported in the Local Topology
sent to the MDS MU Agent as supporting CP-CP sessions. It should not since
this link is inactive and cannot support CP-CP sessions until it is active.
JR07086: Incorrect Key Response from AS/400 Error Hangs Session
Using an AS/400 CASE development tool, a system generated error message was
received on the 5250WSF terminal requesting that you press Reset (Ctrl key) to
exit the error. If Reset is pressed, processing continues without problems but
if any key other than Reset is depressed, the session hangs.
JR07088: EHLLAPI Send Key (3) Receives RC9 When System Request (@A@H) is Sent
on 5250WSF Session
When SYSTEM REQUEST (@A@H) is sent with EHLLAPI SEND KEY function 3 in a
5250WSF session, a return code of 9 is received and messages ACS3209 and
00000042 00000500 are logged.
JR07103: Communications Manager Gateway Sends ACTLU Cold in Error
The SNA Gateway sends out ACTLU(cold)s at startup to all downstream
workstations. This message is no longer supported. As a result, SNA AIX
rejects ACTLU with a Sense Code of X'08350001' which points to the ACTLU type
field, which is X'02' for ERP and X'01' for cold.
JR07115: Copy_PS Does not Return Blanks for Field Attributes
COPY_PS does not return blanks for field attributes when the session type is
5250 logical terminal and set session parms is NOATTRIB. It should be blanks
for field attribute positions.
JR07147: Trap 000D in RPSMAIN Running CMSETUP
Using CMSETUP "Features" can cause a Trap 000D if links are viewed and not
changed. After this is encountered the resulting configuration file will cause
the verify process to trap as well.
JR07148: SDLC LINK Doesn't Reactivate
Starting Communications Manager and activating SDLC links works with no
problems. However, inactivating the link and trying to reactivate again
through Subsystem Management causes the link goes into a PENDING ACTIVE state
and stay there indefinitely.
JR07149: Trap in Twinax Driver
Twinax adapter initializes but when the emulator begins, the Twinax DLC begins
sending messages that the DLC cannot connect because the cable is loose or not
connected. When enter is pressed to remove the error message, the machine
locks up.
JR07150: NLS Translation Table Files Packed Incorrectly
The host translation table files, *.mod in the ZIP, are not packed correctly.
They do not unpack correctly when uploaded to the host.
JR07151: Trap 000D in Gateway While Deactivating
Trap 000D received in gateway while deactivating the host links from the
gateway after NCP abends.
JR07169: ACS2386 - MDS_MU Data Not Being Logged
When message ACS2386 is received on the startup of gateway configuration, the
message indicates that the local SNA received unsupported Network Management
data but there is no way to debug the problem since the data is not logged.
JR07181: Error X'0020', x'00000008' Missing from Common Services
Major error codes of '0020' are 'ATTACH_REJECTED' errors originated in APPC.
The error code is issued when an ATTACH is received for a
Queued_Operator_Preloaded transaction program that has not been started.
Common Services does not log a message when 0020-00000008 return code is
received.
Communications Manager/2 Sysroute APARs
---------------------------------------
The following APARS are sysroutes of problems reported on previous releases (ES,
EE 1.3), which were not fixed in the initial release of Communications
Manager/2. These problems have been corrected.
JR06942: No Message When Link Stations Exceeded
Communications Manager does not produce a distinct message indicating that the
maximum number of link stations defined has been exceeded. The problem
normally occurs when a downstream workstation tries to access the host thru a
Communications Manager SNA Gateway. The Communications Manager SNA Gateway
machine is out of link stations therefore the downstream workstation cannot
connect to the host.
JR07063: Message ACS0619 Not Explained in SC31-6159
Message ACS0619 reports CNOS return code 0017 00000000. This is not explained
in the Message Reference, SC31-6159. Text should be as follows under the User
Response section: 0017-00000000 - APPC is currently processing a CNOS verb
issued by a local LU. Retry the CNOS verb after a short delay.
JR07116: Communications Manager Not Accepting All Characters
Communications Manager does not accept $, @, #, or period for userid or
password on the 'Creating Program Security - Configname' window. All
characters listed in the help should be accepted.
JR07117: TRANS026 Using File Transfer Panel
TRANS026 occurs when trying to receive a file from the host using the File
Transfer window. There is no problem when using the RECEIVE command. The
problem occurs if OS/2 is installed on any drive other than drive C.
JR07118: Communications Manager Send Unbind With Sense Code 2004
Communications Manager incorrectly issues an UNBIND with sense type 2004 which
indicates that it received an RU of data while in send state. There is no
indication that the send/receive indicator is set to return to the workstation.
JR07119: SYS3175 If No Define_Defaults Verb in .NDF
A call to APPNUTL.DLL to do a Compare_Field traps and results in SYS3175. The
APPNUTL call was from RDSLAN.DLL (used when SQLL00 is the mode used by
Database Manager).
JR07120: SYS3175 Using Non-Supported Font
If 5250WSF receives an unsupported font, message SYS3175 is issued, the AS/400
job ends, and the AS/400 device descriptions get damaged and must be recreated.
The 5250WSF printer was emulating a 5219 with PFT4019.
JR07121: Response Delay for SSCP-PU Session
The SSCP-PU session between VTAM and a Communications Manager Gateway is taking
longer than expected even with the #Y coded on the SDLC device driver
statement. The #Y statement on CONFIG.SYS responds the same way on a link in
"contacted" state as it does when the link is initially brought up. With #Y,
the first XID is still ignored as if the #Y was not there in a "contacted"
state.
JR07122: CP-CP Sessions Deactivated During TDU Processing
CP-CP session between NNs are being unbound. This is happening during TDU
processing. The TDU TP is suspended waiting for an IPM so that it can send the
TDU GDS variable. The link goes down, but the entry on the timeout list is not
removed. When the link is reactivated and the CP-CP sessions are restarted,
the presence of the TP on the timeout list is causing the CP-CP sessions to be
deactivated.
JR07123: Re-Connect Fails to ES/1 Server After Link Failure
Communications Manager/2 Database server not responding properly to a
null XID when the link is supposedly in a contacted state. The
server should respond with a non-activation XID to the null server
should respond with a non-activation XID to the null XID with sense
data.
JR07124: Sense Code 10030023 Not Forwarded by Communications Manager
Sense code of X'10030023' was received in the Locate GDS variable of a
LOCATE_REPLY. This is not forwarded on the LOCATE GDS variable sent to the
originating CP of the LOCATE because it is not in the list of expected return
codes for LOCATE processing. This hangs the session that issued the LOCATE.
JR07125: SYS3175 When Upgrading and Using Display-Verb
When upgrading an EE 1.3 or ES configuration to Communications Manager/2, the
system may crash with a memory fault when Display_Verb is used. Symptoms
include message SYS3175 and Trap 000D. Some of the parameter values other than
MAX_NEGOTIABLE_SESSION_LIMIT are being changed.
JR07126: DLC Not Reactivated after VTAM is Recycled
The Communications Manager SNA Gateway workstation is attached upstream via
token ring to NCP then VTAM, and downstream to Token-ring workstations. The
Communications Manager SNA Gateway does not re-establish connections with VTAM
even though on the CM SNA Gateway workstation a 3270 emulator session is
defined via the upstream connection to reactivate the DLC Layer when VTAM is
recycled.
JR07127: 5250WSF Hang Running TWINAX to AS/400
5250WSF hangs while using various AS/400 functions. Failure occurs while using
the PF4 key (PROMPT) within System Editor Utility (SEU) only on workstations
using the ISA BUS and with the TWINAX APAR JR06476 applied.
JR07128: No Retry Limit Set if CLEAR 00 From X25 Network
On X25 network (SVC) sends continuous CALL without any possibilities to set a
retry limit. If for any reason the host comes down (hardware trouble, etc.),
the Gateway receives a CLEAR from TRANSPAC (SVC circuit) then Communications
Manager issues a CALL to the host. As the request can not be delivered to its
destination, TRANSPAC sends a CLEAR 00 to the Gateway and Communications
Manager reissues a CALL.
JR07129: Communications Manager Workstations Losing Connection with DBM Server
Communications Manager workstation users periodically lose contact with the
Database server workstation after they were previously in session with the
database from a Communications Manager application. The Communications Manager
workstation received ACS1231, ACS0619 and, Error 001B Subtype 00000700. The
problem occurs when Communications Manager is trying to drive up the link with
a XID null. Communications Manager receives an XID3 with SNA sense 0809003A
(causing the 001B 00000700).
JR07130: BCH0001 (RC=1) Running Programmable Config Cmd File
Running programmable configuration command file results in BCH0001 message
(return code = 1). The FILE ADD fails with the following in the MYCONFIG.LG:
Job MYCONFIG Processing Has Started.
BCH0001: File Add MYCONFIG.INI
The file MYCONFIG.INI was not found.
JR07131: Sense Code 08390004 During Topology DB Update
CP-CP sessions go away due to unbind flowing with Sense Code 08390004
indicating that a node did not respond within a given timeout period while a CP
architected TP was in operation. There was a topology DB update going on at
the time of the failure. When CP-CP sessions are activated, they either fail
to come up or one or both links go away. The link remains active, but with
both CP-CP sessions gone.
JR07132: SLI-CLOSE or RUI-TERM Fails to Complete
A SLI-CLOSE or RUI_TERM verb issued by an LUA application following an SNA
protocol violation committed by the Primary Logical Unit fails to complete.
The customer must stop the LUA application and restart it. It may be necessary
to reboot the workstation.
JR07133: PC Does Not Provide UPM Checkmark
Programmable Config does not provide the local security option to use UPM.
This function was provided in EE 1.3 in the Batch Utility function, but was not
ported to Extended Services Programmable Configuration.
JR07134: PC for 802.2 Adds NETBEUI Section in Error
If Programmable Configuration is used to configure 802.2 then a NETBEUI section
is also added to the PROTOCOL.INI though it should not be. All the keywords in
the NETBEUI section are ending with just the = character (no parameters).
After doing a REINST with this PROTOCOL.INI, the DEVICE= statements are added
to CONFIG.SYS, but the device drivers are not copied to the system. This
results in not found messages for the device drivers when the system is booted.
JR07135: Large File Transfer Using NvDM/2 Hangs
When transferring a large file from NvDM/2 to NvDM on the Host using
Communications Manager, the file transfer stops after having transferred about
1MB of data. The RU size does not seem to matter. This is observed using
adaptive pacing between Communications Manager and NCP. One of the
contributing factors is the window size given by NCP to Communications Manager.
Additional symptoms include: slow response time, link outages, sessions lost,
one Communications Manager waiting on an IPM from another Communications
Manager that is waiting on an available frame to respond to the IPM,
Communications Manager waiting on an available frame to respond to an IPM, and
unable to send large file (1meg+) from the NvDM/2 node to the host after
installing Release 4 at the host and XR20249 on the PC.
JR07136: SYS3175, Trap 000D Upgrading Config File
Upgrade of an EE 1.3 configuration file via the advanced configuration windows
may result in SYS3175 Trap 000D. The trap indicates a problem in APPNUTL.DLL
with CS:EIP=B187:00001271 CSLIM=00002EB2.
JR07137: Data Segments Not Freed Properly
APPC, which processes the Display Verb that Subsystem in Communications Manager
uses, does not free a data segment that is passed to it on the Display Verb
until the process that passes that segment is terminated (this processing is
done by APPC.DLL in the ExitList of the process). Therefore, Communications
Manager should re-use the same data segment for Subsystem Management rather
than to allocate a new one each time. Not doing this causes Communications
Manager to waste 64K of data every time that Subsystem Management is exited
since the 64K segment is not re-used.
JR07138: Pointer not Set Causes Trap 000D in PSPOST
Running an application that is running several conversations from a single TP
(the conversations shared a single TP_ID), each conversation has a session to
a different machine. Two of the conversations had last issued a
MC_Receive_and_Post verb; one had last issued a MC_Send_Data verb. All the
data had been sent, but the verb had not been posted. One of the conversations
receives a Change Direction indicator. It has not yet posted. The problem
occurs when the post processing for the send verb is started. Trap occurs in
PSPOST processing in APPC.DLL.
JR07139: WS Binds as MOD2 but Acts Like MOD5
Running a CICS transaction which performs DYNAMIC QUERY to determine the
presentation space size of the workstation, the workstation is configured as a
MOD5, bound as a MOD2, but acts as a MOD5 instead of a MOD2.
JR07140: RC24 for EHLLAPI Search Presentation Space
Search presentation space (6) fails with return code 24 (the search string was
not found) running sample program HLLSAMP. On PC/3270 a string containing
blanks or nulls as the match string is found when doing a Search_PS(6) call but
the same string on Communications Manager/2 is not found.
JR07141: Updates to PS or OIA Not Sent
DOS PC/3270 sends the data to the EHLLAPI application for every update on the
PS or OIA (Host update or Terminal update), but Communications Manager
Query_Host_Update EHLLAPI commands send the data to the EHLLAPI application for
updates on the PS or OIA to the host only.
JR07142: Incorrect Return Code for PS Update
When an Erase Write command and WCC is sent from the host system without any
data or orders, the return code of EHLLAPI QUERY HOST UPDATE function becomes
RC=21. The return code should be RC=23 reflecting the PS (Presentation Space)
update.
JR07143: EHLLAPI Connect to PS Fails With RC=9
EHLLAPI application issues Connect to PS and fails with RC=9 and the trace
shows Error Type: 0042 Subtime: 00000500. CONNECT_PS sends @S@T and @J to
set focus when session parms are selected as CONPHYS but when it is rejected
due to host_busy it returns RC=9 instead of RC=4.
JR07144: RC=9 Returned Against To Copy PS(5)
Running the EHLLAPI application, CM3270 emulator token ring sessions are
disconnected. The EHLLAPI return code is 9 (system error).
JR07145: 3270 Print Control Hangs and Traps
SYS3175 or trap in ACS3ETQ.DLL while performing Host Print and hangs may occur
with following symptoms: 3270 Print Control shows STARTED but no files are
sent or 3270 Print Control shows STARTED yet Host Print files are queued on the
Host waiting to be sent.
JR07155: IKT00405I for 3270EM Session With Geomanager
IKT00405I screen erasure caused by error recovery procedure. This message is
issued when in Communications Manager 3270 emulator session to an application
via VTAM, TSO, and GDDM. Communications Manager rejects the PIU with sense
code x'1003'. The PIU contains an outbound 3270 data stream which is correctly
built.
JR07158: Free Unused Link Parm Default Incorrect
Communications Manager CID install uses the default (ACSCFGUS) configuration
file as the model configuration. This model does not contain a Token Ring DLC
profile and the customer's CID response file did not contain the FREE_LINK
keyword. This causes Communications Manager CID to default the free unused
link parm of the output DLC profile to YES when it should have been NO.
JR07159: Incorrect Output for OS/2-5250 SDA Created Screen
When S/36 sends SNA SIGNAL command (Request to Send), 5250WSF will not send
back Change Direction (DC) to the S/36 until the user presses an AID key.
JR07160: SYS3175 Trap When Formatting an LUA Trace
SYS3175 trap in FMTTRACE.EXE when formatting an LUA trace because of length
check error.
JR07164: Print Data Not Divided with Host Send Data With Brackets
Print data is not divided in spite of host send data with brackets. The
problem is caused by logical printer (LP) base code. CM3270 LP cannot handle
SPOOLER_CLOSE when print data + EB (end bracket) is sent from the host after
QUERY_REPLY is sent for QUERY command + BB (begin bracket).
JR07165: No Vertical Scroll Bar Provided for MOD5 Session
Using XGA monitor as MOD5 with font size of 30 x 128 under 3270 emulation,
doesn not provide vertical scroll bar. Additional symptoms: Using MOD5 and a
font size of 30 x 128 when 3270 emulator window is maximized there are lines
missing even though there are less than 30 lines to display.
JR07166: Extra Blank Lines Added to 3270 Hostprint
On a hostprint job directed by CICS to a 3270 non-DFT printer session,
hostprint emulation adds several lines of spaces where there should be only one
line of space.
JR07168: Host Print Fails After INFOPAK Job Prints
Host directed print fails after printing from INFOPAK. Various host jobs can
be printed (CICS, NETPASS, INFOPAK, etc.), but print jobs fail following an
INFOPAK job. Error and message logs are empty.
JR07177: Problems Printing Using GPI Mechanisms
When a line being processed is longer than what can be held in the buffer
(maximum length = 200), a buffer overflow can occur wiping out data. Symptoms
include corruption of print spooler files, and multiple page ejects within a
job.
May 1993.
