Home
Contact Us
Products
benefits
customers
resources
services
support
corporate

Technical FAQ

1. I can see from the Event Log Enquiry that SMS Messages have attempted to be sent out from the iSeries and that they are failing? Any ideas?

2. I have a Novagem Cellular Connection Kit. How do I set it up to use it?
Where do I attach it?


3. I wish to set up EOM to monitor my Windows Servers. How do I do this?

4. I had to remove and re-install the Windows Client but now the Windows Event Log Enquiry is not being updated.

5. How do I check what happened to my remote message reply or command that I sent back to the iSeries?

6. I currently use the EOM report scanner to E-mail reports around as PDFs, Word Documents and Excel spreadsheets. Is it possible for these reports to be placed directly onto the Hard Drive of Users' PCs?

7. I use the Rota and Escalation function in order the direct messages to the relevant on-call staff. I wish to override this rota in order to handle staff holidays, absences etc. How can I do this?

8. Within the Scheduler, we run a command when any job step ends abnormally. We have entered individual Abnormal EOJ commands from steps 10 to 70 and the same command is run if any part of the job ends abnormally. Is there any easier way to handle this rather than have to re-type the same command for each step?

9. I have a Batch Job that runs overnight. Sometimes it will error with a MSGW and EOM will pick that out and message me, but sometimes it will not error and will continuously sit in LCKW until somebody arrives at the office in the morning and ends the Job, by which time all overnight jobs are running late which in-turn stops users from doing any work on the system. Is there any way to monitor for this happening?

1. I can see from the Event Log Enquiry that SMS Messages have attempted to be sent out from the iSeries and that they are failing? Any ideas?

For Modems: Failed message attempts are logged within Active Control Centre. This option is available from the Communicator Menu, Option 9- Active Control Centre . The details within the error logs may help you to pinpoint the issue. Place the cursor over the error log entry at the bottom of the screen and press F4. This will give you a description of the error such as No Dialtone etc. Ensure that the modem is switched on, attached to the v24 cable on the iSeries, the resource that it is on is correct and that the phone line it is going into is a fully operational phone socket without any barring to calling '07' numbers. Is the phone line going through a switchboard which would need a prefix of a '9,'. If this is so, this can be changed within Define Module Options- Option 8- Configure Land Line Modem Parameters . If the modem is an ECS modem, is it in Asynchronous or Synchronous Mode? Are the DIP switch settings correct (see EOM User Guide) and was the line created correctly using the NMSCRTLIN command? Use Option 72 from the Communicator Menu to verify the modem installation. When sending land-line SMS messages, we recommend using the command NMSSMS.

For Cellular Connection Kits: Failed message attempts are logged within Active Control Centre. This option is available from the Communicator Menu, Option 9- Active Control Centre . The details within the error logs may help you to pinpoint the issue. Place the cursor over the error log entry at the bottom of the screen and press F4. This will give you a description of the error. Ensure that the Cellular Kit is powered on, the SIM card is inserted correctly and that either a red or green steady light is flashing. If the light is not flashing then it is probable that the SIM card has a PIN lock which needs removing. Place the antennae in a high position to improve reception. Ensure the line created using the NMSCRTLIN command is on the correct resource entered. Use Option 71 from the Communicator Menu to verify the Cellular kit installation. When sending messages via the CCK, either the command NMSSMSMOB should be used or the Users Details within Common Module Setup should have an Event Type of 'Y'.
back to top

2. I have a Novagem Cellular Connection Kit. How do I set it up to use it? Where do I attach it?

The Novagem Cellular Connection Kit should simply be attached to the V24 cable from the iSeries machine. If you had a modem line for use with our software (Line Description of NMSTELNxx) then this should be removed. Use the command NMSCRTLIN to create a new line for the CCK. Use Option 71 from the Communicator Menu to verify the Cellular kit installation.
back to top

3. I wish to set up EOM to monitor my Windows Servers. How do I do this?

Firstly, you will need to install the Windows Client (via the EOM CD or from our Website) onto the desired Windows machine. Once the install is complete, the directory C:\NMS41WIN must be shared to allow access to it.

On the iSeries, from the System Manager Menu, take Option 1 - Define Module Options . From within this, take Option 10- Configure Windows Monitored Hosts . Enter the machine name here. Note: If the User ID and Password on the iSeries you are working from is different to the User ID and password on the Windows Machines, then an error may be displayed saying that the machine's directory NMS41WIN cannot be seen. This is normal. The User ID and passwords on both machines must be exactly the same otherwise Microsoft Security will not allow access to the machine. Therefore, make the User ID that the NMSWINMON runs under and a User ID on the PC match each-other.
back to top

4. I had to remove and re-install the Windows Client but now the Windows Event Log Enquiry is not being updated.

Whenever the Client software is re-installed, the Windows Monitor (NMSWINMON) must be re-started.
back to top

5. How do I check what happened to my remote message reply or command that I sent back to the iSeries?

When you run a command via Mobile phone, the outcome of the command (i.e. Any reason for failure or confirmation of success) is sent back to the Mobile Phone. From the Communicator Menu, take Option 1- Define Module Options . Now take Option 6- Configure Cellular Connection Kit Parameters . Check the Inbound Gateway SMS Command Level. Level 1 disallows any commands to be run, Level 2 checks authority against the PIN number provided to see if the command is allowed to be run and Level 3 will allow all commands to be run.

Return to the Communicator Menu and take Option 22- Inbound SMS Gateway Audit Enquiry . This will display what has been read in from the Cellular Connection Kit. Ensure that the command is syntactically correct and then the PIN number parameter and Message Key parameters are correct. Also you can use Option 9- Active Control Centre . Look at the error logs at the bottom of the screen and there will be entry with the word NMSR within it. Place the cursor upon this and press F4. This will explain what details were incorrect within the command sent to the iSeries.
back to top

6. I currently use the EOM report scanner to E-mail reports around as PDFs, Word Documents and Excel spreadsheets. Is it possible for these reports to be placed directly onto the Hard Drive of Users' PCs? >

Yes. From the Common Module Setup Menu, take Option 3- Define EOM Users . Place the cursor upon the User and press F9. Currently, if this User is receiving reports via E-mail, then there will be an Event Type of 'B' present along with the Users' E-mail address. Change the 'B' to a 'C' and in the command to run field type NMSCPY and press F4. Specify the path name to the PC from the iSeries here. Considerations have to be taken with regards to accessing the PC's drive from the report scanner. If the User ID and Password on the iSeries that the report scanner is running under is different to the User ID and password on the PC, then NMSREPMON will be unable to place anything into the PC directory. The User ID and passwords on both machines must be exactly the same otherwise Microsoft Security will not allow access to the machine. Therefore, add a User ID on the PC Server to match the name which NMSREPMON is running under.
back to top

7. I use the Rota and Escalation function in order the direct messages to the relevant on-call staff. I wish to override this rota in order to handle staff holidays, absences etc. How can I do this ?

There are a couple of ways of achieving this. From the Common Module Setup Menu, take Option 21- Alert Rota Maintenance . A single manual entry can be added by pressing F6 and entering the relevant details. If you wish to add a selection of manual entries the press F22. This will display a Calendar. Place an 'X' against the required dates and specify the times that the staff should be included or excluded from the Rota.
back to top

8. Within the Scheduler, we run a command when any job step ends abnormally. We have entered individual Abnormal EOJ commands from steps 10 to 70 and the same command is run if any part of the job ends abnormally. Is there any easier way to handle this rather than have to re-type the same command for each step?

Yes there is. Within any of the Sequence Add/Amend Sequence details screens, press F7. This will display a Command to Run on Normal and Abnormal EOJ. The Command to Run on Normal EOJ is the command that will be run when ALL job steps within the schedule entry have completed normally. If a Normal EOJ Command has been entered against an individual job step, then this would override the Global Normal EOJ command. The Command to Run on Abnormal EOJ will be run if ANY of the job steps end abnormally. If an Abnormal EOJ Command has been entered against an individual job step, then this will override the Global Abnormal EOJ Command entered here.
back to top

9. I have a Batch Job that runs overnight. Sometimes it will error with a MSGW and EOM will pick that out and message me, but sometimes it will not error and will continuously sit in LCKW until somebody arrives at the office in the morning and ends the Job, by which time all overnight jobs are running late which in-turn stops users from doing any work on the system. Is there any way to monitor for this happening?

There are two ways to monitor for this event occuring. Within EOM Scheduler, place the cursor upon the entry in question and press F4. From this screen, press F9. The 'Maintain Event Parameters' screen will be displayed. Within this screen, you can specify that if this job takes over a specified amount of time to run or this job runs too quickly, it will send out an Alert.

Alternatively, from the System Manager Menu, take Option 7- Define Object Monitors . From within this, take Option 10- Define Monitored Batch Jobs . Place the cursor upon the 'Monitored Status' parameter and press F4. This will display all the statuses that EOM can monitor batch jobs for. Select LCKW as a Monitored Status and bring the cursor down to the Duration parameter. Press the Page Down key and complete the Command(s) to Run and Alert Group parameters. This entry would now read that if any Batch Job is in LCKW for a longer duration than specified here, commands and Alerts can be executed.
back to top

 

our solutions
our customers
how can we help you
© Novagem Ltd 1989 - 2016  
privacy
web terms