Skip to main content

Someone is using initialize (which works fine in unmanaged code) to initialize linkage.

He says the pic x's are correctly set to spaces, but numerics are not set to zero.  Is there more involved?

Thanks.


#managed

Someone is using initialize (which works fine in unmanaged code) to initialize linkage.

He says the pic x's are correctly set to spaces, but numerics are not set to zero.  Is there more involved?

Thanks.


#managed

I cannot reproduce this behavior. It works fine for me.

Can you please provide a small example of what you are doing?

Thanks.

I cannot reproduce this behavior. It works fine for me.

Can you please provide a small example of what you are doing?

Thanks.

He says heI can't initialize the linkage record (using a simple initialize statement) in a new program using the ILSMARTLINK directive.  I don't have an example unfortunately.

He says heI can't initialize the linkage record (using a simple initialize statement) in a new program using the ILSMARTLINK directive.  I don't have an example unfortunately.

I cannot reproduce this using VC 7.0 PU7.

What product version are you using?

Is it a COBOL main program that is calling the subprogram or is it C# or something else?

I cannot reproduce this using VC 7.0 PU7.

What product version are you using?

Is it a COBOL main program that is calling the subprogram or is it C# or something else?

The problem occurred when initializing the linkage record of a called COBOL program from another COBOL program.

The problem occurred when initializing the linkage record of a called COBOL program from another COBOL program.

Does it work if the ilsmartlinkage directive is not set?

I cannot replicate that behavior. I will need an example from you that fails.

Does it work if the ilsmartlinkage directive is not set?

I cannot replicate that behavior. I will need an example from you that fails.

Hi, we are on Micro Focus Visual COBOL 5.0 Version 5.0.00077.- wionder if that has to do with it...

Hi, we are on Micro Focus Visual COBOL 5.0 Version 5.0.00077.- wionder if that has to do with it...

I just tested this on V5.0 as well and I cannot reproduce the problem with my test program. I would recommend that you open up a support incident and attach a cutdown project that replicates the behavior.

Terms & ConditionsAccessibility statement