Hi
Thank you Kirk
It is completely new for me also(i.e. REST), but about the performance.
Are you sure that it is faster as SDSF/REXX ?
I mean, I have never seen something slower as zOSMF.(We are in z/OS 1.12)
On 2/29/2012 4:10 PM, Kirk Wolf wrote:
Have you looked at the new "z/OS Jobs REST Interface"? If it meets
your requirements, I believe that you will find that it far
outperforms a REXX/CGI program, which requires a new process (address
space) and SDSF startup/initialization for each request.
This new web services API is shipped as part of z/OS MF, and oddly is
documented in the "z/OS MF Configuration Guide" (SA38-0652-06)
==================================================================
"The z/OS jobs REST interface is an application programming interface (API)
implemented through industry standard Representational State Transfer (REST)
services. This interface allows a client application to perform
operations with batch
jobs on a z/OS system.
With the z/OS jobs REST interface, an application can use REST services to
perform the following operations with batch jobs:
v Obtain the status of a job
v List the jobs for an owner, prefix, or job ID
v List the spool files for a job
v Retrieve the contents of a job spool file
v Submit a job to run on z/OS
v Cancel a job
v Change the job class of a job
v Cancel a job and purge its output."
=================================================================
Any client or browse-side scripting language that can make web
services calls can use this API. The client will need to be able to
encode and decode JSON, but many languages and toolkits support that
readily.
Kirk Wolf
Dovetailed Technologies
http://dovetail.com
+1 636.300.0901
On Wed, Feb 29, 2012 at 8:27 AM, Dana Mitchell<mitchd...@gmail.com> wrote:
I'm working on a simple REXX/SDSF/CGI exec to display output from selected
STC's via browser and HTTP server on z/OS 1.11. I can get it to partially
work, but there seems to be some inconsistencies in the way userid's are
handled.
If I run a REXX CGI with the ISFEXEC WHO command it shows as running with the
ID that the web server is running under, not my ID that I used to sign on when
the browser asked for credentials.
Further, the output of ISFEXEC WHO shows the web server's ID, but it shows
GRPNAME=ISFUSER which is the catch-all least powerful group in ISFPRMxx, *not*
the group that the web server's ID should be placed into. If I log onto TSO
using the web server's ID and issue WHO, it shows the proper GRPNAME group
assigned.
Has anyone done much work in this area and solved these sorts of probems?
Dana
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
