TMG channel RPC issue

[elanchezhiyank]

Even after installing TMG1-1.0-9 KID, the issue exist. No RPC details like routine,tag,input parameter information are created.
 I'm able to find the routines in r directory.

Press <RETURN> to see more, '' to exit this list, OR
CHOOSE 1-10: 5 TMG CHANNEL
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number

    (IEN)

NUMBER: 2324 NAME: TMG CHANNEL

there is case difference between the Labels in TMGRPC1D and calling program TMGUSRIF. Gives error while importing TMG-CPRS-IMAGING-1.0-1.KIDS

please paste the TMG CHANNEL RPC details and let me tryout manually.

[Kevin Toppenberg (kdtop3)]

Thank you for locating and reporting this bug.

I am attaching a KIDS file that I hope will correct this problem. I will get it up with the other patches with my next release cycle. But I wanted to get it to you earlier.

About the missing TMG CHANNEL, I don't understand why it is missing. I tried to include it in the attached patch, but maybe I am doing something wrong on the patch creation.

Just in case, I am including a dump of the RPC below.

I hope that helps.

  -= RECORD DUMPER =-

Select FILE (or SUBFILE): remote proc
Select entry in file# 8994
Select REMOTE PROCEDURE NAME: TMG CHANNEL
#: 2379,
#: 2379,
Display empty fields? No// (No)
Enter Output Device: HOME// TELNET

Record# 2379, in FILE: 8994
   .01-NAME : TMG CHANNEL
   .02-TAG : CHANNEL
   .03-ROUTINE : TMGRPC3
   .04-RETURN VALUE TYPE : ARRAY
   .08-WORD WRAP ON : TRUE
   .09-VERSION : 1
     1-DESCRIPTION :
  This RPC will be used to pass multiple requests back
  and forth from client to server

     2-INPUT PARAMETER :
       Multiple Entry #1
       .01-INPUT PARAMETER : INPUT
       .02-PARAMETER TYPE : WORD PROCESSING
       .04-REQUIRED : YES
       .05-SEQUENCE NUMBER : 1
         1-DESCRIPTION :
      This is the data array sent from client.
      Format still to be decided.

     3-RETURN PARAMETER DESCRIPTION :
  This is the result array passed from server back to client.
  Format still to be decided.
  See documentation in CHANNEL^TMGRPC3