Page 1 of 1

Assign special device name

Posted: 30 Aug 2021, 22:09
by jaimosky
Another question. In the old Server there was the possibility to assign the name of the device in the aXesTSUsers.conf file.

Is there something like this in this new server, or how can I see if the session was started with aXes or not?

Code: Select all

###############################################
# S T A R T   O F   C O N F I G U R A T I O N #
###############################################
#
# aXes TS User configuration file
# Uncomment (remove the #) and alter lines as required
#
 
# The list of user attributes:
# user*=enable,device,InlPgm,InlMenu,CurLib,IP mask,view,sessions,devType,kbdType,charset,codepage
#
# user name supports generic values using wildcards: ?,*
# device name can include the following substitution values:
#   $U is replaced by the user's OS/400 user profile name
#   $* is replaced by a sequential number
# ip mask supports generic values using wildcards: ?,*,**
#
# Examples:
#
# JOE=1,JOE000001,QCMD,SYSTEM,USERLIB,192.10.1.*,noview,1
#   JOE is allowed to use aXes sessions
#   JOE will also acquire the JOE000001 device and will run
#       QCMD as the initial program, the initial menu will be SYSTEM,
#       and the current library will be set to USERLIB.
#   JOE is required to logon only from the specified IP address range.
#   JOE sessions may not be viewed via the Administration interface.
#   JOE is restricted to a single session.
#
# QSECOFR=0
#   User QSECOFR may not sign-on to this terminal server instance.
#
# TST*=1,AXESTS2$*,,,,,,2
#   All users with profiles starting with TST are allowed to use aXes sessions
#   All users with profiles starting with TST will be assigned devices named AXESTS2...
#   All users with profiles starting with TST are limited to 2 sessions
*=1,AXESTS2$*,,,,,,

Re: Assign special device name

Posted: 31 Aug 2021, 10:00
by bark
Hi Jaime,

You must be at fixpack001 for aXes 4.2.0 (that is, 4.2.0.001) to get access to the user device options in aXes-JSM.

The configuration file is httpd.xml in the system folder eg. /axes420jsm/jsm/instance/system/httpd.xml.
Its documented here: https://axesdocs.lansa.com.au/index.php ... ation-file
however, just looking at it and the device.options isn't documented.

But i have set it up previously and the parameter looks like this
<parameter name="device.options.TIPAS" type="json" value="{device:'AS$U='}"/>
where
The prefix is a string value AS
The $U is the user profile
The suffix = is an incrementing number
(Note): a suffix of * is incrementing A to Z
Which produced a device name like below

Subsystem/Job User Type CPU % Function Status
QINTER QSYS SBS .0 DEQW
ASTIPAS01 TIPAS INT .0 MNU-MAIN DSPW


HTH
Bark

Re: Assign special device name

Posted: 31 Aug 2021, 17:15
by jaimosky
Hi Bark,

I placed

Code: Select all

<parameter name="device.options"       type="json" value="{device:'AXESTS2='}"/>
and did the trick!

Thanks a lot.

Jaime

Re: Assign special device name

Posted: 31 Aug 2021, 17:27
by bark
Hi Jaime,
In case it wasn't clear, TIPAS was just an example user.
with this line in place, if I sign in with this TIPAS user, AS gets prefixed to the device name and 01 gets appended to the device name.
By the way, the wildcard does not work
<parameter name="device.options.TIP*" type="json" value="{device:'AS$U='}"/>
and you log in as TIPAS or TIP01 or TIP02, the device won't be set to the value.

Re: Assign special device name

Posted: 31 Aug 2021, 17:47
by jaimosky
Sorry, I have changed the first post.

Re: Assign special device name

Posted: 31 Aug 2021, 18:13
by jaimosky
Hi Bark,

is there a list with all the possible parameters to configure?
I mean like f.e. the time a unatended session keeps open?
Jaime