Re: Can't do DSPPTF, am I on the A side, or B side?

To be clear, using the _"old trace"_ TRCJOB. If the /trick/ has not
been performed to effect using the pre-V5R4 trace job facility, then
database opens are going to be required. That is, the new ¿and
improved? TRCJOB facility requires database opens to be functional, for
the tracing to function. The *old* trace does not require database file
opens for the TRCJOB *OFF OUTPUT(*PRINT), as long as both creating and
viewing of spools is unaffected by the same problem origin; i.e. if/when
Spool open is functional, even though Database open is not functional.
I believe the Piranha tool should be able to be used to find the
exception stack in the flow [for the process repeating the simple
recreate] where a DSPPFM of a newly created file fails.

Regards, Chuck
--
All comments provided "as is" with no warranties of any kind
whatsoever and may not represent positions, strategies, nor views of my
employer

rob@xxxxxxxxx wrote:
> Thank you for the explanation.
>
> Attempts by IBM to use TRCJOB failed because that tried to update files
> that were "locked". (PMR 93365,500). IBM connected using "Assist On
> Site" (which is like a customized version of Sametime or WebEx). Since my
> PC was doing remote HMC control and HMC 5250 control this worked fine. As
> we were getting ready to break for the night they were able to get the
> connection direct from my HMC to them working (Piranaha - which, I think,
> doesn't give 5250).
>
> Back on the job after a few hours sleep. On the phone with IBM trying to
> bring a new team of support personnel up to speed.
>
> DSPOBJD OBJ(QSYS/QDBOPEN) OBJTYPE(*PGM) DETAIL(*SERVICE)
> PTF number . . . . . . . . . . . . . : SI23412
>
> DSPOBJD OBJ(QSYS/QDMCOPEN) OBJTYPE(*PGM) DETAIL(*SERVICE)
> PTF number . . . . . . . . . . . . . : SI23552
>
> Rob Berendt

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.