NT bat file to Perl script conversion

By jcabe ·
I am trying to take a system that uses BAT files on NT and convert them to Perl Scripts. I am going to run the Perl scripts from Windows scheduler, and I need to know if I schedule them to run as root on the box if the schedule will always be active? Where if it is schedulled as a user it appears that the user has to be logged in. I am not a NT admin and I don't know if our admins are running schedulled jobs on this box.

I am a long time UNIX/Linux KSH/Perl developer and am trying to convert the bat files to a more standard modular platform.

Any suggestions or insight are appreciated.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

AT command in NT

by Toivo Talikka In reply to NT bat file to Perl scrip ...

If you want to find out if the BAT files were scheduled jobs under NT, go to the command prompt while logged in as Administrator and type in AT. If the scheduler is running, you will get the list of the scheduled jobs.

The user Administrator has the same power as the root user in Unix/Linux. If a username belongs to the local user group Administrators, it is the same as a Linux user belonging to the group root.

If your platform is now Windows XP or Windows Server 2003 and you are setting up the job to run unattended through the scheduler, you should be able to test it by specifying the username and password during the setup of the scheduled job, whether the user has to be the Administrator or not. If you view the details of the scheduled jobs folder, you will see the last status code of how the job finished.

Collapse -


by jcabe In reply to AT command in NT

I am an administrative user on the box.
It is great to hear tha there doesn't need to be an active session on the server for the jobs to run. I didn't know if the jobs had to run as root or if they could run as other non-logged on users on the box out of scheduler.

We have some Cognos stuff running on the server that we are going to have to migrate to use Cognos macros. Currently they login and leave an open session running to keep the login security open for the one session. The batch processes take advantage of the secure established connection since they are schedulled under that user name. There are no security issues since it is running on a secure network to build the data. It then deploys the data via a different server that can be reached via the internet.
I think my root challenge will be Cognos at this point, since the open session onthe server has to go away.

Related Discussions

Related Forums