Giter Site home page Giter Site logo

Comments (9)

kadler avatar kadler commented on May 29, 2024

Original comment by Kevin Adler (Bitbucket: kadler, GitHub: kadler).


This is an upstream XMLSERVICE bug: https://bitbucket.org/inext/xmlservice-rpg/issues/17/calling-xmlservice-from-a-64-bit-pase-job

For now, the workaround is to use the database transport:

#!python
# Instead of this
from itoolkit.lib.ilibcall import *
itransport = iLibCall()

# Do this
from itoolkit.db2.idb2call import *
itransport = iDB2Call()

from python-itoolkit.

kadler avatar kadler commented on May 29, 2024

New XMLSERVICE bug is IBM/xmlservice#17

from python-itoolkit.

dmabupt avatar dmabupt commented on May 29, 2024

Original comment by Kevin Adler (Bitbucket: kadler, GitHub: kadler).

This is an upstream XMLSERVICE bug: https://bitbucket.org/inext/xmlservice-rpg/issues/17/calling-xmlservice-from-a-64-bit-pase-job

For now, the workaround is to use the database transport:

#!python
# Instead of this
from itoolkit.lib.ilibcall import *
itransport = iLibCall()

# Do this
from itoolkit.db2.idb2call import *
itransport = iDb2Call()

@kadler
It should be uppercased B ->itransport = iDB2Call() , not iDb2Call()

from python-itoolkit.

jkyeung avatar jkyeung commented on May 29, 2024

@kadler
It should be uppercased B ->itransport = iDB2Call() , not iDb2Call()

@dmabupt - Ah. Actually, it should be Db2, since that is consistent with IBM's current branding. However, it does look like the actual code in itoolkit.db2.idb2call still has a class named iDB2Call. It's probably reasonable to make an alias there, like

iDb2Call = iDB2Call

or vice versa.

from python-itoolkit.

kadler avatar kadler commented on May 29, 2024

@jkyeung That would make sense to do, if all the i*Call transports weren't going to be deprecated in the next release anyway.

from python-itoolkit.

ramstein74 avatar ramstein74 commented on May 29, 2024

Hello Kevin
this is my code :
from itoolkit import *
from itoolkit.db2.idb2call import *
itransport = iDB2Call()
itool = iToolKit()

itool.add(iCmd('addlib1', 'addlible SICGA00F55'))
itool.add(iCmd('addlib2', 'addlible $$CLI00F55'))
itool.add(iCmd('addlib3', 'addlible $$CLI00O'))
itool.add(iCmd('callpgm', "CALL PGM($$CLI00O/OC005) PARM(X'001F' X'0056217F' ' ' )"))
itool.call(itransport)
data = itool.dict_out()
print(data)

this is the result :
4.3:zeta@~/pyWork> python3 rpg1.py
{'addlib1': {'success': '+++ success addlible SICGA00F55'}, 'addlib2': {'success': '+++ success addlible $$CLI00F55'}, 'addlib3': {'success': '+++ success addlible $$CLI00O'}, 'callpgm': {'success': "+++ success CALL PGM($$CLI00O/OC005) PARM(X'001F' X'0056217F' ' ' )"}}

all i see is success , however the call
CALL PGM($$CLI00O/OC005) PARM(X'001F' X'0056217F' ' ' )
does not call the programm OC005.
How can i debug it ?

Also i tried this approach to call my program :

itool.add(
iPgm('my_key','OC005')
.addParm(iData('gcnusr','1','2p0'))
.addParm(iData('gcnuec','56217','6p0'))
.addParm(iData('$status','1a',' '))
)
but always returns error!!!
4.3:zeta@~/pyWork> python3 rpg1.py
{'addlib1': {'success': '+++ success addlible SICGA00F55'}, 'addlib2': {'success': '+++ success addlible $$CLI00F55'}, 'addlib3': {'success': '+++ success addlible $$CLI00O'}, 'my_key': {'error': '*** error OC005', 'version': 'XML Toolkit 1.9.9.3', 'xmlhint': 'p(44) 2p0 ', 'xmlhint1': 'p(69) <data type="1" var="gcnusr"', 'xmlhint2': 'p(69) 2p0', 'xmlhint3': 'p(69) 0000000000000000', 'xmlhint4': 'p(44) <parm io="both" var="p1"', 'xmlhint5': 'p(44) 2p0 ', 'xmlhint6': '<parm io="both"', 'xmlhint7': 'p(44) <parm io="both" var="p1"', 'xmlhint8': 'p(44) 2p0 ', 'jobipc': '*na', 'jobipcskey': 'FFFFFFFF', 'jobname': 'QSQSRVR', 'jobuser': 'QUSER', 'jobnbr': '167411', 'curuser': 'RAMOS', 'ccsid': '1140', 'dftccsid': '1140', 'paseccsid': '819', 'syslibl': 'QCIRES QSYS QSYS2 QHLPSYS QUSRSYS UTILIT', 'usrlibl': '$$CLI00O $$CLI00F55 SICGA00F55 QGPL QTEMP QFNTCPL300 QFNTCPL QFNT09'}}

any help ?

Regards

from python-itoolkit.

kadler avatar kadler commented on May 29, 2024

@ramstein74 Seems like a different issue than this one - please open a separate issue.

from python-itoolkit.

richardschoen avatar richardschoen commented on May 29, 2024

Whew, good thing this was documented. I was banging my head trying to get iLibCall to work today :-)

from python-itoolkit.

kadler avatar kadler commented on May 29, 2024

This is fixed in XMLSERVICE 2.0.1. The necessary PTFs are now documented in here an the code will now attempt to detect this condition and raise an exception with the PTF numbers in the exception message.

from python-itoolkit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.