Thank you for reporting this problem Joep.
Please open a PMR and we will investigate it.
From: Joep Beckeringh <joep.beckeringh@xxxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Date: 09/02/2016 08:52 AM
Subject: [WDSCI-L] Push to client - Compile options and user actions
don't get imported
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Last week I was experimenting with Push To Client; I noticed the following
strange behaviour:
After I exported my configuration I created a new workspace, connected to
the same server, got a prompt to accept the configuration, accepted it and
everything I expected to be there was there; including a number of added
compile options and user actions.
Then I went to a colleagues PC and created a new workspace, connected to
the same server and accepted the prompt. After that, the connection and the
filters were there, but only the default compile options were there and no
user actions. When I go to 'Work with compile commands' I see the (only)
filter pool is PTHPC096, which is the name of my PC, where the export file
was created.
Then I exported my configuration to a different location, mailed the
configuration file to my colleague and imported it on his PC. Same effect.
Does anybody else export configurations and if so, do compile commands and
user actions come across?
Joep Beckeringh
Pantheon Automatisering b.v.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
