Navigate from CICS region to the CEEMSG log

[Joe-Winchester]

For developers who use the DISPLAY statement for debugging programs, this ends up being written to the CEEMSG JES file for the CICS job.

The request is to provide a point and shoot solution to go from a CICS region to open the CEEMSG file.

Issues to solve:

• How to know the right z/OSMF, FTP, RSE (i.e. base profile) is associated with the CICS profile.
• Existing analogous things are submit job and navigate to job, however this just goes from tree view to tree view. For CICS it may be possible to remove the need for a user to even open the JES view and just go directly to open the CEEMSG file.

ruc.dk

[zFernand0]

Thanks for outlining the issues to solve
I'm still not sure if this is entirely possible, but this might be related to something that @t1m0thyj is working on (profileLinks)
He might be able to provide more details and maybe a link to some design doc if needed

[Joe-Winchester]

Hi @t1m0thyj , I love the idea of profileLinks and would like to find out more. Do you have a design doc link, or maybe a scrum recording I could look at, or perhaps find some time to just chat 1:1 and I can show you the sort of scenario we were thinking to navigate between different VS Code plugins with related data (that would also cover some of the Db2 plugins) and it'd be great to see if profileLinks are going to be able to help ?

[t1m0thyj]

@Joe-Winchester Here is a design doc link: https://ent.box.com/s/thqbdjbz9rd2heohxb2ds27kv4sdlgv3

Feel free to reach out on Slack, would be happy to take some time to chat 1:1 to better understand your use case 🙂

I'm curious to know your opinion about which direction links should be defined. For example if you want to associate a z/OSMF profile with a CICS profile, which of the following profileLinks definitions seems more intuitive:

  "profileLinks": {
    "lpar1_zosmf": ["lpar1_cics"]
  }

or

  "profileLinks": {
    "lpar1_cics": ["lpar1_zosmf"]
  }

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[zFernand0]

Removed stale label since this was added to the 3.2.0 release plan 🙏