Currently when we want to schedule new tasks in report caster and go to the domain where most of the key code resides we cannot see more than twelve folders. Ironically we can go to the prototype folder, a/k/a Focexecs_Not_Ready_for_Prime_time, we can see all sixteen folders. Even when stretching the selection box horizontally the same folders appeared.


We did open a case with IBI and they requested running traces. However, traces would only display jobs run and not activities scheduling jobs. Also, while we do have workarounds, such as copying code to other domains and folders, the workaround ends up in maintaining two codesets, which might be great for job security but clearly poses issues.


Anticipating question #1: I did an ECL search through IBI Tech Support and Focal Point.
Anticipating question #2: We have Java version 7.0.45.


If anybody has run across this issue please respond.

All the best for the holidays, peace in 2014 and beyond and success for your favorite NFL, NHL, NBA and NCAA teams.
Rock on Focal Nation.
Sandy Kadish

This message has been edited. Last edited by: S.J. Kadish,

Hi S.J. Kadish,

While we wait to see if another customer can help with this issue, please keep us posted on the final solution from your case. Thank you in advance for sharing with all.

Regards,

Kathryn

We posted log traces for the case with IBI and are waiting to hear back.

I will follow up.

After considerable review we created a clone version of the production domain containing all folders and attempted to schedule jobs from each of the folders. I deleted and re-added several of the domains in the clone version and isolated one folder that was unavailable from the report caster screen. Looking further we found that this specific domain had focexec names twenty-four (24) characters long. The developer who developed these focexecs saved new versions with shorter names.

After renaming the focexecs with longer names in the actual production domain all focexecs in all folders are now accessible in Report Caster. This is a crucial lesson learned because while we no longer have the eight character name restriction in mainframe Focus there are still limits. Moving forward we will apply focexec naming conventions consistent with corporate best practices for file names.

The case is closed.

Happy New Year and everybody go to Summit in Orlando.