-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to access objects that are in Auxiliary Storage Pool (ASP) ? #47
Comments
If you call the |
@kadler I didn't try that but If you want I can give it a try. |
Yep, exactly. You'll have to do that at the same time you call your programs as every time you make a call, you'll get a new job. |
@kadler I tried below snippet didn't work it's throwing following error
|
Looks like the code as written will not call if asp_group:
itool.add(iCmd('command', "SETASPGRP({})".format(asp_group), {'error': 'on'})) |
@kadler sorry we fixed that and we are getting following message
|
@kadler any ideas ? |
My guess is that because it's coming in through a stored procedure and the default is to run in that job instead of using a spawned job, it won't let you run |
Though truthfully, I'm not an ASP expert, so I'm not sure if that will work either. |
Or instead of connecting to |
@kadler It worked when I used DirectTransport. Thank you |
@kadler Noticed when we use
we don't need stand output for this particular command but we have other commands that requires stand output to do some operation based on that. Is there way to get around the problem ? |
Do you want the display output? Not sure what you mean by "stand output", but for display output you can use iCmd5250. |
@kadler I tried with
|
Please open a new issue for this. |
I'm not a RPG developer but we are trying automate some using
ansible
onIBM I
and we came across an issue to relatedAuxiliary Storage Pool
. We have our libraries or programs inASP
and we are trying to access them viaitoolkit
. Is it possible to access viaitoolkit
?If it's not right place to ask this question, please close the issue.
The text was updated successfully, but these errors were encountered: