IT47351: PCOM 15.0.2 64BIT RUN1 STATEMENT IN BCH DOES NOT EXECUTE

APAR status

• Closed as program error.

Error description

• Using a BCH with 4 RunX statements like this:
  ....
  Run1=C:\Program Files\IBM\Personal Communications\pcsws.exe
  "SessionA.WS"
  Run2=C:\Program Files\IBM\Personal Communications\pcsws.exe
  "SessionB.WS"
  Run3=C:\Program Files\IBM\Personal Communications\pcsws.exe
  "SessionC.WS"
  Run4=C:\Program Files\IBM\Personal Communications\pcsws.exe
  "SessionD.WS"
  ....
  The Run1 statement does not function. If I change the group to
  Run2-Run5, all 4 sessions will start.
  

Local fix

• Do not use Run1 statement.
  

Problem summary

• If user creates the batch file from Session Manager, run1
  normally is occupied by a comment, but when the user manually
  creates the batch file, run1 also can be assigned to launch a
  session, and PComm code is not reading the run1 command as a
  session file path.
  

Problem conclusion

• PCSBAT.EXE code changes have been made to account the run1
  session path as valid to run entries in the batch file and
  launch all the sessions.
  

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:

Fix information

• Fixed component name

  PCOMM COMBO-ENG

• Fixed component ID

  5639I7000

Applicable component levels