Hi..
was off and could not respond...but I would try making the cmdstring a
CHAR(xxx).
One example I had was to create a record with something like:
record CLCOMMANDREC type basicRecord
3 cl_cmd char(256);
3 cl_cmd_len decimal(15,5);
end
I would then set the cl_cmd_len to 256 also.
I know this example works from a generated COBOL program, so have not
tested with remote call..but should work. I am thinking the use of the
"string" datatype is causing an issue.
Also, you can define the length of the CHAR to be longer if needed...as
the QCMDEXC doc says the text can be up to 32,702 bytes... but the key is
that is fixed length (CHAR) vs variable length (string).
Mark Evans
VAGen, VAST, VAJava Product Manager and EGL Development
919-486-2488 tieline 526-2488 cell 919-656-1128
Internet mail id: evansm@xxxxxxxxxx
Lotus mail id: Mark Evans/Raleigh/IBM@IBMUS
egl-i-request@xxxxxxxxxxxx
Sent by: egl-i-bounces@xxxxxxxxxxxx
07/04/2009 01:00 PM
Please respond to
egl-i@xxxxxxxxxxxx
To
egl-i@xxxxxxxxxxxx
cc
Subject
EGL-i Digest, Vol 2, Issue 41
Send EGL-i mailing list submissions to
egl-i@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/egl-i
or, via email, send a message with subject or body 'help' to
egl-i-request@xxxxxxxxxxxx
You can reach the person managing the list at
egl-i-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of EGL-i digest..."
Today's Topics:
1. Re: Trying to execute a command on the i (Pete Hall)
2. Trying to execute a command on the i part dux (Pete Hall)
----------------------------------------------------------------------
message: 1
date: Fri, 03 Jul 2009 15:18:21 -0500
from: Pete Hall <pete@xxxxxxxxxxxxxx>
subject: Re: [EGL-i] Trying to execute a command on the i
Pete Hall wrote:
William A Smythe wrote:
Hey - here is a response from the EGL development team:
Your build descriptor is missing the linkage property to tie the
linkage to
the build descriptor. Try adding this:
<BuildDescriptor
linkage="ExternalLinkages" >
</BuildDescriptor>
That did it. Thank you VERY much. It least it talks to the remote i now.
Onward!!!
One small addendum. Although I could now contact the remote server, the
command string was not being translated to EBCDIC. I dinked around with
it for a while and finally discovered that if I changed library="%LIBL%"
to library="*LIBL", it seems happy. I also temporarily changed the
command to "DSPLIBL OUTPUT(*PRINT)" and discovered that the library list
on the i is the library list associated with the requesting user's job
description. Job QZRCSRVS was started by the signon server in response
to the request, and since my credentials were used, my default library
list was assigned to the job.
The eglbld file now looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE EGL PUBLIC "-//IBM Corporation, Inc.//DTD EGL Build Parts
6.0//EN" "">
<EGL>
<BuildDescriptor
name="Submit835BatchWebBuildOptions"
genProject="Submit835Batch"
system="WIN"
J2EE="YES"
genProperties="GLOBAL"
genDataTables="YES"
dbms="DB2"
sqlJNDIName=""
deploymentDescriptor="Submit835Batch"
serverType="TOMCAT6.X"
linkage="ExternalLinkages"
</BuildDescriptor>
<LinkageOptions name="ExternalLinkages">
<callLink >
<remoteCall pgmName="COMMANDONI"
alias="QCMDEXC"
conversionTable="CSOE037" library="*LIBL" luwControl="CLIENT"
remoteBind="GENERATION" remoteComType="JAVA400"
location="systemb.vcpi.com" remotePgmType="STATEFUL"/></callLink>
</LinkageOptions>
</EGL>
It's a lot more fun now.
midrange.com
