Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
Page 1 / 1
Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
I think an interactive session (WEBEX) should help address your questions. I will contact you via your support case 00786068.
Regards
Jay
Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
In addition to working with Support, I thought you'd appreciate some links to places where you can find additional documentation on how to work with ILE in LM(i):
- First, log in to the Rocket Customer Portal here
- If you don't have a sign in, you can request one down in the bottom right under the "sign in" bar.
- Click on the menu bar that says "Knowledge Base" and do a search on "ILE". There are three documents there.
- Click on the menu bar that says "Documentation" and do a search on "ILE". You will find some hits under the Rocket Aldon Lifecycle Manager IBM i Edition in the Daily Operation Reference, the General Topics Reference and in the Setup/Administration Reference.
Joe
Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
Yes, I come from the Turnover world, so I am still learning to speak Aldon. I am looking for a simple step-by-step to create a service program. I would expect to create the module, a copy source with the interface, a bindery source (not a binding directory), and the instructions to wrap the pieces together as the final service program? See samples.
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
How does Aldon deal with the service program and signatures once we start using the tools and keeping the consumers up to date?
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.