In fact, the command is xPJES2, where x is what is specified as CONCHAR=
on the CONDEF init statement. The default is $ but you may want to
select something else for a secondary JES.
2 more comments:
That CONCHAR (in case of my alternate JES a .) also precedes HASP-Messages.
They look like this:
In [EMAIL PROTECTED], on 01/04/2006
at 11:32 AM, Edward E. Jaffe [EMAIL PROTECTED] said:
|Cmd JobName StepName ProcStep
|--- /
|VTAM VTAM VTAM
Perhaps at your shop, but I've got IBM documentation that calls for a
proc name of NET.
--
Shmuel
Since this was originally a discussion related to SUBSYSTEMs:
VTAM is not a subsystem.
It doesn't listen on the SSI for commands but seems to get
its commands internally from the MVS command handler.
Peter Hunkeler
Credit Suisse - Information Technology
Baloney. Here is the start of the IEFSSNxx member from my Test system
called MVS4 so JES2 runs as JES4;
SUBSYS SUBNAME(JES4) /* JES4 IS THE PRIMARY SUBSYSTEM NAME */
PRIMARY(YES) START(YES)
Two questions:
1,here you use 'JES4' and maybe I could use another name such as
'ABCD'.Then,
how
Also remember that the command to shut it down is $PJES2, not $PJES4.
In fact, the command is xPJES2, where x is what is specified as CONCHAR=
on the CONDEF init statement. The default is $ but you may want to
select
something else for a secondary JES.
Peter Hunkeler
Credit Suisse -
2,START(YES),means that system will automatically issue a START
command to invoke JES2 procedure. However,which procedure name
system'll use in STARTcommand? S JES4?
First an answer to your second Q (it's a short one): The SUBNAME.
1,here you use 'JES4' and maybe I could use another name such
On Wed, 4 Jan 2006 16:32:27 +0800, Johnny Luo
[EMAIL PROTECTED] wrote:
Two questions:
1,here you use 'JES4' and maybe I could use another name such as
'ABCD'.Then,
how could the system know that the subsystem you want to initialize is
JES2?
Put it in another word,how to establish the
In
![EMAIL PROTECTED],
on 01/03/2006
at 08:14 AM, Lizette Koehler [EMAIL PROTECTED] said:
The main reason is that every piece of documentation is for JES2.
You might get someone confused at operations or Level2 if you say my
JESA system is down. Trust me, you do not want to confuse Level2 at
Shmuel Metz (Seymour J.) wrote:
Why would you say my JESA system is down? The name of the component
is JES2, regardless of the name of the cataloged procedure used to
start it. Would you describe a VTAM problem as my NET is down?
|Cmd JobName StepName ProcStep
|--- /
In a message dated 1/4/2006 1:32:47 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Cmd JobName StepName ProcStep
|--- /
| VTAM VTAM VTAM
Kinda of a special case. ===c vtam or ===z net,quick
Short answer is that the primary subsystem (for JES2) must be
named JES2
Someone may have already mentioned this but when JES2 and JES3
initialize, they mark their SSCT entry that the subsystem is
either JES2 or JES3 in the SSCTSSID byte. So if you are
looking for the JES2 subsystem, you
On 1/5/06, David Alcock [EMAIL PROTECTED] wrote:
Short answer is that the primary subsystem (for JES2) must be
named JES2
Someone may have already mentioned this but when JES2 and JES3
initialize, they mark their SSCT entry that the subsystem is
either JES2 or JES3 in the SSCTSSID byte.
New to mainframe..so the question maybe look a little silly.
Here is what IEFSSN00 of our site defines JES2:
SUBSYS SUBNAME(JES2) /* JES2 AS PRIMARY SUBSYSTEM */
PRIMARY(YES) START(NO)
My question is concerning parmameter SUBNAME:
Is it true that it must be the same name as JES2 procedure?
Short answer is that the primary subsystem (for JES2) must be named JES2
and the procedure must have the same name.
Johnny Luo wrote:
New to mainframe..so the question maybe look a little silly.
Here is what IEFSSN00 of our site defines JES2:
SUBSYS SUBNAME(JES2) /* JES2 AS PRIMARY SUBSYSTEM
: Tuesday, January 03, 2006 10:04 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Define and start JES2
Short answer is that the primary subsystem (for JES2) must be named JES2
and the procedure must have the same name.
Johnny Luo wrote:
New to mainframe..so the question maybe look a little silly.
Here
You will probably get different answers on this question. Here is my
answer.
My memory says that the MAIN JES2 Subsystem needs to be JES2. If you define
addition JES2 subsystems (secondary) then they can be JESA, JESB, etc...
The main reason is that every piece of documentation is for JES2.
No matter what you name it, keep the PROC and SUBNAME names in
sync. An STC whose name matches a subsystem name is started
under the MASTER instead of under the primary JES, which is what
you want for JESx. (Otherwise, you would need to explicitly specify
SUB=MSTR on the start command.)
And,
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Johnny Luo
Sent: Tuesday, January 03, 2006 7:47 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Define and start JES2
New to mainframe..so the question maybe look a little silly.
Here is what
I believe that you are incorrect. We had one
system in our sysplex have a JES2 running as
JESR for several years. No problems at all.
We had a three site complex with JES2 at two
sites and JES3 at another.
We always called the sub-systems 'JES', with
no number. It made automation easier.
Short answer is that the primary subsystem (for JES2) must be named JES2
and the procedure must have the same name.
Baloney. Here is the start of the IEFSSNxx member from my Test system
called MVS4 so JES2 runs as JES4;
SUBSYS SUBNAME(SMS) /* SMS SHOULD BE THE FIRST ENTRY*/
20 matches
Mail list logo
