As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
This procedure works when I use my userid/password as the first-two parameters, but I do not want to put my userid/password into a production. Besides, it's likely the system will force me to to change it soon and I don't want to have to update the focexec everytime it does. So, there must be a way to do this, maybe by setting up a "production" userid/password that doesn't change.
Does anyone else have a solution?
Alan
WF 7.6.6, FOCUS 7.6.4, IBM MVS/TSO, Windows 2003 Server, DB2, MSSQL
Posts: 65 | Location: Chicago, IL | Registered: July 26, 2007
I've come across this situation before, and it was then advised to create a special functional userid for just this purpose. These id's are usually set up such that they will not expire the password. That way you will always have the same userid and password, which will be more or less 'static'. Another solution might be to encrypt your fexes, although I've never tested that.
Hope this helps ...
GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007
So it sounds like the consensus is that you must set up a "production" userid/password at the network level that does not expire, right? Can you place other restrictions on the network id, like "no terminal access" to further lock it down?
Thanks, Alan
WF 7.6.6, FOCUS 7.6.4, IBM MVS/TSO, Windows 2003 Server, DB2, MSSQL
Posts: 65 | Location: Chicago, IL | Registered: July 26, 2007
Okay, then. Prarie, your post got me to thinking so I went back and tried different combinations of userid/password and discovered that I can use the ADMIN userid without a password as the first-two parameters to DSTRUN and it submits the job just like it ought to.
Slick.
WF 7.6.6, FOCUS 7.6.4, IBM MVS/TSO, Windows 2003 Server, DB2, MSSQL
Posts: 65 | Location: Chicago, IL | Registered: July 26, 2007