TEC Configuration – Device Naming

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #521
    AvatarSteven
    Member
    • Total Post: 3
    • Newbie

    Working with the Linux TEC. I’m having a bit of an issue setting up the TEC for a 5250 emulation. I’ve got most of it, including getting the UTILS to ftp my files to the WDM.

    I have an issue, though. I need to be able to set a parameter for the device name to equal the thin client terminal name (as set in the Network Configuration). So if my thin client is named “terminal1”, I need the ptc file device-name parameter to be the same.

    Any ideas?!?
    ❗ 😯 😕

    #9895
    Avatargerjan
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    Hello,

    I presume you only set this once.. Right? You are possible to give a target name in the configuration (under tab Remote Configuration)

    Or you have to work with a ftp-able wlx.ini put the connections of your desire in it and receive it the “right” one based on MAC.

    Kind regards,

    Gerjan

    #9896
    AvatarSteven
    Member
    • Total Post: 3
    • Newbie

    Thanks for the response. But maybe I’m not being clear in what I’m looking for.
    All of our TEC sessions need to have a different device name. This device name should be the same as the thin client terrmina name. So if the thin client has a terminal name of abc123, the TEC session should have the same device name. I have not found a parameter to enter so the TEC automatically picks up this name. I used to use teemtalk, and there was a parameter (I think something like %S) that I would enter as the device name. This parameter then picked up the thin client terminal name. That way I could use a wlx.ini file on the WDM. Otherwise, the WDM will always send the TEC connection with either a blank name, or a singe name, causing many more issues.
    You do mention having the TEC connection pick up a MAC, but I’m assuming you are referring to the Network Terminal Name of the thin client, not the TEC device name.

    Thanks for any assistance.

    #9911
    Avatargerjan
    Member
    • Total Post: 10
    • Regular Joe
    • ★★

    @Steven wrote:

    You do mention having the TEC connection pick up a MAC, but I’m assuming you are referring to the Network Terminal Name of the thin client, not the TEC device name.

    Thanks for any assistance.

    The use of a configuration based on MAC is for the entire wlx.ini. There you give specific connection properties etc etc.

    I don’t know any parameters with %S..

    #11935
    AvatarBinskin
    Member
    • Total Post: 5
    • Newbie

    Im in the same boat here, terminal sessions obviously need meaningful unique names (having hundreds of ‘QPADEV’ devices is meaningless to users / support staff) so i am trying the same thing, we can have the central config for our S50’s if we could only use variable names for the ‘description’ / ‘termname’ fields in the ini files.

    I had hoped that $TN would work but from what i have tested it does not seem to work.

    We currently setup 2 sessions on each device ie ‘DEVNAMEA’ / ‘DEVNAMEB’ if we could achieve this through the wlx.ini file individual setups would become redundant saving a huge amount of time for setup / deployment.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.