PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 06/17/2020 10:36 AM by  LauraPat
Error setting up Multi-Step Job in Portal
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages
LauraPat
Sr. Application Engineer
Private
Advanced Member
(90 points)
Advanced Member
Posts:44


Send Message:

--
06/16/2020 8:22 AM

    I have never seen this one before.  Trying to set up a multi-step job using a custom batch program for the first step and a user token for the second step.  I constantly get the error - IllegalValue Exception: JobType:getValue(): Invalid value for job type - trying for the step with the custom program.  And it only happens in Portal - I can set up the job fine in LID.  I can set up a multi-step job using a Lawson-delivered program and the same user token from the job that errored - no errors.  I can set up a job using a DIFFERENT custom Lawson program and the same user token - no errors.  It is only with this one program.  I'm completely baffled why this is happening and as of right now so is Infor support.  Thanks in advance for any ideas!

    Ragu Raghavan
    Private
    Private
    Veteran Member
    (1117 points)
    Veteran Member
    Posts:389


    Send Message:

    --
    06/16/2020 9:21 AM
    What is the name of the custom program? Sometime back, I had a custom program called 501RQ. Worked fine in V9. Continued to work in V10 LID, but had issues in V10 Portal/Mingle. Looks like there was an undocumented limitation that the program name cannot start with a number. Changed in to XX501 and it worked fine.
    LauraPat
    Sr. Application Engineer
    Private
    Advanced Member
    (90 points)
    Advanced Member
    Posts:44


    Send Message:

    --
    06/16/2020 9:31 AM
    Interesting - but no, this one is BP635. I just remembered one other thing - I had the program all written, compiled, etc. No job set up yet. Test system crashed. No backup to restore from. The code for the program was still in the source library - but the pgmdef was gone. I had to go in and recreate the pgmdef and then compile the program. Then I tried to set up the job and started getting that error. I set up the job in LID without any issue so I continued to test that way. I then brought up the job in Portal (after it was set up in LID) and it worked fine so I just figured it was something stupid I did. Then everything was dumped/loaded from the test system to the prod system and now that error is rearing it's ugly head again. I'm wondering if something is "broken" because the test system crash and things being recreated manually. All of the GEN tables were lost. The sys admin was able to dump some from PROD, change the product lines in the files and then loaded to test. Others, like pgmdef, I did manually. I completely forgot about it until this morning. I had put this aside for a while due to COVID priorities.
    LauraPat
    Sr. Application Engineer
    Private
    Advanced Member
    (90 points)
    Advanced Member
    Posts:44


    Send Message:

    --
    06/17/2020 10:36 AM
    I just wanted to provide an update that I figured this out. Infor is actually going to write up a KB article on it with the error that occurred and the resolution. In the pgmdef for the custom program - the Run Type was set as "Executable" instead of "Four G/L" like all of our other programs. I'm not sure how that happened but it is most likely due to a system issue we had where we lost our GEN database and it had to be recreated. The program compiled fine and ran fine through a job set up in LID. The only consequence of this flag being set to "Executable" was the program could NOT be used in a multi-step job in Portal. It could be used in a Single step job in Portal (and LID) - but a multi step job ONLY in Portal. Just wanted to make everyone else aware in case you ever came across this.
    You are not authorized to post a reply.