Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

About quality in NATURAL/ADABAS

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Java & MQSeries
View previous topic :: :: View next topic  
Author Message
GaaZzz

New User


Joined: 24 Nov 2008
Posts: 2
Location: France

PostPosted: Tue Nov 25, 2008 2:40 pm    Post subject: About quality in NATURAL/ADABAS
Reply with quote

Hi guys,

I'm french, so sorry for my bad english ...

I'm searching information about best practices in NATURAL/ADABASE because I use a quality product at my job and I don't understand all the diagnostic because I don't know a lot about this langage/db.

I've work a long time on MVS system, but in COBOL/CICS/IMS.

I'm very stressed about these explanation because I have to support friday this analyse in front of the customer. So I have to show that I know what these diags are looking for.

If you can spend some time to explain me the real reason of these diags I give you the list :

What I understood :

Parameter data area = communication Zone betweem programme

Global data area = general view of the application on ADABAS

Local data area = local view of the application on ADABAS



And here are the diags that I don't explain me :

1 - Avoid Programs using IGNORE statement

2 - Avoid empty ON ERROR clauses in Programs .... est ce comme les handle cics ?

3 - Avoid Programs in REPORTING mode

4 - Avoid Programs using a MAP while access Adabas via a Natural View

5 - Avoid Nested Programs using IGNORE statement

6 - Avoid Programs using MOVE BY NAME .... est ce comme le MOVE CORRESPONDING ?

7 - Avoid Programs using plain UPDATE statement

8 - Avoid Programs using WHERE statement in Read operation

9 - Avoid not processing the default handling in a Switch Statement in Programs

10 - Avoid Programs using STOP and TERMINATE

11 - Avoid using WITH LIMIT(xx) in Programs

Thank's to everyone whor read this post and a lot of thank's to who can spend some time to help me.

Jean-Charles
Back to top
View user's profile Send private message

sriramp777

New User


Joined: 29 Sep 2008
Posts: 6
Location: Bangalore

PostPosted: Wed Nov 26, 2008 4:30 pm    Post subject:
Reply with quote

Hi,

1 - Avoid Programs using IGNORE statement
IGNORE stmts could be used in DECIDE ON/FOR stmts and these stmts could be avoided by having some meaningful execution of some routines. For eg, having a error routine in IGNORE clause.

2 - Avoid empty ON ERROR clauses in Programs .... est ce comme les handle cics ?
ON ERROR stmts could be coded anywhere in the program. To have a better programming practice, this is coded either in begining of the program or at the end of the program. This is to handle any unexpected errors in the program.

3 - Avoid Programs in REPORTING mode
Now a days, only Structure mode is used upon and has other advantages too to have the code in Structured mode. For eg, Better readability of the code.

4 - Avoid Programs using a MAP while access Adabas via a Natural View
Maps are used whenever we deal with any online screens ( similar to CICS maps). Nothing wrong in having the access of ADABAS along with Maps.

5 - Avoid Nested Programs using IGNORE statement
Not sure about what you mean with this.

6 - Avoid Programs using MOVE BY NAME .... est ce comme le MOVE CORRESPONDING ?
It is better to have MOVE CORRESPONDING, that is, moving based on the structure of the group or redefined variable

7 - Avoid Programs using plain UPDATE statement
Need to better careful with this UPDATE stmt, that this should be used alongwith the END TRANSACTION or the BACKOUT TRANSACTION correspondigly.

8 - Avoid Programs using WHERE statement in Read operation
Using WHERE stmt along with READ, which require more of the SIO and it is like having a complex query to fetch the information from the ADABAS Files.

9 - Avoid not processing the default handling in a Switch Statement in Programs
This is nothing but the NONE clause in the DECIDE ON/FOR stmt.


10 - Avoid Programs using STOP and TERMINATE
STOP / TERMINATE will abruptly stop the processing of the program. Nothing wrong in using this, but with appropriate error message to be thrown out.

11 - Avoid using WITH LIMIT(xx) in Programs
LIMIT will surely help us limiting the READ / FIND and it is advisable to use this LIMIT when you are not sure about when to stop the processing.

More info cud be found at http://documentation.softwareag.com/natural/default.htm

Hope this helps.

Regards,
Sam
Back to top
View user's profile Send private message
GaaZzz

New User


Joined: 24 Nov 2008
Posts: 2
Location: France

PostPosted: Wed Nov 26, 2008 9:06 pm    Post subject:
Reply with quote

Many thank's to you Sam

I'll analyse your answer immediatly

There will help me for sure

Jc
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Java & MQSeries All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Release of Adabas Cursor mohitsethi All Other Mainframe Topics 1 Mon Feb 06, 2017 8:36 pm
This topic is locked: you cannot edit posts or make replies. Natural ADABAS Opening with CTS enikhilk Mainframe Jobs 0 Wed Nov 30, 2016 5:37 pm
No new posts Casting a Binary Number to Numeric in... Bob Steinkraus Java & MQSeries 6 Tue Aug 09, 2016 5:58 pm
No new posts How Adabas works in Mainframe ranujn Java & MQSeries 5 Sat Jun 04, 2016 11:20 am
No new posts Natural/Adabas - Migration/Replatform Virendra Shambharkar Java & MQSeries 5 Tue Apr 05, 2016 2:37 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us