It's all about the answers!

Ask a question

view the build output using the ISPF-client

Bernd van Oostrum (21725269) | asked Dec 03 '14, 9:15 a.m.

When I try to view the build output using the ISPF-client, I get an error telling me that there is an "Error loading the log file".

In the "/var/jazz406/logs/ISPF_log0.log.0" - file I see more details:

 BROWSE    /SYSTEM/var/jazz406/logs/ISPF_log0.log.0   Line 00000183 Col 001 080 
  Command ===>                                                  Scroll ===> CSR 
Dec 3, 2014 2:40:13 PM
SEVERE: Invalid request                                                        
Throwable occurred: Invalid request                       
Dec 3, 2014 2:40:13 PM
INFO: Loading /.LogfEdit/LOG52813 with serverEncoding=UTF-8 codepage=null      
Dec 3, 2014 2:40:13 PM handle
SEVERE: /.LogfEdit/LOG52813 (EDC5129I No such file or directory.)              
Throwable occurred: /.LogfEdit/LOG52813 (EDC5129I
.at Method)                               

Why is this happening? When using the eclipse-client, the logfiles can be opened correctly.

It looks like the output is being written to the user's home directory on USS. However, there is no home directory configured. Is it possible to change the location where the .LogfEdit - directory is created?

2 answers

permanent link
Xavier Houis (161) | answered Jan 08 '15, 6:37 a.m.

Hi Bernd,

The .logfEdit directory is created under the tso USERID USS home directory, and as I saidd in my first comment, ISPF client is coded to cover the case where no USS home directory is configured for the userid. In this case there is a ISPF error message returned on the View Build Logs panel, withe this  message :

"No HOME specified" - "Your userid does not have a USS Home directory specified in your OMVS segment in your security product. Some functions of RTC will not work without one."

So if this ISPF error message is not display when you're trying to View the build log files, and else the load operation seems to be performed and failed, it should be interresting to have the ISPF client trace file corresponding to your Build work.

You can obtain this trace starting ISPF Client with the following command :

ex '<your HLQ>.sblzexec(blz)' '<your HLQ> enu tracei(blzbuild)'        

After navigating thru your Build scenario to reproduce the View build logs issue, disconnect from ISPF client, and the corresponding ISPF Client trace file will be available in the data set : USERID.RTC.TRACE

Can you send me this trace file.


permanent link
Xavier Houis (161) | answered Dec 08 '14, 5:31 a.m.
Hello Bernd,
There are some RTC operations performed using ISPF client, that requests USS Home directory specified in the ISPF userid OMVS segment of the security product, and The View Build Logs is one of these (also some View remote or Compare on change sets are concerned).
Concerning the Build View Log, if the ISPF userid have no USS Home directory specified, you should have an error as follow :

If the View Log failed for another reason, during the load of the Log file on USS, it should be a system space problem.

Bernd van Oostrum commented Dec 17 '14, 9:00 a.m.

Hi @xhouis,

I'm not sure if the problem is related to not having the home-directory; something went wrong with your reply...


Bernd van Oostrum commented Jan 07 '15, 9:58 a.m.

Does anybody have an idea?

Your answer

Register or to post your answer.