aktuellen AS400 User in eine variable schreiben in einem RPG Programm

[S.Neinawaie]

Ich glaub folgender Beitrag von Barbara Morris bringt etwas Licht ins Dunkel:

That's a documented difference between OPM and ILE. See point 9 here http://publib.boulder.ibm.com/infoce...c092507488.htm. The current-user-profile subfield is in positions 358-367 for ILE.

You can also get the current user profile by initializing a 10A variable with INZ(*USER). If you put that in a subprocedure, the INZ(*USER) value will get fetched fresh each time you call the subprocedure. With the PSDS, the value is only fetched during the *INIT phase of the module, so you'd have to set on LR and call your program again to get the value refreshed.

As far as we know, it was an undocumented feature for OPM to have the job-user subfield filled with the current user profile. When this difference was discovered, we thought that it was more important to keep the 26-byte job name/user/number available in the PSDS, rather than to maintain the OPM/ILE compatibility (and aside from that, by the time it was discovered around v4r2, there was already a release-to-release compatibility issue for ILE). So we created a separate PSDS subfield for the current user profile.

https://www.ibm.com/developerworks/c...4733323&ps=100

[Fuerchau]

Dann würde ich das eben so wie vorgeschlagen realisieren (eigene Function, ggf. im ServiceModule).
Ich habe mein altes API ja auch ausgelagert, allerdings in einem kleinen OPM. Der Aufruf von OPMs ist ab dem 2. Call auch nicht langsamer.