IBM Mainframe Forum

And what happened when you accessed a member of TSSDN.DATA.COPY1 with a batch job?

I can assess and check from 3.4 mvs

enter TSSDN.DATA.COPY1

TI TSSDN.DATA.COPY1

showing Tape Information

BillyBoyo

Please mind your writing.

You have posted over 1300 questions in one year and I noticed you were rude to many of us.
what I said earlier I had proof.

You need to give ur example to make sense. Again please be nice to every one

smile:-)
D

I am curious as to how you feel what I wrote for you might be rude. Indeed, how you feel I've been rude to "many of us". Not curious enough, however, to be interested in your thoughts on the subject.

Please do what I suggested. Print this entire topic out, and take it to your mentor. Allow them time to read it, and then have a chat about it. I'd even suggest doing that with all your previous topics. If you do that and let us know the results, then you'll be the sort of person who can get somewhere in this business, though it always takes work.

Unless of course you are not what you purport to be, in which case we're not really "biting" properly, are we?

And what happened when you accessed a member of TSSDN.DATA.COPY1 with a batch job?

I can assess and check from 3.4 mvs

enter TSSDN.DATA.COPY1

TI TSSDN.DATA.COPY1

showing Tape Information

You either do not understand written English, or you have some reason to deliberately NOT answer posted questions -- it appears BillyBoyo may be onto something there. Using "TI" on a data set in ISPF 3.4 is (1) NOT doing what I asked you to do, (2) using a site-specific tool not available to most people, and (3) almost certainly guaranteed to access data in the tape management system, NOT from the tape.

Try this job (replacing xxx with any member name in your data set):

dn2012,

Show us your tape info of Input and Output files.

Thanks
-3nadh

what I said earlier I had proof.

OF WHAT ?
( that You created a dataset on tape ?... pretty useless proof collection )

instead of criticizing other people writing why don' t You meditate on Your reading.
since we reply on our own time and free of charge it is most reasonable that we get pissed off
at people like You who make everybody waste time by insisting on wrong concepts, accompanied by poor terminology.

in IT proper terminology is essential to effective communication.

as said umpteen times A PDS CAN NOT RESIDE ON TAPE.

the only dataset organization that can reside on tape is the Physical Sequential FULL STOP

the content of the PS file residing on tape depends on the program which created it.

when You take a PDS on DASD and using IEBCOPY You copy it to TAPE
what You get is not a PDS...
it is a PS file containing and UNLOADED copy of the disk PDS,
which can be processed only by IEBCOPY to copy iy back to dasd.
WHATEVER YOUR BELIEFS ARE. AMEN

//********************************************************************
//************* TSSDN.JCL.CNTL(CPYTP2TP) ****************************
//*THIS JOB WILL COPY FROM TAPE AND WRITE IT ON TAPE.
//****** >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> *********
// EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DISP=SHR,DSN=TSSDN.DATA.COPY2
//SYSUT2 DD DISP=(NEW,CATLG),UNIT=TAPE,DSN=TSSDN.DATA.COPY3
//*
******************************** Bottom of Data *******************************

Command - Enter "/" to select action Message Volume
-------------------------------------------------------------------------------
TSSDN.DATA.COPY2 TI RC=0 513179
***************************** End of Data Set list ****************************
**********************************************************************************************************

Data Set Name . . . : TSSDN.DATA.COPY2

General Data Creation Information
Volume Serial. . . : 513179 Date . . . . . . : 2012/095
Alternate Volume . : Time . . . . . . : 13:09:00
Media type . . . : VIRTUAL Jobname . . . . : IEBCOPY2
Record Format. . . : VS Program . . . . : IEBCOPY
Record Length. . . : 32016 Last Used Information
Block Size . . . : 32020 Date . . . . . . : 2012/095
Number of blocks . : 44 Time . . . . . . : 13:13:00
Percent utilized . : 0 Jobname . . . . : IEBCOPY2
Batch ID/Hook ID . : CLOSE IO Expiration Information
Status . . . . . : ACTIVE Expire Date. . . : 2012/100

File / Volume Set Vault Management Information
Base Volume. . . . : 513179 Outcode. . . . . :
Sequence Number. . : 1 Slot . . . . . : 0000000
Total Files in Set : 1 Outdate. . . . . :
Secondary volumes:
USER DATA: H134501100011000000000000ICSDBS.BN58
****************************************************************************************************
Command - Enter "/" to select action Message Volume
-------------------------------------------------------------------------------
TSSDN.DATA.COPY3 TI RC=0 791082
***************************** End of Data Set list ****************************


Data Set Name . . . : TSSDN.DATA.COPY3

General Data Creation Information
Volume Serial. . . : 791082 Date . . . . . . : 2012/095
Alternate Volume . : Time . . . . . . : 13:13:00
Media type . . . : VIRTUAL Jobname . . . . : IEBCOPY2
Record Format. . . : VS Program . . . . : IEBCOPY
Record Length. . . : 32016 Last Used Information
Block Size . . . : 32020 Date . . . . . . : 2012/095
Number of blocks . : 44 Time . . . . . . : 13:13:00
Percent utilized . : 0 Jobname . . . . : IEBCOPY2
Batch ID/Hook ID . : SMF 83 Expiration Information
Status . . . . . : ACTIVE Expire Date. . . : 2012/100

File / Volume Set Vault Management Information
Base Volume. . . . : 791082 Outcode. . . . . :
Sequence Number. . : 1 Slot . . . . . : 0000000
Total Files in Set : 1 Outdate. . . . . :
Secondary volumes:
USER DATA: H134501100011000000000000ICSDBS.BN58

dn2012 , you continue to post completely irrelevant material. You are non-responsive to requests. This thread is locked to prevent any further foolishness.

c'mon mods...close/lock/delete this thread!