Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] job name will always be XMLSERVICE #59

Open
NattyNarwhal opened this issue Apr 1, 2022 · 2 comments
Open

[feature] job name will always be XMLSERVICE #59

NattyNarwhal opened this issue Apr 1, 2022 · 2 comments

Comments

@NattyNarwhal
Copy link
Collaborator

arg1 = %trim(mydir) + %trim(mypgm) + x'00';

Because dir+pgm will always expand to /libname.LIB/XMLSERVICE.PGM, and SPAWN_SETJOBNAMEARGV_NP gets set, this will always make a job of the name XMLSERVICE when spawning. A user asks if this could be customizeable. My guess is to set argv0 to whatever, but still pass what is currently argv0 as the first parameter to spawn.

@jimoibm
Copy link
Contributor

jimoibm commented Jun 28, 2022

Those were defined in src\plugconf.rpgle.in

     D PLUGSPNPGM      c                   const('XMLSERVICE.PGM')
     D PLUGSPNDIR      c                   const('/QSYS.LIB/@[email protected]/')

Change to what you want and rebuild.

@kadler
Copy link
Member

kadler commented Jun 28, 2022

Personally, I think XMLSERVICE is too oriented around compile-time customization. This may have made sense long ago before IBM started shipping it. Since we did start shipping it, we've encouraged users to use that version of XMLSERVICE (all the toolkits default to this version and the Node.js doesn't even let you change it IIRC). This means that options which are compile-time only may as well not even be there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants