Invoking helproutine from MAP

monasu1998 · Active User Joined: 23 Dec 2005 Posts: 176 Location: India

Hi,

After a long time I have got to post a crucial (for me) query in this forum.
The requirement first:
I have a map and for a specific field I need the NEW(replacing the older one) helproutine to work for me.
The problem:
I have an existing PDA defined for the MAP. This Data area is populated with data from a call to COBOL program.
Now my aim is to pull some more data(3 more variables) thru the COBOL program and pass these 3 varaibles to the Helproutine during invoking the Helproutine.

I am succeeding till the time I get these 3 variables populated from the COBOL call. But when the INPUT USING map is getting executed, it is giving me the error 936 (format/length conflict).

I have STOWed all the modules in proper sequence(I hope). But always the error is the same.

The variables I declared in PDA are
#CTX-ID A 40
#PROCESS A 8
#HDL-ACT N 3

I have passed these 3 variables to the Helproutine from the HE= in the MAP

But to my surprise, when I listed the MAP(Not in EDIT), I have seen that
DEFINE DATA PARAMETER
1 #BLOCKAGE (A005)
1#CTX-ID (N7.0)
-----
------
----
1 #PROCESS (N7.0)----
-----
1 #HDL-ACT-ID (N7,0)

I do not understand, from where this format/length is coming.

And finally when the INPUT statement is getting executed, the error comes as
Format/Length conflict in parameter (Map MVSMP01M).

I doc has been attached for reference.

I hope I am clear with my problem. If not, I am here to clarify.

Thanks in Advance

monasu1998 · Active User Joined: 23 Dec 2005 Posts: 176 Location: India

Hi All,

I am sorry in posting the answer to this post after a long time.

Here goes the answer

In general when we change the parameters to the helproutine, Natural system takes the default format and length as N7,0 even if we define the variables in Data area with our own format/length.

In this case what we have to do is go the map editor.

Display the variable definition
Press PF9 (Parameter) and then modify the format/length and save the map.

This resolves this problem.

dick scherrer · Posted: Wed Nov 11, 2009 12:20 am

Thank you for letting us know

Hopefully, it will help someone else one day,

d