Posts

Basics of batch job monitoring, production support - part 2

 Hi AS400 aspirants ! Well this blog is actually a continuation of my last post, if you haven't read that I'd recommend you going through that first and come back again on this post.  Here's the link to my previous post https://sortedibmi.blogspot.com/2020/12/basics-of-batch-job-monitoring.html  Today we will try to understand - How we can find out if there is any issue or any job in MSGW. before we dive into that, let me first explain you what is MSGW (Message Wait status), In RPGLE, CLLE, there are standard exception handlers. ( We will talk about what's an exception handler in next post) if any command operation goes into error.  But, what if the programmer did not add any exception handler in the program itself, at that instance system will jump in and say, ''hey programmer, you have a piece of code that is not behaving as you intended, could you please check ?" That's essentially how you get a MSGW status for a Job. So, let's go back to our or

Basics of batch job monitoring, production support of AS400

I am assuming that the reader of this article is new to IBM i world. Congratulations on landing up in IT and working with IBM i (As/400 system). There are multiple websites which can help you in understanding batch job monitoring in IBM i, in this article I am trying to share whatever I have learnt over the past few years of my experience in IBM i (also known as AS/400). --> You can start with WRKACTJOB command, this command will show all the subsystems, job queue, jobs running in those job queue. Once you have located where your job is, you can use option 5 to pull a list of options. On this list you can find 3 important options, option 1, option 11, option 14  If you select option 1 - you will be able to see what is the job name, number and the user who submitted this job. Another good thing that you can see, if you hit page down is what command the job is executing.   If you select option 11 - you can see the call stack of program ( what is a call stack ? --> Its basically the