Here's our situation: we have at the moment a LANSA-job that is running unattended on standalone windows PC. We wish to port this job to our IBM i host and run it as a background batch job.
It seemed an easy task. I wrote a new LANSA function to call the processing RUPs. All went smooth until some actual processing had to be done. Then a number of other RUPs are called that fail to load, because they are based on #PRIM_PANL.
Now I can't see why the RUPs were designed that way. They have no visuals whatsoever and contain no coding for user interaction. They are also used in our main interactive application, so maybe that was the reason.
Anyway, I'm not sure how to proceed now. Maybe you folks can help?
- Is there a way to load the #PRIM_PANL object to our IBM i? It's functionality will not actually be used.
- Can I simply chance the #PRIM_PANL reference to #PRIM_OBJ in the RUPs? Or will that have consequences for our main interactive application? (no actual visual stuff being done in these RUPs)
- Should I forget about an easy option and copy all the code to new RUPs that have a #PRIM_OBJ reference? (I'd hate to do that)
- Any other options?
Hope you can help! Thanks in advance,
Annemiek.
#PRIM_PANL in batch jobs?
Re: #PRIM_PANL in batch jobs?
You should be able to change the reusable parts to be prim_obj just in the top line and selecting the correct value for target platform.
If you are not using any visual things from the panel you won't have anything else to change. If something maybe a leftover width top left or height parameter left behind
If you are not using any visual things from the panel you won't have anything else to change. If something maybe a leftover width top left or height parameter left behind
Re: #PRIM_PANL in batch jobs?
thank you, I will do that 