I have an email watch job and in the JAL I am trying to obtain the subject or message body text using either V"subject" or V"message", byt when i do this they are NULL.
I have seen an older thread about this and another paerson had the same problem.
I am using version 3.4.22
any ideas ?

cheers

Please try the following:
Enable on "job start" notification action of the JAL or VBScript type. In the job script code MessageBox "@V"subject"". Make sure the job runs synchronous and non-detached.
Save changes and send a test email, which should trigger the job. Don't run the job manually.

Please let me know if it works and whether the message box displays correct subject of the test email.

: I have an email watch job and in the JAL I am trying to obtain the subject or
: message body text using either V"subject" or
: V"message", byt when i do this they are NULL.
: I have seen an older thread about this and another paerson had the same
: problem.
: I am using version 3.4.22
: any ideas ?

: cheers

: Please try the following: Enable on "job start" notification action
: of the JAL or VBScript type. In the job script code MessageBox
: "@V"subject"". Make sure the job runs synchronous and
: non-detached.
: Save changes and send a test email, which should trigger the job. Don't run
: the job manually.

: Please let me know if it works and whether the message box displays correct
: subject of the test email.

no it doesn't work. I cannot programmatically trap either the subject or the message body as they both return NULLs.
this is a problem as this is how I wanted my job to work as I may have many jobs to run depending on an email.

I have this :
in the JAL code I have nothing.
I have ticked run asynchronous to run asynchronously.
I have selected to run when a certain email arrives
email subject and text is set to *
I have ticked Send e-mail message on job error and Run Script on Job Start on the notification events.
In the script to be execute for notification events I have :
Dim emailBody String
Dim emailSubject String
MessageBox("@V"subject"")

when I send an email the job kicks in and the message box is dislpayed but all it says is Continue ?
it doesn't seem to matter if i run this script in the job notification script or the main job script - it still doesn't work.

any ideas ?

cheers

Please email this case to support@softtreetech.com.

: no it doesn't work. I cannot programmatically trap either the subject or the
: message body as they both return NULLs.
: this is a problem as this is how I wanted my job to work as I may have many
: jobs to run depending on an email.

: I have this : in the JAL code I have nothing.
: I have ticked run asynchronous to run asynchronously.
: I have selected to run when a certain email arrives
: email subject and text is set to *
: I have ticked Send e-mail message on job error and Run Script on Job Start on
: the notification events.
: In the script to be execute for notification events I have : Dim emailBody
: String
: Dim emailSubject String
: MessageBox("@V"subject"")

: when I send an email the job kicks in and the message box is dislpayed but
: all it says is Continue ?
: it doesn't seem to matter if i run this script in the job notification script
: or the main job script - it still doesn't work.

: any ideas ?

: cheers

: Please email this case to support@softtreetech.com.
i already have - i filled out the online form this afternoon.

cheers

Hi,

Any succesfull fix for this problem yet as I may need to use a similar mechanism to allow users to trigger privileged file replication scripts ?

Thanks,

Jim

: i already have - i filled out the online form this afternoon.

: cheers

It think it is fixed in most recent version.
Here is the link to 3.4.25 http://www.softtreetech.com/24x7/fixes/3-4-25.zip
Simply unzip files to 24x7 installation dir. It also includes fixes for SyncFTPDir with SFTP protocol

: Hi,

: Any succesfull fix for this problem yet as I may need to use a similar
: mechanism to allow users to trigger privileged file replication scripts ?

: Thanks,

: Jim

Thanks,

We are currently running enterprise wide with 3.4.16 and it is a major exercise
to upgrade all production servers so is there a workaround or alternative mecahnism
which could be used to allow unprivileged users to trigger a JAL script to run ?

Thanks,

Jim

: It think it is fixed in most recent version.
: Here is the link to 3.4.25 http://www.softtreetech.com/24x7/fixes/3-4-25.zip
: Simply unzip files to 24x7 installation dir. It also includes fixes for
: SyncFTPDir with SFTP protocol

I think you misunderstood the problem. The job runs fine, but the email subject of the message that triggered the job in not available in scripts.

Anyway, if you run 24x7 as a service you cannot use email-watch jobs because MAPI access is not available to the service. A workaround for that is to use 24x7 Event Server, which can run as a service and monitor multiple POP3 mailboxes. From the Event Server you can trigger 24x7 Scheduler jobs.

: Thanks,

: We are currently running enterprise wide with 3.4.16 and it is a major
: exercise
: to upgrade all production servers so is there a workaround or alternative
: mecahnism
: which could be used to allow unprivileged users to trigger a JAL script to
: run ?

: Thanks,

: Jim

You're correct - I misunderstood extent of the problem - I only (at present) need to be able to staort the script on receipt of the email - but how do I tell if it's the "correct" email if I cannot check the subject ?

Also if I have multiple jobs how do I select whichnone to trigger using email ?

Thanks,

Jim

: I think you misunderstood the problem. The job runs fine, but the email
: subject of the message that triggered the job in not available in scripts.

: Anyway, if you run 24x7 as a service you cannot use email-watch jobs because
: MAPI access is not available to the service. A workaround for that is to
: use 24x7 Event Server, which can run as a service and monitor multiple
: POP3 mailboxes. From the Event Server you can trigger 24x7 Scheduler jobs.

You specify the desired subject/message text in the job properties and the scheduler checks if the received email matches your subject and message filter. If yes, it runs the job, otherwise the email message is marked as read and the scheduler checks for new messages again after the specified time interval.

The problem discussed in that thread was that some people wanted to use variable subjects using email filter with wildcards and then in the job script analyze the actual subject text extracting some information required for further processing. If the subject is always constant then you don't need to do anything other then to enter subject text in the job properties.

Well, to trigger different jobs you can either use different mailboxes for different jobs (with different MAPI profiles setup on the same computer) or upgrade to a more recent version and go with variable subjects as described above. Another solution is to use 24x7 Event Server, it can monitor pass the email subject text as a parameter to a batch file or any user defined program selected in the event response actions. It can be also used to write subject text to a a file and then run 24x7 Scheduler job which can read subject from the saved file.

: You're correct - I misunderstood extent of the problem - I only (at present)
: need to be able to staort the script on receipt of the email - but how do
: I tell if it's the "correct" email if I cannot check the subject
: ?

: Also if I have multiple jobs how do I select whichnone to trigger using email
: ?

: Thanks,

: Jim

I see - what about if the email is SMTP and not MAPI based ?
I seem to recollect that if the scripts are running on a scheduler
configured as an NT service you cannot use MAPI?
Or am I getting confused again and this only applies to sending mail from within the jobs ??

Jim

: You specify the desired subject/message text in the job properties and the
: scheduler checks if the received email matches your subject and message
: filter. If yes, it runs the job, otherwise the email message is marked as
: read and the scheduler checks for new messages again after the specified
: time interval.

: The problem discussed in that thread was that some people wanted to use
: variable subjects using email filter with wildcards and then in the job
: script analyze the actual subject text extracting some information
: required for further processing. If the subject is always constant then
: you don't need to do anything other then to enter subject text in the job
: properties.

: Well, to trigger different jobs you can either use different mailboxes for
: different jobs (with different MAPI profiles setup on the same computer)
: or upgrade to a more recent version and go with variable subjects as
: described above. Another solution is to use 24x7 Event Server, it can
: monitor pass the email subject text as a parameter to a batch file or any
: user defined program selected in the event response actions. It can be
: also used to write subject text to a a file and then run 24x7 Scheduler
: job which can read subject from the saved file.

24x7 Scheduler service (service mode only) and MAPI don't go together. MAPI is not available to the service, neither for sending or receiving messages.

Email-watch jobs in 24x7 Scheduler can use MAPI to check incoming emails when 24x7 is not run as a service. When running is a service it cannot check incoming email because of the MAPI.

24x7 Scheduler can use MAPI, SMTP or Lotus Notes to send email. It can use only SMTP for sending email when running as a service.

In comparison, 24x7 Event Server can run as a service only. It can watch incoming emails using POP3 protocol and it can send SMTP emails

: I see - what about if the email is SMTP and not MAPI based ?
: I seem to recollect that if the scripts are running on a scheduler
: configured as an NT service you cannot use MAPI?
: Or am I getting confused again and this only applies to sending mail from
: within the jobs ??

: Jim

O.K. - This appears to mean that even on the master scheduler system ONLY MAPI
email can be used to trigger waiting jobs ?

Jim

: 24x7 Scheduler service (service mode only) and MAPI don't go together. MAPI
: is not available to the service, neither for sending or receiving
: messages.

: Email-watch jobs in 24x7 Scheduler can use MAPI to check incoming emails when
: 24x7 is not run as a service. When running is a service it cannot check
: incoming email because of the MAPI.

: 24x7 Scheduler can use MAPI, SMTP or Lotus Notes to send email. It can use
: only SMTP for sending email when running as a service.

: In comparison, 24x7 Event Server can run as a service only. It can watch
: incoming emails using POP3 protocol and it can send SMTP emails

Yes. This is not about mater or agent, this is all about service mode or non-service mode.

: O.K. - This appears to mean that even on the master scheduler system ONLY
: MAPI
: email can be used to trigger waiting jobs ?

: Jim