View previous topic :: View next topic
|
Author |
Message |
chitanya
New User
Joined: 25 Jan 2008 Posts: 6 Location: Hyderabad
|
|
|
|
Hi
Can anyone please help me to know the usage of QENTERS and QMVC macros in assembler s/390.
I need syntax format also.
Thanks in advance... |
|
Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
|
|
|
|
AFAIK, these aren't documented IBM Assembler Macros and they're probably "In-House" written (IE: Site Specific).
Have you consulted with any of your colleagues?
When you view the source, is there any documentation (comments) within the Macro's themselves regarding their origin and/or usage?
Regards, |
|
Back to top |
|
|
chitanya
New User
Joined: 25 Jan 2008 Posts: 6 Location: Hyderabad
|
|
|
|
I am not an expert in assembler need to convert a assembler programs to cobol program.
I found QENTERS at the starting line of the program
Code: |
CA015M04 QENTERS 'CA015M04 - RECORD CREATION AND AMENDMENTS',R11,R10
CA015M04 AMODE 31
CA015M04 RMODE ANY
SPACE 3
|
Please i need the format or need of the instruction to decode into cobol |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
You asked 15 days ago and You got a reasonable answer
QENTERS and QMVC are not standard IBM macros
ask somebody inside Your organization
at first glance QENTERS looks like a macro to carry on the initial housekeeping in the assembler program
it does not have an equivalent High Level Language equivalent |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
When converting from assembler to cobol, it is not a good proctice to try to convert line by line. . .
A far better approach is to understand what business process is provided by the assembler code and write cobol code that provides the same functionality. Many things in assembler do not have a 1-to-1 equivelent in cobol. The part of the assembler code that requires the best understanding is the implementation of business rules - not "housekeeping" and file definition/access.
Both programs should be able to read the input and produce the exact same output. |
|
Back to top |
|
|
|