View previous topic :: View next topic |
Author |
Message |
Deepthi Beginner

Joined: 20 Aug 2005 Posts: 27 Topics: 6 Location: MN
|
Posted: Thu Sep 08, 2005 12:35 am Post subject: Parser Programs |
|
|
Hi,
This is my first post to the forum.
Can anyone let me know what are parser programs ?
And How are they related to CICS transactions?
In case if related , if we are deactivating any CICS transaction from CICS region ,do we need to delete these parser programs as well?
Thanks,
Deepthi |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12383 Topics: 75 Location: San Jose
|
Posted: Thu Sep 08, 2005 4:28 am Post subject: |
|
|
Deepthi,
A parser is nothing but an analysis of the operands entered with a command in addition to the creation of a parameter list for the command processor. It can also refer to the initial processing of source code by a compiler, when it divides up each program statement into its component parts, also known as tokens. ex: xml parser.
You need to clear on what type of parser you are talking about. Take a look at the sample xml program here
http://mvsforums.com/helpboards/viewtopic.php?t=3575&highlight=xml
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
 |
Deepthi Beginner

Joined: 20 Aug 2005 Posts: 27 Topics: 6 Location: MN
|
Posted: Thu Sep 08, 2005 10:10 am Post subject: |
|
|
Thanks Kolusu.
Actually, i was doing an analysis on the task of removing some cics transactions from test region.Till now i was under the impression that the components that needs to be removed for the same will be online programs and the maps related to the screens and the screen definitions.Today i got to know that every time we recompile a program in test and test the screen in test, a assembler parser definition will be created for the same. And this also needs to be removed along with all other components.This parser program takes care of mapping the values entered in the screen to the maps.
Please correct me if i am wrong as i am not sure of this.
Also,Could you please throw some light on this?
Thanks,
Deepthi |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12383 Topics: 75 Location: San Jose
|
Posted: Thu Sep 08, 2005 10:21 am Post subject: |
|
|
Quote: |
Today i got to know that every time we recompile a program in test and test the screen in test, a \b{assembler} parser definition will be created for the same.
|
Assembler definition? hmm Can you compile one of your pgm and post the compile options? I am guessing that your pgm's are compiled with compiler option LIST which will generate the assembler code of your pgm which is also saved. If that is the case all you need is compile your pgms with NOLIST option.
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
 |
Bithead Advanced

Joined: 03 Jan 2003 Posts: 550 Topics: 23 Location: Michigan, USA
|
Posted: Thu Sep 08, 2005 11:55 am Post subject: |
|
|
Is this possible the generation of the DSECT? Here is the JCL we use:
//DSECT EXEC PGM=ASMA90,PARM='SYSPARM(DSECT),DECK,NOOBJECT'
//SYSLIB DD DSN=CICS.SDFHMAC,DISP=SHR
// DD DSN=SYS1.MODGEN,DISP=SHR
// DD DSN=SYS1.MACLIB,DISP=SHR |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12383 Topics: 75 Location: San Jose
|
Posted: Thu Sep 08, 2005 12:11 pm Post subject: |
|
|
Bithead,
I believe that JCL you show is used to compile the assembler macro's for CICS Screens. Back in the days when SDF(Screen Definition Facility ) is not available, all the cics screens are written using Assembler macros.
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
 |
Deepthi Beginner

Joined: 20 Aug 2005 Posts: 27 Topics: 6 Location: MN
|
Posted: Fri Sep 09, 2005 6:13 am Post subject: |
|
|
Kolusu,
Did you mean this 'LIST' option while compiling?
//LINK EXEC PGM=IEWL,COND=((5,LT,COB2CICS),(4,LT,PRECOMP)),
// PARM='XREF,LIST,LET,MAP'
Moreover, i am not sure where do these parser definitions get saved when they get created.Can you direct me as to where to check for these assembler level codes that are generated during the compile.This can help me in verifying when i compile the program with NOLIST option.
Thanks,
Deepthi |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12383 Topics: 75 Location: San Jose
|
Posted: Fri Sep 09, 2005 6:35 am Post subject: |
|
|
Code: |
Did you mean this 'LIST' option while compiling?
//LINK EXEC PGM=IEWL,COND=((5,LT,COB2CICS),(4,LT,PRECOMP)),
// PARM='XREF,LIST,LET,MAP'
|
Deepthi,
The JCL you have shown is actually link-edit step.
Code: |
Can you direct me as to where to check for these assembler level codes that are generated during the compile.
|
Compile your pgm and check the sysprint from the job of the compile step. The sysprint will have the compile options listed in the beginning like shown below
Code: |
PP 5655-G53 IBM Enterprise COBOL for z/OS 3.3.1
Options in effect:
NOADATA
NOADV
....
|
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
 |
|
|