Page 1 of 1

JCL internal error

PostPosted: Wed Oct 20, 2010 7:08 pm
by anubhav.1982
/*PROFILE CPU=(45,00),TAPE=0
/*ROUTE PRINT SDSF
/*NOTIFY VQ104
//*
//STEP01  EXEC PGM=RESTART,
//         PARM='SB900.GIPRIC.ALMFTP.DVLP.PRG.DEV.ANUBH2'
//STEP02  EXEC PGM=RESTART,
//         PARM='SB900.GIPRIC.ALMFTP.DVLP.PRG.DEV.ANUBH1'
//*
//MASTER   DD DSN=SB900.GIPRIC.ALMFTP.TLS.MOINFO.D1024300,DISP=SHR
//SMCMACRO DD DSN=MI000.MI3SAS.MACROS,DISP=SHR
//MBSFD    DD DSN=SB900.GIPRIC.ALMFTP.TLS.MBSFUND.D1024300,DISP=SHR
//INCBFLE  DD DSN=SB900.GIPRIC.ALMFTP.DVLP.PRG.DEV.ANUBH2,
//           DISP=(NEW,CATLG,DELETE),UNIT=INFOREAL,
//           LABEL=EXPDT=60001,SPACE=(CYL,(95,30),RLSE)
//EXTRACT  DD DSN=SB900.GIPRIC.ALMFTP.DVLP.PRG.DEV.ANUBH1,
//           DISP=(NEW,CATLG,DELETE),UNIT=INFOREAL,
//           LABEL=EXPDT=60001,SPACE=(CYL,(95,30),RLSE)
//SYSIN   DD *


SAS code starts here
It giving error JCL internal error
Can somebody tell me what is the problem with JCL

Re: JCL Error

PostPosted: Wed Oct 20, 2010 7:30 pm
by MrSpock
/*PROFILE CPU=(45,00),TAPE=0


??? I see no such documented construct in the MVS JCL Reference manual.

Re: JCL Error

PostPosted: Wed Oct 20, 2010 7:32 pm
by Robert Sample
JCL specifics -- such as JOB card requirements, UNIT names, and data set name standards -- are controlled by individual sites. Unless you talk to someone at your site (coworker, team leader, or site support group), you will not be able to find out the precise problem. Generic JCL issues we can help with, but site-specific issues we cannot, and a JCL internal error could definitely be a site-specific problem.

Re: JCL Error

PostPosted: Wed Oct 20, 2010 7:48 pm
by steve-myers
/*PROFILE is not a standard JES2 JECL statement.

In /*ROUTE PRINT SDSF, the SDSF string in very non-standard, but it may have meaning at your site.

The format of the operand in /*NOTIFY is not valid. See the JCL reference manual.

UNIT=INFOREAL is site dependent You will have to find out what INFOREAL means (if anything) at your site.

I cannot guess what PGM=RESTART does.

Re: JCL Error

PostPosted: Wed Oct 20, 2010 7:49 pm
by Akatsukami
I agree with both Messieurs Sample and Spock. Moreover, I note that you have not told us what the error actually is, only that there is one, which makes it difficult to diagnose.

Re: JCL Error

PostPosted: Wed Oct 20, 2010 7:50 pm
by enrico-sorichetti
the only place to ask for help is Your suppoort
the /*profile is not a standard jes control statement
most probably a user local mod or some product addon

from my point of view the JCL internal error
could be the result of a clobbered jes user modification

Re: JCL Error

PostPosted: Wed Oct 20, 2010 7:57 pm
by anubhav.1982
Thanks guys I deleted the three statements
/*PROFILE CPU=(45,00),TAPE=0
/*ROUTE PRINT SDSF
/*NOTIFY VQ104

and submitted my job ,then I went to 10.st to see log This is what is displayed over ther
SDSF STATUS DISPLAY ALL CLASSES                         NO DISPLAYABLE DATA
NP  ,JOBNAME ,JobID   ,Owner   ,Prty,Queue     ,C, Pos ,SAff ,ASys,Status
S   ,VQ104    TSU03498 VQ104   ,  15,EXECUTION         ,Z200 ,Z200


What does the Queue->Execution means??? and why it says NO DISPLAYABLE DATA

Re: JCL Error

PostPosted: Wed Oct 20, 2010 8:15 pm
by enrico-sorichetti
PF1 is Your friend
SDSF help will tell all You might want to know about the meaning of the columns displayed

Re: JCL Error

PostPosted: Fri Oct 22, 2010 1:20 am
by anubhav.1982
My priority of the job is showing 15 that means the leaset priority and its is in execution queue.How can i increase the priority so that my job moves from the execution queue and I am able to see results at SDSF.

Re: JCL Error

PostPosted: Fri Oct 22, 2010 1:33 am
by enrico-sorichetti
the <job> in the execution queue You are seeing is Your tso userid!
the wisest thing would be to review Your understanding of jes/mvs queues and prioprities

since You did not care to tell the name of Your job,
You did not care to tell the settings of Your SDSF session
we cannot tell anything about Your issue