KB Article 16361
2020/01/16

Close
X
Contact Tech Support

 Email Tech Support
 (250) 655-1766
 [7:30 - 5:00 PST]
Your Meeting ID will be Provided by a Rep.
Tech Support
Tech Support Home
Software Updates
Knowledge Base Search
Recent KB Articles
Product FAQs
Code Samples
Documentation
Tech Blog
System Requirements
Installation Instructions
Support Testimonials
Contact us to...
Create a Ticket
Request a Free Demo
Suggest a New Feature
Submit Feedback
Upload a Large File
Other Services
Software Training
Professional Services

Why do saving certain documents take a long time or fail?

Product: Presto Type: Troubleshooting

Presto uses QSH commands when it saves certain files (for example skin files, or config.bws). If these are taking a long time or even failing it might be due to DNS configuration issues.

If this is failing it can result in partially saved files resulting in environment failure. If this is the case there still may be an existing back up of the file that can be renamed to restore to the original file. If you turn on logging in the EXWORK job before triggering the error (since it may die) you may see errors related to PR_SRV call program or procedure $UPDIFSFIL.

Workaround:

If saving is failing extending the Exodus timeout in the IDE Settings can give it enough time to complete.

A Quick Test:

1. On the greenscreen run the command: QSH CMD('echo "Test"')

If this takes a long time (is not instant) then that is indicative of an issue.

More In-Depth Test:

1. On the command line run: QSH

2. Type 'hostname' and hit Enter.

This displays the hostname that QSH is using. Note this value.

3. Exit QSH and run the command: CHGTCPDMN

Note the 'Host name search priority' value. If this is *REMOTE the system is going to an external DNS. Page down to see the IPs listed for the DNS. If this is *LOCAL it's using the local host table names.

4. If the 'Host name search priority' value is *REMOTE, from the PC open up Command Prompt and verify that we can reach the hostname QSH is using from the DNS specified from the CHGTCPDMN screen by running the command:

nslookup hostname_From_QSH DNS_IP_Address     

example call: nslookup my.domain.com 8.8.8.8 

This will try to reach the hostname_From_QSH via the DNS server: DNS_IP_Address. If this fails it means something is misconfigured at the DNS and it is not aware of the hostnamethat QSH is using.

If the 'Host name search priority' value was *LOCAL it will use the local host table entries ( CFGTCP >> 10 ).

---

If the DNS server specified in the *REMOTE case fails to identify the domain name it will fall back on the local host tables. This requires it timing out though and is what results in the slow saving or the save failure if Exodus times out.

Solutions:

1. Go to the Network Administrator for the DNS being used and have them add the hostname that QSH is using.

2. Setting the 'Host name search priority' value to *LOCAL will have the system search the local host table before using the DNS server. If the hostname QSH is set here then this should speed up the save time.

One should consult with their system administrator before making changes like these. If you have further questions don't hesitate to reach out to the Technical Support Team.

Further Reference:

https://www.ibm.com/support/pages/qshell-session-takes-long-prompt-or-time-start-and-run-commands

Rate This Article

Did this example help you to achieve your goal?
 Yes  No  Don't Know

Enter additional comments below.   If you want to hear back from us, include your contact information.

Email Address:
Comments:
Please enable JavaScript in order to rate this page.