Skip to main content

CICS in Netexp/Server Enter 6.1 - SSTM not working

  • November 6, 2012
  • 22 replies
  • 1 view
D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

22 replies

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Hi BikerBob

Can you please copy paste the contents of your SSTMCICS.JCL and does this jcl remains active while you bring up the server.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Hi BikerBob

Can you please copy paste the contents of your SSTMCICS.JCL and does this jcl remains active while you bring up the server.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Hi BikerBob

Can you please copy paste the contents of your SSTMCICS.JCL and does this jcl remains active while you bring up the server.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

SSTMCICS.JCL - does remain active when the server is up.

//MFIDSACI JOB 'CICS JOB',CLASS=A,MSGCLASS=X

//CICS     EXEC PGM=NOTUSED

//SYSOUT   DD SYSOUT=*

//SYSPRINT DD SYSOUT=*

//TEMPJCL  DD DSN=&&TEMPJCL,DISP=NEW

//OUTJCL   DD DSN=MFIDSA.DSA.SSTMCICS.OUTJCL,DISP=(MOD,CATLG)

//INTRDR   DD SYSOUT=(*,INTRDR),HOLD=NO

Job submitted thru INTRDR above:

//WAIJ85   JOB (99,45609900,P),CLASS=A,

//    MSGCLASS=D   TYPRUN=SCAN

//JOBLIB    DD DSN=FIXX.LINKLIB,DISP=SHR

//*

//* **

//* **  PRINT VILLAGE CREEK INACTIVE PARTS REPORT

//* **  PRINT TO MOBIUS       / LOCATION   / YR=01  DT=093012

//* **

//JS010     EXEC PROC=WAIN8500

//WAIR8501.CNTLCRD  DD *

01 093012

//*

//WAIR8501.SYSIN DD *

L

//WAIR8501.WAIP8501 DD SYSOUT=X,FREE=CLOSE

//*

//*

//*

//*

//*SWEEP    EXEC PROC=RDSSWEEP

//

/*EOF

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

SSTM is looking fine, i tried same in my environment. However i am looking at JCL. comma is missing between ("//    MSGCLASS=D   TYPRUN=SCAN)

also are there any steps which are getting executed in PROC

//*SWEEP    EXEC PROC=RDSSWEEP - this is also commented.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

SSTM is looking fine, i tried same in my environment. However i am looking at JCL. comma is missing between ("//    MSGCLASS=D   TYPRUN=SCAN)

also are there any steps which are getting executed in PROC

//*SWEEP    EXEC PROC=RDSSWEEP - this is also commented.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

yes there are steps in the proc., the typrunscan does not have a comma meaning it is a comment. That last statement is also a comment.

What would keep the internal reader from executing submitted jcl?? syntax errors wouldn't be recognized

by the reader but by JES. A sysout class that if held wouldn't be recognized by the reader but by JES. I would think that any jcl that comes thru the INTRDR would always be executed.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

yes there are steps in the proc., the typrunscan does not have a comma meaning it is a comment. That last statement is also a comment.

What would keep the internal reader from executing submitted jcl?? syntax errors wouldn't be recognized

by the reader but by JES. A sysout class that if held wouldn't be recognized by the reader but by JES. I would think that any jcl that comes thru the INTRDR would always be executed.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

yes there are steps in the proc., the typrunscan does not have a comma meaning it is a comment. That last statement is also a comment.

What would keep the internal reader from executing submitted jcl?? syntax errors wouldn't be recognized

by the reader but by JES. A sysout class that if held wouldn't be recognized by the reader but by JES. I would think that any jcl that comes thru the INTRDR would always be executed.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

I don't know what the problem might be here, to be honest. I'll pass the question along to some of the other developers.

What product, version, and platform are you using?

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Ignore the question about product and version - I see you supplied that in your initial post.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Here's a response from a developer who works in this area:

I think this may be a misunderstanding about what SSTM is for. On the mainframe CICS is run as a batch job and files can be allocated to CICS via the CICS JCL job just as they would be to any other batch job. The SSTM job emulates this in a Micro Focus environment allowing the allocation of  DDs and the associated datasets to CICS. It is just there to handle file allocations with the correct dispositions.

Submission to the internal reader is something different. From CICS this would normally be done in one of 2 ways, either by writing JCL to a CICS TRANSIENT DATA QUEUE that is defined as an internal reader, or by executing the EXEC CICS SPOOL command. 

In other words, in Enterprise Server, you can't use SSTM to submit jobs from CICS. The recommended method for submitting jobs from CICS is to use the internal reader. Configuring the internal reader is described in the product documentation, in "Chapter 20: Integration with CICS Support", which in the Studio/Server 6.0 documentation can be found in Programming | Mainframe Support | Part 4: JCL Support.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Here's what I've been going by to get jcl submitted from cics.

This tells me I HAVE to use SSTM job in order for the internal reader to communicate.

My internal reader TDQ: I have 2 1) IRDR as an intra Q 2) JOBT as an indirect Q.

The doc only says I need an internal TDQ defined as an internal reader but SSTM isn't putting out the executable JCL to JES. So I'm not sure what is wrong, but it all looks right.

Knowledge Base

33752: Using the Enterprise Server internal reader - INTRDR                  

Resolution:

The MicroFocus emulation of JES supports the IBM z/OS internal reader (INTRDR) for submitting batch jobs from within CICS or from a batch job, with certain restrictions.

N.B. All job streams must be composed of records less than or equal to 80 characters. Records longer than this will either be ignored, cause JCL errors, or result in the job stream "disappearing" (i.e. it will not appear in any of the ES/JES spool queues).

1) Submitting one or more batch jobs from another batch job

2) Submitting batch jobs from within CICS.

Before you can submit jobs to the internal reader from within CICS, you must set up the necessary connections between CICS and ES/JES, as described in the documentation, using the following steps:

a) Enable subsytem support by setting the environment variable ES_SSTM_CICS to point to the SSTMCICS job file (e.g. ES_SSTM_CICS=C:\\ESadmin\\MyCICS\\CICS.JCL)

b) Add a definition for the internal reader to your SSTMCICS job :- //INTRDR   DD SYSOUT=(*,INTRDR)

2.1) Submission via a Transient Data Queue

Prior to release 6.0 SP2, this was the only method of job submission from within CICS. Define a TDQ as the type "Internal Rdr", using the drop-down selection box, and submit your JCL, record by record, using the command EXEC CICS WRITEQ TD directed to that TDQ.  Multiple jobs can be written to the queue, each delimited a record containing /*EOF in columns 1 to 5. To ensure that your jobstream does  not get interleaved with another user's jobstream, access to the TDQ should be serialised using the CICS enqueue and dequeue facilities.

2.2) Submission via the Spool Queue

From release 6.0 SP2 of Studio/Server Enterprise Edition, you can also send jobs to the internal reader using the CICS spool. Open the spool with the statement EXEC CICS SPOOLOPEN USERID('INTRDR') NODE('LOCAL'), and then use the SPOOLWRITE command to write your JCL statements, and SPOOLCLOSE to terminate the jobstream. CICS will handle the serialisation of the spool, but if a single transaction submits multiple jobs, it should close and reopen the spool between each job. Delimiting jobs by writing /*EOF, as described above, is optional.

Incident #2503558

Thanks for your reply.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

The using of a TDQ to internal reader appears to work in my NetExpress (CICSDEMO) and in the CFWTEST region of the server. The spoolwrite to the internal reader appears to no longer work. We began using the spoolwrite when we first bought M>F> because we had so many issues with the TDQ's and that included after upgrading last Feb to SP2WP2. Now it looks like the system has reversed itself and the use of TDQ's are working just fine.

I have some more tests to make on the CFWTEST region before moving the programs to the PROD region.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

The using of a TDQ to internal reader appears to work in my NetExpress (CICSDEMO) and in the CFWTEST region of the server. The spoolwrite to the internal reader appears to no longer work. We began using the spoolwrite when we first bought M>F> because we had so many issues with the TDQ's and that included after upgrading last Feb to SP2WP2. Now it looks like the system has reversed itself and the use of TDQ's are working just fine.

I have some more tests to make on the CFWTEST region before moving the programs to the PROD region.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Thanks for the update. I've made an internal query about the SPOOLWRITE issue.

Your old support incident (2503558) is marked as closed - it looks like it was closed back in April, after the information about using the TD queue was supplied. You might want to open a new one for the SPOOLWRITE problem.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

I've found a reference which claims that when using SPOOLWRITE with the internal reader, the job card should specify "NODE('INTRDR')", and not "USERID('INTRDR') NODE('LOCAL')". You could give that a try if you like.

I've posted an internal query for clarification.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

An update from Development:

I've done quite a lot of testing of CICS job submission, and have found that:-
1) NODE   ('*') USERID ('INTRDR') works
2) NODE  ('INTRDR') USERID('MFUSER') results in the JCL being written to a dynamically allocated SYSOUT within the SSTM job
3) You can also use direct Cobol I/O to a DDname in the SSTM job that points to SYSOUT=(*,INTRDR)

The above were all tested with SP2 WS2, and (1) was also tested with SP2 WS1.

I hope that helps.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Whoops - I meant "an update from Support". Specifically from Steve Verdier.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Sorry it took so long to respond. I tried your suggestion. It still does not work. Have a ticket opened and we have done a live meeting. Can't explain it, but at least the TDQ option works.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Sorry it took so long to respond. I tried your suggestion. It still does not work. Have a ticket opened and we have done a live meeting. Can't explain it, but at least the TDQ option works.

D

CICS in Netexp/Server Enter 6.1 - SSTM not working. I can get the Jcl from CICS to JES and into the Job SSTMCICS.jcl, but instead of executing the JCL from the internal reader - the job prints out the JCL as sysout. Any clues anybody???

I've got ES_SSTM_CICS = C:\\......\\SSTMCICS.JCL    and it does exist and runs.
I've got ES_HOLD_SYSOUT = XZ   which should has no impact on the internal reader nor the job submitted except for sysout.
Obviously the internal reader IS working because the JCL is spooling to JES.


#CICS
#EnterpriseDeveloper
#SSTM.SSTMCICS
#INTRDR

Sorry it took so long to respond. I tried your suggestion. It still does not work. Have a ticket opened and we have done a live meeting. Can't explain it, but at least the TDQ option works.

Recent badge winners

Explore all badges
Terms & ConditionsAccessibility statement