sasjs
sasjs submitted job did not show up in SAS EVM
Currently we use the compute API (useComputeApi:true) for running jobs with sasjs job execute. We should switch to JES API (useComputeApi:false) to resolve this issue (in sasjs flow also)
Can this be implemented quickly ? If yes, let me know when this can be done ?
From: Allan Bowe @.> Reply to: sasjs/cli @.> Date: Wednesday, 30 June 2021 at 4:49 PM To: sasjs/cli @.> Cc: "Toluchuri, Venkateswarlu" @.>, Author @.***> Subject: Re: [sasjs/cli] sasjs submitted job did not show up in SAS EVM (#807)
Currently we use the compute API (useComputeApi:true) for running jobs. We should switch to JES API (useComputeApi:false) to resolve this issue
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sasjs/cli/issues/807#issuecomment-871314495, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AET4YOMBVJJQP4MHX5DNQFTTVL4KNANCNFSM47SDPIFA.
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
how to switch from useComputeApi:true to useComputeApi:false ? Is it a simple change can be done from myside in any sasjs config file ?
Hi @venkattoluchuri - it's a setting we need to apply during the build of the CLI, in relation the sasjs/adapter which handles all the communication with SAS.
There are three ways you can run jobs in Viya with this flag:
- true - will use the compute apis directly (fastest for web apps, by far, due to hot session). Works through code injection on a running session.
- false - will use the JES API to execute an existing job. No code injection, also no hot session, so slower. This is the setting that I expect will resolve this issue.
- undefined - if not set, then the adapter reverts to the web approach (calling /SASJobExecution via http). This isn't relevant for the CLI, it's more a fallback for browser based communication.
There's more info in the README here: https://github.com/sasjs/adapter#configuration
We should have some capacity to look at this tomorrow
@venkattoluchuri - we'd be happy to work on this however we would need some sponsorship to make it happen. We estimate that at 3 developer days. The implementation would include a switch in the sasjsconfig, so the execution option can be down to the end user. It would also include tests and documentation.
Do you have some budget available?