Closed MS615511 closed 12 months ago
Hi @MS615511 Thank you for opening this request. I do agree that looking for the processor output that way (going to the SYSVIEW) is very tricky in case EWS is working with pool of STCs. We plan to resolve this situation by providing the reports (C1MSGS and APIMSGS) after each command that submitted a Endevor request. This way, you can get the C1MSGS with processor output directly in the vscode after the generate and will not have to look for it in the SYSVIEW STCs. Do you think this will be sufficient solution for you?
Hi @mmeldo Yes. It addresses my requirement. Is this going to route the reports to VSCode and prevent output to Endevor web services tasks as well?
@MS615511 The reports are not routed, they are read from STCs and stored in Tomcat running EWS. They can be then downloaded by a client. Thus VSCode can just download them from EWS if requested by user after the action is completed.
@mmeldo Thats ok. So I am waiting to have it available. Tks
Hey Mauro, This will be included in the 1.5.0 release, which we aim to get out in early to mid-April. I hope that sounds alright. Thanks, Zach
Hi Zach, Thank you for letting me know. That sounds great. Regards, Mauro
On Tue, Mar 7, 2023 at 1:01 PM Hrabal33 @.***> wrote:
Hey Mauro, This will be included in the 1.5.0 release, which we aim to get out in early to mid-April. I hope that sounds alright. Thanks, Zach
— Reply to this email directly, view it on GitHub https://github.com/eclipse/che-che4z-explorer-for-endevor/issues/308#issuecomment-1458420950, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALJ3ZYTD5CPXARBK6KNTFEDW25LXHANCNFSM6AAAAAAVJ3V4KE . You are receiving this because you were mentioned.Message ID: @.***>
--
Mauro Saito Client Services Consultant - MFD
Broadcom office: +55 11 5503-6291 | mobile: +55 11 96435-0040
AV. Dr. Chucri Zaidan 1240 - Morumbi Coporate Golden Tower - 27 andar
@. @.> | broadcom.com
-- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
Hi @MS615511,
We introduced an Explorer for Endevor Activity view with the release 1.6.0, which also provides access to the Endevor C1MSGS and APIMSGS reports for all the Endevor requests were made during the working session (including the GENERATE commands that were issued).
We encourage you to try it out and let us know your thoughts, comments or suggestions. Please, open an another request if necessary.
Thanks, Explorer for Endevor Team.
Is your feature request related to a problem? Please describe.
The GENERATE action available with E4E runs the command at the Endevor WebServices system task. It works ok. But if we look for the Endevor processor output messages, this is going to be tricky. Lets consider that EWS should be in a pool of tasks, and we need to enter SDSF or SYSVIEW (or even zowe explorer) to find in which one the GENERATE command got executed. To perform this search, we will select each task sysout and there we find a lot of other commands that were addressed to these tasks to be executed. This way after a while, the task's sysout can become very large.
Describe the solution you'd like The idea is to have a parameter to drive the GENERATE action as it is today, or to submit a job. If the parm is set to submit a job, a sample job JCL should be parameterized (could be a json config file or something like this) and the GENERATE SCL demanded. Then the job is submitted using zowe. This will behave as we were using QE interface. QE action options dictates how GENERATE action is to be performed. Once we have the batch job submitted, we can access its whole sysout using zowe explorer.
Describe alternatives you've considered An alternative considered was to issue zowe endevor generate command. It works perfectly as well, but need to issue this command. Another alternative considere was to have a sample library member where Endevor batch commands could be tailored. We could edit the member, write the GENERATE scl, save and submit. In this case need to know scl syntaxes.