Binding service programs on the iSeries

[Roy Wilsker]

We would appreciate anyone's help with the following issue:

We are in the midst of implementing EnterpriseOne (version 8.95 with the 8.11 tools set) and trying to bind BSFNs to RPG service programs. We have not been able to find the right jde.ini parameters to make this work. We get the following error in the joblog:

30 03/15/06 08:22:02.094352 QCANPARS QSYS 0625 JDELIB
To module . . . . . . . . . : JDE400U
To procedure . . . . . . . : ExecuteCmd
Statement . . . . . . . . . : 13
Message . . . . : Qualifier missing from qualified
name 'THCGPRDDV '.
Cause . . . . . : A qualifier delimiter character was
specified, but no qualifier was found.
Recovery . . . : Specify the missing qualifier or
specify *N if no value is required for the qualifier.

We need to use this functionality to connect to legacy code which needs to be called in a highly efficient manner.

Thanks in advance for any help.

 

[richardjackson]

I don't know the answer to your question but no-one else posted a suggestion so here are some ideas to start thinking about the problem.

The error is coming from the IBM command analyzer QCA. This is the program that validates command parameters and calls command processing programs. Some command parameter is being passed as blank but the underlying command wants a value. The blank value is part of a qualified name as in "lib/file". It would be helpful to know what command generated this message, figure out which parameter value is missing then work backwards to the solution. It could be an IBM command or a JDE-created command (what does the value JDELIB in the error message header line mean in this case?). The error suggests a missing name in a qualified name -- library, service program, table, a *LIBL command parameter...something like that. Contemplate the business function creation parameters in the INI file.

You might also check to see if you turned on Use Owner on a data source. That inserts a dot in front of table names and then, when sending SQL to the server, inserts the database table owner. If the owner name in the data sourceis blank, you get ".name". The leading dot might be telling the command analyzer that this is part of a qualified name and trigger that error message. Dot was the qualified name separator in an ancient version of the iSeries product, the genes to respond to a leading or trailing dot may still exist in the command analyzer code.

Richard Jackson

[ QUOTE ]
We would appreciate anyone's help with the following issue:

We are in the midst of implementing EnterpriseOne (version 8.95 with the 8.11 tools set) and trying to bind BSFNs to RPG service programs. We have not been able to find the right jde.ini parameters to make this work. We get the following error in the joblog:

30 03/15/06 08:22:02.094352 QCANPARS QSYS 0625 JDELIB
To module . . . . . . . . . : JDE400U
To procedure . . . . . . . : ExecuteCmd
Statement . . . . . . . . . : 13
Message . . . . : Qualifier missing from qualified
name 'THCGPRDDV '.
Cause . . . . . : A qualifier delimiter character was
specified, but no qualifier was found.
Recovery . . . : Specify the missing qualifier or
specify *N if no value is required for the qualifier.

We need to use this functionality to connect to legacy code which needs to be called in a highly efficient manner.

Thanks in advance for any help.

[/ QUOTE ]

 

[oneEyedJack]

How did you attempt to bind? Did you modify the JDE.INI file? Do you have a copy of the cmd that's failing? Did the job that attempted to process the cmd fail? If so, do you have a spoolfile with the callstack?

 

[oneEyedJack]

Troubleshooting such problems is easier if you have the command that failed. Do you have it? If so, try copy/pasting it to green screen command line and see what happens. You might need to set up such things as the correct library list to allow the command to execute correctly.