IC82520: PCOM: PCSBAT HANG STARING SESSIONS ON WINDOWS 7

Personal Communications 6.0.5

APAR status

• Closed as program error.

Error description

• PCOM 6.0.2 on Win7 32bit running JAWS or MAGIC software. When
  the user logs onto Windows and launches a BAT file that starts
  PCOM sessions it just hangs.
  
  Task Manager shows PCSBAT.EXE running but no emulator sessions
  ever appear on the desktop. Killing PCSBAT and re-running the
  batch file will usually get sessions started.
  
  PCOMSTOP /ALL is used to end sessions on these machines and some
  times all the processes do not terminate successfully so this
  can also cause PCSBAT to hang.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of BCH (pcsbat) multiple session   *
  *                 startup feature.                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Intermittent hang of pcsbat.exe when    *
  *                      starting multiple session.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  User launches a BCH file (pcsbat) to start PCOMM sessions and
  uses "PCOMSTOP /ALL" or Exit All to close the sessions. The
  hang error will occur intermittently either during close of
  the sessions or restart of the BCH sessions.
  
  Task Manager sometimes will show pcscm.exe process alone
  without any pcsws.exe process.
  
  The error is caused by failing to terminate a 3270 TSO printer
  session normally so the start session hang problem is actually
  caused by the previous abnormal termination.
  
  The hang of PCOMSTOP is caused by the API call to terminate
  sessions going into a endless loop waiting for the TSO printer
  session that does not terminate normally.
  
  The hang of Exit All is also caused by abnormal termination of
  the TSO printer session but it was trapped in PCSWS.
  

Problem conclusion

• PCSTLNET.DLL has been changed to close the TSO printer session
  normally. PCSWSAPI.DLL and PCSAPI32.DLL have been changed to
  check for and kill a stand-alone pcscm.exe process during
  PCOMSTOP /ALL function. PCSWS.EXE has been changed to check for
  and kill a stand-alone pcscm.exe process duing Exit All
  function. PCSBAT.EXE and PCSCW.DLL have been changed to work
  with these new session start and terminate functions.
  
  Fix scheduled for PCOM 6.0.5 Refresh Pack
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• PCSAPI32 PCSBAT   PCSCW    PCSTLNET PCSWS    PCSWSAPI
  

Fix information

• Fixed component name

  PCOMM V5 COMBO-

• Fixed component ID

  5639I7000

Applicable component levels

• R601 PSY

     UP