Age vs. Youth, and Rebooting Your Value
CAMUS schedules manufacturing meeting on epic date for 3000 managers

Vladimir resolves a 3000 jobs question

More than one kind of jobs question is on the landscape this year.  The most obvious question is how to keep your job as the head coach of a vital 3000 server in your organization. The other question, which has been on the table since 2002, is how to manage jobs on the server where your applications will run, after your organization makes its transition.

There are too many answers to the first question to list them all here. I invite you to send us helpful answers. Based on your responses, we can pay them forward. On Friday Oct. 25, I wrote about one answer: Be an entrepreneur for the first time in your life, even while you're older than 55. It's the biggest age group of entrepreneurs. Another answer might be to master a more nouveau environment for apps. Your value on MPE/iX is kept vital, but mostly because you've acquired new skills for an environment that runs alongside MPE/iX. Be ready, in that case, to embrace more change, plus adopt respect for much younger colleagues.

The second jobs question has not had good answers for Windows -- the migrator's favorite platform -- until 2011. Then MB Foster released a scheduler that replicates the power of MPE/iX scheduling and jobstream management. MBF-Scheduler was built by developers who were masters of MPE/iX jobs.

But the third aspect of a jobs question emerged in the past week from a longtime, advanced MPE manager, Tracy Johnson. Working at Measurement Specialties -- one of the strongest and most devoted users of MPE/iX servers, running 10 factories around the world -- Johnson posed a question about job numbers.

'What's the highest job number allowed before it rolls back to #J1?"

VEsoft's founder Vladmir Volokh gave Johnson an answer, according to the manager. It resolves an everyday need, even though other answers came from experts with decades of MPE/iX experience. Vladimir's name isn't invoked a lot on the 3000 newsgroup where the question emerged. Johnson tagged the answer as one of the best. But that's because he talked with the creator of MPEX.

"I'm using MPEX in a night job that cleans up old spool files after midnight," Johnson told me this afternoon.

I really care how to set the job number, using MPEX:

%deletespoolfile @.@.@(spool.readydate < today-7)

-----Deleting #O...

... several hundred spool files later...

-----Deleting #O315330, $STDLIST, #J1225, MMAUDJAS,MANAGER.MMV090 (704 sectors)

The above $STDLIST was created the same day, (not > seven days before)

I have noticed this symptom occurs after JOB numbers have rolled over from #J16383 back to #J1, so I there must be a counter when using spool filesets.  In other words, it happily deletes spool files it finds using the date criteria, (working sequentially). But when the job number rolls back to one, it assumes the next spool file with a lower job number encountered is "earlier" than the one before it. (#J1 must be 'earlier' than #J16383, yes?)

Via a phone conversation -- how fundamental, that old-school contact -- Johnson learned this about 3000 jobs:

Before the fix:

%deletespoolfile @.@.@(spool.readydate < today-7)

After the fix: