It *appears* that upgrading to Torque 2.1.0 worked for me. At least, I no longer see a response of the original 32, but rather the value I set it to system-wide. Dan W. > > > So I submit a job, through Torque, and I simply execute a "ulimit -l" > > > only to find that my limit is set to the original value, 32. Using a