Re: ACS "Generated" work station IDs / iSeries Access saving/migration of custom settings

I had the problem with generated ID's. I use WORKSTATION ID = &USER= now.
This limits the number of ID's generated over time. I had it set to &USER==
and over time each workstation created many device descriptions in the
system. My standard has been to use the User ID as the name of the work
station(s).

Darryl

On Wed, May 30, 2018 at 9:04 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

We copy the .HOD file from a master and set the workstation ID locally.
Then right-click on the .HOD file and create the desktop shortcut.



-----Original Message-----
From: Steinmetz, Paul [mailto:PSteinmetz@xxxxxxxxxx]
Sent: Wednesday, May 30, 2018 7:30 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: ACS "Generated" work station IDs / iSeries Access
saving/migration of custom settings

I tested the "Generate" work station IDs, that works fine.
How did you create the initial .hod file on each PC, along with the
shortcut?
Was it done manually or via some deployment scripts?

Paul


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD