Jump to content


Click the link below to see the new game I'm developing!


Photo
- - - - -

Minor Bus & Tasks bug


1 reply to this topic

#1 Rick Young

Rick Young

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 266 posts
  • Gender:Male
  • Location:Guelph, Canada

Posted 11 March 2005 - 03:15 PM

Track ID:
Kernel Version: 5.5r411
Platform: HP-UX 11

It appears that a Task will not accept @LFUNCT = $VARNAME.

Example:
Have a Task which ends in a Report function, that is used as a normal part of our system (i.e. non Bus & Tasks).
Logic: @LFUNCT = @$COM1(20,27)

Causes p4task to crash:
Error 51: p4ExecTask: EXEC 'TK_CREATE_SALES_ORDER' returned non-zero kernel status -1, reason 5, sub-error 102

p4ExecTask failed: Last Error 51, StatusCode -1, FailReason 5, SubError 102



Added the logic:
IF @$COM1(20,27) = 'BUS99' THEN @LFUNCT = 'BUS999';

#2 Joseph Bove

Joseph Bove

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 756 posts
  • Gender:Male
  • Location:Ramsey, United States

Posted 18 March 2005 - 05:53 PM

Rick,

You may want to try @LFUNCT = RMTRAIL(@$COM10(20,27))

RMTRAIL is a global logic that we use to strip off trailing spaces. It's possible that BUS and TASKS is not differentiating between 'SUB99 ' and 'SUB99'

hth,

Joseph



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

Click the link below to see the new game I'm developing!