|
| Can a job name be retrieved for a webfacing session from a webfaced |
 |
Thu, 21 Jun 2007 11:55:09 -040 |
|
| Post Reply
|
| Re: Can a job name be retrieved for a webfacing session from a |
 |
Thu, 21 Jun 2007 15:45:34 EDT |
> Can a job name be retrieved for a webfacing session
> from a webfaced menu?
You have to remember that the only thing webfacing uses are the display files,
the actual programs never change. If you are now able to retrieve the job name,
it will not change when webfaced.
|
| Post Reply
|
| Re: Can a job name be retrieved for a webfacing session from a webfaced<br> |
 |
Thu, 21 Jun 2007 15:55:40 -040 |
bob_l@charter.net wrote:
>> Can a job name be retrieved for a webfacing session
>> from a webfaced menu?
>
> You have to remember that the only thing webfacing uses are the display
files, the actual programs never change. If you are now able to retrieve the
job name, it will not change when webfaced.
>
>
I am counting on the job name not changing. I need the job name, user
id and job number (example: Job: QQF0D4E520 User: XXXXXXXXXX Number:
872800) to pass as parameters to a java routine. If I can retrieve this
info from a menu I will just add the necessary code to my webfaced menu
dds source, otherwise I will have to create a display file and program
to act as a menu.
|
| Post Reply
|
| Re: Can a job name be retrieved for a webfacing session from a webfaced<br> |
 |
Thu, 21 Jun 2007 16:30:52 -040 |
Rodney Hawkins wrote:
> bob_l@charter.net wrote:
>>> Can a job name be retrieved for a webfacing session
>>> from a webfaced menu?
>>
>> You have to remember that the only thing webfacing uses are the
>> display files, the actual programs never change. If you are now able
>> to retrieve the job name, it will not change when webfaced.
>>
>>
> I am counting on the job name not changing. I need the job name, user
> id and job number (example: Job: QQF0D4E520 User: XXXXXXXXXX Number:
> 872800) to pass as parameters to a java routine. If I can retrieve this
> info from a menu I will just add the necessary code to my webfaced menu
> dds source, otherwise I will have to create a display file and program
> to act as a menu.
>
Probably what you want to do is create hidden fields in your DDS record
and fill the job info into them before sending them to the display.
Then you can pick the values up in the app server and run whatever java
program you want from there.
By default hidden fields will not be sent to the browser and I think
this is likely the behaviour that you would desire in this case.
If you are running on a machine where people are starting and ending
WF'd apps a lot it is likely that the job name will be different on each
run.
|
| Post Reply
|
| Re: Can a job name be retrieved for a webfacing session from a webfaced<br> |
 |
Thu, 21 Jun 2007 16:39:33 -040 |
Mike,
Hidden fields would work great if I could find a way to populate them
with the desired information. I know that I could populate the hidden
fields in a regular Display File (DSPF) by getting the job info either
from a CL program or from an RPG program via the INFDS. Unfortunately I
have not found a way to get this type of info for a MENU Display File
(MNUDDS). If you know a way of doing this with a MENU that would be great.
Rodney..
M.Hockings wrote:
> Rodney Hawkins wrote:
>> bob_l@charter.net wrote:
>>>> Can a job name be retrieved for a webfacing session
>>>> from a webfaced menu?
>>>
>>> You have to remember that the only thing webfacing uses are the
>>> display files, the actual programs never change. If you are now
able
>>> to retrieve the job name, it will not change when webfaced.
>>>
>>>
>> I am counting on the job name not changing. I need the job name, user
>> id and job number (example: Job: QQF0D4E520 User: XXXXXXXXXX Number:
>> 872800) to pass as parameters to a java routine. If I can retrieve
>> this info from a menu I will just add the necessary code to my
>> webfaced menu dds source, otherwise I will have to create a display
>> file and program to act as a menu.
>>
>
> Probably what you want to do is create hidden fields in your DDS record
> and fill the job info into them before sending them to the display. Then
> you can pick the values up in the app server and run whatever java
> program you want from there.
>
> By default hidden fields will not be sent to the browser and I think
> this is likely the behaviour that you would desire in this case.
>
> If you are running on a machine where people are starting and ending
> WF'd apps a lot it is likely that the job name will be different on each
> run.
>
|
| Post Reply
|
|
|
|
|
|
|
|
|
|