That design decision by SSA back in the early days of BPCS drove me crazy.
I argued (clearly unsuccessfully) that Twinaxial terminals were all but dead
and Token Ring/Ethernet would take over. Guess I was partly right, I though
Token Ring would win. I think MAPICS had the same issue for a while, and
IBM created that in the first place.
Now in the days of Telnet, that problem just keeps biting. Any design that
relies on a specific device name in the world of virtualization and
redundancy is just plain foolish. Was back then, and is still that way now.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Thursday, May 17, 2018 6:52 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: ACS profile migration issues/questions
Session names can be important, for example ERP systems which may tie
batches to the job session name. Or "user preferences" tied to data area
associated to the session name. For this reason we tend to create our
session names as the PC name with a suffix, for example GDL57S1 as in my
laptop (GDL57 - Group Dekko Laptop 57) S1 for Session 1. The problem is
when they get a new laptop these session IDs will change. But, like how
often do your uses get new computers? If they don't like the hassle then
let them keep their old computer.
We did have a case recently where someone (actually our computer operator)
was still using session names from her old computer. This caused some
interesting confusion last week. Apparently it was good that we caught when
we did because her old computer was out of service long enough they were
about to reuse the name. Dueling session names between her and the other
person would have put her into a rabid fit.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 05/16/2018 10:55 AM
Subject: RE: ACS profile migration issues/questions
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Jim,
It's not the change I'm worried about, most users will not notice a
difference.
We have about 200 users, currently using iSeries Access for Windows
V7R1M0 SI66062, Win7 , each with 3 or 4 sessions which point to their own
devices ids, which they launch from shortcuts on their desktops.
Most of these PCs will be reloaded with a new Win10 image as part our Win7
to Win 10 migration within the next year.
I was trying to come up with a plan without having to manually visit each
PC, one at a time, creating the new HOD sessions, shortcuts, and replace
existing shortcuts with the new ones.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Wednesday, May 16, 2018 10:29 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: ACS profile migration issues/questions
Honestly Paul, since most of my customers elected to do the central copy
and
set up sessions that most everyone uses to start with, we did not even
bother to try and migrate anything. They put icons for the 5250 sessions
in
the folder which many users copied to the desktop. Done.
The exception were file up/download processes and a few one offs, but we
just told everyone "It's new", deal with it. In the 20 or so
organizations
I've worked with so far, only one individual had an issue and that was the
font we used. That individual has some vision issues and needed a
slightly
different set up.
I strongly wonder if the cutover is getting to be, maintain the old while
using the new. It's new, just like Win7 was different from XP, and Win10
is
different than Win7. Users get used to change, I suggest you let them and
stop stressing out on the small stuff.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Wednesday, May 16, 2018 9:05 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: ACS profile migration issues/questions
Has anyone done a successful iSeries Access for Windows to ACS migration
without having to manually recreate the ACS hod sessions?
The option,
Do you want to make ACS the default program for your existing 5250
session
profiles did partially work.
But the migrated sessions cannot be changed/updated.
So IMO, worthless.
I'm looking for other options.
It was suggested I review 9.4.1.
Has anyone in the group successfully completed this?
9.4.1 Automatically import configuration settings
The following properties may be used in the AcsConfig.properties file to
automatically set up a configuration for new users or to update a
configuration for existing users:
com.ibm.iaccess.autoimport
com.ibm.iaccess.autoimport.version
Here are the necessary steps:
1.Create the configuration you want to propagate to one or more users.
2.Export the configuration to a file using File->Export Configuration from
the main GUI or use the command line option in section 9.1.1 Backup.
3.Move the configuration file to the desired location. There are several
available options described later.
4.Set the com.ibm.iaccess.autoimport property in AcsConfig.properties to
the
path of the configuration file.
5.Set the com.ibm.iaccess.autoimport.version to an integer value that
represents the version of the configuration file.
Here is how it works:
The saved configuration referenced by the com.ibm.iaccess.autoimport
property will be automatically imported when the integer value of the
com.ibm.iaccess.autoimport.version property mismatches the last value that
was imported. In addition to providing a way to set up an initial
configuration and provide updates to an existing configuration, this also
provides a way to back-level a configuration. The configuration will be
updated anytime there is a mismatch between the integer value of the
version
property with the last version that was imported. However, while an
imported
configuration may change the configuration for an existing system in the
user's configuration, a system will never be deleted from the user's
configuration.
The path for the com.ibm.iaccess.autoimport property may be specified as
an
absolute path, a URL or with keywords defined in section 9.3. For example:
com.ibm.iaccess.autoimport=C:/acs_bak.zip
com.ibm.iaccess.autoimport=file///C:/acs_bak.zip
com.ibm.iaccess.autoimport=
http://your.company.com/path/file/acs_bak.zip
com.ibm.iaccess.autoimport=
ftp://your.company.com/path/file/acs_bak.zip
com.ibm.iaccess.autoimport={PRODUCTDIR}/acs_bak.zip
Additional flexibility is provided by allowing the configuration file to
be
distributed within acsbundle.jar or in the same directory as
acsbundle.jar.
For either case, set com.ibm.iaccess.autoimport with the name of the file
without a preceding path:
com.ibm.iaccess.autoimport=acs_bak.zip
A special value of * is allowed for com.ibm.iaccess.autoimport.version:
com.ibm.iaccess.autoimport.version=*
This will always import the configuration regardless of any previous
version.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Tuesday, May 15, 2018 2:59 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: ACS profile migration issues/questions
Below is an update from IBM PMR.
So what you are seeing is all working as designed. However, it is a bit
confusing on what it is doing. I'll explain everything one at a time.
1) When you see the option for "Do you want to make ACS the default
program
for your existing 5250 session profiles" Their is also this on that
Window:
"5250 session profiles created by IBM i Access for Windows or IBM Personal
Communications can also be used by IBM i Access Client Solutions (ACS).
These files have a file extension of .ws. ACS will not update .ws files,
but is able to use them to start a 5250 session."
Now the reason I point this part of that window out as well is 2-fold.
When
you use a .ws file that has been converted we can not make any changes to
that file. What it does is it opens that file and it prompts ACS. If you
have a config created in ACS that is set to use SSL and Kerberos then it
will find that and utilize those settings. If it doesn't find that System
Config then it defaults to ACS Default settings. This is what you are
seeing. ACS also doesn't have the ability to change .ws files which is
why
when you change it in the .ws file it doesn't update. Because ACS doesn't
have the ability to update those files.
In order to get it to use SSL and Kerberos in the main ACS window you will
want to create a system config with the SAME EXACT NAME as the .ws file.
Set that to use SSL and Kerberos and when you launch the .ws profile it
too
will use those settings.
2) What you could do differently and what I recommend would be to take no
at
that prompt. Then when you get ACS installed create new System
Configurations and .hod sessions that can be updated by ACS. In saying
this
that is all good for 1 PC but for getting this to others I would look into
the Export Configuration option. That would allow you to set this all up
on
1 PC and then export the config and utilize the Import Configuration when
you go to put it on other PC's. This is covered in more depth in the
GettingStarted.html which is in the Documentation folder you downloaded
(Section 9.4.1).
Now, in saying all of this I also have to point this out. The version you
are currently using wasn't tested with Java 10. So long as you continue
to
use that with 1.1.7.3 anything that should work as designed is hit or
miss.
The next version of ACS coming out in June is supposed to work with Java
10
but it was not tested with the version you are using. I would recommend
staying with Java 8 (especially since Java 10 is still in sort of a Beta
state).
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Winchester Terry
Sent: Tuesday, May 15, 2018 2:36 PM
To: Midrange Systems Technical Discussion
Subject: RE: ACS profile migration issues/questions
Interesting.
Thanks for the heads up on this...
We just tried installing this today and pointed it a V7R2 system and using
a
standard V6 Client Access session install.
The keyboard mapping failed...look like it didn't even attempt to convert
the KMP file associated with the workstation (WS) file.
We certainly won't be rolling this out to 300+ users any time soon...lol
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Tuesday, May 15, 2018 2:14 PM
To: 'Midrange Systems Technical Discussion'
Subject: [EXTERNAL] ACS profile migration issues/questions
I'm testing the migration of the .ws to .hod profile by answering yes to
the
below.
Do you want to make ACS the default program for your existing 5250 session
profiles?
All my current iSeries Access for Windows shortcuts were automatically
updated to launch using ACS instead.
The below items did not migrate correctly.
1) Security was migrated from SSL port 992 to Use IBM iAccess Client
Solutions setting, which is nonSSL, port 23. Had to manually change.
2) User ID was migrated from Use Kerberos principal name, no prompting to
Use IBM iAccess Client Solutions setting, which is prompting for
user/password. Had to manually change.
3) Preferences Tab Setup is defaulting with Open new sessions in a new
tab.
Had to uncheck Open new sessions in a new tab
4) After saving the changes, closing and reopening the sessions, all
changes
were lost, back to the defaults.
I'm sure there's a setting to preserve these preferences, not able to
locate?
And why are the saved changes being lost?
Also, in the ACS hod session toolbar,
I have some buttons on my PC that my operator does not.
What controls these additional buttons/features.
Integrated file system
Nav for I
Printer Output
Schemas
Run SQL scripts
SQL Performance Center.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pencor.com_&d=DwICAg
&c=usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=LD1savGZ6Gc4gIcG9yLPnyfe5Wy
5IgPnRmF3qDwpJN4&m=bghZhIZL9OJUqU-7IP5SK1AU77E45NPvDNpixPNFevU&s=okN28RyGLtX
ASqI7VjyRgIuwa1OKaYFfcYfes52NcsM&e=
--
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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mail
man_listinfo_midrange-2Dl&d=DwICAg&c=usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7Op
WXXY&r=LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=bghZhIZL9OJUqU-7IP5SK1A
U77E45NPvDNpixPNFevU&s=g91rL_EFITkwfODiFd3WpVwIHcIdwVZdYWzKIvHfRU4&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_mi
drange-2Dl&d=DwICAg&c=usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=LD1savGZ
6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=bghZhIZL9OJUqU-7IP5SK1AU77E45NPvDNpixP
NFevU&s=DtJORbC2630mXEQLoMmT4B3796Ggfrz1RmJV-gz8yew&e=.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_2dEadiD&d=DwICAg
&c=usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=LD1savGZ6Gc4gIcG9yLPnyfe5Wy
5IgPnRmF3qDwpJN4&m=bghZhIZL9OJUqU-7IP5SK1AU77E45NPvDNpixPNFevU&s=TRzBYpMO2yD
ULetwhzAOqND1T-c22cQdcxWVj83Ye3M&e=
----------------------------------------------------------------------
Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected by
applicable legal privileges, or constitute non-public information. It is
intended to be conveyed only to the designated recipient(s). If you are
not
an intended recipient of this message, please notify the sender by
replying
to this message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is
not
authorized and may be unlawful.
--
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
--
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
--
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
midrange.com
